29 August 2026
An async standup is a written post each person makes once a day — what shipped, what's next, what's blocked — instead of a live call. It only earns its place if someone reads yesterday's post before today's, because the whole point is catching a blocker that repeats, which a fifteen-minute verbal round almost never does.
Three lines, in this order: what got done since the last post, what's happening today, and what's blocked. Anything longer than three or four sentences per line gets skimmed, not read, and a standup nobody reads is just a status log nobody checks.
Date and name at the top of every post, even in a threaded channel. Without a timestamp there's no way to see that the same sentence appeared Monday and is still there Wednesday — which is the entire mechanism this format depends on.
'Shipped the login fix' and 'starting on the API docs' are status theater — pleasant to read, changing nothing about anyone's day. The blocker line is different: it's the one sentence that should cause another human to do something, today, in response.
If a team's blocker lines sit empty for three weeks straight while work visibly slows down, the standup has become decorative. The fix isn't a better template — it's someone whose job is to read that one line across the whole team and act on it, the way a lead in a live standup is supposed to but usually doesn't have time to.
This is the actual job a fifteen-minute meeting exists to do, and rarely does. In a live standup, each person gets fifteen seconds and says 'still waiting on staging' fresh every morning — it sounds like new information each time because nobody in the room is comparing it to what was said yesterday.
A written record fixes this by accident, if someone bothers to look: search the blocker channel for 'waiting on' or 'blocked by' and a repeated phrase across three consecutive dates is visible in one scroll. That's the tell that a ticket, a dependency, or a person outside the team needs to be pulled in — not another day of the same post.
Pick one channel and one cutoff time — post by 10am, not 'sometime today.' A standup with a soft deadline decays within two weeks because the first missed day makes the second easier to miss.
One thread per person per day, not one thread per project. It's the only structure that lets a reader scan five people's blocker lines in under a minute, which is the whole trade you're making against the live meeting.
Async breaks when a blocker needs back-and-forth — three sentences of context, a question, a decision — because a thread reply the next morning is slower than the thirty seconds it would've taken live. That's not a reason to keep the daily meeting; it's a reason to pull the one blocked person into a two-minute call instead of the whole team.
AVAY doesn't run text-only async standups — it's a video meeting product, and there's no substitute there for a written post that people scan in their own time. What it does do is keep a transcript of any check-in call the team still holds, searchable across weeks, so if the standup itself occasionally happens on a call rather than in text, someone can search 'blocked on' and see the same phrase turn up in three consecutive Monday syncs without having to remember it themselves.
| Time cost per person | Catches a repeated blocker | Leaves a record | |
|---|---|---|---|
| Live daily standup | 10-15 min, every day | Rarely — nobody compares to yesterday | No, unless someone takes notes |
| Async written post, unread | 2-3 min to write | Never — posts pile up unread | Yes, but inert |
| Async post + daily blocker scan | 2-3 min to write, 5 min to scan | Yes — repeats are visible in one scroll | Yes, and searchable |
One or two sentences per line, three lines total. Longer than that and people start skimming instead of reading, which defeats the format before it starts.
Pick one fixed cutoff — most teams use mid-morning, like 10am local time — and hold it. A standup with a soft deadline gets skipped within two weeks because the first late post makes the second one easier to excuse.
Write 'none' explicitly rather than leaving the line blank. A blank line is ambiguous — it could mean no blocker or it could mean the person forgot that line exists — and the whole method depends on being able to trust what's there.
For most teams, yes, once someone owns reading the blocker lines every day. The one exception is a blocker that needs real back-and-forth — those are worth a two-minute call with just the person who's stuck, not a return to the full daily meeting.
An async standup is only worth running if someone reads the blocker line every day and notices when it repeats — that's the one thing the daily meeting was supposed to do and almost never does.
AVAY is a video meeting platform that transcribes the call itself — no bot joins, because there is nothing to join. Start one at avay.ai, read how each part works in the documentation, or see what it costs.