Planning Fallacy
Category: Decision Making
The tendency to overestimate the time, costs, and risks of future actions and at the same time overestimate the benefits of the same actions.
How it works
When you imagine completing a task, your brain runs a single, smooth simulation: you sit down, you focus, the words flow, you finish. This best-case mental movie feels like a realistic plan, but it quietly assumes that nothing goes wrong, no interruptions, no sick kids, no dependency that breaks, no day where you just don't feel like it. You are forecasting from the inside of the task, using your intentions, while the actual outcome is governed by the messy outside world.
The second engine is memory amnesia. You have been late before, on the last paper, the last renovation, the last product launch, but those delays get filed under 'special circumstances' rather than 'this is what tasks do.' Each delay feels like a one-off, so it never updates your model. Worse, focusing on the plan itself (the steps) actively crowds out memory of past results (the slippage).
The fallacy is surprisingly stubborn: it persists even when people know they're usually late, and even when they're explicitly asked for a worst-case estimate. The optimism is baked into the act of planning, not into ignorance.
Where you'll see it
- A couple budgets $40,000 and four months for a kitchen renovation; eleven months and $70,000 later they're still eating takeout, having hit a plumbing surprise, a backordered countertop, and a contractor who vanished for three weeks.
- A software team commits to shipping a feature 'by end of sprint,' confident because the happy-path coding is two days of work, then loses a week to an undocumented API, a flaky test suite, and a teammate out with the flu.
- A grad student tells their advisor the dissertation will be done in six months; the lit review alone eats four, and the defense happens nineteen months later, exactly mirroring how long the master's thesis overran.
Where it comes from
The term was coined by Daniel Kahneman and Amos Tversky in 1979, the same period they were developing prospect theory. Kahneman later told a famous illustrative story about a textbook-writing committee he was on: members estimated the project would take about two years, yet when he asked an expert in the room how long comparable teams had taken, the honest answer was seven to ten years, and roughly 40% never finished at all. The committee pressed on anyway and finished in about eight years. Researchers Roger Buehler, Dale Griffin, and Michael Ross later documented the effect experimentally, showing that students' confident self-predictions about finishing academic work systematically beat their actual completion times.
How to counter it
Use reference class forecasting, the single most effective antidote. Instead of estimating this project from the inside, find a basket of similar past projects (yours or others') and ask how long they actually took. Your renovation will take as long as renovations take, not as long as your optimism says.
Force the 'outside view' with a hard rule: take your gut estimate and apply a multiplier drawn from history. If your last three projects ran 1.7x over, plan at 1.7x. Then unpack the task into sub-steps before estimating, decomposition surfaces the hidden plumbing, integration, and review work that the smooth mental movie skips.
Finally, run a pre-mortem: imagine it's the deadline and the project blew up. List every reason why. The delays you can name in advance are the ones you can buffer against, so build the slack in now, not as a guilty apology later.
The tell
You're doing it when your plan only describes the version where everything goes right.
Related biases
Featured in
- How to Actually Beat Your Cognitive Biases (Awareness Isn't Enough)
- Why Smart People Make Dumb Decisions
- Cognitive Biases in Decision-Making, and how to debias your choices
- How Rational Are You, Really? (take the 5-minute bias test)
Common questions
What is Planning Fallacy?
Planning Fallacy is the tendency to underestimate the time, costs, and risks of future actions while overestimating their benefits. It leads people to expect tasks and projects to go faster, cheaper, and more smoothly than they actually do. You are doing it whenever your plan only describes the version where everything goes right.
Why does Planning Fallacy happen?
Planning Fallacy happens because when you imagine completing a task, your brain runs a single smooth best-case simulation: you sit down, you focus, you finish. That mental movie feels like a realistic plan, but it quietly assumes nothing goes wrong, no interruptions, no broken dependencies, and no days you just do not feel like it. You end up forecasting the ideal path rather than the messy real one.
What is an example of Planning Fallacy?
A classic example of Planning Fallacy is a couple who budget $40,000 and four months for a kitchen renovation. Eleven months and $70,000 later they are still eating takeout, having hit a plumbing surprise, a backordered countertop, and a contractor who vanished for three weeks. Their inside-view estimate ignored the setbacks that renovations routinely encounter.
How do you avoid Planning Fallacy?
The most effective way to avoid Planning Fallacy is reference class forecasting. Instead of estimating a project from the inside, find a basket of similar past projects, yours or others', and ask how long they actually took and cost. Your project will take about as long as similar projects take, not as long as your best-case simulation predicts.
How do you spot Planning Fallacy in yourself?
You spot Planning Fallacy in yourself when your plan only describes the version where everything goes right. If your timeline and budget assume no interruptions, no breakdowns, and no off days, that smooth best-case story is the tell. A realistic plan accounts for the setbacks that similar efforts have reliably faced.
References
- Kahneman, D., & Tversky, A. (1979). Intuitive prediction: Biases and corrective procedures. TIMS Studies in Management Science, 12, 313-327
- Buehler, R., Griffin, D., & Ross, M. (1994). Exploring the "planning fallacy": Why people underestimate their task completion times. Journal of Personality and Social Psychology, 67(3), 366-381
- Buehler, R., Griffin, D., & Peetz, J. (2010). The planning fallacy: Cognitive, motivational, and social origins. Advances in Experimental Social Psychology, 43, 1-62
- Kahneman, D. (2011). Thinking, Fast and Slow (Chapter 23: The Outside View). Farrar, Straus and Giroux