Your Standups Are Status Theater

The daily standup was supposed to be a quick sync. Fifteen minutes max. Three things: what I did, what I'm doing, what's blocking me. Done.

Now I sit through 45-minute standups where the team lead reads every ticket in the sprint, asks clarifying questions about features from Q3, and everybody's still confused at the end.

Nobody's getting unblocked. We're just performing status updates. For an audience. That watches every day.

The Standup Theater Problem

Here's what happens in your 45-minute standup:

Person one talks for five minutes about a bug they're fixing. It's interesting context for them and maybe the QA person. Nobody else cares. But everyone listens. You've got to be in the room in case you're next.

Person two is waiting. They describe their work. Nobody asks questions because we're on a schedule.

Person three mentions they're blocked on a database schema change. The person who can unblock them is on mute. By the time the standup ends, they're still blocked, but now the whole team knows about it.

The team lead sums up. "Okay, we're on track for the sprint." But you're not. You're just on pace to ship what's already assigned.

The real blockers didn't get solved. The opportunities for collaboration didn't surface. But you've all now spent 45 minutes confirming that people are working on the things they said they'd work on.

That's not a standup. That's a status meeting. It's for the benefit of someone who's not in the room, and you're all just reciting your lines so they can report up.

Why It Doesn't Work

Daily standups only work if they have a specific purpose: to unblock people right now.

If you spend 90% of your standup reporting status and 10% solving problems, you've got the ratio backwards.

The standup should go like this: "Hey, I'm stuck on X. Does anyone know?" If yes, you solve it immediately. If no, you move on. Five minutes. Done.

But standups have drifted. Now they're a management tool. A way to track who's doing what. A way to ensure nobody's slacking. A way to have artifact that shows the team was coordinated.

That's not what standups are for. And it's making them useless.

The Asymptote Problem

Here's the thing: in a small team (3-5 people), standups work great. You naturally unblock each other. You coordinate on who's working on what. Five minutes. Useful.

Add people. Now you've got 10. Five minutes isn't enough time for everyone to talk. So the standup expands. Now it's 15 minutes. Still not enough. 25 minutes.

At some point, you hit the asymptote. You've got 12 engineers. The standup is 30 minutes minimum, and half of it is irrelevant to you. You attend because it's mandatory. You're not getting unblocked. You're just... attending.

That's when you know the standup has become broken.

What Actually Works

There's a hierarchy. Use the format that fits your team size:

3-5 people: Daily standup, in person or video, five minutes. Works great.

6-10 people: Daily standup, but split by team or feature area. If engineering is one team, maybe you have two standups. Five minutes each. Less noise.

10+ people: Async updates. Post in Slack. Read in the morning. Reply if you're blocked. Takes two minutes. Questions get answered in thread.

I've seen teams scale past 20 with async standups and no weekly meeting. They ship faster.

The async model works because it forces clarity. When you write "I'm stuck on database migration," it's now documented. The right person sees it and responds. You're not waiting for a meeting. You're not hoping the person reads your lips during standup.

For problems that need real-time discussion, you schedule a small working session. "Hey, three of us need to figure out the API design." Thirty-minute block. Right people. Done.

The Real Question

Before you run your daily standup, ask: "If I skipped this meeting, what would break?"

If the answer is "I wouldn't know if people were working," that's not a standup. That's a surveillance tool. Replace it.

If the answer is "I wouldn't find out that I'm blocked," then the standup is valuable. Keep it.

If the answer is "nobody would know what everyone's working on," well... why do they need to know? If there's an actual coordination problem, a standup won't solve it. You need better communication channels.

Most standups that've metastasized are solving a visibility problem, not a coordination problem. And visibility should be async. It's less important and time-sensitive than coordination.

The Fix

If your standup is longer than 15 minutes, you've broken something. Either split it, move it async, or admit it's not a standup anymore—it's a team meeting, and you should call it that.

But don't lie and pretend 45 minutes of status reading is a standup. It's not. It's your team sitting in a room, not working, for three hours a week.

That's ten hours a month. Fifty hours a quarter. That's a whole person. You could have that person fix bugs, ship features, or mentor other engineers.

Instead, they're performing status theater. For what?

Get your time back. Make your standups short, valuable, and asyncable. Use the time you save to actually ship.