Why Tasks Take Longer Than Expected, and How to Make Better Estimates
Separate effort from waiting, find the hidden steps and scope changes, and use past work to make estimates you can keep.
“This should take two hours” becomes a two-day delay. The next estimate gets a bigger buffer, but the same thing happens again.
Before adding more padding, find out what the estimate missed.
A task can run late because the hands-on work took longer, because the task grew, or because it spent time waiting. These are not the same problem. Better estimates begin by separating them.
Measure effort and elapsed time separately
Effort is the time spent actively doing the work. Elapsed time is the period from the agreed start to the finish, including waits and gaps.
Suppose a flyer needs two hours of design, 30 minutes of review, and 30 minutes of changes. That is three hours of active work. If the reviewer is unavailable until Thursday, a Tuesday start does not make Tuesday delivery realistic.
Record both figures for a few recent tasks. A timer can help with effort. Submission, review, and completion dates help explain elapsed time.
Do not log waiting as if somebody was actively working. You need an honest picture of where the delay happened.
Open the task and list its hidden steps
“Write a case study” may include finding a customer, arranging an interview, checking quotes, drafting, getting customer approval, adding design, and publishing.
If the estimate included only drafting, it was not an estimate for the whole task.
- 1Find a customer willing to take partCustomer1h
- 2Arrange the interviewCustomer30m
- 3Check the quotesCustomer45m
- 4Draft the case study2h
- 5Get customer approvalCustomer30m
- 6Add designDesigner1h 30m
- 7Publish30m
Ask the person doing the work to walk through it. Include preparation, access, review, corrections, and delivery. Note which steps depend on another person.
You do not need a detailed plan for every small task. Break down work when it is unfamiliar, has several handoffs, or keeps exceeding estimates.
Diagnose the overrun before changing the estimate
Pick what happened to see what to change next time.
Next time it’s in the estimate from the start, not discovered halfway through.
A large buffer cannot fix all of these. If approval is the issue, the best improvement may be a booked review slot, not a slower-looking author estimate.
A two-hour landing-page update
In this fictional example, a marketer estimates two hours to update a landing page. The work ends up taking five active hours across three days.
The active time adds to five hours. There was also a one-day wait for offer approval.
The lesson is not “multiply every estimate by 2.5.” The next comparable task should include the missing preparation and checks. Offer approval should happen before the delivery date is promised. A simpler copy-only edit would still need a different estimate.
Use a small set of comparable past tasks
Find a few completed items with a similar scope. Look at the range, not only the quickest example. Ask what made the slower one different.
If comparable tasks took three, four, and six hours, promising two hours needs a specific reason. If the six-hour task included a new requirement, separate that change from the normal work.
Use plain-language confidence: “About four hours if the source material is complete; closer to a day if we need to gather it.” This helps the requester see what the estimate depends on.
For highly uncertain work, time-box a first step. “Spend one hour checking the integration and report what is needed” is a more honest promise than guessing the full build before inspecting it.
Agree what happens when the scope changes
Use a short change note:
This is not bureaucracy. It prevents an old estimate from being used to judge a different piece of work.
Review estimates without making them a contest
If people are rewarded for small estimates, they may hide uncertainty. If every overrun leads to blame, they may add large buffers to protect themselves.
Ask what was learned. Keep assumptions visible. Compare similar tasks only, and do not use hours alone to rank employees. A more experienced person may handle harder work that is not obvious from the title.
M-Tracker can keep recorded time against tasks, giving you a record to review instead of relying only on memory. Add the reason for a delay to your task notes or review process. The timer shows effort; it does not explain the cause on its own.
Get started for freeNo credit card required. No employee surveillance.
Common estimating questions
How much buffer should we add?
There is no universal percentage. Use the uncertainty and history of comparable work. Name what the allowance is for so it can improve as you learn.
Should every task have an hourly estimate?
No. Use estimates where they help schedule, price, or choose work. A rough size may be enough for small tasks. Complex work may need ranges and checkpoints.
When should someone flag an overrun?
As soon as new information threatens the agreed delivery, while there is still time to change scope or get help. Waiting until the deadline removes those options.
Pick one late task this week and separate the doing from the waiting. That distinction often reveals a more useful fix than “try to work faster.”
Work you can trust, without redoing it.
Your team gets feedback before work reaches you, or your client.
Copyright © 2020 – 2026 M-Tracker. All Rights Reserved. Privacy Policy