You know that documentation project you've been meaning to start? The one you told yourself would take "just a couple of hours" last month?
There's a name for why it still isn't done. It's called the planning fallacy, and 30 years of research shows it affects virtually everyone — even people who know about it.
The Study That Started It All
In 1994, researchers Buehler, Griffin, and Ross ran five studies on how people estimate task completion times. The results were stark.
They asked 37 senior psychology students to predict when they'd finish their thesis. Average prediction: 33.9 days. Average actual completion: 55.5 days. That's 64% longer than predicted. Only about 30% finished on time.
But the probability calibration study was even more revealing. Students gave three estimates for when they'd finish:
- At their "50% certain" deadline: only 13% had actually finished
- At their "75% certain" deadline: only 19% had finished
- At their "99% certain" deadline: only 45% had finished
Read that last one again. When people said they were ninety-nine percent certain they'd finish by a specific date, fewer than half actually did.
It's Not Just Students
If this were only an academic curiosity about undergrads, it wouldn't matter. But the same pattern appears everywhere.
Megaprojects (Flyvbjerg, thousands of projects across 104 countries):
- 9 out of 10 megaprojects have cost overruns
- ICT projects: 1 in 6 become outliers with 200% cost overruns
- Dam projects: 96% cost overruns, average 45% schedule delays
- This pattern has held for 70+ years
Software projects (Standish CHAOS 2020):
- Only 31% of software projects succeed on time and budget
- 50% are "challenged" (late, over budget, or feature-incomplete)
- 19% fail outright
- The original 1994 report found 52.7% of projects ran 189% over budget
Douglas Hofstadter captured the problem perfectly in 1979: "It always takes longer than you expect, even when you take into account Hofstadter's Law."
Why Knowing About It Doesn't Fix It
Here's what makes the planning fallacy particularly insidious: awareness alone doesn't help.
Buehler et al. found that people readily acknowledged their past predictions had been optimistic. They could see others' predictions were optimistic. But they insisted their current prediction was realistic.
Kahneman and Tversky explained why. When we estimate a project, we default to the "inside view" — we imagine the specific steps, picture them going well, and construct a narrative of success. What we should use is the "outside view" — looking at how similar projects have actually gone in the past.
Every new project feels unique and controllable. This time we have a clear plan. This time we know the pitfalls. This time it's different.
It's not different.
Your Nervous System Makes It Worse
Sharot et al. (2007, Nature) found that optimistic forecasting is driven by the amygdala and rostral anterior cingulate cortex. When we imagine positive future outcomes, these regions activate more strongly.
This means optimism bias isn't a character flaw — it's a neural default.
But here's the important connection: chronic stress and elevated cortisol impair prefrontal cortex function — the very brain region responsible for realistic planning. Under stress, we rely more on fast, heuristic thinking (System 1) instead of careful analysis (System 2).
Low HRV = compromised prefrontal function = more susceptible to the planning fallacy.
The burned-out entrepreneur is the person most likely to underestimate how long documentation will take. And they're also the person who most needs that documentation to reduce their workload.
This creates a vicious cycle: overwhelm → bad time estimates → more overwhelm.
What Actually Reduces the Planning Fallacy
Since awareness doesn't work, what does?
1. Reference class forecasting (endorsed by the American Planning Association in 2005): Instead of imagining your specific project, look at how similar projects have actually gone. Use the distribution of real outcomes, not imagined plans.
2. Breaking projects into small pieces: Shorter estimation horizons produce smaller absolute errors. This is partly why agile software projects are 28% more likely to finish on time compared to waterfall.
3. Removing the estimation entirely: If the structure already exists — templates, frameworks, pre-built systems — there's nothing to estimate. You're filling in blanks, not planning a project.
The Documentation Procrastination Loop
Here's how the planning fallacy specifically traps customer documentation:
- "I'll document this next week" — the inside view says it'll take 2 hours
- Next week arrives — other urgent tasks fill the time
- Documentation pushed again — "definitely next month"
- Months pass — documentation debt compounds
- Support costs rise — but the cause isn't recognized
- "We should really document this" — cycle restarts from step 1
The planning fallacy makes this cycle feel like reasonable decision-making each time. You're not procrastinating — you're realistically assessing that you'll have more time later.
Except you won't. Buehler, Flyvbjerg, and Standish have 30 years of data confirming that.
Breaking the Loop
The research points to one clear strategy: don't plan documentation as a project. The moment it becomes a "project" with estimated timelines, the planning fallacy activates.
Instead:
- Start with 3 questions your customers actually ask (not a documentation plan)
- Use existing templates (nothing to estimate)
- Ship imperfect answers today (not a perfect FAQ next quarter)
The Buehler data shows that even at 99% certainty, people are wrong more than half the time. The only way to beat those odds is to make the task so small that estimation becomes irrelevant.
Sources
- Buehler, R., Griffin, D., & Ross, M. (1994). Exploring the "planning fallacy": Why people underestimate their task completion times. Journal of Personality and Social Psychology, 67(3), 366-381.
- Kahneman, D., & Tversky, A. (1979). Intuitive prediction: Biases and corrective procedures. TIMS Studies in Management Science, 12, 313-327.
- Flyvbjerg, B. (2006). From Nobel Prize to project management: Getting risks right. Project Management Journal, 37(3), 5-15.
- Standish Group (2020). CHAOS Report 2020.
- Hofstadter, D. (1979). Gödel, Escher, Bach: An Eternal Golden Braid. Basic Books.
- Sharot, T., et al. (2007). Neural mechanisms mediating optimism bias. Nature, 450, 102-105.
- Gollwitzer, P. M. (1999). Implementation intentions. American Psychologist, 54(7), 493-503.