The Daily Standup Is for the Team, Not the Manager

I can tell within thirty seconds whether a standup is healthy. If every team member faces the Scrum Master or PM while speaking, it is a status report. If they face each other, it is a coordination meeting. The difference matters enormously.

The daily standup exists so the development team can synchronize their work and identify blockers. It is a team ceremony. The Scrum Master or PM is there to listen and help remove impediments, not to receive reports.

How It Goes Wrong

The most common dysfunction is when the PM or manager runs the standup as a roll call. "Alice, what are you working on? Bob, what about you?" This creates a hub-and-spoke dynamic where everyone reports to the center. Team members stop listening to each other because the information is flowing to the manager, not across the team.

The second dysfunction is using the standup to solve problems. Someone mentions a blocker and the next twenty minutes are spent debugging it in the meeting. The standup is for surfacing problems, not solving them. Take it offline.

How to Fix It

Stop calling on people. Let the team self-organize the speaking order. Walk the board instead of going around the room. Start with the rightmost column and ask "what needs to happen to get this to done?" This shifts the focus from people to work.

As the PM, I physically step back during standup. I do not stand in the circle. I stand slightly outside it. This is a deliberate signal that the meeting is not for me. When someone directs their update at me, I redirect: "Tell the team, not me."

It takes a few weeks to shift the dynamic, but when it clicks, the standup becomes something the team actually values. They start coordinating. They start helping each other. They stop waiting for you to solve their problems. That is the whole point.