9am. The team assembles in a rough circle, or more likely in a video call with fourteen faces in fourteen boxes. The ritual begins. “Yesterday I worked on the login bug. Today I’ll keep working on the login bug. No blockers.” Next. “Yesterday I finished the API integration. Today I’ll start on tests. No blockers.” Next.

Nobody is making eye contact. Half the people are typing. In eleven minutes it will be over and everyone will return to whatever they were doing before they were interrupted.

This is not a standup. This is a status report delivered standing up.

Kent Beck and the XP practitioners who formalized the daily standup did not design a status meeting. They designed something much closer to a military briefing: a quick, structured exchange of information among peers coordinating around work in progress. Three questions - what did you do, what will you do, what’s in your way - were never meant to be answered to anyone. They were meant to surface information for everyone.

The distinction matters. When you answer to someone - a manager, a scrum master, a team lead - you’re performing accountability. When you answer for everyone, you’re doing coordination. The first is theater. The second is useful.

What XP intended: fifteen minutes, standing so the meeting couldn’t get comfortable, focused on the work itself. You’re supposed to leave knowing what everyone else is working on so you can unblock each other, identify collisions, and spot opportunities to help. The three questions are a scaffold for that. They’re not the point.

What most teams do instead is a standup-shaped status meeting, with all the theater that implies.

The failure modes are consistent. “No blockers” becomes the default answer because admitting to a blocker in front of a group feels like admitting incompetence. The three questions become a script recited by rote rather than a genuine exchange. People prepare their answers in advance, which means they’ve stopped listening to everyone else’s. And the meeting’s value gets measured by whether it stayed under fifteen minutes, rather than by whether the team coordinated any better because of it.

The worst version is when the standup becomes a reporting mechanism for someone who isn’t doing the work. A manager who attends standup to know what the team is doing has turned a coordination ritual into a surveillance one. The team learns immediately. They answer for the manager, not for each other. The meeting stops producing coordination and starts producing performance.

There’s a format that works better, and it’s not new: instead of going person-by-person, go story-by-story. Walk the board. For each active piece of work, ask: what’s the status? What’s blocking it? Does anyone need to talk after this?

This is a different meeting. You’re looking at the work, not the people. Everyone’s attention is on the same thing at the same time. Blockers are visible because they’re attached to specific work rather than to individuals who have something to prove. The meeting ends when the work is covered, not when everyone has had their turn.

When the standup is organized around work in progress, it produces the thing it was designed to produce: a shared understanding of where the team is and what’s in the way.

Some teams run genuinely useful person-by-person standups, and it’s usually because the team is small enough and trusts each other enough that the three questions surface real information. Four people who actually listen to the answers can make the format work. Fifteen people going through the motions cannot.

Scale is the killer. Beyond a certain team size, the person-by-person format produces so many updates that nobody can track all of them. You stop listening after the fourth person because you can’t retain it anyway. The meeting delivers information nobody processes, which means it delivers nothing.

The daily standup is not a broken idea. The idea is sound: a short daily touch point that surfaces blockers and keeps the team aligned. Teams that skip it drift into isolation. People work for days on something that someone else could have unblocked in five minutes if they’d known.

The problem isn’t the standup. The problem is the standup that looks like a standup but functions like a status meeting. Once the meeting is about accountability rather than coordination, it stops serving the people doing the work and starts serving the people watching it.

Fix the question. Instead of “what did you do?” ask “what’s moving?” Instead of going around the room, go around the board. Let the work lead, and let the team coordinate around it.

The standup doesn’t take fifteen minutes because Kent Beck liked round numbers. It takes fifteen minutes because that’s how long coordination takes. Reporting takes longer. Don’t confuse the two.