Async standup is supposed to save distributed teams from pointless meetings. Often it just moves the pointlessness into a channel nobody reads. The format you pick decides whether it helps or becomes noise.
There is no perfect format. Each one is good at something and fails in a specific way. Here are three common ones, what each does well, and the exact point where each breaks down.
1. The three-question update
This is the classic. Everyone posts an answer to three prompts, usually some version of: what did I do yesterday, what am I doing today, what is blocking me. It is the direct translation of the old standing meeting into text.
What it is good at: it is simple, everyone already knows the shape, and it takes two minutes to write. For a small team that mostly needs a heartbeat, it works fine. You can skim the channel and see that people are moving and nobody is silently stuck.
When it fails
It fails as the team grows and the answers turn into theater. "Yesterday: worked on the dashboard. Today: continuing the dashboard. Blockers: none." That is technically an update and it tells you nothing. The format rewards posting, not communicating. Nobody reads twelve of these every morning, so the updates get written for no reader, which means they get written to be done, not to be useful. The blockers line is the worst casualty. "None" becomes the default even when someone is quietly stuck, because saying "none" is faster than explaining.
2. The blocker-only format
This format throws out the status recap entirely. The only rule is: post if you are blocked or if you are about to block someone else. If you are moving fine, you say nothing. Silence means progress.
What it is good at: it fixes the theater problem head on. The channel is quiet most days, so when something appears, people actually read it. It respects everyone's time by refusing to manufacture updates nobody needs. Senior teams that trust each other often drift toward this naturally, because the daily recap was never telling them anything they did not already know.
When it fails
It fails when the team needs shared awareness, not just unblocking. Silence is ambiguous. Is that person heads down and fine, or stuck and too proud to say so, or out sick? You cannot tell, because the format only speaks up for blockers. It also loses the passive context that a status recap quietly provides. A teammate might have mentioned they touched the auth module yesterday, which is exactly what you needed to know before you touched it today. In a blocker-only channel, that detail never gets said, so two people collide on the same file with no warning.
There is a cultural cost too. When the only reason to post is to admit you are stuck, posting starts to feel like a confession. On a team where people already worry about looking slow, the blocker-only format can make them quieter, not more honest. The person who most needs to raise a hand is the one least likely to, because the format has made speaking up mean weakness. That is the opposite of what you wanted.
3. The written-thread-per-project format
Instead of one update per person, this format organizes around the work. Each project or workstream has a standing thread, and people post progress into the thread for the thing they are working on. The unit is the project, not the person.
What it is good at: context stays with the work. Anyone who cares about a project can follow its thread and see the whole arc of it, without digging through a dozen personal updates to find the two lines about the thing they care about. It scales better than per-person updates on a larger team, because you read the projects you touch and ignore the rest. It is also a far better record weeks later, since the history of a project sits in one place.
When it fails
It fails on cross-cutting awareness and on people who span many projects. If your work touches six threads, you either post the same update six times or the whole team loses the shape of what you personally did this week. New people find it hard to get a sense of who is doing what, because there is no single place that shows the team at a glance. And a person who is quietly stuck across several small tasks can hide, since no thread owns their overall state. The work is visible. The person can disappear.
Picking one, honestly
The pattern across all three is the same trade. The three-question format gives you awareness and drowns in noise. The blocker-only format kills the noise and loses awareness. The per-project format keeps context with the work and loses the person. You are not choosing a winner. You are choosing which failure you can live with, given your team's size and how much people already trust each other.
A small, tight team can run blocker-only. A large team with lots of moving parts is better served by per-project threads. The three-question format is a fine starting point that most teams eventually outgrow. Whatever you pick, name the failure mode out loud so people watch for it.
The problem no format solves
Here is the thing every standup format shares. It captures what a person chose to write, in the moment they wrote it. It cannot answer the question a teammate asks tomorrow that the update did not happen to cover. That gap is not a format flaw. No format can predict every future question.
This is the narrow job StandIn does, alongside whatever standup format you run. Each person writes a short brief at the end of their day, and while they are off, it answers teammates from what they actually wrote down, with a source under each answer. When the answer is not in the record, it says so instead of guessing. The standup keeps the team's shared heartbeat. StandIn handles the follow up question that would otherwise wait in someone's inbox until they wake up.
When you're off, your StandIn is on.
It answers your teammates' questions from work you've already done, in your words, with a source under every answer.