The Planning Fallacy

What Is the Planning Fallacy?

The planning fallacy is a cognitive bias first described by Daniel Kahnemanand Amos Tversky in their 1979 paper “Intuitive Prediction: Biases and Corrective Procedures.” It describes the systematic tendency of people and organizations to underestimate the time, cost, and risks of future actions while simultaneously overestimating the benefits of those same actions.

What makes the planning fallacy particularly insidious is that it persists even in the face of direct personal experience. A person who has repeatedly underestimated how long tasks take will continue to underestimate future tasks. An organization that has experienced multiple cost overruns will continue to approve optimistic budgets. This is not because people are irrational in any general sense — it is because the planning fallacy is rooted in how the brain generates predictions about the future.

Kahneman later expanded on this concept in his bestselling book “Thinking, Fast and Slow”(2011), where he distinguished between the “inside view” — the natural way we plan by imagining the specific steps of our project — and the “outside view” — consulting the actual outcomes of similar projects. The planning fallacy occurs because people overwhelmingly default to the inside view.

Why Humans Consistently Underestimate

Optimism Bias

Tali Sharot, a neuroscientist at University College London, has documented that approximately 80% of the population exhibits optimism bias — a tendency to overestimate the likelihood of positive events and underestimate the likelihood of negative ones. In planning contexts, optimism bias causes people to envision the best-case version of their plan: the one where hiring goes smoothly, technology works as expected, customers adopt eagerly, and no unforeseen obstacles arise.

Optimism bias is not a character flaw; it appears to be an adaptive trait. Sharot's research suggests that mild optimism is associated with better mental health, greater persistence, and higher achievement. The problem is not optimism itself — it is that optimism biases our estimates without our awareness, leading us to commit resources based on unrealistically favorable projections.

The Inside View

When planning, the human brain naturally constructs a narrative of how the project will unfold: step one, then step two, then step three. This is the “inside view” — reasoning from the specific features of the plan. The inside view has a critical blind spot: it imagines the plan proceeding more or less according to plan. It does not naturally account for the full range of things that can go wrong because most of those things are, by definition, unpredictable.

Kahneman contrasts this with the “outside view”: rather than reasoning from the plan's specifics, you look at the base rate of outcomes for similar plans. If you are estimating how long a software rewrite will take, the outside view asks: “How long have software rewrites of comparable scope taken historically?” The outside view almost always produces more pessimistic (and more accurate) estimates, but it feels less relevant because every plan feels unique from the inside.

Anchoring

Anchoring is the cognitive tendency to rely disproportionately on the first piece of information encountered. In planning, the initial estimate — however it was generated — becomes an anchor that subsequent estimates gravitate toward. If a project is initially framed as a “six-month effort,” future estimates will cluster around six months even as evidence accumulates that the project will take nine or twelve months. Research by Tversky and Kahneman demonstrated that even arbitrary anchors (like a random number from a roulette wheel) influence subsequent numerical judgments.

Single-Point Estimates

The convention of expressing plans as single-point estimates (“the project will cost $500K”) is both a symptom and an amplifier of the planning fallacy. A single number conceals the underlying uncertainty. It invites no conversation about the range of possible outcomes. And it creates a false sense of precision that makes the estimate feel more reliable than it actually is.

When you replace a single-point estimate with a range (“the project will cost between $350K and $800K, most likely around $500K”), the uncertainty becomes visible and the conversation changes. Stakeholders ask different questions: “What would drive it to the high end?” “What is the probability it stays below $600K?” These are better questions because they engage directly with the uncertainty rather than pretending it does not exist. Read more about this in our article on the hidden costs of false precision.

The Research Evidence

Kahneman and Tversky (1979)

The original research demonstrated the planning fallacy through controlled experiments showing that people's predictions about their own future performance were systematically more optimistic than warranted by their past experience. Participants who had repeatedly missed deadlines still predicted they would meet the next one. This finding has been replicated across numerous studies and domains.

Buehler, Griffin, and Ross (1994)

In a widely cited study, Buehler, Griffin, and Ross asked university students to predict when they would complete their senior thesis. On average, students estimated 33.9 days; the actual average was 55.5 days. Only 30% of students finished by their predicted date. More strikingly, students' “best guess” estimates were virtually identical to their “best case” estimates — they were literally planning as if nothing would go wrong.

Flyvbjerg, Holm, and Buhl (2002, 2005)

Bent Flyvbjergand his colleagues conducted the largest empirical study of cost and schedule estimation in large projects. Analyzing 258 transportation infrastructure projects across 20 countries and five continents, they found cost overruns in 9 out of 10 projects. Rail projects averaged 45% cost overrun; road projects averaged 20%; bridges and tunnels averaged 34%. These were not small, immature organizations — they were major government agencies with decades of experience in similar projects.

Flyvbjerg's subsequent work proposed “reference class forecasting” as a corrective: rather than estimating from the inside view, calibrate estimates against the actual outcomes of similar past projects. The UK government adopted reference class forecasting for all major transport projects in 2004, and the approach has since spread to other domains and countries.

Standish Group CHAOS Reports (1994–present)

The Standish Grouphas been tracking IT project outcomes since 1994. Their CHAOS reports consistently find that roughly 70% of IT projects fail to meet at least one of their original targets (schedule, budget, or scope). While the precise methodology and definitions have been debated, the directional finding — that the majority of IT projects miss their targets — is consistent with independent research from other organizations.

McKinsey and Oxford (2012)

A joint study by McKinsey and the University of Oxford analyzed 5,400 large IT projects (those with budgets over $15 million). They found that 45% of projects ran over budget, 7% ran over time, and 56% delivered less value than predicted. Crucially, 17% of projects went so badly that they threatened the existence of the company — what the researchers called “black swans.” These catastrophic failures were not predicted by the organizations' planning processes.

How Probability-Based Planning Counteracts the Planning Fallacy

Probability-based planning — what Incertive calls uncertainty-first planning — counteracts the planning fallacy through several mechanisms:

Ranges Instead of Points

By requiring estimates to be expressed as ranges rather than single points, probability-based planning forces planners to confront their uncertainty. “Development will cost between $300K and $650K” is a very different starting point than “development will cost $400K.” The range naturally invites discussion about what drives the upper and lower bounds, which surfaces risks that would otherwise go unexamined.

Monte Carlo Simulation

Monte Carlo simulation models the compounding effects of multiple uncertainties simultaneously. This is critical because the planning fallacy is not just about underestimating individual variables — it is about failing to account for how multiple sources of uncertainty interact. When costs run high AND timelines slip AND market adoption is slow, the combined effect is far worse than any individual shortfall. Monte Carlo simulation captures these interactions automatically.

Probability of Success

Perhaps the most powerful corrective is the simple act of stating the probability of success. When a go/no-go analysis reveals that a plan has only a 35% chance of meeting its stated objectives, the planning fallacy becomes visible. The team can no longer maintain the fiction that the plan will succeed because “we are doing it right this time.” The probability statement forces an honest conversation about whether to proceed, modify, or abandon the plan.

Sensitivity Analysis

Sensitivity analysis identifies which assumptions matter most. This counteracts the planning fallacy by directing attention away from the variables the planner finds interesting and toward the variables that actually drive the outcome. Often, the most important variable is not the one the team has been focused on.

How Incertive Helps

Incertive was built specifically to counteract the planning fallacy and related biases. When you describe a business plan on the Incertive platform, the system automatically:

Identifies hidden assumptions. Plans often contain implicit assumptions that the planner has not examined. Incertive surfaces these assumptions and requires them to be expressed as ranges, making the uncertainty visible.

Models compounding uncertainty. Through Monte Carlo simulation, Incertive models how multiple uncertainties interact, revealing the full range of possible outcomes rather than just the best-case scenario that the inside view generates.

Produces a probability of success.Instead of a narrative argument for why the plan will work, Incertive produces a specific probability: “there is a 52% chance this plan achieves your stated objectives.” This is the single most important output because it makes the planning fallacy visible.

Ranks the risks that matter. Sensitivity analysis shows which variables have the greatest impact on the outcome, directing attention and resources to the factors that most deserve scrutiny. This prevents the common failure mode where teams spend time mitigating low-impact risks while ignoring high-impact ones.

The planning fallacy cannot be eliminated — it is too deeply rooted in human cognition. But it can be systematically counteracted through tools and processes that enforce probabilistic thinking. That is what Incertive provides. Learn more about how it works or see the hidden costs of false precision in planning.

Frequently Asked Questions

Beat the Planning Fallacy

Describe your plan and get a probability-based assessment that counteracts optimism bias, anchoring, and single-point estimate thinking.