Finance & investing
Investors and entrepreneurs systematically underestimate how long it will take for a new venture to become profitable or for a product to reach market, leading to cash-flow crises when runway assumptions prove too optimistic.
Planning Fallacy
aka Optimistic Time Prediction Bias · Inside View Bias
Underestimating the time, cost, and risk of future tasks, even when past experience shows they always take longer.
WHAT IT IS
The glitch, explained plainly.
Imagine every time you pack for a trip, you think 'I'll be done in 20 minutes,' but it always takes an hour because you forget about finding your charger, ironing that shirt, and deciding what shoes to bring. Even though this happens every single time, the next trip you still think, 'This time it'll only be 20 minutes.' That's the Planning Fallacy — your brain keeps imagining the perfect version of the future instead of remembering what actually happened before.
The Planning Fallacy describes a systematic pattern in which individuals and organizations generate overly optimistic predictions about how quickly and cheaply they will complete future tasks, while simultaneously holding accurate knowledge that similar past tasks took much longer. A defining feature is the disconnect between general beliefs about one's track record (which are often realistic) and specific predictions for the current task (which are almost always too optimistic). This bias is driven by a reliance on the 'inside view' — mentally simulating the specific steps of a project under ideal conditions — rather than the 'outside view' of consulting base rates from comparable past projects. The fallacy applies not only to time estimates but also to cost projections, risk assessments, and benefit forecasts, and it scales from trivial personal chores to billion-dollar infrastructure projects.
SOUND FAMILIAR?
Where it shows up.
- 01 A software developer tells her manager that the new feature will take two weeks to build. She has built similar features before and they consistently took five to six weeks, but she focuses on the clean approach she's planned for this one and how she now knows the codebase better.
- 02 A city council approves a new light-rail project with a timeline of four years and a budget of $1.2 billion, relying on the project team's detailed construction schedule. No one on the council checks how long comparable transit projects in other cities actually took.
- 03 A graduate student acknowledges that his last three papers each took twice as long as predicted, yet insists his current paper will be different because he's already done the literature review and has a clear thesis. He sets a three-week deadline.
- 04 A startup founder creates a product roadmap showing a full platform launch in nine months. When her CTO points out that their last two releases each slipped by four months, she explains that those delays were due to specific technical issues that won't recur, and that this roadmap accounts for all known risks.
- 05 An experienced project manager adds a 15% buffer to his schedule, believing he has already corrected for optimism. When asked how past projects with similar buffers performed, he realizes they still ran 30-40% over, but he maintains that this project's detailed Gantt chart makes it uniquely well-planned.
IN DIFFERENT DOMAINS
Where it shows up at work.
The same glitch looks different depending on the terrain. Finance, medicine, a relationship, a team — same mechanism, different costume.
Medicine & diagnosis
Hospital administrators underestimate the time and budget required for implementing new electronic health record systems, leading to extended transition periods during which clinical workflows are disrupted and staff burnout increases.
Education & grading
Students routinely underestimate the time required to complete papers, theses, and study plans, despite consistent past experience of missing self-imposed deadlines, leading to last-minute cramming and lower-quality work.
Relationships
People underestimate how long it will take to plan events like weddings, moves, or home remodeling projects with a partner, creating stress when shared timelines collapse and each person blames the other for poor planning.
Tech & product
Product teams routinely underestimate development sprints and launch timelines, leading to feature cuts, quality compromises, and a culture of perpetual 'crunch time' that damages team morale and product reliability.
Workplace & hiring
Managers set aggressive quarterly goals based on best-case productivity assumptions, then interpret inevitable delays as employee underperformance rather than flawed forecasting, creating a cycle of blame and burnout.
Politics Media
Government infrastructure projects are approved with optimistic timelines and budgets that secure political support, only to face massive cost overruns and delays once construction reveals unforeseen complexities, eroding public trust.
HOW TO SPOT IT
Ask yourself…
- Am I basing this estimate on how I imagine the work going, or on how long similar work has actually taken me before?
- Would an uninvolved outsider who knows my track record agree with this timeline?
- Does my 'realistic' estimate look suspiciously similar to my best-case scenario?
HOW TO DEFEND AGAINST IT
The playbook.
- Use reference class forecasting: identify 3-5 similar past projects and use their actual completion times as your baseline estimate instead of building from scratch.
- Apply the 'outside view' by asking an experienced person who is not involved in the project to estimate how long it will take.
- Multiply your initial intuitive estimate by 1.5 to 2x as a rough correction factor before committing to any timeline.
- Conduct a premortem: before starting, imagine the project has failed spectacularly and list all the reasons why, then plan for those scenarios.
- Break the project into sub-tasks and estimate each one individually — the sum is typically longer than the holistic estimate, and more accurate.
FAMOUS CASES
In history.
- The Sydney Opera House was budgeted at AUD 7 million with a 4-year timeline but ultimately cost AUD 102 million and took 14 years to complete.
- The Denver International Airport opened 16 months late with a cost overrun of over $2 billion.
- The Eurofighter Typhoon defense project was delivered 54 months late at a cost of $19 billion instead of the planned $7 billion.
- Boston's Big Dig highway project was completed seven years late and cost $8.08 billion against a $2.8 billion budget.
- The Berlin Brandenburg Airport was planned to open in 2011 but did not begin commercial operations until 2020.
WHERE IT COMES FROM
Academic origin
Daniel Kahneman and Amos Tversky, 1979, introduced in their paper 'Intuitive Prediction: Biases and Corrective Procedures' published in TIMS Studies in Management Science.
Evolutionary origin
In ancestral environments, optimistic action-taking was adaptive. Individuals who confidently planned hunts, migrations, or shelter-building and acted quickly were more likely to acquire resources than those who deliberated endlessly over worst-case scenarios. Overconfidence in one's ability to complete tasks on time encouraged initiative and persistence, traits that conferred survival advantages even when timelines were occasionally wrong.
IN AI SYSTEMS
How the machines inherit it.
AI project timelines are particularly susceptible: teams underestimate data cleaning, model iteration, and deployment challenges. Additionally, AI systems trained on historical project data may inherit systematically optimistic estimates if the training data reflects planned rather than actual durations, perpetuating the bias in automated scheduling and resource allocation tools.
EXPLORE MORE
Related glitches.
LAUNCH PRICE
Train against your blindspots.
50 cards are free to preview. Buyers unlock the rest of the deck plus the interactive training — Spot-the-Bias Quiz unlimited, Swipe Deck with spaced repetition, My Blindspots, Decision Pre-Flight, the Printable Deck + Cheat Sheets, and the Field Guide e-book. $29.50$59.