Managing time zones for remote teams

Scaling a team across more than three time zones forces real decisions: about what gets discussed live vs. async, about who pays the time-zone tax for any given meeting, and about whether your tooling does the math or makes humans do it.

The math problem

Two teammates in adjacent zones share 7+ hours of overlap. Two teammates 12 hours apart share zero. Most distributed teams are somewhere in the middle — 4-6 zones, 2-4 hours of practical overlap. That overlap window is your only true synchronous space, so you have to choose what to spend it on.

The async-first default

Cultures like GitLab, Doist, and Buffer don't treat async as a fallback — it's the default. Sync is reserved for things that need real-time interaction: hard decisions, debugging, relationship-building. Everything else (status, planning, document review) defaults to written, with a 24-hour read window.

This sounds rigid until you try it. The actual outcome: meetings drop 60–80%, decisions get documented, and the team in Manila stops getting woken up at 6 AM.

Scheduling tactics that work

Anchor on the smallest overlap. Don't pick a time that works for the majority — find the shortest overlap window between any two people, and start there.
Rotate the pain. If someone has to take a meeting outside normal hours, alternate weeks. Don't let it always be the Sydney team eating 11 PM calls.
Use the 9-to-6 rule. Most knowledge workers are willing 9 AM to 6 PM local. Extending the upper bound by an hour doubles the number of available slots.
Don't schedule across borderline DST weeks. Recurring meetings break twice a year. Pick a clearly-spring or clearly-fall date instead.

Tooling that pulls weight

Calendly and Doodle assume everyone's in your time zone or close. For multi-zone teams, you want:

A world clock open in a tab so you can glance at “is the Tokyo office still up”
A meeting planner that visualizes overlaps so you don't accidentally pick a 6 AM slot
Slack/Discord status that shows local time, not just availability
Calendar invites that include local times for every attendee, not just the organizer's

Three patterns to copy

The follow-the-sun handoff. Each region works on the same project for 8 hours, hands off at end-of-day to the next region. Used by Atlassian for support, GitLab for incident response.
The rotating overlap meeting. One weekly hour where every region attends — but it rotates through everyone's zone over a 6-week cycle, so no one always loses sleep.
The async standup. No daily call. Each person writes 3 lines in a thread by their morning: yesterday, today, blockers. Anyone can ping for a sync if needed.