The Planning Fallacy: Why Every Project Runs Late Even When You Know This

Daniel Kahneman and Amos Tversky identified the planning fallacy in 1979: people systematically underestimate how long tasks will take, even when they have extensive experience with similar tasks running over time. Knowing about this bias does not make you immune to it.

## Why Knowledge Doesn't Help

The planning fallacy persists for a structural reason: when we plan, we construct a specific, optimistic scenario. We think about what will go right, not what has historically gone wrong. This is sometimes called "inside view" thinking — you're reasoning from the specific plan, not from reference class data.

The antidote is "outside view" thinking: before you commit to a timeline, ask "what's the base rate of completion for projects similar to this one?" This sounds simple. It almost never happens in practice because:

1. People believe their project is unique (and they're partially right — but the uniqueness doesn't make it faster)
2. Considering base rates feels like admitting defeat before starting
3. Organizations reward optimistic timelines that get buy-in, even when they're wrong

## The Reference Class Forecasting Fix

Kahneman and Flyvbjerg developed Reference Class Forecasting (RCF) as an operational fix. The process:

1. Identify a reference class of similar past projects
2. Establish the base rate of cost, time, and outcome distributions for that class
3. Anchor your estimate to the median of the reference class
4. Adjust for specific features of your project (but less than your intuition suggests)

This method is used in major infrastructure project planning in Denmark and the UK. It consistently produces more accurate estimates than expert-driven bottom-up planning.

## Why Estimates Still Slide After Using RCF

Even with better initial estimates, scope creep, dependency delays, and personnel changes cause slippage. The planning fallacy is partly an estimation problem and partly an execution risk problem. Better estimates without change control still produce late projects.

The most effective combined approach: reference class estimate + pre-mortem (imagine the project failed, write down why, build mitigations for the top causes). This attacks both the estimation bias and the risk blindness that keeps estimates wrong after the fact.

## Organizational Dynamics

Companies that consistently deliver on time don't have fewer planning fallacies — they have better institutional mechanisms to surface slippage early. The signal isn't "we estimated correctly." The signal is "we caught the problem in week 2, not month 5."

The Planning Fallacy: Why Every Project Runs Late Even When You Know This

// COMMENTS

ON THIS PAGE