The async standup is seductive: no meeting, no timezone pain, everyone writes three bullet points in Slack. It works beautifully in theory and falls apart in practice for most teams.
What async standups assume
They assume everyone reads everyone else’s update. They assume blockers get surfaced without the social pressure of a room. They assume people write honestly instead of performing busyness.
“The single biggest problem in communication is the illusion that it has taken place.” — George Bernard Shaw
None of those assumptions hold on a team that hasn’t built trust yet.
What actually works
For distributed teams under six people, a 15-minute video call beats a Slack thread every time. The value is not status — it’s the two minutes someone spends saying “I’m stuck on the auth flow” and getting an immediate “I hit that last week.”
A lightweight sync agenda:
- Round-robin — what shipped since last sync
- Keep it to one sentence per person
- Link PRs, not paragraphs
- Blockers — anything stuck > 24 hours
- Name the person who can unblock
- Decide in the room, not in a thread
- Today — one priority each
- If everything is priority one, nothing is
- Explicitly call out what you’re not doing
The hybrid
Once trust exists, drop to twice-weekly syncs and use written updates on off days. A template that actually gets read:
## Yesterday
- Shipped password reset flow (#412)
- Paired with Alex on migration script
## Today
- Load-test auth endpoints
- Review design for settings page
## Blocked
- Waiting on staging credentials from infra (@sam)Async is a reward for a healthy team, not a shortcut to one.