Planning Fallacy
Underestimating time, costs, and risks
What is it?
The planning fallacy, named by Daniel Kahneman and Amos Tversky, is the tendency to underestimate the time, costs, and risks of future actions, often while overestimating their benefits. It persists even when people have repeatedly seen similar projects run over. The Sydney Opera House, budgeted at around A$7 million, finally cost about A$102 million and opened a decade later than planned. The pattern recurs in construction, software development, and personal projects alike. The fallacy arises because we plan using an "inside view"—focusing on the specific case and imagining everything going to plan—rather than an "outside view" that considers how similar past projects actually went. We also underweight potential obstacles, assume tasks will proceed without delays, and fall prey to motivational biases (wanting projects to seem feasible). Reference class forecasting—looking at how long similar projects actually took—tends to improve accuracy, but requires overcoming the belief that "this time is different." Adding buffer time helps, though buffers are often too small to absorb real overruns. Good planning treats past overruns as informative rather than exceptional.
Example
Estimating renovation at $20,000 when similar projects cost $40,000. Thinking you'll finish a report in 2 hours when it always takes 4. Underestimating moving time.
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.
How to Prevent It
Doxa uses AI and can make mistakes. How it's built
How long did similar projects actually take in the past?
What could go wrong that I haven't considered?
Am I being overly optimistic about best-case scenarios?
Have I accounted for interruptions, dependencies, and unknowns?
What does my track record say about my estimation accuracy?
Use reference class forecasting based on similar projects.
Size your buffer from your past overruns, not from a gut-feel percentage.
Break projects into smaller tasks and estimate each separately.
Ask team members for independent estimates and compare.
Track actual vs. estimated time to calibrate future predictions.
Scientific Sources
Related Decisions
Starting a new project
Likely to underestimate time and costs
Buying a home
May underestimate renovation costs and delays
Setting project deadlines
Systematically underestimate time needed
Launching a product
Likely to underestimate the time left before a solid launch
Starting your own business
Likely to underestimate time to profitability
Pursuing a degree or certification
May underestimate time to complete
Going freelance
May underestimate time to build client base