Back to field notes

Time blocking: how to plan a day you actually follow

Time blocking means giving specific work a specific slot in your day instead of working from a to-do list. When a block plan collapses, the cause is rarely willpower. Usually the plan was built on optimistic estimates, with no buffer and too many blocks. The fix is a smaller plan: honest estimates, a few blocks you actually protect, and a rule for the moment the day breaks.

It is 10:40 and the plan is already fiction. The 9:00 writing block started at 9:25 because one message needed an answer. The quick call ran twenty minutes long, everything after it slid by half an hour, and by two o'clock you will have stopped opening the calendar.

Nothing about that morning was unusual. The plan needed a perfect day and got an ordinary one.

What time blocking is (and what it is not)

Time blocking divides the day into blocks and gives each block one job: 8:30 to 10:00 for drafting the report, 11:30 for email, the late afternoon for small tasks. A to-do list says what. A block plan says what and when, and it shows you at once when the list does not fit the day.

Cal Newport described the method on his blog in 2013 and popularized it through Deep Work (2016) and The Time-Block Planner (2020). A block plan is not a promise that every minute goes as drawn. Newport expects the plan to break, and when it does, he redraws the rest of the day's blocks instead of abandoning the schedule.

Why time-blocked days fall apart

Three design problems sink block plans, none of them about willpower.

The estimates are optimistic. In a classic planning-fallacy study, Buehler, Griffin and Ross (1994) asked students when they would finish their honors thesis. They predicted 33.9 days on average and took 55.5. Only 29.7 percent finished by their own estimate, and about half missed even their worst-case date. A day plan invites the same error in miniature, with each block sized for the version of the task where nothing goes wrong.

Nothing is left for overruns. With every half hour filled, the first late block pushes the next, and by mid-afternoon the calendar describes a day that is no longer happening.

There are too many blocks. Every boundary is a switch. In lab tasks, Rubinstein, Meyer and Evans (2001) measured costs of roughly 0.6 to 1.1 seconds per switch, trivial on its own. The bigger cost is probably what a switch leaves behind. Sophie Leroy (2009) called it attention residue: leave a task unfinished to start another, and part of your attention stays with the first while work on the second suffers. Over a day of half-hour blocks this likely adds up, but that total is an inference, not a measurement.

How to build a block plan that survives

1. Start with what is fixed. Meetings, classes, school pickup, the commute and lunch go on the grid first. What remains is the time you actually have.

2. Place one to three focus blocks. Give the hardest work 60 to 90 minutes at a stretch, in your best hours. Treat that range as a starting point, not a research finding; if you can protect 45 minutes, use 45. How to improve focus covers what happens inside the block.

3. Estimate honestly. Pad your first estimate by your usual overrun. If last week's one-hour tasks took ninety minutes, add half again. Stanford's Center for Teaching and Learning gives students the same advice.

4. Leave real buffer. The same Stanford guide suggests keeping at least 15 hours a week fully blank in a student's schedule. Blank time is where overruns land instead of toppling the rest of the day. Start with thirty minutes after each focus block.

5. Batch shallow work. Email, messages and small admin get one or two blocks of their own instead of leaking into every block.

6. End with a five-minute replan. Check which blocks happened, move what did not, and choose tomorrow's first block. It fits into an evening routine that closes the day.

Add an if-then rule for the moment the plan breaks

Even a good plan breaks. Without a rule, you decide what happens next at the worst moment: write off the day, or cram everything back in. Decide in advance instead.

Psychologists call this an implementation intention: "if situation X happens, then I will do Y." Gollwitzer and Sheeran's 2006 meta-analysis of 94 tests found that such plans improved goal attainment (d = .65). A 2024 update by Sheeran, Listrom and Gollwitzer pooled 642 tests and found a smaller but still positive effect, d = .36 overall and .15 after correcting for publication bias (the tilt toward publishing positive results).

In that update, plans written as a plain schedule did less (d = .29) than plans written in if-then form (d = .43). A block plan on its own is a schedule, so give each block one rule for whatever is most likely to derail it:

  • "If a meeting eats my focus block, I move the block. I do not delete it."
  • "If I open my phone during a block, I put it in another room and restart the timer."
  • "If a task runs past its block, I note the next step and finish it in the buffer."

A sample time-blocked day

An example, not a prescription. Your grid will look different.

TimeBlockNotes
08:30-10:00Focus blockHardest task, phone in another room
10:00-10:30BufferCatches the morning overrun
10:30-11:30MeetingsGrouped, not scattered
11:30-12:00Email and messagesFirst batch
12:00-13:00LunchAway from the desk
13:00-13:30Email and messagesSecond batch
13:30-15:00Focus blockMoves if a meeting takes it; never deleted
15:00-15:30BufferBlank on purpose
15:30-16:30Shallow tasksAdmin, calls, errands
16:45ShutdownFive-minute replan for tomorrow

If you can protect only one focus block, keep the morning one and its buffer.

When time blocking is the wrong tool

Support queues, on-call shifts and parenting a toddler are reactive by design. A full grid breaks every hour until it teaches you that planning does not work. Use one or two anchor blocks instead, such as the hour before the house wakes or the queue opens, and run the rest of the day from a list.

Is time blocking good for ADHD? Many people with ADHD find external structure helpful, and a block plan is exactly that. It is not a treatment, and ninety minutes may be the wrong size. Try shorter blocks and a visible timer, and keep what works. If attention problems follow you across work and home, take them to a clinician, not a planner.

Parkinson's law gets quoted as a reason to keep blocks tight: "work expands so as to fill the time available for its completion." That line comes from a satirical 1955 essay by C. Northcote Parkinson in The Economist, not from an experiment. Use it to give each block a finish line, not to cut the buffer.

Measure the plan, not your worth

Each week, check which blocks actually happened. A block that fails three days running is a planning error, not a character flaw. Usually it sits at the wrong time, runs too long, or lacks a buffer; change one of those and check again. If the same dreaded task keeps losing its block, the problem may be avoidance rather than scheduling.

Is time blocking actually effective? Aeon, Faber and Panaccio's 2021 meta-analysis of 158 studies looked at time management in general, not time blocking specifically. It found a moderate correlation with job performance (r = .26) and a stronger one with wellbeing (r = .31), but most of the studies were cross-sectional self-reports, so they show an association, not proof that planning causes either. Your own record is the better test.

Baseline keeps that record: you log builds and drains, each day nets out to one number, positive or negative, and you see the trend plus a rank that only climbs. A finished focus block is a natural build; a block lost to scrolling is a drain.

Start with one protected block

Tomorrow, skip the full grid. Put in the fixed commitments, one focus block in your best hours, a thirty-minute buffer after it, and one if-then rule for its likeliest derailer. In the evening, check whether the block happened.

Add a second block only after the first holds for most of a week. A plan small enough to repeat does more for consistency than a perfect grid you abandon by Wednesday. Get Baseline if you want to log each block as a build and see which parts of the plan survive.