Running a Team Across 12 Time Zones: What Actually Works
At one point, I had team members in San Francisco, London, Bangalore, Sydney, Tokyo, and Sao Paulo. That's roughly 12 time zones. The math says there's no overlap where everyone is awake. The practice says you find a way.
What Doesn't Work
First, the obvious failure: trying to have one meeting that includes everyone. You can't. Someone will always be at 11 PM or 5 AM. If you do this regularly, you'll lose people — first their engagement, then their job.
Second: async-only purism. "We'll just use Slack and never meet." That works for about three weeks. Then people feel disconnected, projects drift, and you realize that some conversations need a human voice.
What Actually Works
We settled on a rhythm. Not a perfect one — a workable one.
The Overlap Windows
We identified two daily overlap windows:
- London morning / Bangalore evening: 9:00-11:00 AM GMT = 2:30-4:30 PM IST
- London late afternoon / San Francisco morning: 4:00-6:00 PM GMT = 8:00-10:00 AM PST
Tokyo and Sydney joined when they could, but we never required it. Those two windows covered 80% of what needed real-time discussion.
The Handoff Document
Every day, each timezone wrote a 3-paragraph handoff: what they did, what they're doing next, and any blockers. Not a status report — a narrative. "I finished the API integration. Tomorrow I'll test against staging. Blocked on the auth token from the security team." Simple. Human.
This meant someone in Tokyo could pick up where London left off without waiting for a meeting. The document was always current because everyone contributed before signing off.
The "No Meeting Wednesday" Rule
One day a week, no meetings. Anywhere. People used it however they wanted: deep work, catching up on handoffs, or just breathing. It became the most popular rule we ever implemented.
The Mistake I Made
Early on, I tried to rotate meeting times so the pain of early/late calls was shared equally. Sounds fair, right? In practice, it meant nobody could plan their life. "Sometimes I'm up at 6 AM, sometimes I'm in a meeting at 10 PM" is worse than "I always have Tuesday early mornings." Predictable pain is better than random pain.
We settled on fixed times. The West Coast team accepted that they'd always take calls at 8 AM. The India team accepted they'd always take calls at 3 PM. Everyone else worked around those fixed points.
The Tool Stack (For What It's Worth)
We used Google Calendar with world clock enabled, a shared Notion page for handoffs, and a Slack channel called #async-updates for non-urgent communication. Nothing fancy. The tools matter less than the agreements about how to use them.