Planning Fallacy
The tendency to underestimate the time, costs, and risks associated with a task, while overestimating the benefits, leading to overly optimistic projections.
THE IDEA
The planning fallacy is a cognitive bias first identified by Kahneman and Tversky (1979). It describes our propensity to base predictions on overly optimistic scenarios, ignoring past experiences and potential obstacles. For example, in the Star Trek scene, Captain Kirk asks Spock about their chances of surviving a dangerous situation. Spock replies with a conditional statement—'If the density grows no worse we should be able to ride it out'—which hedges the estimate but still leans toward success. They do succeed, but the bias often leads to failure when real-world complexity and uncertainty are underestimated. The planning fallacy is particularly common in project management, where individuals and teams routinely underestimate deadlines and budgets, despite historical evidence to the contrary. Mitigating it requires using reference class forecasting, pre-mortems, and explicit consideration of risks.
When to use it
When setting deadlines for a personal or professional project, explicitly review historical data from similar tasks to adjust expectations.
In team planning, conduct a 'pre-mortem' where everyone imagines the project has failed and works backward to identify potential pitfalls.
When making a budget for a large purchase or renovation, add a realistic buffer based on past overruns rather than assuming best-case pricing.
For personal goal-setting (e.g., learning a new skill), break the task into smaller milestones and track progress against realistic benchmarks.
FROM THEORY TO EVERYDAY LIFE
In practice
Spock's Probability Estimate
In the Star Trek episode, Captain Kirk asks Spock about their chances of surviving a dangerous situation. Spock responds with a conditional estimate ('If the density grows no worse we should be able to ride it out'), and they succeed. The planning fallacy appears here: even a cautious estimate fails to account for potential worsening conditions, yet the outcome reinforces an overly optimistic view.
Software Development Project
A software team estimates a project will take three months based on an ideal scenario. Past similar projects took six months, but the team ignores that data. They end up taking eight months, exceeding the initial estimate by 160%.
A MOMENT TO REFLECT
Put it to work.
Think of a recent project you planned. How did your initial estimate compare to the actual time, cost, and outcome? What might you have overlooked?
How can you use reference class forecasting (looking at similar past projects) to counteract the planning fallacy in your next major undertaking?
Often confused with
References
- Intuitive prediction: Biases and corrective procedures — Kahneman, D., & Tversky, A. (1979)
CONTINUE THE CONVERSATION
Source texts
- The Scout Mindset (Julia Galef)