Time Blocking That Survives a Real Week

Time blocking is one of the few productivity practices with a genuinely good idea inside it. It is also one of the most commonly abandoned, usually within a fortnight, and the reason is structural rather than a failure of discipline.

The version described in most productivity books — every hour of the day assigned, reviewed nightly, adjusted continuously — is brittle by design. What follows is why it breaks, and the looser version we would actually recommend — the one people are still running months later.

Why the strict version failed

Three reasons, in order of how quickly they showed up. Do any of them describe your last attempt?

1. One unexpected thing invalidates the whole day. A 40-minute problem at 10am does not cost 40 minutes; it costs every block after it, and rebuilding the day costs another fifteen.
2. Estimates were wrong, consistently and in one direction. Everything took longer. Six months later they are still wrong, just less so.
3. Maintaining the schedule became work. Twenty minutes a day of rescheduling is not a productivity system, it is a hobby.

What survived

Rule 1: block two or three things, not the whole day

Pick the two or three things that would make the day worthwhile and give each a real block. Leave everything else unstructured. That unstructured time is not wasted — it is where the unexpected goes, and having nowhere to put the unexpected is precisely what makes the strict version collapse.

A schedule with slack in it survives contact with reality. A schedule without slack fails the first time anything happens.

Rule 2: block by finishing, not by duration

"Write the comparison section" beats "90 minutes on the article". A block with a finish line ends with something done. A block with only a duration ends when the timer does, often mid-thought.

Ninety minutes is a reasonable floor for anything requiring real concentration. Below that, setup and re-orientation consume most of the block, and you end up with the feeling of having worked without the artefact that proves it.

Rule 3: a missed block is information

The strict version treats a missed block as failure to be corrected by rescheduling. That is how days become impossible.

Instead: if a block gets missed once, it was a busy day and means nothing. Three times, and the task is not actually a priority — you have simply not admitted it yet. Delete it, and notice that the relief you feel is the information you were avoiding. This is usually the most useful of the three rules and reliably the least comfortable.

What it looks like now

Time	What is there
09:00–10:30	One blocked deep-work item, with a finish line
10:30–13:00	Open — meetings, review, whatever arrived
13:00–14:30	Second blocked item
14:30–17:00	Open

Two blocks, roughly three hours protected, the rest of the day free to be a day. Across a good week that is somewhere around fifteen hours of genuinely focused work — considerably more than most people manage without any structure, and considerably less than the books imply is available. Both halves of that sentence matter: the practice works, and the promised transformation does not arrive.

The benefit nobody advertises

The clearest change is usually not output. It is that over-commitment becomes visible before it becomes a problem. When someone asks for something and the two blocks for the day are already spoken for, the answer is obvious and does not require a negotiation with yourself at eleven at night.

That is a smaller claim than the productivity literature makes, and it is the one that holds up. A system that makes your actual capacity legible is worth more than a system that promises to expand it.

If you want to try it this week

1. Tomorrow morning, name the one thing that would make the day worthwhile. Block ninety minutes for it with a finish line, not a duration.
2. Do not block anything else. Resist the urge — the empty calendar is doing work.
3. At the end of the week, count how many of the five blocks happened. If it is three or more, add a second daily block. If it is fewer, the blocks are too long or the finish lines are too vague.
4. Delete anything you have now missed three times, without rescheduling it.

That is the entire practice. It fits on an index card, which is roughly the correct amount of infrastructure for a system whose main failure mode is becoming a job of its own. The same warning applies to the app you keep the list in.