Our reliability team spans Lisbon, São Paulo, Bengaluru, Austin, and Auckland. Here is what stopped working, and what we built instead.

A synchronous daily standup across five time zones means someone is always joining at 6am or leaving at 11pm. We tried it for a year out of habit before admitting it was quietly punishing whoever drew the short straw that quarter.

The standup that nobody could attend awake

We rotated the standup time monthly to "share the pain fairly." It didn't help — it just meant everyone was miserable on a schedule instead of some people being miserable permanently. The real problem wasn't the time slot. It was that we were trying to force synchronous coordination onto a team that didn't need it for 90% of what standup covered.

What replaced it

We killed the daily sync standup and replaced it with an async written handoff, plus one truly synchronous meeting per week timed to rotate fairly and kept under 20 minutes.

daily_handoff.md (posted by outgoing region lead, any time in their day)
---
region: BLR (UTC+5:30)
shift_window: 03:00-11:00 UTC
incidents: none new; watching elevated p99 on ingest-eu (ticket HX-4021)
handoff_notes: >
  Ingest-eu p99 climbing slowly since 07:00 UTC, not yet alerting.
  If it crosses 400ms before your shift ends, page platform-eu directly,
  don't wait for the automated threshold.
blockers_for_next_region: none

Handoffs improved almost immediately because writing forces precision that a rushed verbal update doesn't. Six months in, incident context loss during shift transitions — measured by "did the next region have to re-investigate something already diagnosed" — dropped from roughly 1 in 4 handoffs to fewer than 1 in 15.

The meeting we kept, on purpose

We didn't go fully async. One 20-minute video call a week, rotating start time by region so the same people aren't always the ones losing sleep, is where we do the things text handles badly: disagreement, morale checks, and just seeing each other's faces. Async is efficient. It is also how teams quietly stop feeling like a team if you never balance it with something synchronous.

"I know my Lisbon teammate's dog's name before I know what he shipped last week, and that's not an accident — that's what the weekly call is for."
  • Don't force synchronous rituals onto a distributed team out of habit — audit what actually requires real-time presence.
  • A well-structured written handoff beats a rushed verbal standup for information transfer across shift boundaries.
  • Keep at least one recurring synchronous touchpoint — full async erodes team cohesion even when it improves throughput.