There is probably a decision on your leadership team’s agenda this month that was also there last month. There may be another that was made in a single meeting, and three meetings later you’re still explaining it.
In both situations, it is worth asking whether the pace served the decision. Take a decision about whether to restructure a program before next year’s funding is confirmed, when your board wants an answer this month. If you wait too long and the organization stalls around the question. If you move too quickly and you may be dealing with the downstream costs for months.
Under that pressure, leaders may act quickly, deliberately allow more time, or avoid engaging with a decision. From the outside, the last two choices can look remarkably similar.
The Pace of a Decision
Each of those responses sets a pace. Quicker is sometimes better, and sometimes it isn’t. The same is true of slower. What matters is whether you chose the pace because it suits the decision, or because it makes the pressure easier to live with.
Discomfort has a lot of say in this. In research published in MIT Sloan Management Review, 42% of the business leaders surveyed said they had put off thinking about decisions because it was uncomfortable. Discomfort can speed a decision up just as easily. Some decisions get made to end discomfort, or simply to move them off your plate and onto someone else’s. (See my article, “Deciding from Anxiety, Deciding from Clarity: The Inner State Behind Every Call You Make” about this.) Others get one more round of analysis because studying the question feels better than answering it.
Two questions help before you choose. If you wait, what do you expect to learn that could change your decision? What is the delay already costing the people and the work involved?
Look for Clues in Your Organization
How the decision felt to you is a poor guide to whether you chose well. A well-judged quick call and a rush can feel exactly alike from the inside. The better evidence is around you, in the work and in the people doing it. The patterns you observe are clues, rather than proof. A necessary restructuring can produce anxiety however carefully it was decided, and a popular decision can gather momentum on weak reasoning. The patterns show you where to ask questions.
When a decision has been well paced, the people who need to act on it often find their way to each other, and the work starts to line up. Early signs of success point in the same direction. There’s a sense of forward momentum that people can get behind.
When a decision has been rushed, that coming together is less likely. Implementation meets friction, the decision needs far more explaining than you expected, and parts of it are reworked almost as soon as the work begins. People can be unsure who is responsible for what, or whether their colleagues have their backs, so they proceed with trepidation.
When a decision is avoided or studied for too long, people can end up working in circles. The same question keeps returning to the agenda, and they make their own decisions on ground that keeps shifting. People make provisional plans, knowing they may have to redo the work once a decision is made. What looks like change fatigue or cynicism may be a reasonable response to repeatedly having to plan around an unresolved decision.
Here are three ways to work with this.
1. Treat the Decision as an Experiment Where You Can
Where the consequences can be contained, testing a change on a limited scale lets you move forward before every uncertainty is resolved. Put a stake in the ground. Name in advance the signs that will tell you whether it’s working, and set a date to review them. The research cited above suggests this helps leaders past the paralysis that delays a decision. Clear review criteria and a review date also give your board or funder a basis for assessing progress and understanding any adjustments.
Ask yourself: Which decision in front of me could I make now on a limited scale, if I named what would tell me to adjust it?
2. Learn From People’s Experience of the Decision
In the weeks after a decision, pay attention to more than the milestones. Do concerns come to you directly, or do they surface later in separate conversations? Can people explain what was decided and what they’re responsible for? Are teams coordinating, or building workarounds because something is unresolved? Then test your reading. Ask the people closest to the work what is helping them move forward and what remains unclear.
Ask yourself: What are people experiencing as they act on this decision, and what do I need to understand?
3. Say More About the Process Than You Think You Need To
Whatever the pace, people work better when they know where a decision stands. Tell them what you’re weighing, what you still need to know and when you’ll decide. Then tell them again. This clarity matters especially when a decision is hard to undo, such as closing a program, and requires careful consultation and planning. A date and a reason give people something firm to plan around while the answer is open. They also keep a considered decision from looking, from the outside, like one that is being avoided.
Ask yourself: What do people need to know about where this decision stands, even before I can give them the answer?
You won’t get the pace right every time. The people implementing a decision see consequences you may not see from where you sit. Ask them, and use what you hear to adjust this decision and inform the next one.
If you’d value a thinking partner as you work through decisions like these, my Executive Coaching offers space to test your assumptions and clarify your next step.