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
Ratio of Data to Errors
Ratio of Data to Errors One of the elements of a good data governance plan […]
Back to basics
Back to basics Over the past couple of years I’ve noticed that some AMS vendors […]
Your people matter
Your people matter I’ve written many times about how people, process, and technology have to […]
We remember moments…
We remember moments… “We do not remember days, we remember moments.” – Cesare Pavese Another […]
Acknowledging problems is part of managing expectations
Acknowledging problems is part of managing expectations Research was done some time ago that suggested […]
Need data? Consider third-party sources
Need data? Consider third-party sources I always tell my clients, only collect data that you’re […]
Action must follow the decision
Action must follow the decision When I work with my clients on their projects (whether […]
Everything should be focused on improving user adoption
Everything should be focused on improving user adoption Your AMS is a tool, and a […]
Needs change over time, and that’s OK
Needs change over time, and that’s OK I was speaking with a couple of association […]
The vaguer the question, the vaguer the answer
The vaguer the question, the vaguer the answer As the old saying goes, the devil […]
