Eyes wide open and affirmative decision-making

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

Simpler and Faster is Better

August 24, 2022

Simple and Faster is Better Earlier this week I was fortunate enough to attend a […]

Patience and grace

August 17, 2022

Patience and grace A past client of mine recently told me: “You inspire confidence and […]

Sometimes you just have to try it and see what happens

August 10, 2022

Sometimes you just have to try it and see what happens The single greatest key […]

Training and testing

August 3, 2022

Training and testing I’ve written before that the best form of training follows this process: […]

How to save a “failing” project

July 27, 2022

How to save a “failing” project It is not unusual for me to receive a […]

How to avoid the “IT black hole”

July 20, 2022

How to avoid the “IT black hole” Going all the way back to my days […]

The “People” are important!

July 13, 2022

The “People” are important! I’ve written a lot about people, process, and technology over the […]

Always look for the MVP

July 6, 2022

Always look for the MVP I first wrote about minimum viable product (MVP) just three […]

The longer you take, the longer it will take

June 29, 2022

The longer you take, the longer it will take It may sound like a tautology, […]

Data is for action

June 22, 2022

Data is for action When deciding whether or not to collect a piece of data, […]

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top