Replacing the Daily Standup Without Losing the Information

The daily standup is the most-defended ritual in software, and most of the defence is about the third of it that matters. Sort what it produces and the replacement designs itself: state and blockers can be written, and the unplanned conversation that sometimes follows cannot.

"Fifteen minutes a day times twelve people, for updates nobody remembers."

What a standup actually produces

Output	Needs a live meeting?	Better home
State: what I am on	No	A written brief, readable any time
Blockers: what is stuck	Only if contested	Written, escalated live if unresolved
Incidental conversation	Yes	A short live slot, two or three times a week
Attendance as a signal of effort	No	Nowhere, this is the part to lose

That last row is worth naming, because it is the quiet reason standups persist on teams that get nothing from them. The meeting functions as a daily check that everyone is present and working. If that is the actual purpose, no written replacement will satisfy it, and the honest conversation is about trust rather than about format.

The arithmetic of fifteen minutes

Twelve people, fifteen minutes, five days is fifteen hours a week. That is the visible cost and it is the smaller half.

The larger half is placement. A standup at 09:00 or 10:00 sits at the start of the day, which means the morning splits into a fragment before it and a block after it, and nobody starts deep work into a fifteen-minute gap. Across a distributed team it also sits at a bad hour for at least one zone, which converts a mild cost into a real one. The interruption cost of a mid-morning meeting is covered in what interruptions cost an engineering team.

The replacements that fail

The most popular replacement is a bot that asks everyone three questions at 09:00 and posts the answers in a channel. It is worse than the meeting in two ways: it interrupts twelve people individually rather than once as a group, and the output is a wall of text that nobody reads, which people demonstrate by replying to it with questions already answered in it.

The second failed replacement is a shared document everybody updates. It works for a fortnight. Then one person forgets, then two, and a document with gaps is not trusted, and an untrusted document gets replaced by asking people directly.

Both fail for the same underlying reason: they produce a record nobody reads, because reading a wall of updates is a worse deal than asking one specific person one specific question.

What to do instead

Move the writing to the end of the day, keep it to four fields, and make it answerable.

End of day matters because the information is fresh and because the reader who needs it most is in the next time zone, starting while you sleep. Four fields matters because ninety seconds survives a bad day and five questions do not: current state, open questions, blockers, next actions, as laid out in the end-of-day handoff.

Answerable is the part that distinguishes this from the shared document that died. With StandIn, the brief you confirm in ninety seconds is what your StandIn speaks from while you are off. Someone wondering what you are on does not read a wall of updates hoping the relevant line is in there. They ask, and get an answer in your words with a source under it, and no bot pings anyone at 09:00. When the answer is not in your brief, it says so and names who to ask.

That is the replacement: the information keeps flowing, the fifteen hours a week come back, and nobody performs their status aloud. See how StandIn works.

What to keep live

Keep a short live slot, two or three times a week, for the third output: the conversation that starts when someone says something that makes another person say "wait". That is the genuine value of a standup and it is not reproducible in writing.

Make it explicitly not a round-robin. No one reports. The agenda is blockers that need a human and anything someone wants to raise. Fifteen minutes, cancelled without ceremony when there is nothing. Teams that do this usually find it lands twice a week rather than five times, which tells you what the other three days were.

Common Questions

What should replace the daily standup on a distributed team?

A written brief at the end of each person's day, covering current state, open questions, blockers, and next actions, plus a short live slot two or three times a week for blockers that need a conversation. The written part carries the information, the live part carries the argument.

Are async standup bots a good replacement?

They usually reproduce the problem. A bot that asks twelve people three questions at a fixed hour interrupts individually, produces a wall of text, and still does not answer a specific question at the moment someone has it. If a bot is the answer, the question was probably "how do we keep the ritual" rather than "how do we move the information".

How do we keep visibility without standups?

Visibility is not the same as reporting. What people actually want is to be able to find out what someone is on, at the moment they need to know. A daily broadcast that nobody reads provides much less of that than a record that answers a direct question.

What if the standup is the only time the team talks?

Then it is doing social work, and that is a legitimate need with a better format. Replace the daily fifteen minutes with a weekly half hour that is explicitly not about work. Using a status ritual as the team's only social contact serves neither purpose well.