How to Run an Async Daily Standup That People Actually Read

The daily standup was meant to be fifteen minutes. On most teams it costs far more — fifteen for the meeting and another thirty for the context-switch it forces on everyone's morning. The async version keeps everything the standup was good for and drops the parts that waste time, but only if it is run well. A poorly run async standup becomes a wall of updates nobody reads, which is its own kind of failure.

Here is how to run an async daily standup people actually read.

Keep the Three Questions

The async standup answers the same three questions the live one did: what changed since yesterday, what you are doing next, and what is blocking you. That structure is the whole point. It keeps updates skimmable and forces the writer to say something useful rather than narrate their day.

Resist the urge to add more fields. The moment the format becomes a long form, people start skipping it or filling it with noise. Three short lines, posted once, is the target.

Post on Your Own Schedule, Read on Yours

The defining feature of the async standup is that nobody has to be online at the same time. Each person posts their update when they start their day; everyone else reads when it suits them, skimming for what concerns them and skipping the rest.

This is strictly better than the meeting for a distributed team. It works across time zones, it respects focus time because nobody interrupts deep work to attend, and it leaves a written record you can search later. The recitation format of a live standup, where most people tune out updates that do not concern them, disappears.

Write Updates Worth Reading

The failure mode of async standups is updates that are either novels or non-statements. "Made progress on the thing, will sync later" forces a follow-up and defeats the purpose. "Blocked on the API review from the platform team — can someone there take a look today?" is something a colleague can act on immediately.

Hold updates to one standard: specific enough to act on, short enough to skim. A teammate two time zones away should be able to read your update and know exactly what is happening without asking a clarifying question. This is the same discipline that makes any async status update work.

Surface Blockers Immediately, Not Just at Standup Time

The most valuable thing a standup does is surface blockers — and a once-a-day written post is still too slow for the urgent ones. The async standup should be paired with a norm that real blockers get raised the moment they appear, tagged to whoever can resolve them.

Think of the daily update as the routine sweep and immediate posting as the fast lane. Together they turn blocker resolution from a once-a-day ritual into something continuous, so problems get unblocked in hours instead of waiting for the next morning.

Give It One Durable Home

Async standups break when updates scatter across channels and direct messages. Pick one place — a dedicated update feed — where every update lands, so catching up means checking a single spot. Woyce's update feed is built for exactly this: a single stream where progress accumulates and nobody has to attend a meeting to know what is happening.

Let the Board Carry the Detail

The written update handles narrative; the project board carries the rest. Anyone who wants the full state of the work looks at the board instead of expecting the standup to recap everything.

This only works if the board is trustworthy — statuses current, enough context on each task that someone can act without a conversation. A board people trust eliminates most of the questions a standup exists to answer.

Don't Recreate the Meeting

The biggest mistake teams make is turning the async standup back into a synchronous one — requiring everyone to post within a narrow window, or reading every update aloud in a call "to make sure people did it." That defeats the entire benefit. Trust people to post on their own schedule, and judge the system by whether the team stays aligned, not by whether everyone posted at 9am sharp.

The Standup, Reclaimed

A good async daily standup keeps the three questions, lets people post and read on their own time, demands updates specific enough to act on, surfaces urgent blockers immediately, and leans on a trustworthy board for the detail. Teams that run it this way report the same coordination as the live version with fewer interruptions and a recovered morning — which was the point of a standup all along.