A status report answers the question: “What do I need to tell management about what’s happening?” It flows upward — information moving from people doing the work to people who need visibility into it.
A standup answers a different question: “What does my team need to know right now so that we can meet our commitments?” It flows laterally — information moving between people doing the work, for the benefit of the people doing the work.
The distinction seems subtle. In practice, it changes everything about how the meeting runs and what it produces.
What happens when the standup becomes a status report
When team members understand the standup as a report to management — or to the Scrum Master acting as a proxy for management (which is a Scrum Master behaving like a Project Manager, not Agile at all) — the accountability structure inverts. People are no longer coordinating with peers; they’re reporting upward. And the social dynamics of upward reporting take over: you surface what makes you look productive, you downplay blockers that might reflect badly, you shape the message for the external audience rather than for the team.
Blockers go underground. The honest “I’m stuck and need help” becomes “I’m working through some challenges.” The team loses the signal it most needs: where the work is actually stuck, who needs help, where the handoffs are misaligned.
The standup was designed to surface exactly that information — not for management’s benefit, but to increase the team’s likelihood of overcoming any obstacles that arise during implementation. The three questions it traditionally structures around (what did I do, what will I do, what’s in my way) exist to generate lateral awareness. When the meeting gets reframed as a report, those questions stop producing honest answers. And, no, those are not the best questions to ask during a standup — but they’re a reasonable start.
What a real standup looks like
In a functioning standup, the people doing the work are talking to each other, not to a facilitator. The accountability is peer-level: “I’m stuck here” generates offers of help, not concern about how the answer will look. The outcome is a shared picture of where the work stands and who needs to talk to whom.
Standups that have become status reports tend to be longer, duller, and more carefully managed. Standups that are genuinely lateral coordination tend to be brief, direct, and occasionally generate sidebar conversations: “let’s talk after the standup about your challenge.”
That sidebar is the standup working, where someone stuck on their own work gets what they need from the people beside them and the work moves again. A status report meeting can’t produce that, because the information in a status report is shaped for the recipient above, not for the peers alongside.
Related content
- Do This Instead of Daily Standups (or Risk Failing) — Agile4AI on YouTube
Comments 0