Almost every team has a decision that has gone unmade for months, sometimes years. It's not that nobody sees it: everyone knows it's there, hanging over every retrospective, resurfacing in hallway conversations, creating a silent cost that nobody tracks. And yet, sprint after sprint, it gets postponed. The interesting question is not what that decision is, but what is actually blocking it. Because the reason is rarely the one we say out loud. This article explores the anatomy of postponed decisions and what to do once we discover what is really paralyzing them.
The Invisible Cost of Not Deciding
Not deciding seems like the safe option. As long as we don't commit, we can't be wrong; we keep our options open, avoid conflict, and postpone risk. But that sense of safety is an accounting illusion: the cost of delaying is real, it just doesn't show up anywhere.
Every postponed decision generates what we could call a continuous tax. The team keeps working with the unresolved ambiguity, which multiplies conversations, rework, and energy spent managing the uncertainty. People who were waiting for a resolution lose motivation. And, above all, an opportunity cost builds up: while we don't decide, we can't move forward on what the decision would have enabled.
Don Reinertsen, in The Principles of Product Development Flow (2009), argues that the biggest waste in product development is often invisible precisely because it doesn't appear in the usual metrics: the cost of delay. Not measuring the cost of not deciding doesn't mean it doesn't exist; it means we are paying it without seeing it.
Not All Postponed Decisions Are the Same
Before asking what is blocking a decision, it helps to distinguish what type of decision it is. Jeff Bezos popularized a very useful distinction: "one-way door" decisions versus "two-way door" decisions. The first are irreversible or very costly to reverse; the second can be undone with relative ease if they go wrong.
The mistake that paralyzes many teams is treating every decision as if it were irreversible. We apply to a two-way-door decision, which is easily reversible, the caution and level of analysis that only a one-way-door decision would deserve. And so decisions we could make in an afternoon and correct the following week if we got them wrong drag on through endless deliberation.
The first question to ask about a postponed decision, then, is: is it really irreversible, or are we treating it as if it were without it being so? Many blocked decisions would unlock simply by recognizing that the cost of being wrong is manageable and reversible. The paralysis doesn't come from the real risk, but from the magnitude we attribute to it.
What We Say Is Blocking the Decision vs. What Really Is
When we ask a team why it hasn't made a certain decision, the answers usually sound reasonable: "we lack information," "it's not the right time," "it depends on something that isn't clear yet," "it's not a priority right now." Sometimes they are true. But often they are rationalizations that hide the real blocker, which is of a different nature.
"We lack information" (when in reality there will never be enough)
Some decisions are postponed forever while waiting for a certainty that will never arrive. Beneath the appearance of prudence lies an intolerance of uncertainty: the belief that with a little more data the decision will become obvious and stop being risky. But difficult decisions are difficult precisely because perfect information doesn't exist. Waiting until we have it is an elegant way of never deciding.
"It's not the right time" (when in reality nobody wants to take responsibility)
Often the real blocker is that the decision has consequences and nobody wants to be the one who bears them if it goes wrong. This connects to how authority is distributed. L. David Marquet, in Turn the Ship Around! (2013), describes organizations where the authority to decide is separated from the information needed to do so: those who know cannot decide, and those who can decide do not know. The result is a structural paralysis in which the decision bounces between levels without anyone making it.
"We need to reach consensus" (when consensus is impossible and is used as an excuse)
Seeking unanimous agreement on decisions where interests are legitimately different is a recipe for permanent gridlock. Sometimes "we need everyone to agree" really means, in practice, "nobody is willing to decide over someone else's disagreement." Consensus becomes a distributed veto.
The Blocker We Almost Never Name: Fear of Conflict
Patrick Lencioni, in The Five Dysfunctions of a Team (2002), traces a revealing chain. At the base of dysfunctional teams is the absence of trust. From it grows fear of conflict: avoiding the open, passionate debates that every hard decision requires. And from that fear of conflict grows, directly, a lack of commitment: teams that don't truly debate don't truly commit to their decisions.
This is perhaps the most frequent and least confessed cause of postponed decisions. The decision isn't made because making it would require an open disagreement that the team doesn't feel safe enough to sustain. It's more comfortable to leave it in limbo, where nobody explicitly loses, than to face the difficult conversation in which someone would have to give ground.
Lencioni points out an important paradox: teams that avoid conflict in pursuit of harmony usually generate more resentment, not less. Disagreement doesn't disappear because it isn't discussed; it goes underground, where it festers. Decisions postponed to avoid conflict rarely avoid anything: they only delay and aggravate the tension.
How to Identify the Real Blocker
If the stated reason is rarely the real one, how do we get to the true one? A few questions help dig deeper.
What would happen if we made the decision tomorrow, one way or the other? If the answer is "nothing catastrophic or irreversible," the blocker isn't the risk: it's something else. Who would have to agree for it to be made, and why don't they? Sometimes the blocker is a specific person or interest that nobody names. What information are we waiting for, and what would we do differently depending on what it reveals? If we can't answer that, we aren't waiting for information: we are postponing. Who loses something if this decision is made? The blocker is often where someone has an incentive for nothing to change.
These questions have an uncomfortable but useful effect: they make visible that many postponed decisions aren't blocked by the complexity of the problem, but by dynamics of power, fear, or avoidance that we would rather not look at. Organizational diagnostic tools such as AgiLevel can help determine whether the blockage lies within the team or in the system around it, a distinction that completely changes which intervention makes sense.
The AI Context: More Data, More Paralysis
One might think that artificial intelligence, by giving us more analytical capacity, makes deciding easier. The reality is more ambiguous, and we shouldn't idealize it.
AI can genuinely relieve certain kinds of blockage: when what's missing is processing information that exists but is scattered, it helps synthesize it quickly. But it can also worsen paralysis in two ways. The first is feeding the fantasy that with a little more analysis the decision will become obvious. Now that we can generate reports, scenarios, and projections without limit, the temptation to "analyze a bit more" before deciding becomes almost irresistible. We have an endless excuse for not committing.
The second is more subtle. Postponed hard decisions are rarely hard because of a lack of data, but because of conflicts of values, interests, or priorities. And AI doesn't resolve those. A team that doesn't dare to have the uncomfortable conversation won't have it just because a model offers one more analysis; it will simply add the analysis to the pile of reasons to keep postponing. Technology can inform the decision, but it cannot take on for us the responsibility of committing, nor can it sustain the conflict that commitment sometimes requires.
Unblocking: From Analysis to Reversible Decisions
So what can be done about the decision the team has been dodging for months? There is no universal formula, but there are some moves that usually help.
Reclassify the decision according to its actual reversibility, and treat the reversible ones with the lightness they deserve: decide, test, correct. Clearly assign who decides (not who has an opinion, but who has the final word), because diffused authority is a primary source of paralysis. Put the cost of not deciding on the table, make it explicit and, if possible, quantify it, so that inaction stops seeming free. And when the real blocker is fear of conflict, name it: sometimes it's enough for someone to say out loud, "I think we haven't decided this because the disagreement it implies makes us uncomfortable," for the conversation to finally happen.
None of these moves guarantees a good decision. But all of them break the worst outcome, which is not deciding badly, but not deciding and continuing to pay the invisible tax of indecision.
The decision your team has been putting off the longest is probably a symptom, not a problem in itself. What keeps it in limbo (fear of conflict, diffused responsibility, intolerance of uncertainty, interests that prefer nothing to change) says more about how the team works than about the inherent difficulty of the decision.
That is why it's worth looking at it head-on, not only to resolve it, but to understand what it reveals. The decisions we avoid are an X-ray of our dynamics. And often, honestly unblocking one of them, by naming what truly holds it back, teaches the team something that no retrospective about processes could.
So the question is a genuine one: what is that decision on your team? And if you are honest with yourself, what is really holding it back?
Agile Club: postponed decisions are one of those topics we all have stories about. Share yours, and learn how other teams unblocked theirs, in Agile Club.
Comments (0)
Log in to your Scrum Manager area to comment