Trap/Cognitive Bias/No. 0740
Planning Fallacy
The planning fallacy is a bias in which people underestimate the time and cost of tasks despite past delays on similar work. Named by Daniel Kahneman and Amos Tversky in 1979, it reflects an optimistic inside view that discounts relevant past outcomes.
- Evidence
- Well established
- Read
- 6 min
- Links
- 10 connections
- Useful when
- Deciding under uncertainty · Estimating time and cost · Forecasting · Running projects
01You've seen this when…
- in life
You leave Saturday afternoon free to paint the living room. By dinner, you’ve moved the furniture and patched the holes, but haven’t opened the paint.
- at work
The migration schedule includes a day for each technical step. Nobody includes the week spent waiting for security approval.
- out in the world
A transit agency announces a station renovation budget based on the construction plan. Comparable renovations have needed expensive utility work, but this budget assumes no surprises.
02The idea
The planning fallacy is an overly optimistic forecast: you underestimate the time and cost a task requires and how difficult it will be. Its clearest form appears when you expect this attempt to go better than comparable attempts already have, even though you know that history.
You can remember that the last three reports took a week and still believe this one will take two days. The earlier delays each have an explanation: missing data, a sick colleague, revisions. This time, you expect to avoid those particular problems. Other problems can fill their places.
The mistake is treating a workable plan as a likely outcome. A plan describes a route to completion. A forecast must also account for how often people actually travel that route without interruption.
That distinction separates the inside view, built from the details of your task, from the outside view, built from what happened to comparable tasks. Details matter, but they shouldn’t erase the record.
03Why it happens
- The imagined sequence takes over. Once you picture drafting, reviewing, and sending the report, the sequence feels like evidence for its duration. Waiting, rework, and competing responsibilities sit outside that picture. This is a form of focalism: the task gets attention while its surroundings fade.
- Past delays look exceptional. You explain each previous overrun as a special case rather than treating overruns as part of the usual process. The exact problem may not recur, but the category does.
- Small risks disappear between steps. Each step looks manageable on its own. Across twenty steps, several opportunities for delay can turn a plausible schedule into an unlikely one.
- A desired date becomes an expected date. You want the move finished before school starts or the product ready before a trade show. That preference can pull the forecast toward the deadline. Wishful thinking makes the convenient answer feel credible.
04A worked example
In a 1994 study, Roger Buehler, Dale Griffin, and Michael Ross asked university students to predict when they would finish their honors theses. The students gave an expected completion time and estimated how it would change under favorable or unfavorable conditions.
What it looks like People who know their own projects making informed estimates, with a pessimistic scenario included as a safeguard.
What’s actually going on Their expected completion time averaged 33.9 days. Actual completion averaged 55.5 days. Even their unfavorable-scenario estimates averaged only 48.6 days. Across the group, reality took longer than the supposedly pessimistic forecast. Knowing the project closely did not produce a well-calibrated schedule.
What would have helped Begin with completion times for comparable theses at a similar stage, then adjust for specific differences. The same paper found that prompting people to connect relevant past experience to their current predictions reduced the bias. They had to use their experience in the forecast to benefit from it.
The students needed to use outcome evidence to decide how much time to allow. A forecast needs that evidence, not just a detailed account of the work ahead.
05How to spot it
06What to do instead
- Find comparable outcomes before estimating. Look at several completed tasks with similar scope and constraints. Use total elapsed time, including time spent waiting. For budgets, use the final costs of completed projects. This is reference-class forecasting.
- Start from the record, then adjust. If similar work usually takes six weeks, make six weeks the starting point. Change it only for concrete differences, such as completed preparatory work or a smaller scope. Keep the starting point when confidence is your only reason to change it.
- Account for the surrounding work. Add review queues, approvals, handoffs, competing assignments, and likely rework. Account for limits on when people and resources are available.
- Separate the forecast from the commitment. A deadline expresses what you need or promise. A forecast expresses what you expect. Show a range, and explain which date is the ordinary expectation and which allows more room for delay. Avoid disguising a hopeful target as a reliable estimate.
- Keep estimates beside actuals. Record both in a decision journal, along with what the estimate included. After several tasks, look for repeated omissions. A short pre-mortem can supplement historical data by surfacing missing obstacles.
07When it isn’t a planning fallacy
Even an honest forecast can miss a project’s completion date, especially when the task is unfamiliar or conditions change sharply. A repeated pattern of optimistic estimates despite relevant experience provides stronger evidence of biased planning.
Some low estimates reflect deliberate understatement. A contractor may submit a cheap bid to win work; a manager may announce a date to create pressure. Those can be strategic choices or deception rather than forecasting errors. The remedy must address incentives as well as thinking.
The planning fallacy is narrower than optimism bias, which concerns favorable expectations more broadly. The outside view can mislead when comparisons are poorly chosen. Match the scope, starting point, resources, and definition of completion. Adding the same arbitrary buffer to every task leaves those differences unexamined.
08Roots
While helping develop a school curriculum in Israel, Daniel Kahneman asked his team to write down estimates of the time needed to finish. Their answers clustered around two years. Then he asked a colleague with experience of comparable curriculum teams how those projects had turned out. Teams that finished had generally taken seven to ten years; many had never finished.
In Kahneman’s later account, the team absorbed this unsettling information and carried on much as before. Their familiarity with their own work made the longer history feel less relevant. The project eventually took eight years. He told the story in Thinking, Fast and Slow as an example of how difficult it is to let the outside view change an appealing plan.
Kahneman and Amos Tversky named the planning fallacy in their 1979 work on intuitive prediction. The puzzle was why people made optimistic project forecasts even when they knew similar projects had run badly. Their answer emphasized forecasts built around the current plan, with the distribution of previous outcomes left in the background.
Buehler, Griffin, and Ross later brought the idea into studies of ordinary tasks, including theses and personal projects. That helped turn a recognizable observation into a testable forecasting bias: compare the prediction with completion, then examine what changes when past experience is made part of the estimate.
09How solid is this?
Optimistic completion estimates are well documented across studies of academic, personal, and work tasks. Using relevant past outcomes can reduce the bias, though effects depend on the task and forecasting method. Large project overruns can also reflect changing scope, incentives, or deliberate understatement.
10Connections
- Often confused with Hofstadter’s Law, Optimism Bias, Parkinson’s Law
- Countered by Margin of Safety, Outside View vs. Inside View, Reference-Class Forecasting, Decision Journal, Pre-Mortem
- Can follow from Focalism
- Part ofWishful Thinking
11Origin and sources
Daniel Kahneman and Amos Tversky named the planning fallacy in 1979 in their work on intuitive prediction. Roger Buehler, Dale Griffin, and Michael Ross provided influential experimental evidence in 1994.
- [1]Kahneman, D., & Tversky, A. (1979). Intuitive prediction: Biases and corrective procedures. TIMS Studies in Management Science, 12, 313–327.
- [2]Buehler, R., Griffin, D., & Ross, M. (1994). Understanding the planning fallacy: Why people underestimate their task completion times. Journal of Personality and Social Psychology, 67(3), 366–381.
- [3]Buehler, R., Griffin, D., & Peetz, J. (2010). The planning fallacy: Cognitive, motivational, and social origins. Advances in Experimental Social Psychology, 43, 1–62.
- [4]Kahneman, D. (2011). Thinking, Fast and Slow, chapter 23. Farrar, Straus and Giroux.
Suggest an edit· Updated 2026-10-02