9 AM standup in San Francisco is 5 PM in London and 10:30 PM in Bangalore. Someone is always losing. The fix isn't finding a "good" time — it's choosing the right standup format for your timezone spread.
The Distributed Standup Challenge
Traditional standups assume everyone is in the same place at the same time. With distributed teams:
- 9 AM standup in San Francisco = 5 PM in London = 10:30 PM in Bangalore
- Someone is always joining at an inconvenient time
- Async participants miss context and energy
- Blockers go unresolved for hours
Option 1: Rotating Standup Times
Rotate the standup time weekly or bi-weekly so the inconvenience is shared. This ensures fairness — everyone takes turns with bad times.
Best for: Teams with relatively even distribution across time zones where no single zone should bear the burden.
Option 2: Async-First Standups
Replace live standups with async updates:
- A bot prompts at the start of each person's day
- Everyone posts answers to a dedicated channel
- Team members read updates during their work hours
- Use reactions or threads for items needing discussion
Sample format:
Yesterday: Completed PR #234 for auth refactor Today: Start database migration scripts Blockers: Need design specs for dashboard (cc @design)
Best for: Teams with large time zone spreads (8+ hours) where live overlap is limited.
Option 3: Regional Clusters
Split the team into regional groups, each with their own standup:
- Americas Standup: 9 AM PST / 12 PM EST
- EMEA Standup: 9 AM GMT / 10 AM CET
- APAC Standup: 10 AM IST / 12:30 PM SGT
Regional leads sync once or twice weekly to share cross-cutting blockers and coordinate dependencies.
Best for: Larger engineering teams (15+) with clear regional concentration.
Option 4: The Hybrid Model
Combine async updates with a weekly live sync:
- Daily (Async): Post updates, flag blockers, review teammates' updates
- Weekly (Live): 30-minute team sync with demos, architecture discussions, social time
Best for: Most distributed engineering teams — balances efficiency with human connection.
Find Your Team's Overlap Window
Add every engineer's city and see the exact hours where everyone is awake — then pick a standup slot or go async.
Open Meeting PlannerMaking Any Format Work
- Time-box ruthlessly: Max 2 minutes per person, 15 minutes total
- Focus on blockers: The #1 purpose is to surface blockers fast
- Document decisions: Absent team members shouldn't miss critical info
- Record live standups: Post recordings with timestamp markers
- Respect time zones in tooling: Show times in each person's local timezone
Engineering-Specific Patterns
Add these to your standup format:
- PR Review Queue: Surface aging PRs to prevent bottlenecks
- Incident Updates: Keep the team informed on critical issues
- Sprint Progress: Link to sprint board metrics
- Tech Debt Flags: Create space for calling out debt
Start here: Measure your team's timezone spread with the Meeting Planner. If the overlap is 4+ hours, rotating live standups work. If it's 1-2 hours, go async daily with one live weekly sync. The format should follow the math, not the other way around.
