Why Every Task Takes Longer Than You Think (And How to Plan for It)

It was only supposed to take forty minutes. You had a clear idea of the work: open the file, make the changes, send it off. Then the file wouldn't open. You needed a fact from somebody else. One paragraph took three rewrites. You spotted a mistake in something you'd finished yesterday.

At 4:30 you look at the calendar and wonder where the afternoon went. The calendar says you should already be working on the next thing.

There are plenty of articles about making yourself work faster. This one starts with a different possibility: the time estimate may have been wrong before you ever sat down. Here's how to estimate work with more evidence and less wishful thinking, especially when your day contains real people, dependencies and surprises.

A plan is a story. An estimate needs evidence.

When you imagine yourself doing a task, you usually imagine the most coherent version: open the relevant material, think clearly, make progress, finish. The small ordinary frictions are outside the frame. That's one reason the future seems shorter than the past.

Psychologists call this tendency the planning fallacy. In experiments reported by Roger Buehler, Dale Griffin and Michael Ross, participants often predicted completion sooner than their own previous experience suggested. Reminding them to connect past experience to the prediction improved estimates in one study. Read the APA's short definition or the original paper.

That doesn't mean every late task is proof of a psychological bias. A genuine new requirement, illness or another person's delay can change the work. It does mean optimism is not enough evidence to promise a delivery date.

First define what “done” actually includes

“Write the proposal” might mean a rough draft, a reviewed draft, or something ready for a client to approve. Those are three different jobs. The person asking may picture the third while you silently estimate the first.

When a deadline matters, ask a simple question: “Do you need the first version by Thursday, or the approved final version?” People often agree on a date while quietly disagreeing about what happens on it.

Borrow evidence from your actual last three tasks

Don't start with a spreadsheet of every minute of your life. Think of three comparable jobs you recently finished. How long did each really take, including the final proofread and corrections? Did you need a second session? What made one unusually short or long?

If those jobs took 55, 90 and 115 minutes, a new ninety-minute estimate may be more defensible than “probably half an hour”. But three observations are not a statistical guarantee. They're a reality check. A genuinely different task needs different treatment.

The Project Management Institute explains the outside view: compare a planned job with a meaningful group of previous similar jobs rather than trusting only the plan unfolding in your head. This works best when the comparisons are genuinely comparable, not when you lump a ten-minute email together with a month-long redesign.

Keep effort and elapsed time apart

If you spend an hour drafting and then wait two days for approval, that isn't two days of work. But it may still be two days until the deliverable is finished. Confusing the two makes both workload reports and delivery promises misleading.

Use two fields: hands-on effort and elapsed delivery window. A designer might need three hours of focused work and a separate client review that could take several days. Another request might need twenty minutes of work but be blocked by access that no one has granted.

When a dependency is uncertain, name it explicitly: “I can complete my part Thursday, provided the data arrives Wednesday.” That's a commitment with conditions, not an excuse prepared in advance.

The real cost of a task is not always visible in the task title

Tasks often arrive as verbs: fix, write, send, review. But the actual cost includes understanding the request, finding the source material, handling ambiguity, doing the work, checking it, and sometimes explaining what changed.

Imagine you receive “update the presentation”. The slides themselves may take an hour. If you need to work out which product numbers are approved, locate an image with usage rights, check consistency across twenty slides and make another version for a different audience, the original hour doesn't describe the assignment.

Try listing the stages without estimating them yet. Then mark any stage you haven't done before. An unknown step doesn't deserve an invented confident number simply because your calendar has room for it.

Don't apply a magic multiplier to everything

You've probably heard the advice to take your first estimate and double it. That can be comforting in the short term, but it's a poor system. It treats familiar work, uncertain research and waiting for a legal review as the same kind of risk.

Instead ask: What makes this task different from the last one? Is the input ready? Is the work reusable? Is the quality threshold higher? Are there reviewers? Would failure require starting again?

A familiar email built from a reliable template may need little extra allowance. An experiment with an unknown technical cause may not have a credible finish-time estimate at all. For that, offer a capped investigation and a decision point. Ranges aren't a sign of weakness; they're the honest shape of uncertainty.

Use three estimates, but don't pretend they're probabilities

For example: “The first draft should take an afternoon if the brief is complete. A reviewed version may require another session. If the source figures haven't been approved, I can't give a reliable publication date yet.” That sounds less impressive than “Done by 3”, and it's much more useful.

When your task list is longer than your day

Once you have more realistic estimates, there's another discomfort: the list may simply not fit. That isn't a cue to shave ten minutes off each task until the numbers look cheerful. It's information about capacity.

Count the time already committed to meetings, support coverage, travel and necessary breaks. Then identify the work that truly needs completion today. Ask what can move, what can shrink in scope, what needs another person, and what must be escalated because the deadline cannot change.

If you're in a role with unpredictable demand, avoid scheduling the whole day as though nothing will interrupt it. The related guide on returning after interruptions helps with the mental side; this guide is about making those interruptions visible in the capacity calculation.

A worked example: the six-hour assignment that became ten

Illustrative example only. Sam is preparing a research presentation. Last term, a similar one needed about nine hours across planning, finding sources, building slides and rehearsing. This term Sam writes “six hours” because the topic feels familiar.

After checking the brief, Sam discovers the presentation requires a comparison of two studies, a reference list and a live question-and-answer section. The first estimate included slides, but not sourcing, critical comparison or practice.

The revised plan doesn't automatically multiply six by 1.5. It separates research, structure, slides, evidence checks and rehearsal, places them into available sessions, and leaves the deadline visible. The plan may still change, but now it's possible to see which stage changed rather than concluding that Sam was slow.

A more humane way to communicate a revised date

Be early, specific and useful. “Sorry, it's taking longer” doesn't tell the recipient what can happen next. Nor should you pretend the extra work was inevitable if the real issue was that you forgot to include review. Own the estimate and update the method.

What to track for a week, without tracking yourself to death

Choose just one repeated type of task. Before starting, note your estimate and what “done” means. After finishing, jot down the actual effort, any waiting and the biggest reason they differed. Three or four examples are enough to begin noticing patterns; more data may help later, but don't convert an ordinary day into a time-and-motion study.

Patterns worth watching: are you systematically leaving out setup? Does written work always need an unexpected second pass? Are brief tasks taking longer because colleagues contact you midway? Are estimates accurate for familiar tasks but wildly wrong for the first time you try something?

Look for a practical adjustment to the next plan. If your only conclusion is that you must try harder, the log isn't doing its job.

Where a focus timer actually helps

Calphii's Deep Focus timer can give a realistic piece of work a beginning, while its task board and notes can hold a definition of done and a restart point. We make Calphii, and it isn't an automatic estimator or a project manager. A sixty-minute timer doesn't mean sixty minutes is all the job deserves.

Use the timer for the portion you can work on now. If the task is still open when it finishes, note what changed, reassess the remaining work and carry on deliberately. A session that clarifies uncertainty has still produced something.

Questions worth asking yourself

The small change that matters

The next time something takes longer, try not to turn it immediately into a story about your character. Ask whether you estimated the whole job, whether you had useful past evidence, and whether conditions changed. That gives you something you can actually improve.

We can't make every task shorter. We can stop promising an imaginary afternoon to a real one.