The Standup That Became a Status Report

The original standup came from a simple observation: if a team meets briefly every day and each person says what they are working on and what is blocking them, the team can self-organise around problems before those problems become expensive. Someone is blocked on a decision. Someone else can make that decision. Someone is about to build something that someone else already built. They can share it instead. The coordination that would have taken three meetings and two weeks of email can happen in twelve minutes.

This is a genuinely good idea. It works when it is executed well. It works in almost no teams I have observed in the last several years.

What replaced it is a ritual that looks like a standup from the outside and produces almost none of the value the standup was supposed to produce. Each person reports what they did yesterday and what they plan to do today. Nobody mentions blockers because the culture around blockers is weird and competitive in ways that make admitting them feel risky. The manager listens and nods. The meeting ends. The team disperses and continues working in the same direction they were working before the meeting, which was the same direction as yesterday, which will be the same direction tomorrow.

The team has performed coordination without achieving it.

How the transformation happens

The daily standup becomes a status report through a process that is gradual and feels like nothing is changing.

It starts when someone with authority begins attending the meeting. Before, the standup was a team coordination tool. The team talked to each other. After, there is a person in the room who evaluates what they hear. The social dynamic of the meeting changes immediately, even if nobody says so explicitly. People stop talking to each other and start talking to the authority figure. The content of what they say shifts from what would be useful for the team to know toward what would make a good impression on the person who influences their career.

Blockers are the first casualty. Mentioning a blocker in a standup requires admitting that you are stuck. In a team of peers, being stuck is normal and admitting it is how you get help. In a room with a manager present, being stuck can feel like an admission of inadequacy. The rational response to this incentive is to not mention blockers in the standup and to handle them through other channels, or to just not handle them and try harder on your own.

The second transformation is the lengthening. A standup that is not producing coordination still needs to fill its time slot. People begin elaborating on their updates because elaboration is the only content available once the real information, blockers and coordination needs, has been suppressed. “I’m working on the payment integration” becomes “I’m working on the payment integration, I’ve got the Stripe client set up and I’m now working through the webhook handling, which is a bit complex because there are multiple event types and I need to make sure I’m handling idempotency correctly, and then I’ll move on to writing the tests.” This is a performance of work, not a coordination of it.

The third transformation is the ordering. Someone decides that the standup should go around in a consistent order so nobody gets missed. Now the meeting has a sequence. The first person gives their update. The second person gives theirs. Nobody is listening to the first person because they are thinking about what they will say when their turn comes. The information in the meeting is transmitted but not received. The meeting is producing the form of communication without the substance.

What the meeting costs

A twenty-minute standup with ten engineers costs two hundred minutes of engineering time plus the cognitive overhead of context switching into and out of the meeting. For a team working on complex problems, a context switch is not a trivial cost. The research on this is not ambiguous: returning to deep work after an interruption takes significant time. A standup in the middle of the morning breaks the longest uninterrupted work block available in most engineers’ days.

If the meeting is producing the coordination it promises, this cost is worth paying. If it is producing a status report that the manager could have gotten from a project management tool, it is not.

The second cost is the false signal it produces. A team that has a daily standup has the feeling of coordination. The feeling is not the thing. A team that feels coordinated and is not will discover this during incidents, during integration, during the week before a launch when things that should have been synchronised turn out not to have been. The standup suppressed the signal that coordination was not happening, which delayed the discovery of the problem.

The third cost is to psychological safety. A meeting where people feel they cannot be honest about blockers is a meeting that is actively training the team not to be honest about blockers. This training generalises. The team learns that the appropriate thing to do in shared contexts is to present a version of reality that reflects well on yourself. This is the opposite of the culture required to build things well.

# The blocker that should have been mentioned in the standup
# but wasn't because the manager was in the room:

# Day 1 standup: "Working on the authentication service"
# Reality: blocked on a decision about session storage strategy

# Day 2 standup: "Still working on the authentication service"
# Reality: made a local decision about session storage,
# it's probably wrong, starting to suspect it conflicts
# with something the infrastructure team is planning

# Day 3 standup: "Almost done with authentication"
# Reality: the session storage decision does conflict,
# discovered it by reading a slack message from two weeks ago,
# need to redo three days of work

# Day 4 standup: "Running into some complications"
# Reality: should have mentioned this on day 1,
# the infrastructure team could have answered in five minutes,
# three days of work wasted, launch date at risk

# What should have happened on day 1:
# "I'm working on the authentication service and I need a decision
# on session storage strategy before I go further.
# Can someone from infrastructure join a fifteen-minute call today?"
#
# Total cost: fifteen minutes
# Actual cost: three days

What the standup is for

The standup is for one thing: surfacing the information that would change what the team does today, before the team goes off and does it.

This is a much narrower scope than “update everyone on what you are working on.” Most updates do not contain information that would change what anyone does today. They are true and they are fine and they do not need to be shared in a synchronous meeting.

The information that does need to be shared is the exception, not the rule. Someone is blocked and someone else can unblock them. Two people are about to build the same thing. Someone has discovered that the approach the team agreed on does not work and the team needs to know before they proceed. Something happened in production overnight that affects what the team should prioritise today.

A standup that is only about exceptions is short. If nothing has changed, if nobody is blocked, if the team is proceeding as planned, the standup takes three minutes. This is not a failure of the meeting. It is the meeting working correctly.

The problem is that a three-minute meeting feels unsubstantial. Management wants to feel that coordination is happening. The team wants to feel that the meeting was worth interrupting their work for. So the meeting gets filled with updates that are not exceptions, and it stops being a coordination mechanism and becomes a broadcast.

The question that changes the meeting

There is a single question that transforms a standup from a status report into a coordination mechanism: “Is there anything blocking you or anything you need from someone else today?”

Not “what did you do yesterday.” Not “what will you do today.” Those questions produce the status report. This question produces the coordination.

The reason it works is that it is specific about what information is being sought. It tells the team that the purpose of the meeting is to surface needs and blockers, not to demonstrate activity. It creates a shared vocabulary for the kind of thing that is appropriate to bring to the standup. It separates the meeting from the performance. Standup structure that produces coordination:

Any blockers? (Go around quickly. Yes or no. If yes, briefly what.) Any collisions? (Is anyone working on something that might affect what someone else is doing today?) Any priorities that have changed since yesterday? Does anyone need anything from anyone else today?

Total time for a team of eight with nothing urgent: four minutes. Total time when something needs coordination: ten to fifteen minutes. The remainder of that time is a focused conversation between the people who need to be in it, not an update session for people who do not.

The people who do not need to be in the focused conversation can leave. This sounds radical and it is not. If the standup reveals that the backend team needs to align on an API contract and that conversation does not involve the frontend engineers, the frontend engineers should not sit in that conversation. They have work to do.

The async alternative

For teams that have tried to fix the standup and found that the social dynamics of the meeting resist fixing, there is an alternative worth considering seriously: the async standup.

Each person writes a brief update at the start of their day. Not a status report. An exception report. They write it only if there is something the team needs to know. If there is nothing, they write nothing. The updates appear in a shared channel. People read them when they start work. Conversations that need to happen get threaded off the relevant update.

This has several properties that the synchronous standup lacks.

The writing requirement changes what people say. Writing requires more thought than speaking. People are less likely to perform in writing because performance in writing is more visible as performance. The updates become more honest and more useful.

The async format removes the status reporting pressure. There is no manager watching while you give your update. There is no audience to perform for. The audience for the written update is the team, and the team reads it to get information, not to evaluate your productivity.

The format scales across time zones. A distributed team that has a synchronous standup is forcing some portion of the team to attend a meeting at an inconvenient time for the benefit of feeling coordinated. The async alternative gives the same information without the forced synchrony. async standup format that works: Post only if you have something in one of these categories: BLOCKED: [what you need and who can help] COLLISION RISK: [something you’re doing that might affect others] PRIORITY CHANGE: [something that’s changed from the plan] NEEDS INPUT: [a decision that needs to be made before you proceed] Do not post:

• what you did yesterday
• what you plan to do today
• updates that are proceeding normally If everyone on the team posts nothing, coordination is working. That is success, not absence.

The first time a team tries this, it feels wrong. The channel is quiet. Nobody is posting. The team is used to equating posts with coordination and silence with dysfunction. The quiet is actually the team working without unnecessary interruption. It takes a few weeks to trust it.

The manager’s role

Most standup transformations from coordination to status report happen because of managerial behavior, and the fix also requires managerial behavior.

The specific behaviors that turn a standup into a status report: asking follow-up questions about individual updates, which signals that updates are being evaluated; staying in the meeting without contributing to coordination, which signals that the meeting is for observation; showing visible reaction to updates that are incomplete or less impressive than others, which signals that the meeting is a performance context.

The specific behaviors that keep a standup as a coordination tool: asking only about blockers and coordination needs; leaving the meeting when no further coordination is needed; making it explicitly safe to mention blockers by responding to them with help rather than evaluation; staying out of the meeting entirely sometimes and trusting the team to coordinate without observation.

The manager who wants real coordination has to resist the pull toward using the standup as a status collection mechanism. The pull is strong because the standup is the only synchronous whole-team touchpoint on most days, and the temptation to use that touchpoint to know what everyone is doing is real. The cost of giving in to that temptation is the meeting itself.

You cannot have both. A meeting that produces coordination cannot also produce status for management. The incentives are in opposition. The team will give you whichever one the structure of the meeting rewards, and if the structure rewards performance, they will perform.

What coordination actually looks like

Real coordination does not look like a meeting. It looks like an engineer who is about to go down a path that will take three days pinging someone who can answer a question in five minutes before they start. It looks like two engineers who are about to build conflicting things noticing it in a pull request review and getting on a call. It looks like a blocked person asking for help as soon as they are blocked rather than spending two days trying to unblock themselves.

These coordination events do not require a standup. They require a team culture where asking for help is normal and valued, where information sharing happens as information becomes available rather than at a scheduled time, and where the cost of interrupting someone for something important is understood to be lower than the cost of not interrupting them.

The standup cannot create this culture. It can reflect it, if it is structured to surface the moments when coordination is needed and respond to them efficiently. But a broken standup cannot be fixed by changing the format while leaving the culture intact.

The format is not the problem. The format is a symptom.

The culture that the standup reveals, where performance is rewarded over honesty, where admitting blockers is risky, where coordination is performed rather than achieved, that culture is the problem. The standup just makes it visible once a day.

Fixing the standup means fixing that, and fixing that is harder and more important than any meeting format change.

The meeting is a mirror. Look at what it shows you.