Distributed teams describe their difficulty in terms of being far apart. The constraint that actually determines how they work is how many hours of the day they are awake at the same time.
Overlap is the resource being consumed
Anything requiring immediate exchange, such as resolving an ambiguity or making a decision with several people, can only happen during shared hours.
As separation increases, those hours shrink, and the demand for them does not, so the overlap fills with meetings and leaves nothing for spontaneous conversation.
Teams several hours apart therefore experience a schedule that feels more congested than a co-located one despite having the same total working time.
Question latency compounds through dependencies
A question asked outside the overlap waits until the next one, which converts a two-minute clarification into a delay of most of a day.
Where the answer prompts a follow-up question, the exchange takes two days, and a task with three such dependencies stretches across a week.
The work itself was never slow. The time was spent waiting, which is why activity reports and elapsed schedules diverge so sharply on distributed teams.
The cost of overlap falls unevenly
Someone must adjust their hours to create shared time, and the burden is usually carried by whichever location is furthest from the company's centre.
Persistent early or late meetings for the same group become an attrition problem, and it is often read as a cultural fit issue rather than a scheduling one.
Rotating the inconvenience distributes it, which is less efficient for the majority and considerably more sustainable for the minority.
Written communication substitutes for overlap
Work described in enough detail to be picked up without a conversation removes the dependency on shared hours entirely.
That requires more effort from the person writing, since the reader cannot ask a follow-up question until the next day.
Teams that adopt this genuinely find distance largely irrelevant; teams that adopt it partially get the writing overhead without the benefit, because the important decisions still happen in calls.
Hiring decisions set the constraint permanently
Every hire in a new region changes the overlap structure for everyone else, and the effect is easy to underestimate during recruitment.
Companies that hire across many time zones without deciding how the team will work usually end up with a schedule dictated by whoever joined first.
Those that define acceptable overlap bands before hiring accept a smaller candidate pool in exchange for a team that can still coordinate.