How Much Overlap Does a Distributed Team Actually Need?

A distributed team needs enough overlap to make decisions together and almost none for anything else. In practice that is two to three hours per seam per week, concentrated rather than sprinkled. Teams that feel starved of overlap are usually not short of hours. They are spending the hours they have on information transfer that could have been written down once and read by everyone.

"We keep adding early calls because two hours of overlap is not enough."

The instinct is understandable and the remedy is usually wrong. Adding an early call does not create overlap, it relocates someone's morning. And the new hour immediately fills with the same content as the old one, because the content was never the problem.

The number, and why it is smaller than you think

Overlap is expensive in a way that hours on a calendar do not show. A 07:00 call in Amsterdam to meet Singapore costs the Amsterdam side a normal morning and the Singapore side a normal evening. It is charged to people's lives, not to a budget, which is exactly why it grows unchecked.

Set the budget deliberately instead. Two to three hours per seam per week is enough for a team that writes things down, because the only thing that truly requires simultaneity is a conversation where the outcome depends on real-time back and forth. That is a much narrower set than most calendars imply.

What overlap is actually for

Three uses justify a shared hour.

• Decisions with real trade-offs. Where the right answer emerges from argument rather than from information. Live time genuinely converges faster here.
• Disagreements. Tension resolves badly in writing and well in a voice. Do not do this async, and do not do it in a channel.
• Relationships. The reason people extend each other the benefit of the doubt at 23:00. Cheap to maintain, expensive to rebuild.

Status is not on that list. Neither is "what was decided last week". Both are questions with a single correct answer that exists somewhere in the record, and using a shared hour to speak them aloud converts your scarcest resource into your least valuable output. This is the whole argument in replace the status meeting, keep the status.

The practical consequence is that status and "what was decided" should need no overlap at all. That is what StandIn is for: each person spends ninety seconds at the end of their day on a brief, and while they are off, their StandIn answers questions from it, in their words, with a source under every answer. The asker in the next zone does not wait for a shared hour, and the shared hour you keep gets spent on the decision that actually needed everyone awake. See working across time zones.

Audit your current overlap in two weeks

Do not reason about this in the abstract. For two weeks, label every minute of live cross-zone time with one of four tags: decision, disagreement, relationship, or information transfer. One line per meeting, filled in by whoever called it.

Tag	Keep it live?	If not, what replaces it
Decision	Yes	Nothing, this is what overlap is for
Disagreement	Yes	Nothing, and do it sooner
Relationship	Yes, sparingly	Fewer, longer, less frequent
Information transfer	No	A written brief anyone can read or ask

Two weeks of honest tagging usually shows that half or more of live cross-zone time is information transfer. That is your overlap budget, already paid for, currently being spent on the one thing that did not need it.

The overlap question in hiring

Overlap requirements in job adverts deserve more scepticism than they get. "Four hours of overlap with CET" narrows your candidate pool sharply and is often a proxy for "our status flow is verbal". If the requirement exists because decisions happen live, say that, and say which hours. If it exists because nobody writes anything down, fix the writing and widen the pool.

The honest version of the requirement is a range plus a reason: "two hours of overlap with CET on Tuesdays and Thursdays for decision reviews". Candidates can plan around that. "Significant overlap" means an unbounded claim on someone's evenings, which is the thing working-hours agreements exist to prevent.

When you genuinely need more

Some situations justify a temporary increase: an incident, a launch week, a new pairing that has not built trust yet, or a genuinely contested architectural decision. All four are bounded. Set an end date when you add the hours, and hold it.

The pattern to avoid is permanent overlap added during a crunch and never removed. That is how a team ends up with a 07:30 standing call that nobody remembers the reason for, at an hour nobody would agree to if asked fresh. If you are already there, the cheapest intervention is to cancel it for two weeks and see what actually breaks. Usually the answer is nothing, and the questions it was absorbing turn out to have written answers.

Common Questions

Is four hours of overlap a reasonable requirement?

For most roles, no. Four hours means one side of the seam permanently works a shifted day. It is reasonable for a role whose job is genuinely synchronous, such as live support or incident command, and unreasonable as a default for engineering, product, or ops work that is mostly independent.

Can a team work with zero overlap?

Yes, for execution, and it is hard for decisions. Zero-overlap teams tend to work well when authority is pushed down so decisions do not need to cross the seam at all. If every choice needs a shared hour you do not have, the constraint is not the time zones, it is where the authority sits.

Should the overlap hour be at a fixed time?

Yes. A fixed, protected slot beats a floating one, because people can build their lives around it. A floating slot means everyone keeps a wide window mentally reserved, which costs more than the meeting does.

How do we handle urgent questions outside overlap?

Separate urgent from unanswered. Genuine urgency needs a named person reachable by an agreed channel, and that should be rare and compensated. The much larger category is questions that feel urgent only because they are unanswered, and those need a record that can answer them, not a person who is awake.