The day
The First Hour: Reading What Arrived Overnight
The first hour of a day on a team with a gap is for reading. Treating it as a warm-up rather than as the hour that sets the day is the standard expensive error.
three things · four nights
The two hours that bracket every day at both ends.
One person's day, drawn to show what each part of it is actually for
Reading what arrived overnight
Not a warm-up and not email; it is the only moment the day can be planned with full information
Work that needs continuous attention
The largest block, protected because it is the only one that cannot be broken up
Afternoon work and whatever the morning turned up
Interruptible, and deliberately so
Writing what the other end needs
The handover, and the block most often eaten by the day running over
four people · no minute of the day when all of them are awake
Four blocks, and two of them exist only because of the gap. The first and the last are not overheads in the usual sense; they are the mechanism by which work moves between two halves that are never awake together. Nothing here is prescribed for anybody else: it is one person's own day, drawn after a fortnight of watching where the time actually went.
On a team with no shared hour, a working day begins with a backlog that accumulated while you were asleep. Nothing in it is new to the people who sent it; all of it is new to you.
A task can look idle simply because nobody sees the part completed in another time zone. open the product page makes that work history available and gives the discussion in The First Hour: Reading What Arrived Overnight a more reliable starting point.
Teams comparing established approaches can also review ActivTrak's workforce analytics for a practical example from a widely used product ecosystem.
That first hour is not a warm-up. It is the only point in the day when the day can be planned with complete information, and it is routinely spent on whatever arrived last.
What the hour is for
Three things, in order.
Finding out what changed. What was decided, what broke, what finished, what was handed over. This is the state of the world, and acting without it is how people spend a morning on something that was cancelled yesterday evening.
Finding out what is wanted from you. Which of the overnight arrivals need something, by when, and from whom specifically. Most of them do not, which is worth establishing early.
Deciding what the day is. The plan made last night was made without any of the above. Revising it deliberately, once, is much cheaper than having it revised for you four times before lunch.
- Finding out what changed: what was decided, broke, finished, or was handed over.
- Finding out what is wanted from you, by when, and from you specifically.
- Deciding what the day is, once, with all of the above in front of you.
Reading everything before doing anything
The discipline that makes the difference is finishing the reading before starting the work.
The instinct is the reverse: open the first item, deal with it, open the second. That produces a day that is ordered by the arrival time of other people's messages, which correlates with nothing. The important thing is as likely to be last as first.
It also produces double handling. Something answered at nine turns out at half past to be superseded by something else that arrived at eleven the previous night.
Reading first costs the forty minutes once. Reading as you go costs the same forty minutes plus the work that gets done twice.
Not answering while reading
A related and harder discipline: read without replying.
Replies written during the reading pass are written without the context of what has not yet been read. On a team with a gap, each one costs a night, so a reply sent at 09:10 that turns out to be wrong at 09:40 has already left.
Marking things to answer and answering after the pass is finished takes no extra time and produces materially better answers. It is difficult to do, because answering is satisfying and reading is not.
The things that are not in the backlog
The hour has a second purpose that is easy to miss: noticing absences.
Something you expected that did not arrive. A question you asked two days ago that has not been answered. A piece of work that should have moved and has not.
Absences do not announce themselves, and on a team sharing a room they do not need to, because the person is visible. Across a gap, a thing that silently did not happen can go unnoticed for a week, and the hour spent reading is the only point at which anybody is looking at the whole picture and might notice.
A short standing list of what you are waiting on, checked during this hour, catches nearly all of it.
Where it goes wrong
Three failure modes, all common.
The hour becomes general correspondence. Everything that arrived gets dealt with, including the things that need nothing, and the hour becomes ninety minutes of administration that leaves no plan behind.
The hour gets interrupted by a meeting. Anything scheduled in the first hour of the day on a team with a gap is scheduled at the one time when nobody present knows what has happened. Meetings at that hour produce decisions made in ignorance.
The hour gets skipped on busy days, which is precisely backwards. Busy days are when the plan matters most and when the overnight arrivals are most likely to have changed something.
What it costs and what it buys
Forty minutes to an hour, every working day. Over a week that is most of a morning, and it is worth being honest that this is real time and not free.
What it buys is a day whose shape was chosen rather than inherited. On a team sharing a room, the equivalent information arrives continuously and for nothing: somebody says it, you overhear it, you see the person is not at their desk. A gap removes that channel entirely, and the reading hour is what replaces it.
It is not a substitute of equal quality. It is slower, it is incomplete, and it only happens once a day rather than continuously. It is simply the best thing available, and the teams that do it deliberately lose less than the teams that do it by accident at eleven.