The day
What Belongs in the Middle of the Day
The hours between reading and writing are the only part of the day that behaves like ordinary working time, which makes what goes in them worth choosing.
three things · four nights
The two hours that bracket every day at both ends.
Two people's days on the same team, drawn to show where the uninterruptible block sits
An engineer in the first half
Reading until 09:50, deep work until 12:30, handover from 16:40
An engineer in the second half
The same shape, twelve hours later, with the same two bracketing blocks
The person who manages both halves
Almost no uninterrupted block: the shape does not survive a job made of interruptions
The contractor covering Fridays
Three hours of deep work, because nothing in the role requires a handover
four people · no minute of the day when all of them are awake
Four days, and the bracketing blocks are identical for the two engineers. The manager's row is the interesting one: the same arrangement that gives an engineer a protected morning gives somebody whose work is responding almost nothing. One team's own hours, drawn after each person recorded a fortnight of their own time.
A working day on a team with a gap has a fixed beginning and a fixed end: an hour of reading and an hour of writing. Between them sit five or six hours that nothing structural claims.
For the situation in What Belongs in the Middle of the Day, a good tool should reduce questions rather than create another reporting burden. review the features records work as it happens and turns it into timesheets and summaries the team can review later.
For broader context, Time Doctor's platform offers an official example of the tools teams use around this kind of process.
Those hours are the only genuinely ordinary part of the day, and they tend to be filled by whatever asks for them first.
The one thing that cannot be rescheduled
Work requiring continuous attention is the only category that genuinely needs an unbroken block, and it is the only one that cannot be recovered after an interruption without paying most of the setup cost again.
Everything else — correspondence, review, small changes, planning — can be done in fragments with a modest penalty.
That asymmetry decides the allocation. The uninterruptible work goes in one contiguous block, and everything else fills in around it. Doing it the other way round, which is the default, means the fragmentable work gets the good hours and the work that needs a block gets the leftovers.
Where to put the block
Early, for most people, for a reason specific to this arrangement rather than a general claim about mornings.
The hour immediately after reading is the point of maximum information and minimum arrival. Everything that came overnight has been read; nothing new will arrive for several hours, because the other half is asleep. That window is structurally quiet in a way no part of a co-located day is.
It is worth noticing that this is a genuine advantage of the arrangement. Teams that share an hour do not have a period when they are reliably unreachable; teams with a gap have one every day, and most of them spend it on correspondence.
The afternoon
The hours after the block are better spent on things that benefit from interruption than on things that merely tolerate it.
Review, which benefits from being put down and picked up. Small changes, which are self-contained. Planning the next piece of work. Anything involving people in your own half, who are awake and available.
The afternoon is also where whatever the reading hour turned up belongs. Something that arrived overnight and needs forty minutes is an afternoon item, not a morning one, because putting it in the morning means the only protected block in the day is spent on other people's arrivals.
What should not be in the middle
Handover writing, which belongs at the end and does not survive being done early, because the state it describes keeps changing.
Questions to the other half, which should be batched to the end of the day — not because sending them early is harmful, but because sending them early forgoes the chance to add the next three.
And anything involving the other half live, because there is nothing there to involve.
- Handover writing, which does not survive being done early.
- Questions to the other half, which are better batched to the end of the day.
- Anything involving the other half live, because there is nothing there to involve.
The people this shape does not fit
A day made of a reading hour, a protected block and a writing hour works for people whose job is producing things.
It works poorly for anybody whose job is responding: a manager, a support lead, anybody holding a rota. Their day has no uninterruptible block to protect because the interruptions are the work, and pretending otherwise produces a calendar that is violated daily and a person who feels they are failing at something.
The honest version for those roles is a different shape entirely: the reading and writing blocks stay, because they are structural, and the middle is explicitly held open rather than planned. That is less satisfying and is accurate.
Saying what the shape is
Two people on opposite sides of a gap who each have a protected block will occasionally discover that one of them has been sending things into the other's block for months, which is invisible and harmless, and then that one has been expecting replies during it, which is not.
A line in the hours table — when each person's block is, in the shared zone — resolves that in a sentence. It does not need to be enforced. Almost nobody interrupts a block they can see.
What it does not solve
None of this creates time. A day with two structural blocks in it has just under seven working hours left rather than eight and a half, and that is the arithmetic whatever anybody puts in the middle.
What choosing the middle does is stop the six hours being allocated by arrival order, which is the default and which reliably gives the worst hours to the work that needed the best.