Planning Fallacy

Prime #

1066

Origin domain

Cognition And Psychology

Subdomain

judgment and decision making → Cognition And Psychology

Core Idea

The planning fallacy is the pattern in which agents forecasting the time, cost, or risk of a novel task systematically underestimate them — even knowing that similar past tasks ran long. The load-bearing mechanism is inside-view substitution for the outside view: the planner mentally simulates the intended steps and produces an estimate consistent with that simulation, which structurally omits the long tail of unimaginable interruptions that the reference class of comparable past tasks captures empirically.

How would you explain it like I'm…

The Five-Minute Fib

When you start coloring a big picture, you think, 'I'll be done in five minutes!' But then a crayon breaks, the dog wants to play, and dinner is ready, so it takes way longer. The Planning Fallacy is how we almost always guess things will be quicker and easier than they really turn out. We forget about all the little surprises that pop up.

Always Takes Longer

The Planning Fallacy is the way people guess that a new task will take less time and money than it really does, even when they know past projects ran long. The reason is that when you plan, you picture the steps you mean to take, and that picture looks smooth and quick. But it leaves out the traffic jams, the broken tools, and the waiting on other people, because you can't imagine surprises you've never thought of. A better trick is to look at how long similar jobs actually took before, instead of trusting your mental movie. People skip that trick because they feel 'my project is different.' That's why even experts who plan a lot still fall for it.

Inside-View Underestimate

The Planning Fallacy is the robust pattern in which people forecasting the time, cost, or risk of a novel task systematically underestimate it, even knowing that similar past tasks ran long or over budget. The mechanism is using the inside view instead of the outside view: when you forecast, you mentally simulate the steps you plan to take and the obstacles you foresee, and your estimate matches that simulation. But the simulation only contains steps you can imagine, so it omits the long tail of unanticipated interruptions, partial failures, and dependency surprises. The outside view (the actual spread of completion times for a reference class of comparable past tasks) is far more accurate, but a planner committed to 'my project is different' rarely reaches for it. So two strategies, simulate-the-plan versus check-the-distribution, give systematically different answers, and we default to the first, which is biased low. Because the bias comes from an otherwise reasonable process working on an incomplete picture, more effort and expertise do not remove it.

 

The planning fallacy is the structural pattern in which agents forecasting the time, cost, or risk of executing a novel task systematically underestimate those quantities, even when they know that similar past tasks ran long, over budget, or hit unanticipated failures. It is robust to feedback, persists in experts, and shows roughly constant magnitude across decades and cultures: a median overrun of about 30 to 50 percent on time and cost, with a long right tail. The load-bearing mechanism is inside-view substitution for the outside view. Constructing a forecast, the planner mentally simulates the intended steps, the anticipated obstacles, and the planned resources, and produces an estimate consistent with that simulation. The inside view omits the long tail of unanticipated interruptions, partial failures, dependency surprises, and known-but-unmodelled overhead, because by construction the simulation contains only steps the planner can imagine. The outside view, the empirical distribution of completion times for the reference class of comparable tasks, is far more informative, but it is psychologically unavailable to a planner committed to the inside-view simulation ('but my project is different'). The structural commitment is that two distinct strategies, simulate-the-plan and reference-the-empirical-distribution, yield systematically different estimates, and planners default to the first, which is biased downward. The bias is produced by an otherwise reasonable process operating on an unrepresentative reference class (the actions one can imagine, which omit the interruptions that will actually occur), so it is a property of the strategy's blind spot, not of carelessness, which is why effort and expertise do not remove it.

Broad Use

• Megaprojects: transport, energy, and infrastructure show right-skewed time and cost overruns that do not improve over time.
• Software engineering: nearly every non-trivial project ships late; story points and velocity tracking are functionally outside-view scaffolds.
• Personal and academic work: thesis-completion estimates routinely exceeded, even worst-case ones.
• Surgery and clinical scheduling: procedures run long, so operating rooms moved to empirically calibrated per-surgeon time estimates.
• Military planning: "no plan survives contact with the enemy," met by branch-and-sequel analysis, reserves, and pre-mortems.
• Everyday tasks: cooking and home renovation, where underestimation is folklore.

Clarity

Locates the bias not in either strategy but in the default substitution of inside-view simulation for outside-view reference, separating three merged errors — the planner lacks information (usually false), is dishonest (sometimes true, not necessary), or is using the wrong forecasting strategy (the load-bearing claim).

Manages Complexity

Compresses the "why projects are late" literature into one diagnostic schema — which strategy produced this estimate, and what would the reference class predict? — while predicting a class of interventions that fail: finer decomposition and more careful planning deepen the inside view and worsen the bias.

Abstract Reasoning

Yields a substrate-independent commitment — unbiased forecasts of intentional action come from the empirical distribution of comparable attempts, not internal simulation — and the counterintuitive prediction that domain experts, whose simulations are most detailed and coherent, are more vulnerable, not less.

Knowledge Transfer

• Megaprojects → regulation: reference-class forecasting embedded as a mandatory optimism-bias uplift.
• Medicine → scheduling: per-surgeon, per-procedure empirical distributions replace inside-view estimates.
• Software → general planning: small-batch planning shortens the forecast horizon so fewer surprises accumulate; pre-mortems force the outside view everywhere.

Example

Students forecasting thesis completion default to simulating the steps and cluster their estimates — even worst-case ones — below realized times, because the simulation cannot contain the advisor's sabbatical or the lost data file; adding a finer Gantt chart only makes the estimate more confident and more wrong.

Relationships to Other Primes

Parents (2) — more general patterns this builds on

• Planning Fallacy is a kind of, typical Bias — A named systematic directional forecasting error; a bias. Secondary parent (optimism_bias is itself a child of bias).
• Planning Fallacy is a kind of, typical Optimism Bias — The file: planning_fallacy is 'optimism bias as it manifests in forecasts of one's own goal-directed tasks' — the directional skew specialized to a specific MECHANISM (inside-view simulation substituting for the outside-view reference class). A specialization of optimism_bias with extra mechanistic content (feedback-resistance, detail-worsens-it).

Path to root: Planning Fallacy → Bias

Not to Be Confused With

• Planning Fallacy is not Optimism Bias because the fallacy names a mechanism (inside-view substitution producing feedback-resistant underestimation in one's own tasks), whereas optimism bias names a general direction of favorable expectation.
• Planning Fallacy is not Strategic Misrepresentation because the forecaster is sincerely mistaken and bears the overrun's cost, whereas a promoter who low-balls to win approval is not mistaken at all.
• Planning Fallacy is not Scenario Planning because scenario planning is a remedy that imagines multiple futures, whereas the fallacy is the disease of defaulting to a single self-coherent simulation.