Running a Team Across Five Time Zones

The hardest part of distributed engineering is not the tooling. It is that most management habits were built in a room where you could turn your chair around and ask a question. Move that team across five time zones and the same habits quietly turn into a queue.

Write things down, unreasonably

A decision that only exists in a call did not happen for the half of the team who were asleep. Decisions, context and reasoning go in writing — not because writing is pleasant, but because it is the only artefact that works in every time zone.

Protect the overlap ruthlessly

Most distributed teams have two or three hours of genuine overlap. Spending it on status updates is arson. Status goes in writing; overlap is for the things that genuinely need a conversation — disagreements, design debates, and the human parts.

• Default to async; escalate to a call when the thread turns into disagreement
• Record the call, post the decision, never the whole transcript
• Rotate the inconvenient meeting hours so the same region is not always paying

That last one matters more than people expect. If one office always takes the 10pm call, you are not running a distributed team — you are running a headquarters with satellites, and your best remote engineers will eventually notice.