🧬 kbird.ai

Planning Fallacy

3 min read

Planning Fallacy

Type: Prediction — Time Estimation Also Known As: Optimistic bias in planning, completion bias

Definition

Underestimating the time, costs, and risks of completing a task while overestimating the benefits — despite knowing that similar tasks have taken longer in the past. We make plans based on best-case scenarios rather than realistic assessments.

“This will only take two weeks.” (Actually takes two months.)

Form

  1. A project or task is planned
  2. Estimates are based on ideal conditions
  3. Past similar projects took longer/cost more
  4. These historical data are ignored or discounted
  5. The plan proceeds with unrealistic timelines
  6. Deadlines are missed, costs overrun

Examples

Example 1: Software Projects

Developers estimate a feature will take two weeks. Six weeks later, it’s still not done. Edge cases emerged, integration was harder, testing found bugs. Every project follows this pattern; every new project is estimated optimistically.

Problem: The planning fallacy is the norm in software development.

Example 2: Home Renovation

“We’ll be done in a month.” The contractor finds structural issues, permits take longer, materials are backordered. Three months later, it’s still not done — just like every previous renovation project.

Problem: Even with experience, we don’t apply it to new estimates.

Example 3: Academic Papers

“I’ll finish this paper over the weekend.” The literature review takes longer than expected, the analysis has bugs, revisions multiply. Two weeks later, it’s finally submitted.

Problem: The gap between planning and reality is consistently underestimated.

Example 4: Government Projects

Big Dig, Sydney Opera House, Denver Airport — massive cost and time overruns are the rule, not the exception. Despite extensive planning, estimates are consistently wrong.

Problem: Public pressure for optimistic estimates compounds the bias.

Why It Happens

  • Focus on the task, not potential obstacles
  • Desirability bias — we want it to be quick
  • Inside view — considering task details, not similar tasks
  • Social pressure — optimistic estimates are rewarded
  • Discounting of past failures — “this time is different”

How to Counter

  1. Reference class forecasting: How long did similar projects take?
  2. Outside view: Ask others’ estimates of your timeline
  3. Murphyjitsu: Assume everything goes wrong — what’s your plan?
  4. Buffer time: Add 50-100% to your estimate
  5. Break into small tasks: Smaller estimates are more accurate
  6. Track actuals: Record how long things really take

Inside View vs. Outside View

  • Inside view: Focus on task specifics, unique features, plans
  • Outside view: Compare to similar completed tasks, base rates

The planning fallacy results from over-reliance on the inside view and neglect of the outside view.

References

  • Kahneman, D. & Tversky, A. (1979). Intuitive prediction: Biases and corrective procedures
  • Buehler, R. et al. (1994). Exploring the “planning fallacy”
  • Flyvbjerg, B. (2006). From Nobel Prize to project management

Part of the Convergence Protocol — Clear thinking for complex times.

Graph View

Backlinks