How remote teams work across time zones

A team in one office shares a clock. Everyone arrives, works and leaves inside roughly the same nine-to-six, so the whole day is available for a quick question, an unplanned chat, a meeting called on ten minutes’ notice. Spread the same people across continents and that shared clock is gone for good. You cannot get it back by trying harder or by scheduling more cleverly. The planet is simply turned the wrong way. The teams that make distributed work well are the ones that stop fighting this and design the work around it instead. The scarce overlap is not the problem to be solved; it is the constraint you build on.

The overlap problem gets worse fast

It is tempting to think of time-zone spread as a gentle gradient, a bit awkward at three hours, twice as awkward at six. It does not behave that way. Overlap between two people’s working days shrinks slowly at first and then falls off a cliff. Two colleagues keeping a normal day a few hours apart still share most of an afternoon. Push them to eight or nine hours apart and the shared band narrows to an hour or two at the very edges of each day; push a little further and it disappears entirely, with one person’s morning landing squarely in the other’s night.

The effect compounds as you add people. A pair can almost always find a shared hour; a third colleague, placed far enough away, can wipe out the window that worked for the other two. This is why a growing distributed team so often feels like it got harder to coordinate overnight, not because anyone got worse at their job, but because one new hire in the wrong zone quietly removed the last slot where everyone was awake at once. You can see exactly where a team stands by laying the cities side by side on the meeting planner, which shades the hours that fall inside everyone’s working day, or by checking the raw time difference between the two people who sit furthest apart. Once you accept that the overlap is small and getting smaller, the design question answers itself: the work cannot depend on everyone being online together.

Make writing the default, meetings the exception

The single change that makes distributed work possible is reversing the default. In a co-located team, talking is the normal way things happen and writing is the overhead you add when you must. Async-first teams flip that: a clear written message is how work moves by default, and a live meeting is the exception you have to justify. A proposal is a document, not a pitch in a call. A decision is recorded in text where anyone can find it, not settled verbally and half-remembered. A status update is something each person reads at the start of their own day rather than sits through at the start of someone else’s.

This is not a fringe idea. Companies like GitLab, Automattic, the makers of WordPress, and Zapier have run for years as distributed, async-first organisations with the habit written into how they operate, precisely because they were spread across too many zones to lean on meetings. The discipline it takes is real: writing a thing down well is harder in the moment than saying it, and it front-loads the effort onto the author. But it pays that effort back many times over. The written version does not need everyone in the room, it does not evaporate when the call ends, and it can be read, questioned and acted on by a colleague who was fast asleep when it was written. Favour the message that survives the night over the meeting that needs the night to be shared.

The follow-the-sun handoff

Once writing is the default, a genuinely useful pattern becomes available that a co-located team can never have: the handoff. When two halves of a team sit far enough apart, one side’s working day begins roughly as the other’s ends. Instead of treating that as a coordination failure, you treat it as a relay. The first side leaves the work in a state the second can pick up, a written summary of what moved, what is blocked and what to look at next, and the second side carries it forward while the first sleeps, then hands it back. Work on the shared thing never fully stops; the planet keeps a shift going around the clock.

A handoff like this lives or dies on the quality of what gets written down. A vague note forces the next person to wait a full day for a clarification, which defeats the whole arrangement; a precise one lets them start immediately. So the habit that makes async meetings bearable, recording decisions and state in clear text, is the same habit that makes follow-the-sun fast. For teams that are genuinely far apart, this is often quicker than synchronous work would be, because nobody is ever blocked waiting for the next painful overlap window to come around.

Norms that keep it fair

Designing around low overlap only stays humane if a few norms hold. The first is a small agreed window of core collaboration hours, a couple of hours a day that the team keeps free for the things that really are faster live. It works only when it is chosen honestly, sitting inside a reasonable slice of everyone’s day rather than being a polite fiction that happens to fall at 10pm for one unlucky person. When no such window exists for the whole group, that is a signal to split into regional overlaps rather than to pretend.

The second norm is that decisions are recorded in text, not sealed in whichever meeting happened to have quorum. If a choice can only be understood by the people who were on a particular call, everyone in the wrong zone is structurally shut out of their own team’s thinking. The third is rotation: when a live call genuinely cannot suit everyone, the discomfort of the early start or the late evening moves around rather than always landing on the same easternmost or westernmost colleague. And the last, quietest norm is simply respecting people’s nights, not expecting a reply at what is plainly the middle of someone’s sleep, and remembering that the gap between two places shifts by an hour when one of them changes its clocks for daylight saving and the other does not. A quick look at the world clock before firing off a message tells you whether the person you are about to ping is at their desk or in bed. The practical mechanics of picking fair times are worth their own treatment, which the companion guide to scheduling meetings across time zones covers in detail. Get these norms right and low overlap stops being a daily friction and becomes just the shape of the team, something you designed for on purpose, not something you fight every morning.