Why do I always underestimate how long things take?

Most people underestimate because they picture the best-case run of a task and forget the setup, switching and interruptions around it. The fix is feedback: write a guess, time the real thing with a kitchen timer or a paper log, and plan from what past tasks actually took. On a Mac, Dayflow can record your day automatically so you can compare plans with what happened.

You sit down at 2 p.m. to quickly answer three emails and fix one slide. You look up and it is 4:40. The emails are sent, the slide is half done, and the thing you actually promised to finish today has not been opened.

It happens with bigger things too. The report you set aside a morning for takes two days. The errand that “takes ten minutes” takes forty once you count finding your keys, parking and the line. Each time, the miss feels like a personal failing, and each time you are sure the next estimate will be better.

This article covers why estimates slip so reliably, six things you can try this week with paper, a timer and a calendar, and how to tell whether each one is working. A note up front: Dayflow, which publishes this blog, is our product. It comes up once near the end, in its own section, along with where it is the wrong choice. The Dayflow details in that section come from its own published documentation for version 2.2.0, reviewed on 2026-09-06.

The short version

• Before you start a task, write down how long you think it will take. After, write down how long it took. Do this for a week.
• Estimate the steps you will actually do, including setup, switching and wrap-up, not just the core of the work.
• Plan from what similar tasks took last time, not from how long they should take.
• Add a fixed buffer to every estimate and adjust it from your own notes.
• Put tasks on a calendar as blocks, so you can see when the day is already full.
• Say your estimate out loud to someone and check back with them afterward.

Why does this keep happening?

Underestimating is common enough that it has a name, the planning fallacy, and it shows up in people who are organized and people who are not. A few plain mechanisms do most of the work.

You picture the best-case run. When you imagine a task, you imagine the middle of it going well. You see yourself writing the report, not hunting for last quarter’s numbers, rereading an old email thread, or waiting for a file to sync. The estimate is for a version of the task that rarely happens.

The edges of a task are invisible. Starting takes time: deciding what to do first, opening the right things, getting your head into it. Finishing takes time too: checking, formatting, sending, answering the reply. These parts do not feel like the task, so they do not make it into the guess.

Memory compresses the past. When you think back to how long something took last time, you remember the main stretch of work. The interruptions, the side trip into your inbox and the twenty minutes spent on something unrelated tend to drop out. So even your experience points you toward a shorter number than the truth.

Interruptions and switching add up quietly. A message here, a quick question there. Each one costs a few minutes, plus the time to find your place again. Across a day, that can be the difference between finishing and not.

The future feels roomier than the present. Tomorrow afternoon looks wide open from here. It will not be, because tomorrow will have its own messages, meetings and small surprises. Many people plan their future self as someone with fewer demands than they will actually have.

For some people, including many people with ADHD, time can feel especially hard to sense when it is not happening right now. “Later” and “a while” blur together, and an hour can disappear without registering. If that sounds familiar, our piece on ADHD and time blindness goes into it more. Either way, the pattern is not a character flaw. It is what happens when estimates never get checked against reality.

That last point is the thread through everything below. You cannot fix a guess you never compare with the result.

Things to try

1. Keep a guess-and-check log for one week

What to do. Get a sheet of paper or a notebook and draw three columns: task, guess, actual. Before you start something, write the task and your guess. When you finish, write how long it really took. Use a clock or a kitchen timer to keep yourself honest. If you prefer a ready-made layout, the daily work log template works for this.

Illustration. A Tuesday might look like this:

Task	Guess	Actual
Reply to client email	10 min	25 min
Update project slide	15 min	50 min
Expense report	20 min	15 min
Draft proposal intro	30 min	1 hr 10 min

How to tell it is working. After a week, look for a pattern, not a scolding. Maybe writing tasks run long and admin runs short. Maybe anything involving another person’s files doubles. If you can name one or two patterns, the log has done its job.

2. Estimate the steps, not the task

What to do. Before guessing, list the steps you will actually take, including the boring ones. Then estimate each step and add them up. Make the first step a physical action, like “open the Q3 spreadsheet,” not “work on the report.”

Illustration. “Update the slide” becomes: find the latest numbers (10 minutes), check them against the last version (10), rebuild the chart (15), fix the layout (10), send it and answer questions (10). That is 55 minutes, not 15. The work did not grow. You just counted it.

How to tell it is working. Your step-based estimates should land closer to the actual column in your log than your gut estimates did. If they are still short, look at which step you keep leaving out. For many people it is the last one.

3. Plan from the last time, not from the ideal

What to do. When a task comes up, ask “how long did this take last time?” before asking “how long should this take?” Use your log, your calendar, or your sent mail to find the real answer. If you have no record, make your best guess and mark it as a guess.

Illustration. You need to prepare a monthly report. Your gut says two hours. Your log from last month says it took most of an afternoon once you counted chasing two colleagues for numbers. You block the afternoon and leave the two hours as the hopeful version.

How to tell it is working. Fewer tasks spill past the time you gave them. You will still have surprises, but the familiar, repeated tasks should stop catching you off guard. If you find you have no record to look back on, that tells you where to start. Our guide on how to remember what you worked on covers simple ways to build one.

4. Add a fixed buffer, then tune it

What to do. Pick a simple rule and apply it to every estimate. A common starting point is doubling estimates for unfamiliar work and adding a set chunk of setup time, say fifteen minutes, to familiar work. The rule does not need to be clever. It needs to be consistent so you can see if it helps.

Illustration. You think a new type of task will take an hour, so you plan for two. You think your usual weekly update will take thirty minutes, so you plan for forty-five. At the end of the week, you check your log: the new task took an hour and forty, and the update took thirty-five. The buffer on the new work was about right. The buffer on the update can shrink.

How to tell it is working. You finish the day with roughly what you planned done, instead of carrying half of it forward. If you are now finishing early every day, the buffer is too big, which is a good problem and an easy fix.

5. Put tasks on the calendar as blocks

What to do. Instead of a to-do list, give each task a block on your calendar that matches your padded estimate. Include breaks, lunch, and travel between meetings. A to-do list hides how much you have promised. A calendar shows it.

Illustration. Monday’s list has seven items, which looks doable. When you place them as blocks around three meetings and lunch, only five fit, and the last one runs past 6 p.m. You move two items to Wednesday before the day starts, not after it falls apart.

How to tell it is working. Look back at your calendar at the end of each day and mark which blocks held and which overflowed. After a week, you should see fewer overflows, and the ones that remain will tend to be the same kinds of task. Those are your next targets for step 2.

6. Say it out loud to someone

What to do. Tell a friend, partner or coworker what you are about to do and how long you think it will take. Ask them to check in when the time is up. You can also do this by text. The point is not accountability in a stern sense. It is that a spoken estimate is harder to quietly revise.

Illustration. You message a friend: “Starting the tax forms, think it’s an hour.” An hour later they reply, “Done?” You are about halfway. You both laugh, and you write “taxes: guess 1 hr, actual about 2.5” in your log. Next year, you will know.

How to tell it is working. Your spoken estimates start getting more careful, because you know someone will ask. Many people find they begin padding automatically once they have been caught short a few times in front of a friend.

Where seeing your actual day helps

Every step above depends on knowing what really happened. That is the hard part. Starting a timer for each task is easy to forget, and reconstructing a day from memory runs into the same blind spots that caused the bad estimate in the first place. If you have ever wondered where your day went, you know the feeling.

Dayflow takes a different approach for time spent on a Mac. It records your screen at one frame every 10 seconds and has AI write the day into a readable timeline, so you can compare what you planned with what was actually on screen without remembering to start anything. Full screen recordings and the local timeline are stored on your Mac. You can keep screenshot analysis on-device with Local AI through Ollama or LM Studio, or send selected screenshots to your own cloud provider or to Dayflow Pro. The local and cloud processing page explains the difference. You can export a date range as Markdown from Settings → Export.

Dayflow is free ($0) and MIT licensed, with an optional Pro plan at $20 a month, and it runs on macOS 14 or later. AI summaries can miss or misinterpret work, so treat the timeline as a starting point and check it before relying on it. Details are on the pricing page.

Dayflow is our product, and this article is published by Dayflow.

Where Dayflow is the wrong pick

Be clear about what Dayflow is and is not before trying it.

• It is Mac only. If you work on Windows, Linux, an iPad or mostly your phone, it will not help. A paper log will.
• It sees only the screen. Thinking on a walk, a conversation in the hallway, cooking, a phone call away from the desk: none of that appears. If much of your underestimating happens off the computer, a notebook and a kitchen timer will give you a more honest picture.
• It is a record, not a coach. It will show you that the slide took fifty minutes. It will not tell you how to plan tomorrow, and it does not set estimates for you.
• It is not a blocker. Dayflow has no website blocking. If your tasks run long because you keep drifting to the same sites, a dedicated website blocker is the better tool for that job.
• It has no invoicing, payroll approvals or team reports. If you need to bill clients or report hours to a manager, look at dedicated Mac time trackers built for billing.
• It is not a treatment. If time feels slippery in a way that is affecting your life, no app is a substitute for talking to a professional.

For a lot of people reading this, the honest recommendation is a paper log and a kitchen timer for two weeks. They are free, they work everywhere, and they force you to notice the moment you start and stop, which is part of the point.

When to get more help

This article is not medical advice. If underestimating time is part of a wider pattern, such as constantly missing deadlines despite real effort, feeling overwhelmed most days, trouble sleeping, or wondering whether ADHD, anxiety or burnout is involved, a doctor or licensed clinician is the right person to talk to. They can help with diagnosis and treatment in a way no article or tool can. Reaching out is a reasonable, practical step, not a last resort.

The bottom line

You probably underestimate how long things take because you picture the clean middle of each task and forget the messy edges, and because your memory of past tasks quietly drops the interruptions. It is a feedback problem, not a willpower problem.

Start with a guess-and-check log this week. Estimate the steps instead of the task, plan from last time, and add a buffer you tune from your own notes. Put tasks on a calendar so you can see when the day is full, and tell someone your estimate so it sticks. If most of your work happens on a Mac and you want the record without the bookkeeping, Dayflow can capture it automatically. If not, paper does the job just fine.

Frequently asked questions

Why do I always underestimate how long tasks take?

When you estimate, you usually picture the core of the task going smoothly. You leave out getting started, finding files, small detours, interruptions and the slow last stretch of finishing. Memory makes this worse, because past tasks get remembered as their middle part, not their messy edges. Without a written record of what really happened, each new estimate repeats the same blind spots.

Is always underestimating time a sign of ADHD?

Many people underestimate time, with or without ADHD. Some people with ADHD describe time as hard to feel, especially time that is not happening right now, and that can make estimates slip more often. A pattern on its own does not tell you anything about a diagnosis. If it is affecting your work, health or relationships, a doctor or licensed clinician is the right person to talk to.

How do I get better at estimating how long things take?

Close the loop between guess and reality. Before you start a task, write down how long you think it will take. Time it with a kitchen timer or note the start and end on paper. After a week, compare the two columns. Most people find their misses follow a pattern, such as always forgetting setup time, and that pattern is the thing to correct.

How much buffer should I add to my time estimates?

There is no single right number. A simple starting rule is to double estimates for unfamiliar tasks and add a fixed chunk of setup time to familiar ones. Then adjust using your own log. If a week of notes shows your writing tasks run long and your admin runs short, pad the writing and leave the admin alone. Your own record beats any general rule.

Why does getting started on a task take so long?

Starting usually involves hidden steps: deciding what to do first, finding the right file, clearing a few messages, and getting your head into the work. None of that feels like the task, so it rarely makes it into the estimate. Writing down the very first physical action, such as opening a specific document, can shrink that gap and make it visible.

Is Dayflow better than a website blocker for staying on task?

No. If your main problem is drifting to distracting sites in the middle of a task, a dedicated website blocker is the better tool. Dayflow does not block anything. It records what was on your Mac screen and has AI write a timeline afterward, which helps you see where time went but will not stop you from opening a tab.

Can an app fix time blindness?

No app fixes it. Tools can make time more visible, through timers, calendars or a record of your day, and some people find that useful for planning. They are not a treatment and do not replace a clinician. If time feels hard to track in a way that is causing real trouble, talk to a doctor or licensed professional.

Does Dayflow work on Windows or iPhone?

No. Dayflow runs on macOS 14 or later only. It records what is on your Mac screen, so time spent on a phone, in a meeting away from the computer, or working on paper will not appear in its timeline. If most of your working time happens off a Mac, a paper log or a calendar will give you a more complete picture.

Does Dayflow send my screen recordings to the cloud?

It depends on the mode you choose. Full screen recordings and the local timeline are stored on your Mac. With Local AI, screenshot analysis stays on-device through Ollama or LM Studio. With your own cloud provider or Dayflow Pro, selected screenshots are processed off-device. Under the privacy policy, Dayflow Pro deletes screenshots after processing and may retain Activity Data for sync.

How long should I keep an estimate log before it is useful?

A week is usually enough to see a first pattern, as long as you log most tasks and not just the ones that went badly. Two weeks gives you a better sense of which kinds of work run long. After that, many people stop logging everything and only log new or unfamiliar tasks, which is where estimates tend to be weakest.