Meeting Days Need a Different Focus Plan
A calendar packed with meetings is not an open project day with interruptions in it. It is a different kind of day, and it needs a different plan. Trying to run the same deep work strategy on both is how people end up at 6pm having attended everything and produced nothing, convinced they lack discipline.
They do not lack discipline. They are applying a plan built for four uninterrupted hours to a day that structurally cannot contain one.
The useful reframe is to stop treating meetings as time cost and start treating them as attention cost. A thirty minute meeting rarely costs thirty minutes. It costs thirty minutes, plus the ten before it when you will not start anything meaningful because you know it is coming, plus the recovery afterward while the conversation is still running in your head. A day with four scattered thirty-minute meetings can consume most of your usable attention while showing only two hours as busy.
Once you accept that, the plan changes. You stop trying to find four hours and start protecting one block that will actually survive.
Find the Anchor Block First
Before doing anything else, find the one block on the day that can realistically hold. Early morning before the calendar opens, a lunch gap, or the last quiet hour before shutdown. There is usually exactly one. Occasionally two. Rarely three.
That block gets the hardest task and none of the negotiation. It does not get email. It does not get "quick" admin. It is the thing the day is built around, and everything else arranges itself in the gaps.
- Pick one non-negotiable focus block and put it in the calendar as a real event.
- Assign exactly one important task to it, decided the night before.
- Keep everything else smaller than that block, deliberately.
Deciding the task in advance matters more on meeting days than on open days. If you arrive at your one protected hour and have to work out what to do with it, you will lose fifteen minutes to that decision, and fifteen minutes out of sixty is a quarter of the only real block you had.
Sizing Blocks to the Gaps You Actually Have
The standard advice is a ninety minute block, and on an open day that is good advice, because it lines up with the natural ultradian cycle of alertness. On a meeting day, insisting on ninety minutes means you will schedule zero blocks, because you do not have ninety clean minutes anywhere.
Match the block to the gap instead:
- 25 to 30 minutes: one concrete, pre-defined task. Finish a section, review a pull request, draft one reply that needs actual thought. Do not start anything requiring a long ramp.
- 45 to 60 minutes: real work on the important thing. Enough to get past the awkward start and produce something.
- 90 minutes: if you get one, it is the anchor. Guard it accordingly.
The trap in short blocks is spending the whole thing loading context and never producing anything. That is avoidable if you know in advance exactly what the block is for. A 30 minute block with a defined target beats a 60 minute block spent deciding.
Reduce Context Switching Damage
Meetings leave residue. A conversation about one problem keeps running in the background while you try to start a different task, and your attention is split without your noticing. Researcher Sophie Leroy named this attention residue, and it is why the ten minutes after a meeting feel so unproductive even when you sit down promptly.
Residue is reduced by closure, not by hurrying. The move is to spend sixty seconds finishing the meeting properly before starting anything else:
- Write down any commitment you made, so your brain stops holding it.
- Write the one open question the meeting left unresolved, if there is one.
- Close the meeting's notes and tabs completely.
- Write the first action for the next block, as a verb.
- Start the same timer and the same audio mode, every time.
The consistency is the point. This is not about the sound being magic. It is a repeated signal that the previous context is closed and a new one has started, and repetition is what makes it work. The real cost of context switching is mostly paid in these transitions, which is why a sixty second ritual returns so much more than it costs.
Batch the Meetings Themselves Where You Can
Everything above assumes the calendar is fixed. Often it is partly negotiable, and small changes to shape pay off more than any productivity technique.
Four meetings spread evenly across a day destroys the day. The same four meetings stacked back to back leaves a genuine block on one side. When you get to choose, stack them. When someone offers you a slot, offer back one adjacent to a meeting you already have rather than one that opens a fresh hole.
Two habits do most of the work here. Default to declining meetings without a stated purpose, or ask what decision the meeting needs to reach. And put your anchor block in the calendar as a busy event, because an empty calendar is an invitation and a full one is not. This is task batching applied to your calendar rather than your task list, and it works for the same reason.
Protecting the Block From Yourself
Most interruptions during a protected block are self-inflicted. You check whether anything came in. You remember something for another project and go handle it. You open a tab "for a second."
The fix is a capture surface. Keep one plain text file or notes page open, and when something surfaces, write it down and go straight back. It takes four seconds and it satisfies the part of your brain that was worried about forgetting. Everything on that list gets handled after the block, and almost none of it turns out to have been urgent.
Notifications need to be off at the system level, not per app, because per app is a decision you have to make repeatedly and system level is a decision you make once. If you are genuinely on call for something, keep one narrow exception and let everything else wait an hour. Setting up an environment that removes distractions structurally beats resisting them individually every time.
Review the Day Honestly
If the schedule was overloaded, the review should say so. Missing a deep work target on a seven-meeting day is a planning problem, not a discipline problem, and confusing the two produces guilt without producing change.
The question worth asking is not "did I hit my target" but "was that target ever available on a day shaped like this." If the answer is no, the target was wrong, and the fix is a separate, realistic target for meeting-heavy days rather than more resolve.
Session records make this concrete. If thirty minute blocks consistently complete on meeting days and sixty minute blocks consistently collapse, that is not a preference, it is data, and you should build around it. A weekly focus review is where that pattern becomes visible, because a single day is noise and a month is a signal.
The Meeting-Day Template
Put together, a meeting-heavy day looks like this:
- The night before, identify the anchor block and the one task it holds.
- Stack meetings adjacently wherever the calendar allows it.
- Run a sixty second closure ritual after every meeting: capture commitments, close the context, write the next action.
- Use short blocks in the gaps, each with a target defined before it starts.
- Keep a capture file open so stray thoughts cost four seconds instead of ten minutes.
- Judge the day against a meeting-day target, not an open-day target.
None of it requires a lighter calendar. It requires giving up the idea that a fragmented day can be run like an open one, and building for the day you actually have.