A decision that keeps waiting for “more information” is still a decision — usually the one nobody wants to admit has already been made.
There’s a version of this every senior leader recognizes: the decision that’s been on the table for three months. Nobody has said no. Nobody has said yes. The file gets one more round of review, one more data point requested, one more stakeholder consulted — each addition reasonable on its own, and each one, in practice, another month in which nothing changes.
At some point the question stops being what does the data say and becomes something else: what is this waiting actually protecting?
Two things get called “being careful” that aren’t the same thing
Prudence has an object and an endpoint. There’s a specific thing it doesn’t yet know, and a moment at which knowing enough of it will be enough to decide. A leader who says “I want the Q3 numbers before I commit to the restructure” is naming both — what’s missing, and when the waiting ends.
Postponement disguised as analysis has neither. It rarely names exactly what it’s still waiting to learn, and it has no point at which it would stop waiting even if that information arrived. Another round of input gets requested instead. The file stays open not because the picture is incomplete, but because closing it means deciding — and deciding means owning what comes next.
The two look identical from the outside. Both produce a leader who says “we’re still gathering information.” Only one of them is actually true.
What the delay is usually protecting
The decisions that sit the longest tend to share a shape: they require someone to admit, out loud, that a call already made was wrong, or that a person, project, or relationship they’re responsible for no longer belongs where it is. Neither is a comfortable thing to be the one who says. Continuing to “analyze” is a way of staying in motion without arriving anywhere that requires saying it.
None of that makes the discomfort illegitimate. Ending a project someone built, changing a leadership structure, walking away from a partner — these carry real weight, and a leader who feels that weight is paying attention correctly. The failure isn’t feeling the weight. It’s letting the weight set the calendar.
A short test for telling the two apart
Three questions, applied to whatever is actually sitting unresolved right now.
Can you name, specifically, what new information you’re waiting for, and from whom?
Is there a date by which you will decide regardless of whether that information arrives?
If you had to decide today, with only what you already know, what would you actually do?
If the third answer wouldn’t change even after the “missing” information showed up, the waiting was never really about the information. That third question is close to what the Plan step in the MAPS method is built to force: not more analysis, one concrete, dated action.
Where this shows up
A senior hire who isn’t working out, kept in place through another quarter of “let’s see how the next project goes” — a project chosen, in part, because it postpones the harder conversation.
A reorganization everyone at the leadership table privately agrees is overdue, delayed behind one more round of “let’s make sure we’ve thought this through,” with no one able to say what thinking-through would actually still change.
A partnership or contract renewal revisited every cycle with the same unresolved doubt, never quite reaching a decision either way, because ending it means admitting the original choice no longer fits.
Worth sitting with
Which decision on your desk right now has a test you could run today, and haven’t?
What would you have to admit, if you decided it today?
Waiting is sometimes the right call. It is never a neutral one. Every month a real decision stays open carries a cost — even when that cost is harder to see than the decision itself.