“Time is free, but it’s priceless. You can’t own it, but you can use it. You can’t keep it, but you can spend it. Once you’ve lost it you can never get it back.” (Harvey Mackay)
Estimates lie.
Not on purpose. Your brain takes shortcuts, and those shortcuts cost you days, budgets, and trust.
In 25 years at Microsoft, I learned that a schedule is a set of guesses. The question is whether you know which biases are doing the guessing.
Here are the biases that throw off your time and effort estimates, and what to do about the ones that bite hardest.
Why Projects Run Late
You think things will go faster than they do. You underestimate the surprises, the delays, and the handoffs. And once you put a date on the table, you defend it instead of testing it.
Then you miss deadlines, blow budgets, and your team stops believing the plan.
Time and Resource Estimation Biases
- Anchoring Bias: The tendency to rely too heavily on the first piece of information you get. Example: The first number you hear becomes the number you plan around.
- Bandwagon Effect: The tendency to adopt beliefs or behaviors because many other people have. Example: Everyone says it’s a two-week job, so you say it too.
- Belief Bias: The tendency to let what you already believe override your judgment of the facts in front of you. Example: You say “We always pull it off” instead of looking at this project.
- Clustering Illusion: The tendency to see patterns in random events. Example: You see a couple of fast sprints and call it a trend.
- Confirmation Bias: The tendency to look for and interpret information in a way that confirms what you already believe. Example: You notice the signs you’re on track and miss the ones you’re not.
- Endowment Effect: The tendency to value something more just because it’s yours. Example: Your plan feels more valuable because it’s yours.
- Focusing Effect: The tendency to put too much weight on one part of a situation and overlook the rest. Example: You plan the big piece and forget the dozen small ones.
- Hindsight Bias: The tendency to believe, after the fact, that you could have predicted what happened. Example: After the slip, you say “we knew it would be late,” so nobody learns.
- Illusory Superiority: The tendency to overestimate your own abilities or performance compared to others. Example: You think your team is faster than average. So does everyone.
- Information Bias: The belief that more information always leads to better decisions. Example: You gather more data and feel like you’re making progress, even when it doesn’t change the estimate.
- Normalcy Bias: The tendency to underestimate the chance or severity of a threat because it hasn’t happened before. Example: You assume nothing big will go wrong because nothing big went wrong last time.
- Omission Bias: The tendency to judge harm from acting as worse than equal harm from not acting. Example: You feel safer keeping quiet about a risk than raising it.
- Optimism Bias: The tendency to overestimate the odds of good outcomes and underestimate the odds of bad ones. Example: You plan for the best case and call it the expected case.
- Outcome Bias: The tendency to judge a decision by how it turned out instead of how good it was when you made it. Example: You landed the last project on time, so you think the estimate was good. Maybe you got lucky.
- Planning Fallacy: The tendency to underestimate how long a task will take or what it will cost. Example: You know the last project ran late, but you think this one won’t.
- Pro-Innovation Bias: The tendency to overrate the value of new technology or ideas and overlook their downsides. Example: You think the new tool will save time, so you skip the cost of adopting it.
- Pseudocertainty Effect: The tendency to treat an uncertain outcome as if it were certain. Example: You treat a likely outcome as a sure thing.
- Sunk Cost Fallacy: The tendency to keep investing in a project because of what you’ve already put in, even when it no longer makes sense. Example: You keep funding a late project because of what it already cost.
- Zero-Risk Bias: The tendency to prefer wiping out one risk completely over reducing overall risk more. Example: You remove one small risk completely and leave the big one alone.
The Planning Fallacy
You know the last project ran late. You still think this one won’t.
That’s the planning fallacy. Daniel Kahneman and Amos Tversky named it, and it’s the bias behind most late projects.
The fix is what Kahneman calls the outside view:
- Look at how long the last few similar projects actually took.
- Start from that number, not your gut.
- Add a buffer, and say out loud what it’s for.
Anchoring
Someone in the meeting says, “This should take about a month.”
Now everyone in the room estimates close to that month. Even when the work clearly says three.
The fix: have each person estimate on their own, before anyone shares a number. Then compare.
Optimism and Normalcy
Optimism tells you it’ll go smoothly. Normalcy tells you nothing unusual will happen.
Listen to both, and you make plans with no room for real life.
The fix: ask, “What are the three things most likely to go wrong?” Then put time against them.
Focusing Effect
You estimate the build and forget the reviews, the testing, the approvals, and the launch.
The fix: list every step from start to “done done,” not just the interesting part.
Sunk Cost
The project is late and over budget. You keep going because you’ve already spent so much.
The fix: ask, “If we were starting today, would we fund this?” If the answer is no, stop. See Investment and Commitment Biases for more on sunk cost.
How To Estimate Better
- Use your history, not your hopes.
- Estimate alone, then compare.
- Break the work down until each piece is small enough to see.
- Name the risks and give them time.
- Check the estimate at every milestone and say when it changes.
That’s one reason I like to work in small cycles. In Getting Results the Agile Way, I plan the week with 3 Wins instead of a giant list. You can estimate small batches more easily, and you find out fast when you’re wrong.
Key Takeaways
- The planning fallacy and anchoring do the most damage. Watch for them first.
- Your past projects predict your next one better than your gut does.
- A buffer isn’t padding. It’s you being honest about what you don’t know.
You’ll never make a perfect estimate. You can make one that’s a lot less wrong.

Social Influence and Conformity Biases