At Condor Gaming I ran nine live products with four dev teams — Europe, LATAM, Japan, Canada. The overlap window across all four was 45 minutes a day. A daily standup was mathematically impossible, so we stopped pretending and built something better.
The standup was never the point
The standup exists to answer three questions: what moved, what's next, what's blocked. None of those require synchronous speech. What they require is that the answers are written down, visible to everyone, and impossible to skip. Once we accepted that, the 15-minute meeting became a 3-minute written ritual — and the quality of the answers went up, because writing forces precision that mumbling into a webcam at 9am never did.
Blockers get a channel, not a meeting
A blocker raised in a standup waits up to 24 hours to be spoken and another day to be resolved. A blocker posted in a dedicated channel with a hard SLA — first responder within 4 working hours, whoever is awake — resolves faster than any meeting cadence can. The rule that made it work: a blocker post must name the person or decision it's waiting on.
Meetings are where blockers go to wait. Channels with SLAs are where they go to die.
What broke — and what we kept synchronous
Two things broke. Sprint planning done async produced estimates nobody believed — negotiation needs a live room, so planning stayed synchronous, once per sprint, in the 45-minute overlap window. And new joiners drowned: async culture assumes you know who to ask. We fixed that with a two-week shadow buddy in an adjacent timezone, and onboarding recovered.
The net result across two quarters: 15 hours of weekly meetings became 4, release cadence held, and the LATAM team — previously always the one off-cycle — shipped the two biggest features of the year. Async isn't a downgrade you accept for distributed teams. Done with SLAs and written rituals, it's the upgrade.