How To Run Async Standups That Actually Work

By 9:14 the writing tool’s daily standup channel has nine entries, all of them the same shape, and three of them with the same blocker. Yesterday’s work, today’s intent, the obstacle in the way. A standard format borrowed from the in-person ritual it replaced, with the subtle problem that nobody actually replaces a meeting by writing down the meeting.

The team had moved to async standups for the obvious reason, distributed across four time zones and tired of waking up early to summarise the day they had just finished. The format kept the meeting’s bones and removed its body. Reading the channel in the morning felt like reading a transcript of a meeting nobody attended.

What async standups inherited from the meeting they replaced

The synchronous standup as we know it carried over from a particular kind of room and a particular kind of pressure. Three questions answered in a circle, time-boxed to fifteen minutes, a lead nodding while the engineers spoke and the engineers performing legibility while the lead nodded. The format made sense in a room because the room enforced the brevity. Without the room the brevity collapses.

Most async transitions inherit the three questions and inherit the brevity assumption with them. The result is a channel of skim-worthy, low-information posts that do not change anyone’s day. Yesterday’s work is already in the issue tracker. Today’s intent is already in the issue tracker. The blocker is the only field that does new work, and it is the field everyone underuses because the social pressure of writing it down without a face to soften the ask is real.

A morning standup channel in this shape is, on a generous reading, a vibes check. On a less generous reading it is a status report nobody asked for, written in a register that makes it useless for any audience besides the writer’s lead. The async format gave the team back their mornings and returned the question of why the standup existed at all.

The teams I’ve watched migrate the format successfully are usually the ones that admitted, somewhere around month two, that the daily ritual they were performing in writing was not the standup at all. It was a different meeting wearing the standup’s clothes. Once they let the costume slip, the format had room to become something else.

Where async standups actually earn their format

The async standup earns its keep when the channel stops being a transcript and starts being a thread. Not three questions answered into the void, but a single open prompt that anyone on the team can pick up and complicate. “Anything I should know before I touch this codebase today” is a prompt that produces real answers. “What did you do yesterday” is a prompt that produces a list.

The shift is subtle and structural. The async format moves the daily check-in off the calendar and onto the team’s existing surface area, which is the same writing tool the team already lives in. The lead who wants the daily summary can still get it by reading the channel. The engineers who never had anything to add to the daily meeting now have nothing to add to the channel, which is the same outcome with two-thirds fewer minutes of friction.

Teams that get this right tend to start the day with a question, not a template. The question rotates. Sometimes it is the blocker question. Sometimes it is a planning question. Sometimes it is a question someone genuinely needs answered before lunch. The format flexes to the day instead of the day bending to the format.

The rotating prompt also does something the synchronous standup could not. It tells the team, every morning, what kind of day this is. A blocker prompt signals shipping pressure. A planning prompt signals slack. A reflective prompt signals capacity. The prompt becomes a low-resolution barometer that everyone reads in passing, and the channel becomes legible in a way the templated version never was.

The hidden cost of the async standup that worked

Async standups buy the team back two hours a week and lose something that takes longer to notice. Standups had been the only meeting where everyone was present at once with permission to mention anything. A planning meeting is for planning. A retro is for looking back. The synchronous standup was the leftover bin where small things, observations that did not justify their own meeting, found a moment to surface.

The async format does not have a leftover bin. It has a channel. The channel scrolls. Things mentioned at 9:11 are gone by 9:43, replaced by other things mentioned by other people in other time zones. The half-sentence aside that would have surfaced naturally in person now takes a full paragraph to write down, because the writer has to anticipate every reader who is not currently in the room.

Some teams work around the loss by adding a weekly synchronous meeting that explicitly does not have an agenda. The format is unfamiliar enough that nobody quite knows what to do with the first one, which is the point. By the third or fourth, the meeting has filled up with the small things that the async format could not hold.

Other teams let the channel scroll and accept the cost. They make a different bet, that the small things will find their way to the surface in retros, in design reviews, in the quieter Friday afternoons when the channel slows. Sometimes that bet pays. Sometimes the team ships a product with a problem nobody had felt comfortable raising, and the post-mortem traces it back to the async format that quietly stopped functioning as a leftover bin.

The bet itself is not wrong. The mistake is making it without admitting it is being made.

How to run an async standup that respects the format

The async standup that works does three things the synchronous one did not have to. It picks a single prompt, not a template. It rewards specificity over completeness. It keeps the channel narrow enough that reading it feels like reading a shared document rather than a feed.

A single prompt sets the day’s mood. “Anything blocking you” is good when shipping pressure is high. “What’s the one thing you’d love a second pair of eyes on” is good in the middle of the design phase. “Anything I’d be surprised to learn about your week” is good when the team has been heads-down too long. The prompt changes when the situation changes, and the lead facilitator changes the prompt when the situation has changed. A prompt that has been live for six weeks without rotating has stopped reading.

Specificity is the second thing. A blocker that reads “blocked on review” is not a blocker, it is a passive complaint. A blocker that reads “blocked on review of the third draft of the export flow, which needs an opinion on whether to keep the multi-select behaviour from v1” is a blocker, because someone reading it can act on it. Async writing rewards the specific in a way verbal standups never had to. A team learning the format quickly learns to write specifically, or quietly stops writing.

The third thing is keeping the channel small. A channel that includes the whole engineering organisation, the design team, the product lead, the support lead, and the founder is not a channel. It is a feed. Feeds get skimmed. Channels get read. The async standup earns its read by staying narrow enough that the reader feels personally implicated in the contents, the way the room used to imply.

A useful rule is the dozen-person ceiling. Beyond a dozen, the channel should split. Two adjacent channels, read by overlapping audiences, retain the implicated feeling. One large channel does not. The split feels bureaucratic for about a week and then feels obvious.

The format that does not look much like a standup

Teams that have been running async standups for a year tend to converge on something that does not look much like a standup. It looks like a small daily thread of the team’s actual working concerns, with light social texture, and a low tolerance for status performance. It works because the team has agreed on what the channel is for and what it is not for. The format follows that agreement. The format never leads it.

The standup is not the meeting and never was.