Use reference class forecasting for project estimates
Estimate how long similar projects have taken historically before estimating your specific project.
Why it works
Planning fallacy — the tendency to underestimate time and cost — is a direct application of base-rate neglect: people focus on the inside view (the specific plan) and ignore the outside view (how similar projects actually performed). Reference class forecasting corrects this by requiring the outside view first and treating the specific plan as an adjustment to the base rate, not a replacement for it.
How to do it
- Identify the reference class: "What is the best comparison group for this project?"
- Look up (or estimate) how long and at what cost the typical project in that class was delivered.
- Use the historical distribution as your starting forecast; adjust only for specific, known differences.
Evidence
Reference class forecasting, formalized by Kahneman and further developed by Bent Flyvbjerg, has been validated on large infrastructure projects and is now a recommended forecasting method in several national planning standards. (observational)
Sources
- Flyvbjerg (2008), "Curbing Optimism Bias and Strategic Misrepresentation," European Planning Studies
- Kahneman & Lovallo (1993), "Timid Choices and Bold Forecasts: A Cognitive Perspective on Risk-Taking," Management Science
Common mistake
Choosing a flattering reference class ("similar projects by top teams") rather than the accurate one ("projects with similar scope and constraints, regardless of team").
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for Base-Rate Neglect: Why We Ignore the Odds
- Ask the base rate before evaluating the specific case
Before judging any individual instance, first establish how often this kind of thing happens in general.
- Update beliefs by degrees, not wholesale
Treat new information as evidence that shifts probabilities, not as proof that changes everything.
- Always identify the denominator when evaluating risk or success
When a number or story is striking, ask: "Out of how many total cases?"
- Deliberately invoke the outside view for important decisions
For any high-stakes prediction, force yourself to start with how things typically go, not how your situation feels.
- Practice probabilistic calibration by tracking your predictions
Assign explicit probability estimates to your predictions and track whether they come true at the right rate.
- Expect regression to the mean in extreme outcomes
Unusually good or bad performance tends to be followed by more average performance — not because of what you did.
Related concepts
- Thinking, Fast and Slow, Made Usable
Two systems, the biases they create, and when to slow down
- Bayesian Thinking: How to Update Beliefs Rationally
Holding beliefs as probabilities and updating them when evidence arrives
- Anchoring Bias in Negotiation and Judgment
Why the first number wins — the mechanism, and how to set and resist anchors