← Blog

Focus, explained

Does time blocking actually work?

Search for evidence that "time blocking" works and you will find a great deal of advocacy and almost no research — because the research was never about time blocking. It was about three older, narrower things that time blocking happens to bundle together. Separating them tells you which parts to keep.

By ComunAI · 3 August 2026 · ~6 min read

Start with what doesn't exist

There is no controlled literature on "time blocking" as a named system, and none at all on "monk mode". These are practitioner terms from productivity writing, not constructs anyone has operationalised and tested. When an article tells you time blocking is "scientifically proven", what it is doing is borrowing credibility from adjacent research and attaching it to a branded routine. Evidence: None, as a named system

It is worth being blunt about a related one. Parkinson's law — "work expands to fill the time available" — is quoted constantly as the mechanism behind time blocking. It comes from a satirical essay C. Northcote Parkinson published in The Economist in 1955 about the growth of bureaucracies.¹ It is a witticism about civil service headcount. It is not a finding, and it was never presented as one.

Part one: deciding when and where, in advance

This is the strongest component, and it long predates the productivity framing. Peter Gollwitzer's work on implementation intentions — plans in the form "when situation X arises, I will do Y" — has been tested extensively. The meta-analysis by Gollwitzer and Paschal Sheeran, pooling a large body of experiments, found a medium-to-large effect on goal attainment relative to holding the same goal without the if-then plan.² Evidence: Strong

Note precisely what that supports. It supports specifying the cue and the action ahead of time. Writing "Tuesday 9–11am: rewrite the onboarding doc" is an implementation intention wearing a calendar's clothing. The benefit is in the specification, not in the grid.

Part two: the deadline you set yourself

A block has an end. That end is a self-imposed deadline, and there is a well-known experiment on exactly this. Dan Ariely and Klaus Wertenbroch had students choose their own deadlines for a series of papers, and compared them against evenly spaced externally imposed deadlines and against a single end-of-term deadline.³ Two results matter here: people who set their own deadlines did better than those with no interim deadlines at all — and they did worse than the group given evenly spaced external ones. Evidence: Moderate

So self-imposed structure helps, and it is not as good as structure imposed from outside. That is a more useful finding than "deadlines work", and it explains something people notice in practice: a calendar block you can silently move is weaker than a meeting you would have to cancel on someone.

Part three: what the block keeps out

The last component is the one this site keeps returning to, because it has the clearest mechanism. A block is a container for one task, and the value of one task at a time is not in dispute: switching between tasks carries a measurable cost in time and errors, a literature Stephen Monsell's review summarises well.⁴ Evidence: Strong

And the baseline it is being compared against is genuinely fragmented. Gloria Mark and colleagues, observing information workers in their actual offices, documented work broken into short segments with frequent shifts between them⁵ — and in later work found that interrupted work was completed faster, but at the cost of higher stress and effort.⁶ Evidence: Moderate A block is a defence against that pattern. Whether it succeeds depends entirely on whether anything actually enforces it.

Why the plan itself settles you down

There is one more effect worth naming, because it explains the relief people report on writing the day out. E. J. Masicampo and Roy Baumeister found that unfulfilled goals intruded on attention — but that making a specific plan for an unfinished task reduced those intrusions, without the task being any closer to done.⁷ Evidence: Moderate

That is a real benefit of laying out a day in blocks, and it is a different benefit from the one usually advertised. It is not that the schedule makes you faster. It is that committing the plan somewhere stops you re-litigating it.

What we can and can't say

The calibrated bottom line

Time blocking is a delivery mechanism for three things that work: an if-then plan, a self-imposed deadline, and a container that holds one task. If your version of it delivers those, the label is irrelevant. If it delivers a colour-coded calendar you rearrange each morning and abandon by eleven, the label is doing all the work and none of the parts are.

Two practical readings follow, and both are deliberately unglamorous. First, the weakest link is enforcement — a self-imposed deadline is the softest kind, so anything that makes the block harder to silently abandon is worth more than a better schedule. Second, don't schedule the day you wish you had; if sleep is short or the day is genuinely full of meetings, a grid of deep-work blocks is a plan to feel bad at 4pm.

Once the plan is reasonable, the technique with the clearest support is what happens inside the block: Single-Tasking vs. Multitasking, Does Notification Batching Help You Focus?, How Long Should a Deep Work Session Be? and Exercise and Focus.