Time Zones: Designing for Overlap Instead of Hoping for It

Distance is not the problem in distributed work. Time is. A colleague four hours away might as well be on another planet if your working days share ninety minutes.

The three patterns

Co-located hours. Everyone within roughly three hours. The team behaves almost like a co-located one: synchronous discussion is available most of the day, decisions can be made in a call.

Partial overlap. Four to six hours apart. Real overlap exists but is scarce, so it has to be protected and spent deliberately.

Follow-the-sun. Eight or more hours apart, effectively no shared working time. Requires genuinely asynchronous operation.

Each is workable. Problems come from running one pattern with the habits of another — most commonly a partial-overlap team behaving as if it were co-located, and burning its entire overlap window on status meetings.

Design decisions that matter

Decide the maximum spread before you hire. "Anywhere in the world" sounds generous and produces teams that cannot function. A stated band — for example, within four hours of a named anchor zone — is a constraint you can hire against and a promise you can keep.

Name the anchor. Which zone is the reference for deadlines, meeting times and "end of day"? Unstated, it defaults to wherever the manager lives, and everyone else guesses.

Protect the overlap. In a partial-overlap team the shared window is the scarcest resource you have. Do not spend it on updates that could be written. Spend it on decisions, disagreements and anything requiring back-and-forth.

Rotate the pain. If a recurring meeting is inconvenient for one region, rotate the time. A meeting permanently scheduled for someone's evening is a resignation with a delay on it.

What has to become asynchronous

At four or more hours of separation, the following must work in writing or the team stalls:

Status. Nobody should attend a meeting to learn what happened.

Decisions. Written proposal, comment period, decision recorded with the reasoning. The alternative is a decision made in a call that half the team hears about second-hand.

Requests for review. With a stated deadline, because "when you get a chance" across time zones means several days.

Escalation. A defined path for the case where something is blocked and the person who can unblock it is asleep.

The handoff problem

Follow-the-sun arrangements promise continuous progress and usually deliver continuous confusion, because handoffs are done badly.

A usable handoff states what was done, what was not, what is blocked, what the next person should pick up first, and where the current state lives. Written, in a fixed place, in a fixed format.

Teams that treat handoff as a discipline get the benefit. Teams that treat it as a courtesy lose a day per cycle to re-establishing context.

Meeting scheduling in practice

Publish working hours for every person in a shared place, in their local time and the anchor time.

Use tooling that shows overlap rather than doing the arithmetic in your head. The arithmetic is where the errors are.

Set a floor. No meetings before or after defined hours in anyone's local time, and mean it.

Record everything that anyone might reasonably need and could not attend.

Distinguish optional from required. In a distributed team an "optional" meeting held during someone's evening is not optional in practice — attendance signals commitment. Either it matters, in which case schedule it properly, or it does not, in which case do not hold it.

The uncomfortable arithmetic

A team spread across ten hours has no shared working time. It can still succeed, but only as a genuinely asynchronous organisation — with the documentation, decision records and handoff discipline that requires.

Most organisations adopting that spread do so accidentally, one hire at a time, without adopting the practices. That is the failure mode, and it arrives about six months after the hire that broke the band.