Nine thirty-one on a Tuesday. Eight people in a loose semicircle, and an engineering manager leaning against the wall with a laptop balanced on one arm. One by one, each developer turns to face her and delivers the liturgy: yesterday I worked on the payment refactor, today I'll keep working on the payment refactor, no blockers. Nobody asks a question. Nobody changes a plan. Fourteen minutes later the room empties and every person's day looks exactly like it did before the meeting.
That wasn't a standup. That was a status report performed live, and an email would have done the job with less standing.
The daily exists for one purpose: the team replans its next twenty-four hours toward the sprint goal. Not to prove that everyone worked yesterday. Status radiates upward, to managers and stakeholders who want reassurance that things are on track. Planning radiates inward, between the people doing the work. The moment your standup starts radiating upward, it has stopped being a standup, whatever the calendar invite says.
How the decay happens
No team decides to run a bad standup. It decays, and the decay follows a predictable path.
It usually starts with an audience. A manager or a stakeholder joins, with good intentions, just to stay informed. Watch the body language over the following weeks. People stop talking to each other and start talking to the most senior person in the room. Updates get longer and more defensive. "I fixed the flaky test" becomes "I spent most of yesterday investigating the intermittent failures in the integration suite, which turned out to be more involved than expected." Same fact, but now it's a justification. Once one person performs, everyone performs, because nobody wants to be the one whose update sounded thin.
The three questions accelerate it. What did I do yesterday, what will I do today, what's in my way: those were only ever prompts for a planning conversation. Recited in order, by each person, every day, they turn into a script. And a script invites the worst standup habit of all: rehearsing your own answer while other people are talking. You've done it. I've done it. Half the room is composing "yesterday I..." in their heads, which means nobody is actually listening, which means the one moment where somebody could have said "wait, I hit that exact problem last month" slides past in silence. The 2020 Scrum Guide quietly removed the three questions. Most teams never noticed.
Walk the board, not the room
The strongest structural fix I know is to stop going around the circle and start walking the board. Pull up the sprint board, start with the column closest to done, and go through the items: what does this one need to reach done, who's on it, is anything in the way. Work backwards through the columns until you hit the sprint backlog, then stop.
The reason this works is simple: it centers the work instead of the people. Person-by-person asks "what did you do," and everyone owes an answer, even the person who spent yesterday in interviews and has nothing useful to report. Board-first asks "what does this item need," which is a planning question. It also exposes the things person-by-person hides. The card that's been sitting in review for three days with no owner never comes up when people narrate their own activity, because it's nobody's yesterday. On a board walk it's the first thing you see.
Walking the board keeps the sprint goal in the frame too. Finishing the items closest to done is almost always the fastest route to the goal you committed to at sprint planning, and starting from that end makes the priority physical: we finish things before we start things.
It's not free. Board walks only work if the board is honest; a board that lags reality by a day produces a standup about fiction. And quiet people can disappear even more easily than in a round-robin, so someone needs to notice who hasn't spoken all week. But given a current board, I'd pick this format over person-by-person for any team bigger than four.
The sixteenth minute
Every standup eventually produces the moment where two people lock onto a problem and start solving it right there. That's a good instinct in the wrong slot. Four minutes into a debugging session, six other people are checking their phones, and the meeting has quietly become a hostage situation.
The fix isn't to ban the conversation. The fix is to park it, and to park it properly: name the topic, name who stays. "That's a sixteenth-minute topic. Priya and Tom stick around." The standup ends on time, the real conversation happens immediately after with exactly the people who need it, and nobody learns to dread the daily. The naming matters. "Let's take it offline" with no names attached is where topics go to die. A parked topic with two named owners actually happens.
Remote teams and the async question
Should a distributed team run the daily as a written check-in instead of a call? Sometimes yes, genuinely. If your team spans Warsaw to Wellington, every possible meeting time is somebody's 6 a.m. or 11 p.m., and forcing a call just chooses whose sleep matters least. A mature team with strong writing habits can run a written daily that beats a groggy video call: updates posted against board items, read by everyone, with a hard rule that anything blocking triggers a synchronous conversation within the hour.
Be honest about what you lose, though. The best moment in any standup is unplanned: someone mentions a problem in passing, and someone else says "wait, I can help you with that." Async kills most of those, because reading an update at your convenience isn't the same as hearing the frustration in someone's voice. Written check-ins also hide how people are actually doing, which a room full of humans picks up for free. Distributed teams have to check deliberately, and a lightweight team mood check does more for that than a thread of "no blockers" ever will; it's one of the reasons we built that into ScrumMastr.
So the honest rule: async written standups are for teams that are forced apart by timezones, or that have already proven they help each other without being in a room. For a co-located team, or a remote team in adjacent timezones, going async is usually a downgrade dressed up as efficiency.
The same work, two meetings
Take the team from the opening and give them the same morning back.
Version one you've already seen. Eight recitals aimed at a nodding manager, no questions, no changed plans, fourteen minutes gone.
Version two: same people, same board, same work in progress. The facilitator pulls up the board. First item in review: the payment refactor, waiting two days on Marek, and Marek admits he's buried in the incident writeup, so Lena takes the review instead. Next item, in progress: the export bug. Priya says she still can't reproduce it. Tom mentions he has a local setup with the customer's data shape and offers twenty minutes after the meeting. The remaining items get a "no change, on track." Someone questions whether the caching spike still matters given what the incident revealed; that's parked for the sixteenth minute with the product owner staying. Seven minutes, three changed plans, done.
Same team. Same work. One of those meetings was worth interrupting eight people for.
If you want to know which one yours resembles, watch for three signals over a couple of sprints:
- Blockers surface on day two, not in the final days of the sprint when it's too late to route around them.
- People talk to each other, not to the facilitator. If every sentence is aimed at one person, you have an audience problem.
- Plans change because of what was said. Not every day, but if a whole week passes with zero adjustments, the meeting is decorative.
The four-minute standup
Here's the case nobody prepares you for: you walk the board and nothing needs to change. Everything's moving, nobody's blocked, today's plan is yesterday's plan. Teams that don't understand the daily start filling the silence. Somebody pads an update to seem thorough, someone else asks a question they don't care about, and slowly the team learns that standups take fifteen minutes because standups take fifteen minutes.
End it. "Nothing to replan, see you tomorrow" after four minutes is not a failed standup. It's the meeting working exactly as designed. The daily is a checkpoint, not a quota, and some days the plan simply survives contact with reality. Say so and go.
One caution before you celebrate a month of four-minute standups: if nothing ever needs replanning, sprint after sprint, that's rarely excellence. More often it means everyone is working on fully independent items, a team in name only, and the standup is the symptom rather than the problem. Raise that at your retro. And if your retros aren't producing changes either, we've written about retrospective formats that actually change something; the standup makes a good first test case. Pick one change from this article, run it for two sprints, and see whether the daily starts earning its slot.
And when a manager asks where their status update went, send it upward some other way. A board link, a written weekly summary, whatever fits. Just don't pay for it with the team's one daily chance to plan together.