A to-do list is a set of promises with no prices attached. It will happily hold nine hours of work for a day that has four, and it will never once tell you. Time blocking is the correction: you assign every working hour to a specific activity in advance, on a calendar, so the arithmetic becomes impossible to avoid.
Cal Newport, who has argued for the practice for years, frames it as giving every minute a job. The claim isn't that you'll work faster. It's that you'll stop pretending.
How to actually run it
1. Block tomorrow at the end of today. Ten minutes, at shutdown. Planning in the morning means planning while the day is already pulling at you, and the plan bends to whatever arrived overnight.
2. Put the hard thing first and give it a real block. Cognitively demanding work needs a block long enough to get past the setup cost — 90 minutes is a reasonable floor, and two short blocks are worth much less than one long one, because you pay the ramp-up twice.
3. Batch the shallow work. Email, approvals, admin, the five-minute favours: one or two named blocks, not a background drizzle. The drizzle is what destroys the deep blocks, since every interruption leaves attention residue that makes the return slower than the interruption itself was.
4. Block the buffers too. An unblocked hour isn't slack, it's an invitation. Schedule the gaps deliberately, including a real break — the alternative is discovering at 4pm that the plan had no room to breathe and abandoning it.
5. Keep a capture inbox open beside it. Things will occur to you mid-block that belong to a different block. Write them down and keep going. Without somewhere trusted to put them, each one sits in working memory and taxes the block you're in. A frictionless note inbox is what makes protecting a block psychologically possible.
Why most people quit in week two
Because the plan breaks on the first day, and they read that as failure. It isn't. The plan breaking is the normal case — a meeting overruns, something urgent lands, a task takes twice as long as estimated.
The one rule that saves the practice: when the plan breaks, re-block the rest of the day. Don't abandon it. Thirty seconds, drag the remaining blocks, continue. People who last at time blocking re-plan several times a day without treating it as a defeat. People who quit expected the morning's schedule to survive contact with the afternoon.
Two other predictable traps:
- Over-planning. Early blocks are wildly optimistic. Estimate, then add half again. After two weeks you'll know your real multiplier, and that knowledge is arguably more valuable than the scheduling itself.
- Blocking every minute. A calendar with zero white space is a plan that fails on the first surprise.
Where it genuinely doesn't work
Honest limits, since most advice on this skips them:
| Situation | Verdict |
|---|---|
| Maker work, few meetings | Excellent fit |
| Study and revision | Excellent fit — pairs with spaced repetition |
| Heavy meeting load | Useful, but you're mostly blocking the gaps |
| Support, on-call, ops | Poor fit — block themes, not tasks |
| Highly variable energy | Fragile; a task list may serve you better |
If your day is genuinely reactive, blocking specific tasks will just generate a daily record of failure. Block categories instead — "customer issues", "own projects" — and accept coarser resolution.
Time blocking vs the Pomodoro technique
They solve different problems and combine well. Time blocking decides what happens when, at the scale of a day. The Pomodoro technique decides how you survive a block, at the scale of twenty-five minutes. Use blocking to protect a two-hour slot for the hard thing; use pomodoros inside it if that's what keeps you in the chair.
The larger goal is the same one behind deep work: long, uninterrupted stretches on things that matter are not something a normal calendar produces on its own. They only exist if you put them there first.