A bad decision has a known cost. You make the call, it turns out to be wrong, and you deal with the consequences. The consequences are visible, quantifiable, and correctable.
Indecision has a hidden cost. The decision does not get made, the problem persists, the options narrow over time, and the cost accumulates invisibly until it becomes a crisis or a lost opportunity.
In most organizations, the hidden cost of indecision is larger than the cost of bad decisions. It is also far less discussed, because indecision does not produce a visible failure that anyone can point to.
The economic cost of delayed decisions
Every decision that is not made carries a direct cost that can be calculated, even if it rarely is.
If a decision about a hire is delayed by three months, the cost includes three months of reduced output from the unfilled role, three months of the hiring manager's attention partially consumed by the gap, and potentially three months of the company's trajectory shifting slightly due to the missing capability. That cost is real. It does not appear on any report.
If a decision about a product direction is delayed by four months, the market moves during those four months. Competitors who make a decision — even one that is less carefully analyzed — build four months of product development and customer learning that you do not have. The cost of delay is a compounding disadvantage.
The formula is simple: the cost of a delayed decision equals the cost of the problem that decision would have solved, multiplied by the time the delay lasts. Most founders know this intuitively but do not calculate it explicitly. Calculating it explicitly changes the decision about whether to decide.
Why indecision happens
Indecision is almost never laziness. It is almost always one of three things.
Fear of being wrong. If you decide and you are wrong, the failure is visible and attributable. If you do not decide, there is no single decision to point to as the failure. Indecision is a form of loss aversion — it trades the risk of a visible bad outcome for the invisible accumulation of cost from not acting.
Waiting for more information. This is sometimes rational and sometimes a disguised version of fear of being wrong. The question to ask is: what specific information would I need that I do not currently have, and when would I have it? If the answer is "I don't know" or "it might be available in a few months," the information is not actually the constraint.
Genuine ambiguity about the decision itself. Sometimes the options are not clear, the tradeoffs are not understood, or the people who need to agree have not aligned. This is a design problem — the decision process needs to be structured so that the options are defined, the tradeoffs are explicit, and the decision criteria are agreed on before the decision is made.
A framework for deciding fast with incomplete information
The most useful reframe for decision-making under uncertainty is this: what is the cost of being wrong, and how reversible is the decision?
Decisions that are low-cost if wrong and easily reversed should be made fast, with whatever information is currently available. The cost of delay is certain. The cost of being wrong is manageable. Default to action.
Decisions that are high-cost if wrong and hard to reverse warrant more deliberation. Gather the specific information that changes the decision, set a date by which you will decide regardless of whether that information is available, and commit to the date.
Decisions that are high-cost if wrong but reversible within a reasonable timeframe sit in the middle. Act, but build in an explicit review point at which you evaluate the decision and course-correct if needed.
The framework is not about removing uncertainty. Uncertainty is the condition. The framework is about making the cost and reversibility of each decision explicit, so that the default is action rather than waiting.
The discipline of the deadline
The most effective operational practice for reducing decision latency is the mandatory deadline.
Every pending decision gets a date by which it will be resolved — not a date by which you hope to have more information, but a date by which the decision will be made with whatever information is available at that point.
This sounds simple and it is genuinely difficult in practice. The difficulty is that when the deadline arrives and the information is still incomplete, the instinct is to extend the deadline. Resist this unless the specific information that was expected but did not arrive is information that genuinely changes the decision calculus, not information that would simply make you more confident.
Most of the time, what you know on the deadline date is enough. You were just waiting for certainty that was never going to arrive.
We build decision-making structures that move organizations from waiting to acting.