The daily standup has one job: surface what is blocked so the team can unblock it, fast, before the day burns. It is supposed to be cheap, short, and for the team. In a large number of companies it has quietly mutated into something else entirely, a ritual that keeps the same name and the same fifteen minutes but serves a completely different master.
You can spot the mutation by watching where people look while they talk. In a real standup, people address each other, because the point is coordination. In the mutated version, everyone faces the manager and delivers a small verbal status report, one after another, in a round-robin that has the shape of a team meeting and the function of a reporting line. Nobody is being unblocked. Everybody is being audited, gently, daily.
How the drift happens
Nobody decides to turn a standup into a status meeting. It drifts, one reasonable step at a time. A manager starts attending to "stay close to the work." Because the manager is present, people start framing their update for the manager rather than for their peers. Because the update is now for the manager, it becomes a performance of productivity rather than an honest flag of where things are stuck. Within a few weeks the meeting is optimized to make each person sound busy and on-track, which is the precise opposite of its original purpose.
This is the same gravitational pull that turns every recurring forum into a reporting exercise. The presence of an audience that can evaluate you changes what gets said. People stop raising blockers, because a blocker sounds like a problem you own, and you do not want to narrate problems to the person who writes your review. So the one thing the standup exists to surface is the one thing the mutated standup reliably hides.
The tell: blockers stop appearing
The clearest symptom is that real blockers vanish from the meeting and reappear three days later as missed deadlines. In a healthy standup, "I am blocked on the data team" gets said on day one and resolved by day two. In a status-meeting standup, that same blocker stays unspoken because admitting it in front of the manager feels like admitting you are behind. It surfaces only when it becomes undeniable, which is exactly when it is most expensive to fix.
This is a daily-cadence version of the check-in fallacy: the belief that asking people for an update at a fixed interval produces truth. It does not. It produces a managed answer calibrated to the audience. The cadence creates an obligation to report, and an obligation to report in front of an evaluator creates an incentive to report optimistically, which is why so many check-ins are theater rather than signal.
Why the status function shouldn't be in the standup at all
Here is the deeper point. The standup got captured by status because status had nowhere else to live. The manager attends the standup because it is the only place they can see what is happening. If the only window into the work is a meeting, the meeting will be colonized by the need to see, and coordination gets evicted to make room for visibility.
The fix is to give visibility its own home so it stops parasitizing the standup. When the state of the work is continuously visible without anyone narrating it, the manager does not need to attend the standup to stay close, because they can see the work whenever they want without a human performing it for them. The standup is handed back to the team, freed to do the only thing it was ever good at: surfacing blockers among peers who can actually clear them. This is what it means to run an operating cadence where each forum has one job and visibility is not smuggled into every meeting because it has nowhere else to go.
What to do this quarter
Run a quiet audit of your standup. Count how many genuine blockers get raised in a week, and how many get resolved that same day. If the number is near zero, your standup is a status meeting wearing standup's clothes, and the team knows it even if the calendar does not.
Then try the uncomfortable experiment: have the manager stop attending for two weeks, and give them a live view of the work instead so they lose nothing by being absent. Watch whether blockers start surfacing again. In most teams they do, almost immediately, because the audience that was suppressing them is gone and the meeting reverts to its purpose. If the manager genuinely cannot stay informed without sitting in the standup, you have not found a meeting problem. You have found a visibility problem, and the standup was just where it was hiding.
FAQ
How can I tell if my standup became a status meeting? Watch where people look while talking and count the blockers. If people address the manager instead of each other, and genuine blockers rarely get raised or resolved same-day, the meeting has been captured by reporting. A standup that surfaces no blockers is not unblocking anyone.
Why do blockers stop getting raised? Because an evaluator is in the room. A blocker sounds like a problem you own, and people are reluctant to narrate problems to the person who writes their review. The cadence creates an obligation to report, and reporting in front of an evaluator pushes the report toward optimism. This is the daily version of the check-in fallacy.
Should managers not attend standups? The question is why they attend. If it is to coordinate, fine. If it is because the standup is their only window into the work, the meeting will get colonized by their need to see. Give visibility its own home and the manager can step back without losing anything, which hands the standup back to the team.
What replaces the status function of the standup? A continuously visible view of the work that nobody has to narrate. When progress to plan is always visible, the manager stays informed without attending, and the standup is free to do coordination instead of reporting.