Async standups that people actually read

Most written standups die within a month, and they die the same way. Week one, everyone posts thoughtful updates. Week two, updates shrink to “same as yesterday.” Week three, two people forget. Week four, the manager asks in the team call — the one the standup was supposed to replace — whether people could “please keep up with the updates,” and the ritual is now a chore stapled to a meeting instead of a replacement for one.

I've watched this movie inside our own team and across customer teams. The failures are so consistent that the fixes turn out to be mechanical. Written standups don't fail because people are lazy; they fail because the format quietly asks the writer to do work the system should do.

Failure #1: The update has no reader

In a spoken standup, you watch people listen to you. In most written versions, you type into a channel and get… maybe an emoji. The writing feels like filing a report into a void, and reports filed into voids stop getting written.

The fix is compilation. Individual updates should disappear into one team digest that everyone actually opens — because it's short, it arrives at a predictable time, and it contains the one thing everyone genuinely wants to know: is anything blocked? When the digest is the artifact, reading it is cheap (90 seconds) and writing for it has an audience again. Reply counts on digest items make the audience visible: questions land on your update, not in a DM you'll lose.

Failure #2: The prompt is a blank page

“Post your standup” is a writing assignment. Three specific questions are a form. Forms get filled; assignments get deferred. The prompt set we've seen survive longest:

• What moved yesterday? — past tense, shipped or progressed, one or two lines.
• What's the one thing today? — singular on purpose; a list of six intentions is a wish, not a plan.
• Anything blocked or at risk? — with a hard rule that naming a blocker is rewarded, never punished.

Rotate a fourth, optional question weekly — “what did you learn?”, “what should we stop doing?” — for texture. But the core three stay fixed, because predictability is what makes answering take two minutes instead of ten.

Failure #3: One deadline for five time zones

A 9 am standup prompt is 6 pm for your teammate in Warsaw and tomorrow for Auckland. Any fixed hour privileges one office and taxes the rest — which is exactly the dynamic async was supposed to end. Prompts should arrive at each person's start of day, and the digest should compile when the team's overlap window opens. The updates are asynchronous; the reading is synchronized. That inversion — sync the artifact, not the people — is the entire trick.

Failure #4: Guilt as the enforcement mechanism

Here's the counterintuitive one: let people skip. A standup ritual policed by streak-shaming produces compliance updates — “worked on stuff, more today” — which are worse than silence because they bury the real signal. An unanswered prompt should simply read “no update” in the digest, without a red mark. Deep-work days, meeting-packed days and sick days are all honest reasons for silence.

What keeps participation high isn't pressure; it's usefulness. When blockers named in a digest get acknowledged within hours — because an escalation rule pings the lead if they aren't — people learn that writing the update is how you get unstuck. Utility recruits better than guilt, and it doesn't burn anyone out doing it.

What a digest that people read looks like

Blockers first, always — that's the news. Then per-person entries in a fixed order, each scannable in seconds. Metadata that answers the meta-questions (“7 of 8 checked in”) without anyone asking them. Here's the shape, from our own workspace:

The two-week dip is real — plan for it

Teams switching from spoken to written standups get worse before they get better. The first week's updates are stilted; the second week someone declares async “isn't working for us.” Around week three, something shifts: people start writing updates that reference each other's, blockers surface a day earlier than they used to, and the digest becomes the place decisions get flagged before they're made. Set the expectation of a dip up front and hold the review at six weeks, not two. (For how to structure the larger meeting cleanup around this, the meeting audit is the companion piece.)

The goal was never “no meetings.” It's meetings that are all signal — critique, decisions, actual conversation — because the status layer runs itself in writing. The standup didn't deserve eight people's synchronized attention every morning. The work does.