Distributed teams are usually discussed in terms of geography, but geography only matters through one variable. What constrains the team is the number of working hours its members share.
Overlap converts questions into answers
A question asked inside the overlap window gets answered in minutes. The same question asked outside it waits for the next window, which may be the following day.
Most work contains a steady stream of small blocking questions. Each one is trivial in isolation, and each one costs either minutes or a day depending on timing.
Multiply that across a team and the difference between six hours of overlap and two is not a matter of comfort. It changes the achievable pace.
Dependency chains multiply the delay
When one person waits a day for an answer and then a third person waits a day on them, a two-step chain costs two days of elapsed time.
Longer chains compound quickly, and the compounding is invisible in any individual's calendar. Everyone stays busy while the work itself moves slowly.
This is why splitting a tightly coupled workflow across distant zones tends to disappoint, even when every individual on it is productive and well managed.
The fix is boundary placement, not more meetings
Teams that work well across zones usually divide responsibilities so that dependencies run inside a zone rather than across it. The split follows the seam in the work.
Where a genuine handoff must cross zones, it is defined tightly enough to travel as a written artefact rather than as a conversation that needs both parties awake.
Adding synchronous meetings to bridge the gap generally makes things worse, because the meetings land at hours that suit one side and erode the other.
Rotating the inconvenience does not remove it
Companies often rotate meeting times so that no single region always takes the unsociable slot. This distributes the cost more fairly without reducing the total.
People attending at the edges of their day participate less and retain less, so the meeting produces a weaker shared understanding than the attendance list suggests.
Decisions made in those meetings tend to get relitigated later, which is a second cost that rarely gets traced back to the scheduling arrangement that caused it.
Hiring policy is where the constraint is actually set
Every hiring decision fixes a set of overlap windows for years. A single hire far outside the existing band can reshape how an entire team communicates.
Companies that treat location as a neutral detail in hiring end up with an accidental structure, then attempt to manage around it with process and tooling.
Treating overlap as an explicit hiring criterion is far cheaper, and it leaves the widest possible talent pool inside whatever band the work genuinely requires.