Fifteen minutes. Three questions. What did you do yesterday? What will you do today? Are you blocked?
The circle forms. The answers are delivered. Progress, more progress, no blockers.
The meeting ends. Nobody learned anything they could not have read in a Slack message. The standup fulfilled its format. It did not fulfill its purpose.
⸻
The Performance Script
The standup has a hidden audience: the manager.
Everyone in the circle knows this. So the update is optimized for the listener with the most power in the room. Yesterday's work is framed as decisive. Today's plan is framed as ambitious. Blockers are minimized, because naming a real blocker invites scrutiny.
The engineer who spent four hours debugging a flaky test says "continued working on the pipeline." The engineer who is stuck on a design decision they do not have enough context to make says "exploring options."
Both statements are technically true. Neither contains useful information. The person who actually knew the sprint was in trouble said nothing. She told the tech lead in a DM thirty minutes later. The real information moved through a back channel while the standup produced theater.
⸻
The Synchronization Illusion
The standup is positioned as a coordination mechanism. In reality, it coordinates nothing.
If two engineers are working on conflicting approaches, the standup will not surface it. Their updates are too compressed to reveal the collision. If a dependency is going to miss its deadline, the standup will not surface that either, because admitting a miss in front of the group is a social cost most people avoid.
The real coordination happens in direct messages, hallway conversations, and pair programming sessions. The standup is a scheduled interruption that simulates coordination without producing it.
⸻
The Time Tax
Multiply fifteen minutes by the number of engineers in the room. Multiply that by five days a week. Multiply that by fifty weeks.
A team of eight engineers spends one hundred hours per year in standups. That is two and a half full work weeks. For a meeting that mostly produces information available in the ticket tracker.
The cost is not just time. It is context switching. The engineer who was deep in a problem at 9:45 must surface, perform, and then rebuild their mental state afterward. The rebuild takes longer than the meeting.
⸻
The Honest Signal
If you need synchronization, make it asynchronous. Post updates in a channel. Let people read them when they have context to absorb them.
If you need to identify blockers, ask directly. One-on-one. In private. The engineer will tell you the truth when the audience is one person they trust, not ten people they are performing for.
The standup survives because it makes the manager feel informed. Feeling informed and being informed are different states.
End.