Skip to main content

Planning Fallacy

Underestimating time, costs, and risks

Judgment

What is it?

The planning fallacy, coined by Kahneman and Tversky, is the systematic tendency to underestimate the time, costs, and risks of future actions while overestimating benefits. This bias persists despite repeated experience with projects exceeding their estimates. The Sydney Opera House, originally estimated at $7 million and 4 years, cost $102 million and took 16 years. This pattern repeats across construction, software development, and personal projects alike. The fallacy occurs because we plan using an "inside view"—focusing on the specific case and imagining everything going according to plan—rather than an "outside view" that considers base rates from similar past projects. We also underweight potential obstacles, assume tasks will proceed sequentially without delays, and fall prey to motivational biases (wanting projects to seem feasible). Reference class forecasting—looking at how long similar projects actually took—dramatically improves accuracy but requires overcoming the belief that "this time is different." Adding buffer time helps, but research shows people consistently use buffers too small to account for actual variance. Successful planning requires treating past failures 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

Question

How long did similar projects actually take in the past?

Question

What could go wrong that I haven't considered?

Question

Am I being overly optimistic about best-case scenarios?

Question

Have I accounted for interruptions, dependencies, and unknowns?

Question

What does my track record say about my estimation accuracy?

Technique

Use reference class forecasting based on similar projects.

Technique

Add a buffer of 50-100% to your initial estimate.

Technique

Break projects into smaller tasks and estimate each separately.

Technique

Ask team members for independent estimates and compare.

Technique

Track actual vs. estimated time to calibrate future predictions.