Planning fallacy

The planning fallacy is predicting a project from its best-case internal story while neglecting how similar projects actually went. We see the steps we intend to take and miss delays, rework, coordination costs, and the base rate of overruns.

WikipediaKnowledge quiz Self assessment Microcourse

Mechanism

How it works

The inside view asks, 'What will we do next?' and produces a coherent, optimistic sequence. The outside view asks, 'What happened to projects like this?' and exposes the failure modes that feel exceptional only because they have not happened yet. Incentives can deepen the gap when an ambitious forecast is easier to approve than an honest one.

Examples

Where it shows up

A software team estimates six months from the feature list, then spends another six integrating systems, revising scope, and fixing the edge cases that every prior launch also had.
A student schedules a thesis from the writing time alone and omits research, feedback cycles, revision, and the work displaced by ordinary life.
A city approves a megaproject using the sponsor's best-case forecast instead of the distribution of comparable projects' final costs and completion dates.

Consequences

What it can distort

Budgets and promises fail together: teams commit resources too late, stakeholders lose trust, and rushed recovery work introduces new defects.
Repeated optimism can look like individual bad estimation when the real problem is a planning system that never measures its forecasts against outcomes.

Countermeasures

How to work around it

Use reference-class forecasting: base estimates on the actual completion times of similar past projects, not on decomposing this one.
Take your inside-view estimate and apply your team's historical overrun ratio — it's usually known and usually ignored.
Plan by milestones with buffers owned at the project level, not per-task; per-task buffers get consumed (Parkinson) while project buffers survive.

Caveats

Critiques and limits

Not every low estimate is an honest cognitive error. Strategic misrepresentation, political pressure, and changing scope can produce the same result; reference-class forecasting helps distinguish bad luck from a repeatedly biased or incentivized process.

Taxonomy

Fields of impact

Economics & Finance

Psychology & Social Science

Evidence

How solid is the research?

Robust — replicates reliably

Replicates in lab and field; megaproject data (Flyvbjerg) shows systematic cost/schedule underestimation at organizational scale.

Research

Relevant papers

Intuitive prediction: Biases and corrective procedures

Kahneman, D., & Tversky, A. (1979)

TIMS Studies in Management Science, 12, 313-327

Exploring the 'planning fallacy': Why people underestimate their task completion times

Buehler, R., Griffin, D., & Ross, M. (1994)

Journal of Personality and Social Psychology, 67(3), 366-381

The planning fallacy: Cognitive, motivational, and social origins

Buehler, R., Griffin, D., & Peetz, J. (2010)

Advances in Experimental Social Psychology, 43, 1-62

Case studies

Real-world patterns.

Real-world examples showing how Planning fallacy manifests in practice

Case study

Quarter-End Launch That Missed the Quarter: A Fintech Underwriting Engine

A real-world example of Planning fallacy in action

Context

A midsize fintech company decided to replace its legacy loan underwriting engine to support higher loan volumes and automated risk checks. Leadership set a hard target to launch before the end of the fiscal quarter to satisfy investor expectations and hit growth targets.

Situation

The CTO and product lead agreed on a 12-week development and integration timeline based on optimistic internal estimates and an expectation that most dependencies were 'straightforward'. Compliance, operations, and several legacy banking partners were told the migration would be completed on schedule and to prepare for a single big switch-over.

The bias in action

Project stakeholders anchored on the desired quarter-end date and generated overly optimistic task estimates, ignoring delays from similar past projects. The development team produced a schedule focused on ideal progress (no interruptions, perfect integration), and risk items were listed but given minimal time. Because the leadership wanted to present a clean launch story to investors, dissenting voices about integration complexity and regulatory sign-off were downplayed. No formal historical benchmarking or contingency buffer was used to adjust the timetable.

Outcome

Integration with legacy partner APIs required unexpected custom adapters and an additional security review, extending development by 18 weeks (actual time to launch: 30 weeks). The company incurred an unplanned $450,000 in contractor and overtime costs and missed projected loan origination revenue of approximately $1.2 million for the missed quarter. Investor confidence dipped; one institutional investor postponed a planned follow-on funding conversation citing missed milestones.

What's inside the full case study

Unlock the deeper breakdown with real-world impact, measurable effects, lessons learned, better-approach recommendations, and relevant fields.

Real-world impact

Affected groups, timeframe, and measurable outcomes.

Lessons learned

Practical takeaways and a better path forward.

Full case breakdownEmail access

Want the full analysis?

Request access to the complete case study, including measurable impact, lessons learned, and the recommended better approach.

Recommended books

Thinking, Fast and Slow

Daniel Kahneman, 2011

Judgment under Uncertainty: Heuristics and Biases

Daniel Kahneman, Paul Slovic, Amos Tversky, 1982

Noise: A Flaw in Human Judgment

Daniel Kahneman, Olivier Sibony, Cass R. Sunstein, 2021

Related biases

Nearby patterns.

Optimism bias

Optimism bias is expecting better outcomes for ourselves than for similar other people.

Overconfidence effect

Overconfidence is believing a judgment is more accurate, a skill stronger, or an outcome more controllable than the evidence warrants.

Present bias

Present bias is the tendency to give disproportionate weight to immediate costs and rewards relative to future ones — beyond what any consistent discounting of the future would justify.

Well-traveled road effect

A familiar commute can feel short because it demands little attention; an unfamiliar route can feel long because every turn is new.

Delmore effect

The Delmore effect is the tendency to set clear, detailed, and articulate goals for the lower-priority areas of our lives, while our most important ambitions remain vague and unarticulated.

Time-saving bias

Time-saving bias is misjudging how much time a change in speed actually saves, especially when comparing rates rather than durations..

Study on Microcourse

Learn the wider pattern.

Dive deeper into Planning fallacy and related biases in Decision-Making and Risk Biaseswith structured lessons, examples, and practice exercises.

Study

Practice

Test your knowledge.

Apply what you have learned and reinforce your understanding of Planning fallacy with a short quiz or self-assessment.

Understanding quiz Self-assessment

Entry last reviewed 2026-07-16 · sources verified against the published literature — methodology