Time blocking keeps failing? Compare the plan with the day you had
· 7 min read
When time blocking keeps failing, the cause is rarely discipline. The blocks were drawn from a guess about how long things take, and nobody ever checked the guess. Lay the plan next to a record of the day you actually had, find the two or three blocks that overrun every time, and redraw the calendar from those numbers instead of from hope.
It takes about ten minutes a day for one week, whether you plan in Calendar or on paper.
Why a sensible plan falls apart by eleven
A time-blocked calendar makes three quiet assumptions. It assumes each task takes the length you gave it. It assumes the gaps between blocks are empty. And it assumes nothing arrives that was not on the plan.
None of those survive a normal day. Tasks you have done many times get estimated from the best run you remember, not the typical one. The gaps fill with messages, quick requests and the setup every task needs before it really starts. And the unplanned arrivals (a question from a colleague, a file someone needs now) take their time from whichever block happens to be current.
The result is a calendar that looks disciplined at nine and fictional by eleven. Blocking harder, with shorter blocks and stricter rules, treats the symptom. More structure on top of unmeasured numbers just fails more visibly. Why your estimate of your own workday is wrong by hours explains where that gap between estimate and reality comes from.
What you need for the comparison
Two things, both covering the same days.
The plan. Whatever you blocked. If you use Calendar on the Mac, the day view is enough, and File, then Print, will put a day or a week on paper if you would rather mark it up with a pen.
The record. An account of where the working hours actually went, collected without effort during the day. Most people lack this, because logging as you go is itself a task, and the first one dropped when the plan slips.
A record of which app was in front, and for how long, fits this job well. It is not a perfect map of tasks, since one app can hold several kinds of work, but it is honest about the big shapes: how long mail really took, how much of the focus block went to the browser, whether the afternoon went to the thing you planned or to chat.
Punchcard keeps that record from the menu bar. It notices which app is in front during the day (app names only, never window titles, documents or URLs) and at the closing time you set it prints a receipt: each app with its time, a day total and a stamp. You do not start or stop anything, which matters here, because a timer is one more block on a calendar that is already failing.
The comparison, step by step
Do this at the end of each day for one working week. It is quicker than it sounds.
- Put the plan and the record side by side. Calendar day view on one side, the day’s receipt on the other.
- Match each block to the app it should have lived in. A writing block should show up as time in your writing app. A mail block should show up as time in Mail. Some blocks map to several apps, and that is fine.
- Write two numbers next to each block: planned minutes, then actual. Rough is fine. You are looking for big differences, not precision.
- Circle anything that ran over by half or more. Those are the blocks your plan misunderstands.
- Note what took the time instead. If the writing block came up short, where did the minutes go? One or two apps usually account for most of the difference.
- Write one sentence about the day. “Mail ate the first block again” is enough.
By Friday you will have five pairs of plan and record, and the pattern is usually visible without any arithmetic.
Reading the pattern
A few shapes come up often enough to be worth naming.
The chronic overrun. One kind of block is always too short. Often it is email, review work, or anything that depends on other people’s input. The fix is not to try harder. Make that block the length it actually takes, and move something else to tomorrow.
The invisible block. Time that appears in the record every day but never on the plan. Chat, messages and quick checks in the browser are the usual candidates. If it happens every day, it deserves a block of its own, placed where it does the least damage. A short block before lunch and another late in the afternoon often absorb most of it.
The evaporating focus block. The long block for real work shows up in the record as a string of short visits to several apps. The block was the right length; it was just never protected. That is a notifications and interruptions problem, not a planning one.
The late finish. The last block of the day slides past your finishing time more days than not. The plan had no slack, so every overrun got paid for at the end. Leaving the last hour unblocked often fixes this outright.
Redrawing the plan from the record
Now rebuild next week’s template from what you saw.
- Resize the chronic overruns to their measured length, rounded up.
- Add a block for the invisible work that turned up every day.
- Leave buffer. An unblocked stretch in the middle of the day and another at the end will catch the overruns you did not predict.
- Plan fewer blocks. If the week showed six real blocks of work per day, planning nine guarantees failure.
- Keep the closing time fixed. A time-blocked day with no hard end simply extends until the plan is done, which defeats the point of planning it.
Then run the comparison again for another week. The second week’s plan usually lands far closer to reality, and the third closer still. Why knowing where the time went changes how you plan tomorrow goes deeper into planning from a record rather than from memory.
Honest limits of the comparison
An app record does not know what you were doing inside an app. A browser block could be research or a distraction, and only you know which. It also cannot see work away from the Mac, such as a phone call or a whiteboard session. Add those from memory the same evening.
It will not assign time to projects or clients either. If you need billable totals per client, you want a tool built for that. For the question time blocking actually raises, “why does my plan never survive the day”, the app record is enough.
Questions
Should I give up on time blocking if it keeps failing? Not before you have compared plan and record for a week. Most failing plans can be fixed by resizing two or three blocks and adding buffer. If the comparison shows your days are driven by other people’s requests, a looser plan with fewer, larger blocks may suit you better.
How accurate does the comparison need to be? Rough is fine. You are looking for blocks that are off by a wide margin, and those stand out even with times rounded to the nearest quarter hour.
What if my calendar is full of meetings I do not control? Then plan the gaps rather than the whole day. Meetings versus making: measuring the split on your own Mac covers how to see how much of the day is really left for your own work.