Why Do We Keep Missing Deadlines?
One thing I’ve learned throughout my career as a project manager is that deadlines are rarely met — and more often than not, it’s because of inaccurate estimates.
Estimation accuracy is influenced by many factors, but in this short lesson we’ll focus on the mental traps involved in estimating, and on some techniques for reducing their impact. I believe that becoming aware of these traps — and of how universal they are, regardless of expertise, culture, or familiarity with the context — makes us a little more compassionate toward the imperfect decisions we all make sometimes. And by applying the techniques we’ll cover, the accuracy of your estimates will improve significantly.
So let’s dive in and meet the little tricksters living in our minds.
Before We Begin: A Quick Exercise
Your best friend’s anniversary is next month, and you’ve decided to organize a surprise party at your place. Your friend loves surprises, and this will be your gift to them. As you start planning, you identify a few things you’ll need to take care of:
Make sure everyone invited shows up (roughly 20 people)
- Make a list of people you want to invite
- Contact everyone and get their confirmation
Get the house ready for the event
- Clean the house and rearrange furniture if needed to fit everyone
- Get some party props for guests to wear
Provide enough food and drinks for everyone
- Hire a catering service and decide on the menu
- Order a birthday cake
- Buy drinks
Find a way to make sure your friend is available for the party — without spoiling the surprise
You have exactly one month. If you were organizing this by yourself, how many days would you give each activity, and in what order would you tackle them? Jot down your estimates — you’ll come back to them at the end of the lesson.
The Three Mental Traps
Before we get into estimation accuracy specifically, let’s look at the types of mental traps we fall into when trying to make rational decisions: heuristics, cognitive biases, and logical fallacies.
Heuristics were first studied by psychologists Daniel Kahneman and Amos Tversky, starting in the 1970s. In simple terms, a heuristic is our tendency to simplify things in order to solve complex problems. We live in a world full of stimuli, constantly needing to make quick decisions, so our brains rely on shortcuts built from past experience. These shortcuts help us decide quickly in similar (not identical) contexts, but in most cases, they’re not actually the best decisions we could make.
This kind of decision-making developed over thousands of years of evolution. Our world used to be dangerous, and the speed of our decisions kept us alive. Even though today’s world holds fewer life-threatening dangers, our brains still lean heavily on these shortcuts, mainly because, once learned, they reduce cognitive load. That’s harmless enough when deciding where to buy bread. It’s far less harmless when we elect a mayor based on how likeable they seem rather than on their actual achievements -> that’s affect heuristics in action.
That’s how heuristics work: faced with a complex problem, our brain quietly substitutes it with a simpler one, solves that instead, and lets us believe we solved the original. And we’re rarely aware it’s happening.
In project management, the clearest example is relying solely on lessons learned from past projects, without accounting for the specific context of the current one. Say a client hires us to build a website. Based on initial discussions and our experience building similar sites, we estimate three months. Yet the estimate turns out inaccurate for any number of reasons: the client is more thorough than others we’ve worked with, an unplanned risk materializes, we need to learn a new technology, and so on.
So why didn’t we plan properly from the start? In a perfect world, we would have. But in today’s fast-changing environment, we often need to make quick decisions and heuristics is our best shot at doing that.
Another mental trap our brains set for us is cognitive bias. If heuristics are about simplifying reality to act faster, a cognitive bias is “the tendency to think in one way when other options are just as good, if not better” (McCraney, 2013, p. 11).
Quick example: notice how, once you start thinking about buying something, you suddenly see it everywhere? That’s confirmation bias in action. We simply pay more attention to information that confirms what we already believe or want.
When our biases get challenged in everyday life, we often turn to logical fallacies — starting with a conclusion already in mind and working backward to justify it. Superstitions, for instance, are born from the post-hoc fallacy: if one event follows another, we assume the first caused the second. If I always leave the house with my right foot first, and something bad happens the one day I use my left foot, I’ll start believing the left foot brought the bad luck, when in reality the two events were never related.
Now that we’ve covered the basics, let’s look at three of these mental traps that most affect the accuracy of our estimates.
A note on accuracy: the goal here is to be accurate, not precise. There are too many variables at play in today’s projects for precision to be realistic. Rather than aiming to deliver a project on the exact date of November 15th, we’ll focus on being able to accurately estimate a time range — say, sometime between October and December. And even when the end date is fixed, we still need accuracy when estimating how long each task will take.
Trap #1: The Planning Fallacy
The number one trap we fall into is the planning fallacy: we tend to underestimate how long a project will take, while overestimating our own ability to execute it. That second part is also known as the overconfidence bias.
You might ask — isn’t this something past experience should fix? Instead of answering directly, let me ask you this: how often, when recalling a difficult or unpleasant experience, have you remembered it more kindly than you actually felt while living through it? That’s the brain’s memory-protection mechanism at work. To help us survive, it tends to soften unpleasant memories or reframe them more optimistically. As psychologist David Gilbert puts it: memory is a representation, not a replica. The more we reflect on a past event, the less accurate our memory of it becomes. That’s why the best practice for documenting lessons learned is to do it as things happen — not at the end of the project.
Still, even when we do have accurate knowledge of how long something takes, we often remain overconfident in our ability to get it done. So the planning fallacy can catch us even when we have relevant, well-documented past experience — and it shows up even more clearly with new projects or tasks we’ve never tackled before. We tend to be far too optimistic. And the further away the actual work is from the moment we make the estimate, the stronger this effect becomes.
So what can we do about it?
Accept that everyone falls prey to the planning fallacy.
Awareness is the first step.
Simplify the project or task.
One reason the planning fallacy shows up is that our minds struggle to reason about combined probabilities. The more activities involved, the harder it is to accurately estimate their combined duration. The more complex the task, the more our brain loses track of the odds that something unexpected will happen. Simplifying tasks is one of the most reliable ways to improve estimate accuracy.
Take time for a risk analysis.
And plan how you’d respond to those risks — especially when the schedule is tight. It’s easy to skip this step when we’re short on time or feeling optimistic, but it’s exactly what helps you account for the unforeseen.
Consider all the factors.
When estimating duration, factor in the effort required, resource availability, and how the task depends on, or is depended on by, other tasks.
Back to our exercise: by now you’ve made a rough estimate for each phase. Let’s zoom into the first activity: inviting guests. At first glance, it looks simple — just send everyone the same message with the date, time, and location, and ask them to confirm. Shouldn’t take more than an hour, right? But break it down further: make the guest list, write the invitation, send it out, and get confirmations. The first two steps are quick and depend only on you. The third is trickier — sending the message itself takes maybe 30 minutes, but getting responses depends on your friends’ schedules, and might take a few days. Some invitations might even turn into ongoing conversations you’ll need to keep up with until the event. Now consider another activity: getting the house ready. Say you live alone, and your place can comfortably fit 20 people. You’ll need to clean it and maybe rearrange the furniture. If you’re naturally tidy, this won’t take long. If not, it might take real effort — though even then, one weekend should be enough. But do you actually have a free weekend? If not, and you’re the only one handling this task, you might need to split it across two weekends. Just like that, a “two-day task” stretches into more than a week.
Use reference class forecasting.
Instead of estimating a task purely from how it “feels,” look at how long similar tasks actually took in the past — yours or someone else’s. This is different from the “lessons learned” heuristic we discussed earlier, which is more about general experience. Here, you’re deliberately using historical data as a corrective anchor: if your last three website redesigns were each scoped at “6 weeks” but all took closer to 10, that gap is information — factor it into your next estimate.
Try three-point estimation.
For each task, estimate three numbers: an optimistic duration (if everything goes right), a most-likely duration, and a pessimistic one (if things go wrong). A simple version of this — the PERT formula — averages them with extra weight on the most-likely value: (optimistic + 4 × most-likely + pessimistic) ÷ 6. This gives you a single number that already accounts for some uncertainty, and the spread between optimistic and pessimistic doubles as your estimated range.
As you can see, there’s a lot to weigh when estimating a task’s duration: breaking it into smaller pieces, accounting for effort, resource availability, dependencies between tasks, and even uncertain events that might come up. Doing this reduces the impact of the planning fallacy and gets you closer to an accurate estimate — even when the deadline itself is fixed. In our example, thinking through the constraints around cleaning the house showed us we needed to start early. This is called reverse engineering: distributing task durations backward from a fixed timebox — in this case, our one-month deadline.
Trap #2: The Dunning-Kruger Effect
The second mental trap is the Dunning-Kruger effect — according to The Decision Lab, an ambiguity-related bias:
“The Dunning-Kruger effect occurs when a person’s lack of knowledge and skills in a certain area cause them to overestimate their own competence. By contrast, this effect also causes those who excel in a given area to think the task is simple for everyone, and underestimate their relative abilities as well.” — thedecisionlab.com
When we know nothing about a subject, most of us have no trouble admitting it. But as we start learning, our confidence grows too — sometimes to the point where we believe we’re experts. Then, as we dig deeper, we realize the “iceberg” is much bigger than what we saw at the surface, and our confidence dips. Eventually, we know enough to properly judge what we actually know: our confidence keeps growing from there, but this time in step with our real competence — never again reaching that early, inflated peak.
The bias behind this effect is illusory superiority. Unlike overconfidence bias, which makes us too confident in our own abilities, illusory superiority makes us believe our abilities are above average. As the researchers who coined the term put it: “the miscalibration of the incompetent stems from an error about the self, whereas the miscalibration of the highly competent stems from an error about others” (Kruger & Dunning, 1999).
So, depending on our level of expertise in a given area, we might overestimate — or underestimate — our abilities, and therefore how long a task will take.
I can’t count how many times this effect has shown up in my own life. I’m passionate about many different subjects, but I also get bored easily — so I rarely stuck with one long enough to become a true expert. Because of that, I was often the one eager to take on new kinds of tasks, confident in my ability to complete them, and, more often than not, too optimistic about how long they’d take. Once I actually got into the work and learned more about it, I’d realize there was far more to it than I’d assumed. What saved me every time was my ability to research quickly and pick things up fast — so I always pulled it off, but only thanks to the extra effort I put into researching, analyzing, and synthesizing information. Eventually I realized that’s actually my superpower. For a long time, my tendency to underestimate task duration was masked by my ability to put in that extra effort and learn quickly. More recently, I’ve started factoring that extra effort directly into my estimates.
Back to our exercise: your confidence in organizing this party by yourself will depend on your knowledge and past experience. If you’ve never done anything like it before — or simply believe you’re not an organizer — you’ll probably ask for help. If you’ve successfully hosted a family dinner or attended a surprise party before, you might feel overconfident and estimate too optimistically: a month can feel like plenty of time, and you might even think you could pull it off in two or three weeks (which, in the end, could prove risky). On the other hand, if you have a bit more experience and are aware of the risks involved, you might swing the other way and over-plan. It’s usually only once you’ve become a genuinely seasoned organizer that you can balance past experience with the needs of the current project and land on a realistic estimate.
Some of us have a natural talent for organizing; others learn it along the way. Through feedback, observation, and practice, we get better at judging our abilities against the average — and our confidence grows accordingly. The real danger of this effect shows up when we have very little information about something and fall straight into overconfidence about our ability to handle it.
What can we do about it?
Start with a self-check.
What do you believe you’re genuinely good at, and where do you tend to struggle? Then look around you: why is this task taking my colleague so long? Am I missing something, or is this simply the kind of task I’d normally be good at?
Ask your colleagues for feedback.
This effect can trick us into assuming that whatever comes easily to us also comes easily to everyone else — when in fact, it might be exactly what makes us valuable.
Track your estimates against actuals.
For every task, jot down what you estimated and what it actually took. Over time, a pattern emerges — maybe you consistently underestimate by 30%, or you overestimate simple tasks but underestimate complex ones. This is the standard technique used in forecasting to gradually calibrate a biased estimator, and it works whether you tend to over- or underestimate.
I believe the Dunning-Kruger effect hits hardest when we work alone and have no reference point — which is often the case for solopreneurs and freelancers delivering a project start to finish on their own. Estimating as part of a team helps mitigate this: it gives newcomers a chance to see what they still need to learn, and gives experts a chance to recognize their own talents.
Trap #3: The Anchoring Effect
Team estimation helps counter the Dunning-Kruger effect — but it can fall prey to another trap: anchoring. Anchoring is our tendency to rely too heavily on the first piece of information we receive when making a decision, which is why it plays such a big role in negotiations.
Think about buying a car: the seller names a price, and even if you walked in with a number in mind, the moment you hear their offer, your negotiation shifts to revolve around their number instead of your original plan.
What does this mean for estimation? If, during team planning, one person shares an estimate out loud first, the rest of the team tends to get anchored to it — asking fewer clarifying questions and simply refining that initial number instead of estimating independently.
The fix: let each team member estimate individually first, and only then bring the estimates together for discussion.
Two well-known techniques are built on exactly this principle:
- The Delphi method (also known as “estimate-talk-estimate”) – Gather anonymous estimates from each team member, discuss the results as a group, and repeat the process until you reach consensus.
- Planning Poker — widely used in software development to estimate the complexity of user stories. Each team member privately selects a card representing their estimate; only once everyone has chosen does the team discuss openly and work toward a shared number.
Both approaches help teams avoid anchoring and land on more accurate estimates, thanks to the range of perspectives brought into the discussion.
Anchoring is not only a team problem, either. It shows up just as often on an individual level — for instance, when a client hands you a deadline first (“I need this in three weeks”) before you’ve had a chance to estimate anything. Without realizing it, you can end up reverse-engineering your estimate to fit that number, instead of estimating the task on its own merits and then negotiating the gap. Worth keeping in mind — even if negotiating deadlines with clients is really a topic for its own lesson.
Now that you know about anchoring — please don’t let my earlier comment about “a few days for friends to confirm” influence your own estimate. I may have experience organizing events, but they’re your friends. You know them better than I do.
Before You Go
We’ve covered our three most common mental traps: heuristics, which help us act quickly in complex situations; cognitive biases, which push us toward certain default patterns of thinking — even when they’re not the best ones; and logical fallacies, which help us justify beliefs we’ve already settled on. We also looked at how the planning fallacy, the Dunning-Kruger effect, and the anchoring effect specifically distort our estimates — and what we can do about each one.
Now it’s your turn: go back to the exercise at the start of this short lesson, revisit your original estimates, and refine them with what you’ve just learned. I’d love to see your before-and-after estimates, feel free to share them in the comments below.