How much overlap a team actually needs
Teams either demand far more shared hours than the work requires, or none at all. Both are decisions made without arithmetic.
Overlap — the window in which everyone is working at once — is the central variable in a distributed team. It determines who can be hired, how fast decisions move, and how much of the day belongs to interruption. For broader context on planning work across time zones, Timeanddate Meeting Planner is a useful reference.
Most teams never calculate it. They either insist on core hours copied from an office schedule, or they hire across twelve zones and discover the cost afterwards.
Work out what genuinely needs to be synchronous
List the activities that actually require two or more people at the same moment: pair work, difficult conversations, the meetings that survived the audit, incident response. For a practical software-side reference on recording overlap and project time, this resource adds useful detail.
Total the hours per week. For most teams the honest answer is small — two to four hours a day is generous, and a great deal of work that feels synchronous turns out not to be.
Four hours of overlap is four hours in which interruption is acceptable. Outside it, focused work is possible. Teams that treat the whole shared window as available for calls have no focus time at all.
Three viable models
- High overlap, four hours or more. Feels closest to co-located working, and restricts hiring to a narrow band of longitudes.
- Low overlap, one to two hours. Requires genuine async discipline and opens hiring across most of the world. The overlap is reserved for the things that truly need it.
- No overlap, follow-the-sun. Only workable with strong written handover, and it is a different operating model rather than a variation.
None is better in the abstract. What causes trouble is running one model while believing you are running another — typically a team with ninety minutes of overlap trying to operate as though it had six.
Protect the overlap for what needs it
Where overlap is scarce it should be reserved deliberately. Filling it with status meetings means the genuinely synchronous work — the difficult conversation, the design discussion — has nowhere to go.
A simple rule works: nothing gets scheduled in the overlap window unless it cannot be done async. Everything else moves outside it or becomes written.
Count the cost before hiring outside the band
Adding someone eight hours away is a real decision with a real price: slower feedback loops, an overlap window that shrinks for everybody, and a person who will be structurally less present in decisions unless the team changes how it works.
That can be entirely worth it, and it should be a decision rather than a discovery. The failure mode is hiring across the world and continuing to operate as though everyone were in one band.
Publish everyone's hours
A visible list of who works when, in their own local time, removes an enormous amount of low-grade friction. It stops people guessing, it stops calls being scheduled into someone's evening by accident, and it makes the constraint visible to whoever is planning.
Include the shape of the day, not just the zone: someone who starts at seven and finishes at three is available at very different times from someone in the same city who starts at ten.