There is a phenomenon so consistent across projects of every type and scale that researchers gave it a name in the 1970s. Daniel Kahneman and Amos Tversky called it the planning fallacy. It describes the near-universal tendency of people to underestimate how long a task will take, how much it will cost, and how many things will go wrong along the way — even when they have direct experience of similar tasks taking longer and costing more than planned.
The planning fallacy is not a character flaw. It is a cognitive pattern. And understanding it is the first step toward building a timeline that has a realistic chance of being accurate.
Why It Happens
When you estimate how long something will take, your brain naturally constructs a best-case scenario. You imagine the task proceeding without interruption, without unexpected complications, without the ordinary friction of real-world execution. You imagine yourself working at peak focus and efficiency. You imagine your suppliers, partners, and dependencies behaving exactly as expected.
None of those assumptions are wrong in isolation. Any one of them might be true. The problem is that a project is not one task. It is dozens of interdependent tasks, each with its own best-case scenario, and the probability that every single one of them proceeds without complication is effectively zero.
The delays compound. A supplier who is two weeks late pushes the next milestone. A regulatory process that takes six weeks instead of four pushes everything behind it. A key person who is unavailable for ten days during a critical phase creates a gap that takes three weeks to recover from. None of these are disasters. Together they are the difference between a six-month project and a nine-month one.
The One Adjustment That Changes Everything
There is a simple technique that experienced project managers use to counteract the planning fallacy. It is called reference class forecasting, though the name is less important than the practice.
Instead of estimating how long your project will take based on how you imagine it unfolding, look at how long similar projects actually took for other people in similar circumstances. Not the planned duration. The actual duration.
Talk to people who have done something comparable. Read post-mortems and case studies. Ask your suppliers how long their part of the process typically takes when they are working with first-time clients, not how long it takes in the best case.
Then take your bottom-up estimate, the one your brain naturally produces, and add a buffer that reflects what the reference class data is telling you. For most small business projects, that buffer is between thirty and fifty percent of the original estimate.
A project you think will take six months probably takes eight to nine. Plan for nine. If it takes seven, you are ahead. If it takes nine, you are on schedule. If it takes eleven, you have one buffer month left rather than being two months into crisis territory.
The timeline that feels pessimistic at the planning stage is almost always the one that feels accurate at the execution stage.
Build the honest one first.