Beat the Planning Fallacy
You've done this task a hundred times and you still guess it'll be quick. That's the planning fallacy, and you don't fix it by trying harder, you fix it with data.

You said the report would take an hour. Four hours later you're still in it, the day is gone, and everything you planned after it has quietly collapsed. The strange part is that this has happened before, many times, with this exact task, and you still guessed an hour.
The planning fallacy is the well-documented tendency to underestimate how long something will take, even when you have direct experience of it taking longer. It was named by Kahneman and Tversky in the 1970s, and it holds up remarkably well: people are optimistic about their own projects almost regardless of how often reality has corrected them.
Why your estimates are always wrong
When you estimate, you don't consult your history. You imagine the task running smoothly, start to finish, with nothing going wrong. So the number you produce is the best-case scenario, and the best case almost never happens.
A few specific things get left out:
- The setup and the packing away. Finding the file, opening things, tidying afterwards.
- The interruptions. Messages, questions, the small emergency that always arrives.
- The last ten per cent. Formatting, checking, sending. This routinely takes as long as the middle.
- The transitions. Getting from the previous thing to this one, which is never instant.
Memory is also unhelpful. It compresses. You remember having written the thing, not the two hours of not-quite-writing that came first.
If your internal clock is unreliable to begin with, all of this gets louder. Time blindness means the estimate isn't just optimistic, it's often untethered from any real reference, and half an hour and two hours can feel like roughly the same size of thing.
Fix one: ask what happened last time
The most effective correction is also the least intuitive: stop reasoning about the task at all and look at the record instead.
Instead of "how long should this take?", ask "how long did it take the last three times?". Researchers call this taking the outside view, and it beats careful reasoning about the specific case almost every time, because your last three attempts already include all the friction you're about to forget.
This works best if you have anything at all written down, which leads directly to the next fix.
Fix two: measure for one week
For one week, note the start and stop time of tasks you do regularly. That's it, no system.
After a week you'll have something more valuable than any technique: actual numbers for your own recurring work. Most people find the same pattern, which is that the small tasks they dread are faster than they feared, and the medium tasks they wave off are two to three times longer than they assumed.
A good side effect is that timing a task makes you see it, which alone tends to make you more realistic. Timeboxing gets much more accurate once you have real numbers behind the box.
Fix three: estimate, then multiply
Until you have data, use a blunt instrument: make your honest estimate, then multiply it. Somewhere between 1.5 and 2 is right for most people, and if you have ADHD, start at 2.
This feels like cheating, and it isn't. It's an adjustment for a bias you know you have, the same way you'd adjust a scale you know reads light. If the multiplied number makes the plan look impossible, that's not the multiplier being wrong. That's the plan being impossible, discovered on Monday rather than on Thursday night.
Fix four: estimate the whole chain, not the interesting bit
"Going to the dentist" is not thirty minutes in a chair. It's getting ready, travelling, waiting, the appointment, travelling back, and the twenty minutes afterwards when you're not going to do anything demanding.
When you estimate, walk through the chain from where you're sitting now to being genuinely finished. Breaking the task into steps helps here, as long as you include the boring connective steps and not just the interesting core. Listing only the exciting parts is how a two-hour job gets planned as forty minutes.
Then protect the day around it
Even good estimates go wrong, so the day needs to absorb it. Schedule roughly two thirds of your available time rather than all of it, and leave real gaps between blocks. That's what buffer time is for, and it's the difference between one task overrunning and an entire afternoon collapsing.
When the deadline can't move
Sometimes you discover, honestly and too late, that the work doesn't fit. When that happens, the choice is scope or quality, and it's better made deliberately than at 2am by accident.
Decide what the minimum acceptable version is and aim at that. Cut the polish, the extra section, the nice-to-have. A finished, plain version delivered on time beats an ambitious one that arrives late and costs you a night, and it's a decision you can make calmly on day one, once your estimate is honest.
Read more
Frequently asked questions
What is the planning fallacy?
The planning fallacy is the tendency to underestimate how long a task will take, even when you have experience of it taking longer. It was described by Kahneman and Tversky and it's remarkably persistent: when we estimate, we imagine the task going perfectly, so we produce a best-case number rather than a realistic one.
Why do I always underestimate how long things take?
Because you estimate by imagining the task, not by remembering it. Imagining leaves out setup, interruptions, transitions and the fiddly last ten per cent, and memory compresses past attempts into a shorter version than they were. If your sense of time is unreliable to start with, the gap between the estimate and reality gets wider.
How do I make better time estimates?
Look at how long the same task took the last few times instead of reasoning about this one, and note start and stop times for a week so you have real numbers. Until then, make your honest estimate and multiply it by 1.5 to 2, and always estimate the whole chain, including travel, setup and finishing off, rather than just the interesting part.
Does multiplying my estimate mean I'm being lazy?
No, it's a correction for a known bias, like adjusting a scale that reads light. If the multiplied estimate makes the plan look impossible, the multiplier isn't wrong, the plan is, and it's far better to find that out at the start than at midnight the day before.


