What no relay settles
Saying Out Loud That the Gap Is the Problem
Sometimes the arrangement is wrong for the work. Saying so needs evidence nobody collected, because the costs arrive distributed as ordinary friction.
three things · no nights · three that no number of nights settles
Three things, no nights, and no mechanism proposed for any of them.
What one team wrote down before raising the arrangement itself, and what each line was for
A number rather than a feeling, and the first thing anybody asked for
Five of them, listed, with what each had been about
About a hundred minutes a person a day, which nobody had counted before
The most important line and the one with no number attached
four things · three nights · one that no number of nights settles
Four lines, three nights, and the fourth had no figure and carried the most. Three of the four were counts the team already had the raw material for and had never assembled. Nothing here is a benchmark; it is one team's own record, collected over six weeks specifically to have the conversation.
Everything else in this collection assumes the arrangement is fixed and asks how to work inside it. Sometimes it is not fixed, and sometimes it should not be.
Managers dealing with Saying Out Loud That the Gap Is the Problem need enough evidence to remove uncertainty without turning the process into surveillance. details are available here supports that balance by pairing employee-controlled tracking with clear reports.
For broader context, BambooHR's HR platform offers an official example of the tools teams use around this kind of process.
Raising that is difficult for a specific reason: the costs of a gap arrive distributed, as ordinary friction, and nobody has ever added them up.
Why it is hard to raise
The gap never causes a visible failure. It causes a week that was slightly worse than it needed to be, fifty times a year.
Anybody who raises it without numbers is making a complaint about difficulty, and difficulty is a subjective report that invites a subjective response. The reply is usually some version of adapting better, which is not unreasonable given the evidence presented.
The arrangement also usually exists for a reason — cost, talent, coverage, an acquisition — and the reason is known to whoever would have to change it. An argument without numbers loses against a known reason every time.
What to collect
Four things, over about six weeks, and the first three are counts whose raw material already exists.
Nights per piece of work. How long things actually took in elapsed time, against how much attention they needed. This is the headline number and it is the one that surprises people.
Decisions that took more than three or four passes. Listed, with what each was about. This shows the pattern rather than the total.
Time spent on handover: reading at the start of the day, writing at the end, per person. Most teams have never counted it and the figure is usually around a hundred minutes.
And the fourth, which has no number: things the team stopped attempting because the arrangement made them impractical. That is usually the real cost and the hardest to evidence, which is why it belongs in words rather than in a table.
| What | Where the raw material already is |
|---|---|
| Nights per piece of work | Whatever tracks the work |
| Decisions taking more than three or four passes | The threads themselves |
| Minutes per day on reading and writing handovers | Nowhere; this one has to be measured |
| Things the team stopped attempting | Nowhere, and it has no number |
How to put it
Not as a complaint and not as a demand.
As a description of what the arrangement costs, with figures, followed by what the options are. The options nearly always include some version of: accept the cost knowingly, reduce the overlap gap by moving or hiring differently, or restructure so that each half owns whole areas and the gap is crossed less.
Presenting options rather than a problem changes the conversation from one about whether somebody is coping to one about what to buy.
The answer may be no
It frequently is, and for reasons that are good.
The arrangement may be cheaper by more than it costs. It may be the only way to have the people the team has. It may be a commitment somebody made that cannot be unwound this year.
A no with a reason is a usable outcome: it means the cost is acknowledged, which changes how plans are made and how people are judged. The worst outcome is not no. It is a conversation that never happens, because then the cost is still paid and is attributed to individuals.
What to ask for if the answer is no
Three things, all cheap, and all of which follow naturally once the numbers are on the table.
Planning that assumes the real figures. Six and a half working hours a day, and elapsed times counted in nights.
A budget for the scheduled hours — the two or three occasions a quarter when two people have to be awake together — accepted in advance rather than negotiated each time.
And an acknowledgement in how people are assessed that one half's work is visible in less detail than the other's.
None of these changes the arrangement. All of them reduce the part of its cost that falls on individuals.
Saying it early
The common pattern is that nobody raises it until somebody is leaving, at which point it arrives as a resignation reason and is heard as one.
Raised early, with figures, it is a piece of operational information. Raised late, it is a grievance. The content is identical and the reception is not, and the difference is mostly whether anybody collected six weeks of ordinary data before they were angry.
Separating the gap from everything else
An argument about the arrangement is weaker when it carries other grievances with it, and stronger when it is narrow.
Teams raising this often fold in everything that is difficult: the tooling, the staffing, the amount of work. Each may be true and each gives whoever is listening somewhere else to look, because the other items have familiar answers and the gap does not.
The disciplined version names only the costs that would disappear if the two halves overlapped, and says explicitly which of the team's problems would remain. That second sentence is what makes the first one credible, and it is the one most likely to be left out.