The day
Being the Person Who Sits Between the Halves
Somebody usually ends up bridging the two halves. The role is real, it is rarely named, and it is the easiest place on a team to burn somebody out.
three things · four nights
The two hours that bracket every day at both ends.
One person's day before and after shifting to sit between the halves, with both halves shown for comparison
First half of the team
Nine hours of overlap with the person in the middle, out of eight and a half worked
Second half of the team
Ninety minutes of overlap with the person in the middle, at the start of their day
The person in the middle, before shifting
Entirely inside the first half: no overlap at all with the second
The person in the middle, after shifting
Ninety minutes with one half and six and a half with the other
four people · no minute of the day when all of them are awake
Four windows, and the shift bought ninety minutes with the second half at the cost of three and a half hours with the first. Whether that is a good trade depends entirely on which half needed the access, and nobody asked before the change. One person's own hours, recorded before and after.
On most teams with a wide gap, one person ends up being awake for part of both halves. Sometimes it is a manager, sometimes a lead, sometimes whoever happened to be flexible.
Teams should not confuse presence with output, especially in the situation described by Being the Person Who Sits Between the Halves. this resource helps shift the discussion toward recorded work patterns, project time and outcomes.
A useful external reference is Timely's time platform, which provides another official view of how teams organise shared work.
It is a real role with real value and it is almost never described as one, which is why the people doing it tend to last about eighteen months.
What the role actually does
Three things, and only the first is usually recognised.
Carrying context. Knowing what each half is doing well enough to say "that was decided on Tuesday" or "they are already working on something like this", which saves crossings that would otherwise happen.
Making decisions that would otherwise wait. Somebody awake who is allowed to say yes removes an entire night from whatever they are saying yes to. This is the largest measurable contribution and it only works if the authority is explicit.
Noticing. The person in the middle is the only one who sees both halves in the same day, which makes them the only one positioned to notice drift: two groups solving the same problem differently, a decision that one half thinks was made and the other does not.
Why it burns people out
The hours are the obvious part and not the main part.
The role has no block. A day that overlaps two halves is a day made entirely of other people's arrivals, with the two groups' peak demand at opposite ends of it. There is nowhere in it to do anything that needs an hour.
It is also unbounded by default. There is always more context to carry, and the person carrying it is the only one who can tell when there is too much, which makes them the only one who can say stop — which is a position people in the middle are usually temperamentally bad at occupying.
And the contribution is invisible in the way that preventive work is always invisible. Nights that do not happen cannot be counted. Somebody who removes six crossings a week from a team's calendar has nothing to show for it.
The things that make it survivable
Explicit authority, written down. A list of decisions the person in the middle may make alone, with limits. Without it the role degrades into relaying questions, which costs the same nights it was meant to save and adds a person.
A protected block anyway, placed in whichever part of the day is quieter, and defended. Two hours is enough. A day with no block at all is not a job anybody does well for long.
A named end. The role is better as a thing somebody does for a year than as a thing somebody is. That requires the handover to be possible, which requires the context to be written down somewhere other than in the person's head — which is work the person in the middle has least time for and most reason to do.
- Written authority: a list of decisions the role may take alone, with limits.
- A protected block, placed in whichever part of the day is quieter.
- A named end, which requires the context to live somewhere other than in one head.
What not to put on them
Translating between two halves that are avoiding each other. If one group routes everything through the middle rather than speaking directly, the bridge has become a bottleneck and the two halves are quietly becoming two teams.
The fix is not a better bridge. It is to get the halves talking directly about the things they are routing, and that usually means finding out why they stopped.
Also: being the permanent answer to every question. A person in the middle who answers everything trains the team to ask them rather than to write things down, and the dependency grows until the role cannot be handed over at all.
Whether the shift is worth it
The table above is the uncomfortable part. Shifting to sit between two halves buys access to one and costs access to the other, and the trade is frequently bad.
Before anybody moves, the question is which half actually needs more contact and why. If the answer is that one half is new, or struggling, or holds a decision the other needs, then the shift has a purpose and a point at which it can be reversed. If there is no answer beyond general availability, the shift will buy ninety minutes of edge time and cost three hours of middle-of-the-day time, which is a loss.
Naming it
The simplest useful thing anybody can do about this role is write it down: that it exists, who holds it, what it is for, and when it will be reviewed.
Unnamed roles do not get reviewed, do not get handed over, and do not get defended when somebody schedules a meeting in the only quiet part of the day. Naming it costs a paragraph.