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
How you respond matters
How you respond matters Very recently I wrote that I measure customer service by how […]
Your one non-renewable resource
Your one non-renewable resource For any project, the three primary resources are time, money, and […]
No system is perfect
No system is perfect When working with my clients on the selection of a new […]
Ask your members to update their info
Ask your members to update their info One of the greatest data management challenges any association […]
Customer vs. staff
Customer vs. staff In a properly designed AMS, when the customer goes online to your […]
Measuring customer service
Measuring customer service When I work with clients on AMS selection, one question that often […]
Iterate or innovate?
Iterate or innovate? When moving to a new association management system, there is often an implicit […]
Who is in control?
Who is in control? Speaking with a client once about their database project, the client […]
Sometimes Staff Has to do the Work
Sometimes staff has to do the work… As a child, I was attracted to computers […]
Documentation and the Great Resignation
Documentation and the Great Resignation Unless you’ve been living under the proverbial rock, you’ve heard […]
