What Is the Planning Fallacy? Why Everything Takes Longer Than You Think

You are sure the report will take two hours, so you plan the afternoon around it. At 6 p.m. you are still working. You promise to leave at 8:00 and walk out at 8:40. You estimate the renovation at six weeks and it takes five months. You have done this many times, and you will do it again.

This is the planning fallacy, one of the most reliable quirks of human prediction.

What is the planning fallacy?

The planning fallacy is the tendency to underestimate how long a future task will take, and how much it will cost, even when you know that similar tasks have taken longer in the past. Daniel Kahneman and Amos Tversky introduced the term in 1979, noting that people’s forecasts for their own projects are consistently too optimistic, even when they have relevant experience.

It is not just about time. Plans tend to underestimate costs and risks and overestimate benefits.

The classic research

Roger Buehler, Dale Griffin and Michael Ross asked university students to predict when they would finish their senior theses. On average, students predicted they would take about 34 days; they actually took about 56. Only about 30 percent finished by their own predicted date. Even when asked for a “worst case” estimate, many still finished later than that. The researchers found that the same pattern held for other tasks, such as everyday chores and tax returns.

Interestingly, when people made predictions about other people’s tasks, they were more realistic. We tend to forecast for ourselves with an optimism we don’t extend to others.

Famous examples

• Sydney Opera House: originally expected to take about four years and cost around AUD 7 million, it opened in 1973 after roughly 14 years and a cost of about AUD 102 million.
• Large public projects: Bent Flyvbjerg’s research on infrastructure and megaprojects found that cost overruns and benefit shortfalls are common worldwide.
• Everyday life: home renovations, essays, software projects, weddings and the time it takes to get out of the door.

Why it happens

The inside view

When you plan, you picture the steps you intend to take, a smooth path from start to finish. Kahneman and Tversky called this the inside view. It focuses on the specific details of your plan and neglects what is not in it: interruptions, illness, delays, other priorities and the many small things that go wrong.

Ignoring the outside view

The outside view asks: How long did similar projects take for people like me? It uses the “reference class.” People tend to neglect this information even when they have it.

Optimism and motivation

Buehler and colleagues’ review identifies motivational factors: we want to believe we’ll succeed, and optimistic plans feel good and help us get started. Public commitments, deadlines and social pressure add to this.

Memory

We recall past delays as the result of unusual events, so we do not carry the lesson forward: this time will be different. See what is hindsight bias.

Complexity and dependencies

Tasks have hidden parts. Each step also depends on others, and delays cascade.

What it costs

• missed deadlines and last-minute stress,
• overbooked days and constant lateness. See how to stop being late all the time,
• overcommitting. See how to stop overcommitting,
• budget overruns,
• chronic procrastination and guilt. See how to stop procrastinating,
• clinging to failing projects. See what is the sunk cost fallacy.

How to counter it

1. Use the outside view

Before estimating, ask: How long have similar tasks taken me or others? Use that, not the best case. Lovallo and Kahneman describe “reference class forecasting” as the best remedy: base your forecast on actual outcomes of similar projects. Flyvbjerg’s work on megaprojects advocates the same approach.

2. Track your own data

Keep a simple log of your estimates and actual times for a few weeks. Most people discover a consistent gap, such as everything taking 1.5 times longer than expected. Then apply a personal multiplier.

3. Break the task into steps

Estimating small pieces tends to be more accurate than one big guess. List every step, including the boring ones (setup, review, cleanup, waiting). Research suggests “unpacking” a task reveals components you would otherwise forget.

4. Add buffer

Add a margin, such as 25 to 50 percent, to the total. For high-stakes projects, plan the worst case and the typical case, not just the best.

5. Think about what could go wrong

Do a “pre-mortem”: imagine the project has failed, and list reasons why. Add time for the likely ones. Include the other people involved; their delays become yours.

6. Ask someone else

An outsider is less biased. Ask a colleague or friend how long they think it would take, or ask someone who has done it before.

7. Set intermediate deadlines

Short milestones expose slippage early, while there is still time to adjust.

8. Treat plans as hypotheses

Review at checkpoints, update the schedule and decide what to cut. Accept that the plan will change.

A worked example

Sara plans to write a 3,000-word report in one afternoon.

1. Outside view: her last two reports of that length took six and seven hours.
2. Data: her log shows she usually takes 1.5 times her estimate.
3. Steps: research (2h), outline (30m), draft (3h), edit (1h), formatting and references (45m).
4. Buffer: she adds 25 percent, for a total of about 9.5 hours.
5. Pre-mortem: she notes she may wait on data from a colleague, so she asks for it today.
6. Ask: a coworker agrees that a full day is realistic.
7. Milestones: outline by 11 a.m., draft by 4 p.m.
8. Plan: she starts the previous afternoon and finishes comfortably before the deadline.

Common mistakes

• Planning the best case. Plan the typical case plus a buffer.
• Thinking “this time is different.” It rarely is.
• Ignoring other people’s delays. They count.
• Over-correcting into never starting. Estimates are tools, not guarantees.
• Padding silently and then filling the time. Parkinson’s law can eat buffers; set intermediate deadlines.
• Beating yourself up. It is a universal bias.

Frequently asked questions

What is the planning fallacy in simple terms?

Underestimating how long something will take, despite knowing that similar things have taken longer before.

Who coined the planning fallacy?

Daniel Kahneman and Amos Tversky in 1979; Roger Buehler and colleagues later studied it extensively.

Why do we underestimate tasks?

We focus on our plan and ignore delays and base rates, we are optimistic and we remember past delays as exceptions.

Does the planning fallacy affect everyone?

It is very common, including experts. It tends to be reduced when we consider the track record of similar projects.

How do I avoid it?

Use the outside view, track your estimates, break tasks into steps, add a buffer and ask someone else.

Is the planning fallacy the same as procrastination?

No. The planning fallacy is mis-estimating; procrastination is delaying. They can feed each other.

The bottom line

Plans live in our best-case imagination, but real tasks live in the real world. Take the outside view, track your own data, break tasks into steps, add a buffer, run a pre-mortem and set milestones. You won’t beat the planning fallacy completely, but you can plan with your eyes open.