DEV Community

Cover image for The Standup Theatre
Om Keswani
Om Keswani

Posted on

The Standup Theatre

It’s 9:15 AM. You’re holding a coffee you didn’t want yet, listening to the fourth person in a row say, “Yesterday I worked on the API integration, today I’ll continue the API integration, no blockers.”

Nobody’s fooled. Everyone knows the API integration has been “continuing” for six days. But we all nod anyway, because the real goal of this meeting is no longer coordination. It’s performance.

Somewhere between the agile manifesto and the daily grind, standups stopped being about unblocking work and started being about proving you’re working. The audience shifted. People aren’t talking to their teammates anymore. They’re talking to the manager, the tech lead, the person who might whisper something in a one-on-one. Without anyone saying it, the three questions became a tiny audition. Can you sound productive in under sixty seconds?

The cost of this theatre is bigger than most teams admit.

Real engineering is messy. You spend a morning falling into a rabbit hole only to discover the problem was a misconfigured feature flag from two sprints ago. But “I traced a bug to an old flag and have no fix yet” sounds like you did nothing. So you paraphrase: “Making progress on the checkout issue.” That sanitised sentence protects you, but it buries crucial context. Your teammate who fixed that flag last month never hears about the fallout. The team repeats the same mistake next sprint because the truth never made it onto the board.

Then there’s the help that never arrives. A standup is supposed to surface blockers. But in a performative standup, admitting you’re stuck feels like saying you’re incompetent. So you don’t say it. You go back to your desk, open the same undocumented internal library, and spend another afternoon staring at the screen alone. The ten-minute conversation that could have saved you never happens, because you learned that the safest thing to say is “on track.”

And management loves it. Every day they hear a chorus of “on track,” and they walk away feeling secure. That’s the most dangerous part. A smooth standup isn’t a sign of health; it’s often a sign that problems are being hidden just well enough to blow up spectacularly three days before the sprint ends. The standup becomes the very thing that hides reality from the people who need to see it most.

I once worked on a team where a developer spent two weeks struggling with a flaky deployment pipeline. Every standup he said, “Still working on the deployment stuff.” Nobody asked follow-ups, because the standup was a status broadcast, not a conversation. Two days before launch, the pipeline collapsed entirely. We scrambled, people cancelled weekends, and the fix ended up taking a pair of engineers four hours. If one person had said, “Hey, that sounds painful, let’s look at it together after standup,” the entire crisis would have been a non-event. But the format didn’t invite that. The format invited performance.

How do you break out of it?

I’ve seen one trick work more often than any other: talk about the work, not the worker. Instead of going around the room person by person, walk the board from right to left—closest to done first. Ask about the tickets, not the humans. “What’s stopping this from shipping?” It becomes much harder to perform when the question is about a specific card. You can’t polish a stuck ticket into sounding like progress. You just have to say, “The payment service dependency hasn’t responded,” and suddenly that’s not a personal failure. It’s a fact. And facts invite help.

Another thing: let standups be awkward. A good standup occasionally has a moment of silence where everyone stares at a problem and realises they don’t have an immediate answer. That’s okay. If your standups never feel slightly uncomfortable, you’re probably not surfacing the real stuff. The goal isn’t a clean, reassuring daily ritual. The goal is to make invisible work visible, and invisible work is rarely tidy.

I’ve also seen teams kill standups entirely and replace them with asynchronous Slack threads. That can work, but only if the team already has enough psychological safety to be vulnerable in text. Otherwise, you just get polished bullet points instead of polished monologues—same theatre, different stage.

The standup isn’t the problem. It’s a neutral container. It becomes theatre when people learn that honesty has a cost and performance has a reward. Fix that, and a 15-minute circle can still do its real job: making sure nobody fights the monster under the stairs alone.

So tomorrow morning, when someone says “no blockers,” maybe pause and ask, “Really? Even that nasty logging bug from yesterday?” You might just find that the show is over and the real work begins.

Top comments (0)