No decision is worse than a bad decision.
This is a controversial claim — but the data supports it. McKinsey found that companies with a fast decision cycle grow twice as fast as competitors who decide slowly. Yet 60% of managers regularly postpone key decisions out of fear of making a mistake.
The paradox is sharp: by trying to avoid mistakes, leaders make one. Not making a decision is a decision — and often the worst one available.
The cost of delay is real and easy to underestimate. When a manager spends a month gathering data for a decision that could have been made in a week, they lose more than time — they lose a window of opportunity, demoralize a team waiting for direction, and signal to the organization that decisiveness is not a value. The total of these costs rarely appears in a spreadsheet, but it always shows up in results.
This article is not an argument for impulsiveness. It is an argument for conscious, fast, and structured decision-making — a competency that can be learned.
Why Leaders Avoid Decisions — Cognitive Traps
Before we get to solutions, it helps to understand the mechanism. Postponing decisions is rarely the result of laziness — it is the effect of several well-researched cognitive traps.
Analysis paralysis emerges when a leader collects more and more data, believing that with enough information the decision will become obvious. But every new piece of information generates new questions. Gathering data is exciting — making a decision is risky. The brain readily chooses the former.
Status quo bias is the tendency to prefer the current state of affairs over change — even when change is objectively better. Evolutionarily this made sense (change = risk). In a dynamic business environment, the status quo is rarely neutral: it is a slow erosion of competitive advantage.
The sunk cost fallacy causes people to continue a bad decision because they have already invested significant time, money, or prestige in it. “We’ve put too much into this to pull back now” is a sentence that costs organizations billions.
Decision fatigue is the physiological depletion of decision-making capacity. The brain treats every decision as an effort — and the more decisions made during the day, the worse the later ones become. A study of Israeli judges found that the rate of favorable rulings dropped from 65% in the morning to below 20% before a break — not because the cases were worse, but because the judges were exhausted from deciding.
A Decision-Making Framework for Leaders (Inspired by the Yale Program)
The Yale School of Management identifies six steps in an effective decision process. Each step below includes a concrete tool to apply immediately.
Step 1: Frame — Define the Right Problem
The most common decision error happens before any analysis: leaders solve the wrong problem.
Tool: Before you begin gathering data, write down your answer to this question: “What problem am I trying to solve, and why is it a problem?” Then share it with one person and ask: “Is this the right question?” It often turns out it isn’t.
Step 2: Gather — Collect Sufficient Data, Not All Data
The 70/20/10 rule: you need 70% of available information to make a reasonable decision. The next 20% costs as much to gather as the first 70% — and delivers a marginal increase in certainty. The final 10% is often unattainable.
Tool: Set a data-gathering deadline and a list of key questions you must answer in advance. When you have the answers — stop gathering, even if you want to know more.
Step 3: Structure — Organize Your Options
A good decision requires at least three options (not two). The “do this or that” structure frequently excludes the best outcome. The third option — “do something else entirely” — forces creativity.
Tool: Decision matrix: a table of options (rows) × criteria (columns) × weights (1–5). Complete it without checking — intuition is valuable, but it should be confronted with data.
Step 4: Evaluate — Assess Through the Lens of Consequences
Ask not “what is likely?” but “what is possible, and how costly would it be?”
Tool: Pre-mortem — imagine that a year from now this decision turned out to be a disaster. What went wrong? This exercise surfaces risks that an optimistic analysis overlooks.
Step 5: Decide — Make the Decision and Communicate It
A decision without communication does not exist. A leader who has made a decision but not communicated it has not made a decision — they have only thought one.
Tool: Decision message in three sentences: (1) What I decided. (2) Why. (3) What this means for you/the team. Simplicity in communication increases the likelihood of implementation.
Step 6: Learn — Draw Conclusions
A decision without a retrospective is a wasted learning opportunity. Most organizations analyze decisions only when they end in disaster. That is not frequent enough.
Tool: Decision journal — described in detail in the next section.
Decision Journal — A Tool for Conscious Decision-Making
The decision journal is a simple practice that — applied consistently over 3–6 months — dramatically improves decision quality. It involves documenting every important decision using a fixed template.
Decision journal template:
- Date and context: When am I making this decision and what is my situation (stress level, time constraints, available information)?
- Decision: What exactly am I deciding?
- Alternatives: What other options did I consider and why did I reject them?
- Expected outcome: What do I think will happen? Over what time horizon?
- Confidence: How confident am I in this decision on a scale of 1–10?
- Outcome (filled in later): What actually happened? Where were my predictions accurate, and where was I wrong?
After a few months of keeping the journal, you begin to see patterns in your decision-making errors. One leader discovers they consistently overestimate the speed of implementation. Another finds that decisions made at the end of the week have worse outcomes. Another notices that decisions rated 9/10 in confidence actually perform worse than those rated 6/10. This is self-knowledge that no training can provide — only your own decision history can.
Team Decisions vs. Solo Decisions — When to Involve People
Victor Vroom and Philip Yetton developed a model in 1973 that remains one of the most practical decision management tools available.
In its simplified form, the model identifies three decision modes:
Autocratic (A) — you decide alone. Use this when: time is critical, you have all the information you need, and team buy-in is not required for effective implementation.
Consultative (C) — you gather input, then decide alone. Use this when: you need information or perspectives you don’t have, but accountability for the decision remains with you. You consult with selected individuals or a group — but the decision is yours.
Collaborative (G, for Group) — you decide together. Use this when: the team has critical knowledge you lack, team acceptance is a condition for the decision’s success, and time permits a group process.
Practical heuristic: If you cannot execute the decision without the active engagement of specific people — involve them at the decision-making stage, not the implementation stage. A decision imposed without consultation is always implemented more slowly than one in which those responsible for execution participated.
For more on decisions under time constraints, see the article on decisions under time pressure — strategies for managers, and for a project management perspective — the article on decision-making in project management.
Building Decisiveness in an Organization — Decision Culture
Individual frameworks and tools are one dimension. The second, equally important dimension is decision culture — the informal rules that define how decisions are made across the entire organization.
Organizations with a strong decision culture share several characteristics:
Clear decision ownership. Every important decision has a single owner — the person who makes the final call and is accountable for the outcome. Distributed accountability is no accountability at all. The tool here is RACI (Responsible, Accountable, Consulted, Informed) applied not just to projects but to specific decision types.
Tolerance for good-faith mistakes. Organizations that punish decision errors produce leaders who don’t decide. This creates an environment where inaction is safer than action — precisely the opposite of what a business needs in volatile conditions.
Retrospective learning from decisions. Regular (quarterly, or after each major project) reviews of decisions: what was decided, why, what happened, what was learned. This is the organizational equivalent of the individual decision journal.
Clear separation of decisions from outcomes. This is subtle but critical. A decision can be good while the outcome is bad — due to external factors. A decision can be poor while the outcome is good — due to luck. Judging decisions solely by outcomes (outcome bias) discourages good process and rewards fortune.
A leader who understands these mechanisms not only makes better decisions personally — they build an environment where the whole team decides better. That is a multiplying effect.
Decision-Making in Talent Programs
In next-generation talent programs, decision-making appears as a cross-cutting competency — present in every module, from team management to strategy.
Better a decision than no decision — this principle sounds simple, but it requires active work on the fear of making mistakes. That fear is not eliminated by collecting more data. It is eliminated by building a structure that makes deciding safer — and by building a personal history of decisions from which one can learn.
Organizations that invest in their leaders’ decisiveness gain on two fronts: faster response time to market changes and higher levels of team trust — because a leader who decides clearly and communicates transparently builds authority without imposing it.
At EITT, we run training on AI for Managers and Strategic Decision-Making, which combines classical frameworks with new tools that support analysis and decisions. If you’re interested in the neurobiological underpinnings of decision-making, the Neuroleadership program explains why the brain resists making decisions — and how to work around that resistance.
Jeff Bezos used to say that most decisions are reversible — and it is precisely those decisions that should be made quickly, tested, and learned from. Irreversible decisions warrant more care and process. The skill is knowing which type you’re dealing with. A leader who treats every decision as irreversible never decides fast enough. A leader who treats every decision as reversible takes excessive risks.
This two-dimensionality — speed versus caution — is the heart of decision maturity. And it is precisely what no framework can replace. Frameworks provide structure. Decision maturity comes from experience, reflection, and the courage to decide in spite of uncertainty.
A decision is not an endpoint. It is a starting point for learning.