July 8, 2026 • 11 min read

The Planning Fallacy: Why You Always Think Things Will Take Less Time Than They Do

The Sydney Opera House was projected to take four years and cost $7 million. It took fourteen years and cost $102 million. This isn't a story about one unusually bad project — it's a demonstration of a bias that affects nearly every plan you've ever made, including the one you're making today.

Daniel Kahneman and Amos Tversky named this the planning fallacy: the tendency to underestimate the time, cost, and risk of future actions while simultaneously overestimating their benefits. What makes it distinct from ordinary optimism is that it persists even when you have direct, personal evidence that it's wrong. Ask anyone who has ever renovated a kitchen, written a thesis, or shipped a piece of software how their actual timeline compared to their estimate, and most will tell you the same thing: it took longer than planned, again, despite knowing from prior experience that it always does.

Why Knowing About the Bias Doesn't Fix It

The most counterintuitive finding in the planning fallacy research is that awareness alone provides almost no protection. In one classic study by Roger Buehler and colleagues, students estimating how long their senior thesis would take were also asked to estimate how long it would take "if everything went as poorly as it possibly could." Their worst-case estimates were still, on average, close to their actual completion times — meaning the students had accurate information available to them, but their default planning estimate ignored it in favor of an optimistic best-case scenario.

This tells us the planning fallacy isn't primarily an information problem. It's a perspective problem. When you plan your own project, you naturally adopt what Kahneman called the "inside view" — you focus on the specific details of this particular case, the plan as you currently envision it, and the ways you intend for it to go right. What gets left out, almost entirely, is the base rate: how long similar projects, undertaken by similarly well-intentioned people, have actually taken in the past.

The Inside View vs. the Outside View

The correction Kahneman proposed is what he called the "outside view," now more commonly known as reference-class forecasting. Instead of asking "how long will this specific project take, given its specific plan," you ask "how long have projects like this one, in general, actually taken." The outside view deliberately ignores the specific, seductive details of your current plan — the ones that make you feel confident this time will be different — in favor of the track record of the category your project belongs to.

This is uncomfortable, because the inside view feels more informed. You know things about your specific project that the outside view seems to ignore. But this is precisely the trap: those specific details are exactly what every previous, similarly confident planner also had, and their projects still ran over. The specific details you're using to justify an optimistic estimate are rarely the reason projects run long — the reasons are usually generic ones (unexpected complications, scope creep, competing priorities, underestimated coordination costs) that apply regardless of the specific plan.

"When forecasting the outcomes of risky projects, executives too easily fall victim to the planning fallacy. In its grip, they make decisions based on delusional optimism rather than on a rational weighting of gains, losses, and probabilities." — Daniel Kahneman

Why We're Especially Bad at This With Our Own Goals

Interestingly, people are noticeably better at predicting other people's timelines than their own. The planning fallacy is strongly tied to a form of motivated reasoning: your own plan feels different because you can see, in vivid detail, the version of events where everything proceeds as intended. That vividness — not any actual difference in the underlying odds — is what drives the underestimate. This connects to the broader pattern covered in our piece on decision fatigue, where the mental resources needed for accurate, effortful forecasting are often unavailable, so the mind defaults to the easier, more optimistic story.

Practical Corrections

1. Build a Reference Class Before You Estimate

Before setting a timeline, find three to five past examples of similar work — your own past projects, or others' — and use their actual completion times as your starting anchor. Adjust only modestly from there, and be suspicious of any adjustment that makes your project the exception to the pattern.

2. Use Mental Contrasting Instead of Pure Visualization

Purely imagining success tends to feed the optimistic inside view. Mental contrasting — deliberately picturing the desired outcome and then the specific realistic obstacles standing between you and it — produces more accurate, actionable plans than optimism alone, because it forces the obstacles into view instead of leaving them implicit.

3. Add a Buffer Proportional to Project Length

Research on software and construction projects suggests that longer, more complex projects don't just run late — they run late by a larger proportional margin, because complexity and coordination costs compound. A rough, well-supported heuristic is to add 25–50% to your inside-view estimate for a moderately complex project, and more for genuinely novel undertakings with no close precedent.

4. Set Goals With Explicit, Written Success Criteria

Vague goals leave more room for the optimistic inside view to fill in the gaps. Our article on the science of goal setting covers why specific, measurable targets consistently outperform vague ones — the same specificity that improves follow-through also constrains unrealistic time estimates.

5. Build Feedback Loops That Catch Slippage Early

Because the planning fallacy compounds silently — each small delay feels individually reasonable — feedback loops that regularly compare actual progress against the original plan catch the drift while there's still time to adjust, rather than discovering the full scale of the miss only at the deadline.

Building the Habit of Outside-View Thinking

The planning fallacy isn't a failure of intelligence or effort — it affects experienced project managers and first-time planners alike, because it's built into how vividly we can imagine our own intended path versus how abstractly we consider the historical record. The fix isn't trying harder to be realistic; it's deliberately consulting the outside view before the inside view gets to set your expectations. For more frameworks on setting realistic, well-structured goals, see our resources page.

Key Takeaways