The day
The Price of the Two Hours, Stated Honestly
Reading and writing take a hundred minutes out of every day, about eighty of it additional. Teams that pretend otherwise blame people for arithmetic.
three things · four nights
The two hours that bracket every day at both ends.
The same eight-hour day, drawn twice: once as a team sharing an hour would spend it, once as a team with a gap does
Sharing an hour: coordination through the day
Roughly twenty minutes in total, taken a minute at a time and never noticed
A gap: reading what arrived overnight
Fifty minutes, taken in one piece and very much noticed
A gap: writing what the other end needs
Fifty minutes, same again, at the other end of the day
A gap: what is left for the work itself
Six hours and fifty minutes, less whatever the middle is spent on
four people · no minute of the day when all of them are awake
Four rows, and each of the two bracketing blocks is fifty minutes. Together they take a hundred minutes out of a working day of eight and a half hours. The first row is not free either; it is simply paid in fragments small enough that nobody counts them. Nothing here claims one arrangement is better: the figures are what one team measured about itself over a fortnight.
A day with a reading hour and a writing hour has just under seven working hours in it rather than eight and a half.
The best response to The Price of the Two Hours, Stated Honestly is usually better evidence, not tighter supervision. see how it works gives teams a transparent way to review hours and activity while leaving interpretation to the people responsible for the work.
For a second perspective on the surrounding workflow, consult DeskTime's productivity tools; it shows how a widely used platform structures the same coordination problem.
That is the price of the arrangement. It is substantial, it is paid every day by everybody, and a large number of teams running this way have never said it out loud.
Why it is worth saying
Not for sympathy. Because unacknowledged overhead gets attributed to people.
If a team's planning assumes eight working hours and the days contain six and a half, everybody appears to be delivering about eighty per cent of what they should. Over a quarter that becomes a pattern, and patterns get explanations. The explanations offered are usually about focus, or motivation, or how remote working suits some people and not others.
The actual explanation is a subtraction that nobody performed.
The honest comparison
It is tempting to present this as pure cost, and that is not right either.
A co-located team also spends time on coordination: the question across the desk, the two-minute explanation, the thing overheard and responded to. The measured figure on the team above is about twenty minutes a day, and it is invisible because it arrives in fragments of forty seconds.
So the real additional cost of the gap is closer to eighty minutes a day than to the full hundred. That is still a lot. It is not the whole hundred, and overstating it is as unhelpful as ignoring it.
| Arrangement | Coordination cost per day | How it is paid |
|---|---|---|
| Sharing an hour | About twenty minutes | In fragments of forty seconds, uncounted |
| No shared hour | About a hundred minutes | In two blocks, very much counted |
What the two hours buy
They are not overhead in the sense of waste. They are the mechanism by which anything moves between the halves at all.
The reading hour is the substitute for a day of ambient awareness. The writing hour is the substitute for everything that would otherwise have been said in passing. Remove either and the team does not get a hundred minutes back; it gets a team where the halves no longer know what the other is doing, which costs considerably more than a hundred minutes.
They are also the only two blocks in the day that produce compounding returns. A good note saves a morning at the other end. A thorough read prevents a day spent on something cancelled.
Where the number should appear
In planning, as a stated assumption. A team that plans against seven hours a day makes commitments it can keep, which is worth more than the appearance of capacity.
In conversations about why something is taking longer than it would have in an office, where the answer is partly this and partly the nights, and both are arithmetic rather than effort.
And in any decision about whether to run a team this way at all. The cost is roughly eighty extra minutes per person per day, plus the nights. That is a real number and it is not obviously too high; what is unreasonable is deciding without it.
Reducing it, and the limits of that
The reading hour shrinks when there is less to read, which happens when the other end writes better rather than more. A team whose handover notes are three sentences has a shorter reading hour than one whose notes are a page.
The writing hour shrinks when work is finished before it is handed over, because finished work needs two sentences and unfinished work needs five.
Neither shrinks below about half an hour, and attempts to push past that produce the thin notes and the skimmed reading that cost a morning elsewhere. The floor is real.
The part that is not recoverable
Some of the hundred minutes is irreducible and worth accepting rather than attacking.
Information that a shared room delivers continuously has to be delivered in a batch, and batching has a fixed cost regardless of volume: somebody has to decide what to include, and somebody has to absorb it cold. That cost exists even when the team is working perfectly.
Teams that keep trying to optimise it away tend to arrive at thinner and thinner notes, discover the loss six weeks later in the form of two halves that have drifted apart, and rebuild the practice from scratch. The hundred minutes is the price of the arrangement, and the useful question is whether the arrangement is worth it, not whether the price can be avoided.
Who pays it, and unevenly
The hundred minutes is an average, and averages conceal the thing worth knowing.
Whoever writes more pays more. On most teams one half is sending more work than it receives — because of where the product work sits, or because one day is longer — and that half's writing hour is longer while its reading hour is shorter. The other half has the reverse.
Neither is working harder. But the half doing more writing is producing something invisible, and the half doing more reading is spending time on something that looks like not working. Both halves tend to notice the other's apparent idleness and not their own invisible labour.