A Meeting Heavy Day Routine That Saves One Real Block
I had a Thursday last month with seven meetings on it. Between them I had four gaps: 25 minutes, 15 minutes, 40 minutes and 20 minutes. On paper that is an hour and forty of free time, which sounds like plenty.

I had a Thursday last month with seven meetings on it. Between them I had four gaps: 25 minutes, 15 minutes, 40 minutes and 20 minutes. On paper that is an hour and forty of free time, which sounds like plenty. By six in the evening I had answered 31 messages, reviewed two small pull requests, and written no code at all. Nothing on my own list moved.
The gaps were real. The working time was not. A 25 minute hole between two calls is not a quarter of an hour of thought plus ten minutes of overhead, it is ten minutes of recovering from the last call and fifteen minutes of watching the clock so you are not late for the next one. I kept treating those gaps as capacity and kept being surprised. What finally worked was giving up on them entirely and defending one block instead.
Why the leftover gaps are not working time
There is a measurable startup cost to anything that needs holding several things in your head at once. For me, writing or debugging, it runs about eleven minutes before I am properly in it. I know this because I spent three weeks noting the time I sat down and the time the work started feeling continuous rather than effortful. The shortest was six minutes, the longest twenty two, and most days clustered between nine and thirteen.
That number is the whole argument. If getting started costs eleven minutes and the gap is twenty five, you get fourteen minutes of real work, and you spend the last five of those glancing at the calendar. Call it nine useful minutes out of twenty five. Repeat that four times and the hour and forty collapses to about thirty six minutes of thought, spread so thin that none of it joins up.
The gaps are good for something, which is the part I was slow to accept. They are excellent for work that has no startup cost: approving things, replying to a specific question, filling in a form, booking a flight, reading one document. They are terrible for anything where you need to remember what you were doing. So I stopped putting the hard thing in the gaps and started putting the small thing there deliberately.
The one block, and where to put it
On a day with five or more meetings I aim for a single protected block of 75 to 90 minutes and I accept that it is all I will get. Not two blocks of 45. One.
Where it goes matters more than how long it is. Mine sits first thing, 8:15 to 9:45, before the calendar becomes other people's. I tried the post lunch slot for a month and lost it to overruns roughly half the time, because a meeting that runs long at 11:50 eats into 13:00 in a way that nothing eats into 08:15. If your team is spread across time zones and your mornings are already booked, look for the hour after your last recurring call rather than the hour between two of them.
Three rules make it hold. The block gets a calendar entry with a real title, not a block marked busy, because colleagues respect a named thing and will book over an unnamed one. It has one task on it, written the night before, specific enough to start without thinking. And it ends on a note to myself about where I stopped, which is the single cheapest thing I do and cuts tomorrow's startup cost to around four minutes.
Against the popular fix: stop trying to batch every meeting
The standard advice for a day like this is meeting batching. Push everything into two consecutive hours, protect the rest of the day, and you get a long clean afternoon. I tried this seriously for two quarters and I think it is oversold for anyone who is not senior enough to dictate other people's calendars.
Two problems. First, you cannot batch what you do not control. Of my recurring meetings, four are organised by other people across two time zones, and my preferences are not a factor in theirs. I could move perhaps a third of my calendar. Batching a third of the problem does not give you a clean afternoon, it gives you a slightly different mess.
Second, when batching does work, four or five back to back calls leave you flattened. I measured this too, crudely, by rating my own focus out of five after each meeting. After the third consecutive call my rating dropped by about a point and a half and stayed down. The protected afternoon I fought for was spent reading the same paragraph twice. A long gap arrived, and I was in no state to use it.
So batch what is genuinely yours to move, which for most people is one or two recurring items, and stop there. Then spend your effort on defending one block rather than reshaping the whole day. The weekly reset routine is the right place to do the reshaping, once a week, with the whole calendar in front of you.
A real Tuesday, hour by hour
This is from my notebook, a normal week, nothing special about it. Six meetings, one block, and the small stuff pushed into the gaps on purpose.
| Time | What was on the calendar | What I actually did |
|---|---|---|
| 08:15 to 09:45 | Named block: query timeout fix | The work. Ended with a three line note. |
| 09:45 to 10:00 | Free | Coffee, no screen. The one gap I do not fill. |
| 10:00 to 10:30 | Standup and team sync | Flagged the timeout fix so nobody duplicated it. |
| 10:30 to 11:00 | Free | Two code reviews and an expense claim. |
| 11:00 to 12:00 | Design review | Took notes in the doc, not in a separate file. |
| 13:00 to 14:30 | Three calls, one overran | Nothing else attempted between them. |
| 14:30 to 15:00 | Free | Replied to the nine messages I had ignored. |
| 15:00 to 16:00 | One to one | Brought one problem rather than a status list. |
| 16:00 to 16:20 | Free | Shutdown routine, wrote tomorrow's one task. |
The point of writing it out is that the day looks busy and was busy, but one real thing got finished before ten in the morning. On the Thursday I described at the top, the day looked identical from the outside and nothing got finished at all. The difference was ninety minutes, placed somewhere nobody else wanted.
The habit that protects it
The block survives because of two minutes at the end of the previous day, not because of willpower in the morning. I write one line naming tomorrow's task in terms concrete enough to start cold. Not "work on the query timeout" but "add the index on orders.created_at and rerun the slow query log". The vaguer version means my first ten minutes go on deciding what to do, and deciding is exactly what a tired morning brain avoids by opening the inbox instead.
That line lives at the end of my workday shutdown routine, which takes about fifteen minutes and is the reason any of this holds together. If you want to try one thing from this piece, make it that: tonight, write the first sentence of tomorrow's work. Then put a named ninety minute block in the earliest slot nobody else has claimed, and see what survives contact with a real calendar. There is more in the routines section on building the rest of the day around it.
I will add the obvious caveat. This is one engineer's logbook, not a study. My eleven minute startup cost is mine, and someone who writes prose or reviews contracts may find theirs is five or twenty five. Measure your own for a week before you take my numbers as yours.
FAQ
What if someone books over my protected block?
Move it rather than cancel it, even if the new slot is worse. The habit is more fragile than the hour. If the same recurring meeting keeps landing on it, that is a conversation to have once, not a weekly negotiation.
Is ninety minutes long enough to get anything real done?
For one well defined task, usually yes, as long as the task was chosen the night before. The failure mode is not the length of the block, it is arriving at it without knowing what to do.
Should I keep the gaps completely empty instead?
One of them, yes. I leave the gap straight after my block clear and stay off the screen. The others get small, startup free work. Trying to keep every gap empty just means filling them accidentally with messages.
Does this work on a day with nine meetings?
Not really. Above about seven, I stop pretending and treat the day as a meeting day: no block, no personal task list, and the shutdown note becomes a plan for the next clear morning. Two of those days a week is a calendar problem, not a routine problem.
More in Routines
Routines
A First Day Back Routine After a Week or More Off
You come back from ten days off feeling rested, open your laptop at nine, and by eleven you feel worse than you did before the...
Routines
A Ten Minute Warm-Up Routine Before Deep Work Sessions
You sit down for the two hours you blocked out for real work, open the document, and twenty minutes later you have answered...
Routines
A Weekend Morning Routine That Keeps Saturday Useful
Saturday starts with good intentions and somehow it is 1 p.m., you are still in yesterday's hoodie, and half the day has gone...