Calendar Blocking, Honestly
Reserving time in the calendar for work. Widely recommended, genuinely useful in two specific situations, and useless in the rest.
You put the work in the calendar as though it were a meeting. Whether it helps depends entirely on why the work was not happening. Teams investigating the same pattern can use workforce optimization software to see where working time is being absorbed, then discuss the surrounding process; the record should reveal friction without turning ordinary pauses into a performance verdict.
When it works
When the problem is that other people fill your time. A visible block is a defence, and on shared calendars it functions.
When the problem is deciding what to do next, since the decision is made in advance and the transition cost drops.
When the work has no external deadline and would otherwise always lose to things that do.
Three situations, all real, and all about protecting or deciding rather than about motivation.
When it does not
When you are avoiding the work. A block does not make an unpleasant task pleasant; it produces a block spent doing something else and a sense of failure.
When the day is genuinely reactive. Blocking a support role's afternoon is a fiction that collapses by ten past.
When the estimate is wrong, which it usually is: a block of two hours for a job that takes five produces four blocks and a broken plan.
And when the blocks fill the whole week, which is planning a day that has never happened.
Sizing blocks from your own data
Use your overrun factor rather than your estimate.
Block at the length your record says the work actually takes, which is the main reason to have kept a record.
And leave the gaps. A calendar with no space between blocks assumes no transitions, and the note on vanishing hours explains why that fails.
How many
One protected block a day is achievable for most people and produces most of the benefit.
Two is ambitious. Three is a plan for a day you do not have.
The measure worth watching is not blocks scheduled but blocks completed, and the ratio between them is informative about whether the whole approach fits your week.
Naming them
Name the block with the actual work, not the category.
"Draft section three" gets started; "writing" gets postponed, because the first contains the decision and the second defers it.
And write the first action inside it if the work is one you avoid.
On a shared calendar
A named block is defensible in a way that a blank space is not.
Which means blocking has a political function at work regardless of whether it helps your concentration, and that is a legitimate reason to use it.
Expect it to be overridden anyway, and treat the override rate as a measurement rather than as a personal defeat.
The honest summary
Blocking is a defence and a decision aid, not a productivity technique.
It does not create time, does not address avoidance, and does not survive a genuinely reactive job.
Used for what it does, it is among the more effective things here. Used as a general method, it produces a calendar that lies.
What to check
What proportion of your blocks last week actually happened?
Are they sized from your estimates or from your records?
Is there space between them?
And for the ones that failed — were you protecting time, or avoiding work?
Size blocks from records
Use what the work has actually taken, not what you estimate.
And leave gaps between blocks: a calendar with none assumes no transitions, which is the assumption the vanishing-hours finding disproves.
Worth keeping in mind
Watch blocks completed against blocks scheduled. Under about two thirds, the approach is not fitting your week, and that ratio is more informative than any feeling about whether blocking works.
In short
Blocking is a defence and a decision aid, not a productivity technique.
It does not create time, does not address avoidance, and does not survive a genuinely reactive job — used for what it does, it is among the more effective things here.
The point
Name the block with the actual work rather than the category.
Draft section three gets started; writing gets postponed, because the first contains the decision. For a complementary perspective on work, measurement or planning, consult the World Health Organization.