Eyes wide open and affirmative decision-making
When I work with my clients on any type of project, whether it's selection of a new system or improving data management within the organization, I always emphasize one thing: When we make decisions, we want to make them with eyes wide open.
What I mean is this: Any decision that is made, including decisions to NOT do something, are made intentionally. That is, we've weighed the pros and cons of a given decision, and we've affirmatively agreed to take one path over another.
The alternative, which I've seen happen far too often, is to allow things to happen by default. That is, no discussion of a particular issue is held, or if it is held, no decision is made. (Note that NOT deciding is different than deciding NOT to.) The result is that the default path leads the association to somewhere they don't want to be.
A simple example: an association has multiple steps in their membership join process. Staff feels like there are too many steps and this is suppressing join rates. Even after discussions, no decision is made (either to change the process or keep the current one), and so, by default, the current process continues. Not changing the process may have been the "correct" decision, but it should be made affirmatively, not by default.
So when you're making decisions about anything, even if it is to not change what you're discussing, you should state that affirmatively ("We're going to continue with the status quo") so that everyone knows a decision was made, not avoided.
![]()
Wes's Wednesday Wisdom Archives
Some context, please
Some context, please A pet peeve of mine: A report about associations (e.g., marketing benchmarks report) where […]
Eventually automated emails get ignored
Eventually automated emails get ignored During the discovery and development phase of implementing a new […]
The challenge the AMS providers see
The challenge the AMS providers see Over the years I’ve asked AMS providers what they […]
Be careful about “solutioning” too quickly
Be careful about “solutioning” too quickly One of the great things about software developers is […]
What’s our next action?
What’s our next action? As you can imagine, I spend a lot of time in […]
Don’t automate for the sake of automation
Don’t automate for the sake of automation I’m the laziest person in the world. I […]
Don’t forget about what got better
Don’t forget about what got better Negativity bias is the tendency to focus on only […]
Give a little at a time rather than taking away
Give a little at a time rather than taking away I’m sure there’s research somewhere […]
First, you gotta have the data
First, you gotta have the data When I work with clients on a new AMS […]
Work on your relationship with your AMS vendor
Work on your relationship with your AMS vendor It is no coincidence that my most […]
