Learning how to run an async standup is simple: replace the daily video call with a written update posted by a fixed time every workday — each person shares what they finished yesterday, what they plan today, and anything blocking them, in three short lines, in one shared channel. The meeting disappears, the information does not, and the whole team reads it in two minutes whenever their workday starts.
I killed my first daily standup by accident. It was 2022, and my team spanned four time zones. The “quick 15-minute” call started at 7 AM for one person and 6 PM for another, and by the time the fifth person gave their update, the first person’s update was already out of date. We spent 45 minutes a week in a call that produced roughly three sentences anyone remembered. One Monday I simply posted my update in Slack instead of joining the call. By Friday, four other people had done the same, and nobody had scheduled the call again.
That is the honest origin story of most async standups: nobody plans a grand process change — someone just stops attending a meeting that no longer earns its time. This guide covers how to make that switch deliberately, with a format that actually sticks.
What is an async standup?
An async standup is a written daily update that replaces the live standup meeting. Every team member posts the same three things — what they did, what they will do, and what is blocking them — in a shared written channel, by a fixed time, and everyone else reads it when it suits them. There is no call, no waiting your turn, no repeating yourself for someone who joined late.
The difference from a status report is the audience and the rhythm. A status report goes up to a manager; an async standup goes to the whole team, every workday, in the open. The point is not surveillance — it is shared awareness. Anyone should be able to open the channel and know, in two minutes, what the team is working on and where it is stuck.
How to run an async standup meeting
Running an async standup takes four decisions: the format, the place, the deadline, and the enforcer. Get those four right and the habit runs itself. Get one wrong and it quietly dies within two weeks — usually because the format was too long, the channel was too noisy, or nobody enforced the deadline.
Start with a one-week pilot. Announce it plainly: “For the next five workdays, we are cancelling the daily call and posting written updates instead. At the end of the week we decide together whether to keep it.” A pilot removes the argument about whether async “works in theory” — you will have five days of evidence either way.
What should an async standup update include?
The classic three questions still work — yesterday, today, blockers — but the written version needs tighter rules than the spoken one. Each line gets one sentence. No context dumps, no apologies, no meeting minutes in disguise. If an update needs more than three sentences, it is not a standup update — it is a document, and it belongs in a doc with a link.
Here is the template I hand to every team, word for word:
Yesterday: shipped the checkout bug fix; reviewed Sara’s pull request on the onboarding flow.
Today: start the refund API refactor; answer the two support escalations from yesterday.
Blockers: need the staging database password reset — waiting on DevOps.
Notice what the template forces. “Yesterday” is proof of progress, not a diary. “Today” is a commitment the team can hold you to. “Blockers” is the only line a manager truly needs to read first — a blocker posted in writing, in public, is far harder to ignore than one mentioned in a call while half the room was muted.
Where should async standup updates live?
One channel, one thread-free stream, no exceptions. Slack or Microsoft Teams both work; the tool matters less than the discipline of a single place. The channel should contain only standup updates — no memes, no announcements, no side conversations. The moment the channel becomes general chat, people stop reading it, and the standup dies without anyone noticing.
Resist the urge to buy a dedicated standup bot in week one. Bots like Geekbot are genuinely good, but they solve a problem you do not have yet. A plain channel works for the pilot; add automation only after the habit exists.
One more placement rule: blockers get their own visibility. When someone posts a blocker, the person who can unblock them replies in the same thread that day — not tomorrow’s standup, not a separate meeting. A blocker that sits unread for 24 hours costs a full day of someone’s work. That reply-in-thread habit is the difference between an async standup that feels alive and one that feels like shouting into a void.
What time should everyone post their async standup?
Pick one deadline in the team’s main time zone and publish it: “updates posted by 10 AM Eastern, read by noon.” The deadline should sit near the start of most people’s day, not the end — the update is a plan for today, not a diary of yesterday. For teams spread across many zones, anchor the deadline to the start of the largest group’s workday and let everyone else post the evening before, which their colleagues then read in the morning.
The deadline only works if someone enforces it. Rotate a “standup keeper” weekly — their only job is a friendly nudge at the deadline (“two updates still missing”) and nothing else. No policing tone, no public shaming, just the nudge. After two weeks, the nudge mostly stops being needed; people post because the channel is useful to them, not because someone asked.
How do you know if the async standup is working?
After the pilot week, ask the team three questions: Did you know what everyone was working on? Did any blocker get solved faster than it would have in a call? Did you miss the meeting? The first two answers tell you whether the standup works; the third tells you whether anyone will fight to bring the meeting back.
My own test, the one I run on every team I coach, is simpler: I check whether the standup channel gets opened. If people open it to find out what is happening — not because they were told to — the standup has become infrastructure. The real prize is not the saved 15 minutes a day, though that adds up to a full workday per person per month. The real prize is that the team’s knowledge stops living in a call nobody can replay and starts living in writing anyone can search.
Frequently Asked Questions
How do you run an async standup meeting?
Pick one channel, one template (yesterday / today / blockers, one sentence each), and one daily posting deadline. Run it as a one-week pilot instead of the daily call, rotate a “standup keeper” who nudges late posters, and reply to blockers in the same thread the same day. At the end of the week, decide with the team whether to keep it.
What should an async standup include?
Three lines: what you finished yesterday, what you plan today, and anything blocking you — one sentence each. Never post “continuing the same work” two days in a row without saying what changed, and keep longer explanations in a linked document rather than in the update itself.
Can async standups replace daily standup meetings completely?
Yes, for the daily status update — that is exactly what they are designed to replace. Keep live meetings for things that genuinely need real-time conversation: weekly planning, hard decisions, and celebrations. The daily “what are you working on” check never needed a meeting; it needed three written lines and a deadline.
How do you handle blockers in an async standup?
Blockers get replied to in the same thread on the same day by the person who can unblock them — not in tomorrow’s update and not in a separate meeting. A blocker that sits unread for 24 hours costs a full day of work, so the reply-in-thread habit is the single most important rule in the whole system.