Deep work for people with meetings

Most advice about concentration is written by people who control their own calendars. It assumes the ninety-minute block is available and that your only obstacle is discipline. If you have six meetings today, that advice is not wrong so much as irrelevant. You are not failing to protect a long block. You never had one.

So the question is not how to get four uninterrupted hours. It is what good work looks like in the gaps you actually have, which are twenty-five minutes long and arrive without warning.

Stop treating short gaps as waste

The common move is to write off anything under an hour. Twenty minutes before a call becomes email, Slack, or nothing. The reasoning sounds sensible: real work needs a run-up, and there is no point starting something you cannot finish.

But "cannot finish" is doing a lot of work in that sentence. Almost nothing worth doing gets finished in one sitting anyway. What a twenty-minute gap can hold is a step: the outline, the failing test, the three paragraphs you already know how to write, the review comment you have been avoiding. Steps are what the work is made of. Treating them as too small to start is how a week disappears.

The rule that survives contact with a real calendar is this: know the next step before the gap arrives. If you have to spend eight minutes deciding, twenty minutes is genuinely useless. If you already know, it is enough.

The end-of-block note is the whole trick

The expensive part of an interruption is not the interruption. It is the reconstruction afterwards: reloading what you were holding in your head, which is the part nobody writes down.

So write it down. When a block ends, spend thirty seconds recording where you stopped and what comes next. Not a summary of what you did. A instruction to your future self, in the imperative: "add the empty state to the sessions list", "ask Dan whether the invite token should expire".

This costs almost nothing and changes the economics of a fragmented day completely. The next gap starts with a sentence instead of a shrug. Over a week it is the difference between six real steps and six warm-ups.

The twenty-five minute rehabilitation

There is a reason the pomodoro length has outlived every method built around it, and it is not that twenty-five minutes is a magic number. It is that it fits in the gaps real calendars have.

A ninety-minute block requires a ninety-minute hole, which on a busy week means never. A twenty-five minute block fits before a stand-up, between two calls, in the half hour after lunch that nobody books. If you have six meetings, you probably have four of those holes, and four real steps is a productive day by any honest measure.

The mistake is treating the short block as a degraded version of the long one. For some work it is. You are not going to hold a complicated refactor in your head in four separate quarter-hours. But a surprising share of professional work is not like that, and the part that is can be scheduled into the one block you defend.

Defend one block, not your whole calendar

Trying to clear a day is a losing negotiation. Trying to keep one ninety-minute block, on the same two days each week, usually works, because it is small enough that nobody feels the need to fight it.

Put it on the calendar with a real name. Not "focus time", which reads as "available if pushed", but the actual thing: "Q3 roadmap draft". A named block gets moved less often, by other people and by you.

The rest of the week is gaps, and that is fine. Two defended blocks and a pile of well-prepared twenty-minute steps is a productive week. Waiting for the mythical clear afternoon is not a strategy, it is a way of feeling justified about a week where nothing moved.

What to measure

Not hours. Hours logged in a fragmented week will look bad next to a week with two clear afternoons, and that comparison teaches you nothing you can act on.

Look at how many blocks started with a known next step, and how many of them produced something you could name afterwards. That ratio is the one you can actually move, and it improves with a habit that takes thirty seconds at the end of each block rather than a renegotiation of your entire calendar.

A day that actually works

For the sake of being concrete, here is the shape that survives a calendar with six things in it.

• Before the first meeting, five minutes: read yesterday's last note, pick the next step, write it down. Not email.
• Every gap over fifteen minutes, one block on the step you already chose. Start the timer, name it in a sentence, stop when the meeting does.
• After each block, thirty seconds: where you stopped, what comes next.
• One defended block, twice a week, with a real name on the calendar, for the work that genuinely needs an hour and a half.
• At the end of the day, nothing. No review, no scoring. The notes are already written.

It is unglamorous and it is roughly four hours of actual work on a heavy meeting day, which is about the ceiling anyone hits regardless of how their calendar looks.

What to stop doing

Stop keeping the day clear "in case a block opens up". It never opens, and you have spent the morning being available instead of being finished.

Stop measuring the week against a version of it with no meetings in it. Some jobs are mostly coordination, and the hours you spend in rooms are the job rather than an obstacle to it. What the timer is for, in that case, is making sure the remaining hours went somewhere you would have chosen, not proving that you deserve them.