Why does a daily stand-up drift into a status report to a manager, and what does that cost?
answer
- Who is the audience in the room?
- Output is a changed plan, not information
- Talk about work items, not people
- Blockers surface late when honesty costs something
basics
~20 sA stand-up drifts into a status report when the audience becomes a manager instead of the team. Reporting then replaces re-planning: nobody adjusts the day, blockers surface late, and the meeting stops changing what anyone actually does.
solid answer
~50 sA daily stand-up exists so the people doing the work can re-plan the next day together: surface blockers, spot work that has stalled, and decide who helps whom. It drifts when someone senior starts receiving the update. Attention turns outward, each person speaks *to* that person rather than to peers, and an honest "I am stuck" becomes "making progress". The tells are easy to read: a round of three ritual sentences, people disengaging until their turn, creeping length, and nothing about anyone's day changing as a result. The cost is late discovery - a blocker that a ten-minute conversation would have cleared instead waits days. The fixes are structural: walk the work items rather than the people, take detail to a short follow-up, let observers listen but not ask, and let the team own the format.
go deeper
Be ready to state the purpose in one sentence - the people doing the work re-plan the day together - and to name two signs it has become a report, such as everyone addressing the same senior person.
Explain the mechanism rather than the symptom: the audience determines what people are willing to say. Expect to describe concrete fixes, such as walking work items instead of people and moving detail to a follow-up, and why each one works.
Show that you have repaired one. Talk about what you watched afterwards - how quickly blockers were named, how long stalled items sat unnoticed - and how you handled the observer whose presence changed what the team would admit.
Own the economics and the norm. A daily meeting across a whole team is real capacity, so argue for when a team should stop holding one, what must replace its function, and how you keep management visibility needs from reshaping team meetings.
## What the meeting is for A daily stand-up is a short, same-time-every-day conversation among the people doing the work. Its output is not information — it is **a re-planned day**. Three things should be able to change because it happened: work that has stalled gets named, at least one person's plan for the next few hours moves, and any blocker acquires an owner and a next step. If nothing could change, the meeting produced nothing, however smoothly it ran. That framing is the entire argument for holding it synchronously. Written state is cheaper: a visible work board, a short note in a team channel or a wall of cards all convey who is on what, without pulling a whole team out of focused work at the same minute every day. The only thing the meeting buys over writing is **a conversation between people who can act on what they hear**. Remove that and you are paying a meeting price for a message. ## How the drift happens The slide into a status report is rarely a decision anyone makes. It arrives through one of a few familiar doors: - **The audience changes.** A manager or a stakeholder starts attending "just to listen". People are not being dishonest when they then speak outward instead of sideways; they are answering the person they believe is evaluating them. - **The round hardens into a script.** Three questions asked person by person become a recital. Once the format guarantees everyone speaks for roughly the same length, content stops mattering. - **The work stops overlapping.** If seven people are on seven unrelated items, there is genuinely nothing to co-ordinate, and the meeting survives on habit alone. - **Delivery pressure raises the price of admitting trouble.** When a date is fixed and visible, "I am stuck" is heard as a confession rather than a request for help. A worked example. A seven-person team building an allotment-management service ran a nine-minute stand-up. As an annual conference the release was timed to came into view, a delivery manager began attending. Within three weeks the meeting averaged twenty-three minutes, and every update was delivered to the manager rather than to the team. Two developers spent parts of four days independently chasing the same plot-booking defect. Neither had said "I am stuck" out loud, because in that room the sentence had a different audience and therefore a different meaning. ## The tells | Signal | Working stand-up | Status report | |---|---|---| | Who people look at | Each other | The most senior person present | | What is discussed | Work items and what is blocking them | What each individual did yesterday | | Attention | Everyone follows the whole set of work | People wait for their turn, then disengage | | Result | Somebody's plan changes | State already visible is spoken aloud | | Blockers | Named early, with an owner | Surface days late, usually somewhere else | | Length | Short and roughly stable | Creeps, then earns a discipline reminder | ## Getting it back 1. **Change the unit from people to work.** Walk the items — starting with the ones closest to finished — instead of going around the room. Nobody has a turn to fill, and stalled work becomes visible without accusing anyone of anything. 2. **Take detail offline.** Anything needing more than a sentence goes to a short follow-up with only the two or three people it concerns. Say it out loud in the meeting so the habit becomes normal. 3. **Set the rule for observers.** Anyone may listen; nobody outside the team asks questions or requests updates during it. If a manager needs visibility, give them the work board or a written summary — both are cheaper and neither distorts what the team is willing to say. 4. **Let the team own the format.** The three-question round is one option, not a requirement. Teams that choose their own shape defend it; teams handed a shape recite it. 5. **Check the output, not the ritual.** Every couple of weeks, ask what actually changed because of stand-up. If the honest answer is "nothing, for a fortnight", fix the meeting or stop holding it. ## When the meeting itself is the wrong tool Not every team needs a daily one. A team whose members work on genuinely independent items, or one spread across time zones with a two-hour overlap, may get more from written updates plus one short synchronous slot — provided something else still surfaces stalled work within a day. The failure to avoid is deleting the meeting and keeping none of its function: blockers then appear at the end of the iteration, which is precisely the outcome the meeting existed to prevent.
- The iteration review has the opposite failure - nobody outside the team attends. What is lost there?That event exists to get feedback from the people who will use or fund the work, so an empty room means the team is inspecting its own output and calling it validation. Direction errors then survive a whole iteration instead of a day. The usual causes are inviting the wrong people, demonstrating at the wrong level of detail, or a slot nobody can make - fix those before concluding that stakeholders do not care.
- A manager insists on attending the daily stand-up every day. What do you propose?Say yes to attendance and no to participation: they may listen, but questions and requests go outside the meeting. Then offer something better, because what they actually want is visibility - the team's work board, or a short written summary, both cheaper than a daily meeting. If the outward-facing update habit returns anyway, ask the team privately what went unsaid while that person was in the room.
- How would you run this for a team split across time zones with a two-hour overlap?Move the reporting half to writing and spend the overlap on the conversation: short written notes beforehand, then a brief synchronous slot that walks only the items that are stalled or contested. Guard the function, not the format. Something must still surface stalled work within a day, otherwise blockers reappear at the end of the iteration, which is exactly what the meeting existed to prevent.
A stand-up is a huddle, not a roll call: the huddle only earns its place if the next play changes because of it.
saying these in an interview costs you the question
- Says the stand-up exists so a manager learns what happened
- Treats the three-question round as a required format
- Thinks silence in the meeting means nobody is blocked
- Fixes a long stand-up by asking people to talk faster
- Replaces the meeting with written updates and drops its function