Decision-Making

Estimating How Long a Task Will Take

Practical ways to estimate task duration: use past tasks as a baseline, break work into parts, include hidden steps, and track the gap between guess and result.

On this page
  1. Why bother estimating
  2. Start with what you have done before
  3. Break the work into parts
  4. Include the hidden work
  5. Use a range instead of a single number
  6. Allow for how you work
  7. Track and adjust
  8. When the estimate matters to someone else

Why bother estimating

An estimate is a decision about time. It decides what fits in your day, what you can promise someone else, and whether a task is worth doing at all. A poor estimate does not just make you late; it leads to overcommitted days, rushed work and apologies. A reasonable one makes planning calmer.

The goal is not precision. Few tasks can be predicted to the minute. The goal is an estimate that is usually close enough to plan around, and honest about its uncertainty.

Start with what you have done before

The most reliable input you have is your own history. Instead of asking “How long do I feel this will take?”, ask “How long did the last similar tasks take?”

  1. Think of two or three comparable tasks you finished recently.
  2. Recall, or check from your calendar or notes, how long each really took, including interruptions.
  3. Use their range as your starting estimate.

If you wrote a similar report three times and it took between three and five hours, a guess of one hour is probably wishful. Using the past as an anchor works partly because it corrects the optimism described in the planning fallacy.

If you have no comparable task, say so. Estimates for unfamiliar work deserve a wider range and more caution.

Break the work into parts

Large tasks are hard to judge as a whole, but small pieces are easier. Splitting a job into steps has two benefits: each guess is more accurate, and the list reveals steps you would have forgotten.

For example, “prepare a presentation” might become:

  • gather the source material
  • decide on the main points
  • draft the slides
  • add visuals
  • rehearse once
  • revise after feedback

Estimate each step on its own, then add them up. A simple, checkable illustration: if the six steps come to 30, 45, 90, 45, 20 and 30 minutes, the total is 260 minutes, or 4 hours and 20 minutes. Compare that with your first gut feeling of “about two hours.” The gap is a sign your first guess left something out.

This is the same idea as project breakdown, applied to measuring rather than starting.

Include the hidden work

Many overruns come from the time around the task rather than the task itself. Consider adding time for:

  • setup and finding what you need
  • waiting for answers or approvals
  • switching in and out of other work
  • checking and fixing your own mistakes
  • communicating the result

A quick way to cover these is to add a line item called “extras” to your breakdown, rather than hoping they will not occur.

Use a range instead of a single number

A single figure suggests more certainty than you have. Try giving yourself two numbers: a realistic best case and a realistic worst case. “Two to four hours” is more honest than “three hours,” and it tells you how much slack to leave.

A common rule of thumb is to plan for the upper half of your range when the deadline matters, and the lower half when it does not. Neither is a rule you must follow; they simply prompt a deliberate choice.

Allow for how you work

Time estimates that ignore your own pattern tend to fail. A few things to consider:

  • Your usable hours. Focused work rarely fills a whole day. Meetings, messages and breaks take their share, so a four-hour task may not fit into one working morning, and a realistic workday schedule reflects that.
  • Your energy. Complex work is often easier at certain times of day for certain people. Fit the task to a stretch when you tend to do it well.
  • Working in blocks. If you use a method like the Pomodoro technique, you can estimate in blocks of focused time rather than clock hours.

Track and adjust

Estimating is a skill that improves with feedback, and the feedback is simple to collect. For a couple of weeks, write down your estimate before starting a task and the actual time afterward. Do not try to be perfect; a notebook page or spreadsheet is enough.

After 10 or 15 tasks, look for patterns:

  • Are you usually short by about the same proportion? Then apply a multiplier next time.
  • Are certain kinds of tasks (writing, anything involving other people, anything with new tools) consistently longer?
  • Are some tasks reliably quicker than you guess? Notice those too, since estimating well works in both directions.

Once you have totals, putting them into your weekly calendar planning shows quickly whether everything fits.

Over time, a consistent multiplier or a standard buffer takes the guesswork out of the process.

When the estimate matters to someone else

If you are giving a number to a colleague, client or family member, share the range and the assumptions behind it: “If I get the files by Tuesday, I expect to finish between Thursday and Friday.” This sets expectations honestly and makes it easier to update the number if something changes. Policies about commitments differ between workplaces, so follow your own team’s norms.

Updating an estimate when you learn something new is not a failure. It is the point of having one.

The complete guide to decision-making

A Simple Process for Making Everyday Decisions
Read the guide

Keep exploring

Guides from other topics

All topics →