How to Run a Daily Standup

What the standup is actually for

A daily standup exists to surface blockers while they are still cheap to fix. It is not a status meeting, even though it is frequently run as one. The distinction matters: a status meeting reports what happened; a standup changes what happens next. If nobody in the room adjusts their plan for the day because of something they heard, the meeting had no function beyond attendance.

It should run in about fifteen minutes for a team of six to eight people, standing up if you are co-located, on video with cameras optional if you are not. Anything routinely longer is not a standup anymore. It's a planning meeting wearing a standup's schedule slot.

The three-question format

The classic version asks each person three things: what did you finish since the last standup, what will you work on until the next one, and what is in your way. It is not the only valid format, but it is the one most teams should start with, because each question does a specific job.

The first question is a progress check, not a diary entry: "finished the export endpoint," not a list of meetings attended. The second sets a public commitment for the day, which is a mild but real form of accountability. The third is the one that justifies the meeting: a blocker named out loud in front of the team gets solved faster than one sent in a private message that might sit unread for hours.

A useful discipline: answer the third question first, or at least don't bury it. Teams that leave blockers for the end of their turn tend to run out of time and skip them, which defeats the meeting's actual purpose.

Keeping it under fifteen minutes

Overrun is almost always caused by problem-solving happening live. Someone mentions a blocker, and the room starts debugging it together while six other people wait. The fix is not to forbid discussion. It's to move it. "Let's take that after standup, you three stay on" keeps the meeting moving and still gets the problem solved, usually better, because it's not being solved in front of an audience with nothing to contribute.

The second common cause is people reporting on work that is not on the board. If a task takes real time but never gets a card, standup is the only place its status exists, so people describe it verbally, at length, because there's nothing to point to. The fix here is upstream: if it's worth mentioning at standup, it's worth a card.

When it turns into status theater

There is a recognisable failure mode: the standup keeps happening, on time, every day, and nobody gets any value from it. The tell is that people report to the manager rather than to each other: eyes on the one senior person in the room, rather than on teammates whose work depends on what's said. Fix this by having the facilitator visibly not react, and by having them ask a neighboring teammate to respond to a blocker before offering to solve it themselves.

A second tell: the same three sentences every day, roughly true, entirely uninformative. "Working on the same thing, no blockers" for four days running usually means either the task is bigger than a day and should be split, or there's a blocker that isn't being said out loud, often because the last time someone raised one, nothing happened about it. Standups run on the belief that raising a blocker gets it addressed. Break that belief once and people stop bothering.

If your standup has drifted into either pattern, the fix is rarely a new format. It's usually enforcing the old one: cut discussion, don't let cards go unmentioned, and close blockers loudly enough that people trust the mechanism again.

Before you run one, check

• Is there a single board everyone can see during the meeting?
• Does someone own keeping time, and do they actually enforce it?
• Is there a real parking lot, and does anything ever get taken out of it?
• Would a blocker raised today get acted on today, not next week?
• Could a remote teammate follow the meeting as easily as someone in the room?

A "no" to the fourth one is worth fixing before anything else. A standup where blockers go nowhere trains people to stop mentioning them, and once that happens the meeting has no reason left to exist.

A note on the meeting you might not need

If status is already visible (a board that reflects reality, updated as work moves rather than reconstructed once a day from memory), a chunk of the standup's job is already done before anyone speaks. ShipSprint's "my day" screen is built around that: everyone opens to today's items, logs time in a tap, and can flag "I'm blocked" without waiting for the meeting to say so. It doesn't replace the standup; the human coordination and the live problem-solving still matter. But it means the meeting can spend its fifteen minutes on the third question instead of reconstructing the first two from memory.