The planning fallacy
The planning fallacy is the tendency to underestimate how long a task will take, how much it will cost, and how likely it is to go wrong — even when you know similar past tasks ran over. We plan for the smooth best case, not the messy real one.
An impossibly over-scoped construction, already tilting and structurally doomed yet still being built, is the archetype of a grand project whose planners never reckoned with how it would actually run over and fail.
Pieter Bruegel the Elder, The Tower of Babel (1563) · Public domain
Why does the planning fallacy happen?
We build estimates from an idealised, step-by-step "inside view" of the specific plan, picturing everything going right, and ignore the "outside view" — the track record of how similar projects actually went.
Each project feels uniquely controllable, so you just move the unknown unknowns where you can't see them.
What does the planning fallacy look like in real life?
- Home renovations and software projects routinely running double their estimate.
- The Sydney Opera House: estimated at 4 years and $7M, it took 14 years and $102M.
- "I’ll finish this in an hour" for a task that reliably takes three.
How do you counter the planning fallacy?
- Take the outside view: base the estimate on how long similar tasks actually took, not the plan in your head.
- Multiply optimistic estimates by a reality factor (often 1.5–3×).
- Break the task down — hidden sub-steps are where overruns hide.
The deeper point
It survives experience because each project feels uniquely controllable — "last time had problems, but this time I’ve accounted for them." You haven’t; you’ve just moved the unknown unknowns somewhere you can’t see them yet.
Frequently asked
- What is the planning fallacy?
- The tendency to underestimate the time, cost, and risk of a task — even when you know similar tasks overran — because you plan for the best case and ignore the track record.
- Who discovered the planning fallacy?
- Daniel Kahneman and Amos Tversky coined it in 1979; Kahneman later framed the fix as the "outside view" — basing estimates on similar past cases, not the plan in your head.
- How do you avoid the planning fallacy?
- Use the outside view (how long did comparable tasks really take?), add a buffer, and break the work into sub-steps where hidden effort lurks.
Related
Keep reading
The mere-exposure effect
Do you actually like the song, or have you just heard it a lot?
See this alongside the other thinking tools of building a startup, learning, software engineers and productivity.
This bias distorts planning & estimation, product decisions and studying & learning.
Go deeper
The book behind this idea: Thinking, Fast and Slow by Daniel Kahneman. Hear the whole thing free — start an Audible trial and your first audiobook is on the house.
Read the full summary of Thinking, Fast and Slow →
More canonical picks:
- The Art of Thinking Clearly — Rolf Dobelli
- The Great Mental Models, Volume 1 — Shane Parrish
- Poor Charlie’s Almanack — Charlie Munger
- Super Thinking — Gabriel Weinberg & Lauren McCann
- Seeking Wisdom — Peter Bevelin
As an Amazon Associate, ReadGlobe earns from qualifying purchases and Audible trials — at no extra cost to you.
Cite this page
ReadGlobe. (2026). The planning fallacy. https://readglobe.com/bias/planning-fallacy/
"The planning fallacy." ReadGlobe, 29 May 2026, readglobe.com/bias/planning-fallacy/.
Primary source: Wikipedia
Editorial synthesis © ReadGlobe 2026, drawing on Kahneman’s Thinking, Fast and Slow, the Tversky–Kahneman research program, and the primary cognitive-science literature. · Last reviewed 2026-05-29.