The Reactive Calendar Problem
Left unchecked, a calendar fills from the outside in. Meetings arrive, requests stack, and focus time — the deep, uninterrupted hours where real work happens — gets squeezed to nothing.
Time blocking reverses this. You decide, in advance, what the day is for. Then you defend that structure.
What a Blocked Day Looks Like
A time-blocked day has three kinds of slots:
- Focus blocks: 90-minute windows where notifications are off, the door is closed, and one piece of work gets full attention
- Meeting blocks: grouped into specific windows, not scattered across the day
- Buffer blocks: 30-minute gaps between transitions, for overflow, bio breaks, and the unexpected
The goal is not a rigid schedule. It is a default structure — something to return to when the day gets pulled in six directions.
The Right Granularity
Block at 90-minute intervals, not 30. Short blocks create context-switch overhead. A two-meeting morning with four 30-minute gaps produces almost no deep work.
One 90-minute focus block, placed at your peak energy window (usually the first two hours after you start), is worth more than a full afternoon of fragmented availability.
Defending Blocks from Meetings
The most common failure mode: a well-designed day gets eroded by "just a quick 30-minute call." Once one focus block breaks, the mental model that the day is structured collapses.
Treat focus blocks like external appointments. Mark them as busy. Decline overlapping requests. Offer the meeting slots you have actually reserved for meetings.
Start with Tomorrow
You cannot retrofit today. But tonight, spend ten minutes blocking tomorrow. Three questions:
- What is the one thing that, if done, makes tomorrow a success?
- What is my peak energy window?
- Where are the meetings I cannot move?
Put the most important work in the peak window. Group everything else. Block a buffer at the end.