Operations

Eight engineers, fifteen minutes, zero re-plans

A standup that never changes anyone's plan has stopped coordinating and started reporting to the manager. Kill the format; ask one question instead.

Eight engineers, fifteen minutes, zero re-plans
Illustration · Deimar Gutiérrez

The room went around in a circle. 8 engineers, 15 minutes, one voice at a time: what I did yesterday, what I'm doing today, whether I'm blocked. A textbook three-question standup. Nobody asked for help. Nobody offered any. It ended on time and the team scattered.

Afterward I asked the manager how many of the last 10 standups had changed anyone's plan. He thought about it. He couldn't name one.

The standup had turned into a status report. That is where every round-robin lands without active facilitation. Repeated daily, the three questions harden into a script the team runs the way a tape plays. The performative half of each update, what the engineer wants the manager to hear, drowns out the operational half, what the engineer needs help with. Inside a quarter, the meeting runs for the manager, not the team.

The tell is easy to spot once you look. People report work; they don't coordinate it. Nobody says I'm stuck on this, has anyone hit it before. Nobody says I'm on this today, want to pair. Nobody changes course on anything a teammate said. Zero coordination out, an hour of engineering time a day in. Same failure as a status meeting that should have been three numbers.

It survives because it looks organized. The manager can describe it in one sentence. It runs at the same time daily. Everyone shows. The artifacts of process are all present. That none of the process produces its output stays invisible, because the output, coordination, only shows up in its absence, and the absence is now the baseline.

So delete the three questions. Replace them with one: what does the team need to surface today? Then wait. The silence is the data. Nothing to surface, and you're done in ninety seconds and the team gets its time back. Something to surface, and you're running real coordination instead of a reading of the same status report the all-hands became.

The harder problem is cultural. Teams don't surface blockers because it reads as admitting weakness, and the manager hasn't built a room where admitting it is safe. Until the manager visibly, repeatedly rewards the engineer who says I'm stuck, the format won't matter. The format is the second-order problem. The safety to use it is the first.

Run the test in reverse: if your standup vanished tonight and nobody noticed for a week, it stopped being a meeting weeks ago. It's already gone. All that's left is to stop paying for it.