What is an async standup?

An async standup is a daily team check-in done in writing, on each person's own schedule, instead of in a meeting. Same questions, same visibility, no meeting.

1How it works

Each morning, every participant gets the standup questions in Slack, usually by DM. People answer when they start their day. The answers are collected into one digest and posted to a team channel, where anyone can read the whole team's updates in about two minutes and pull a thread on anything that needs discussion.

2Why teams switch

• Timezones stop being a problem. There is no meeting slot that suits Zagreb, London and San Francisco at once. Async, everyone answers at their own 9:00 and reads at their own pace.
• One interruption becomes zero. A 15-minute meeting costs the whole team a context switch at the same moment. A DM waits until a person surfaces from focused work.
• You get a written record. Yesterday's plans and last month's blockers become searchable, quotable and linkable. Meeting standups evaporate the moment they end.
• It is faster. Speaking eight updates takes fifteen minutes. Reading eight takes two.

3What you give up, honestly

A live standup gives you faces, tone and instant follow-up questions. Async trades those away, so teams that switch well do three things: they keep a weekly live session for actual discussion, they thread follow-ups on the digest instead of letting questions die, and they treat a written blocker as a call to action with a name attached, not a diary line.

4The questions

The classic three: What did you do yesterday? What will you do today? Anything blocking you? They work, but on autopilot they produce diary entries. Variants that keep answers useful:

• What do you need from someone else today?
• What is at risk of slipping this week?
• One thing you learned yesterday?

Rotate one slot occasionally and keep the blocker question always.

5Where async standups fail, and the fixes

• Status theater. Answers become novels written for the boss. Fix: fewer, sharper questions, and make the digest the reader, not the manager.
• Nobody reads it. The digest scrolls by unread. Fix: post it to the channel where work happens, keep blockers at the top, and summarize. This is what an AI digest is for: progress, blockers and next steps in a few lines above the raw answers.
• The zombie standup. Response rates drift down until the ritual is dead. Fix: a response window with one reminder, a visible response rate, and pruning participants who no longer need to be there.

6When a live standup is still better

Co-located teams of three or four lose little by talking. Incident response needs a call, not a form. And a team mid-discovery, where every update is really a discussion, should talk first and write down conclusions. An async standup replaces the status meeting; it does not replace talking.

Try it: asyncmate runs this whole loop in Slack: questions by DM, digest to your channel, AI summary on top. Free for up to 10 people who answer. See how to run daily standups in Slack next, or jump to getting started.