Daily standup meeting format: walk the board, not the room

A standup is a fifteen-minute synchronisation, not a status report to the person running it. The classic three questions — did, doing, blocked — fail in practice because two of the three are already visible in the tracker, so people perform them for an audience that is not listening. Walk the board instead of the people: go item by item from nearest-to-done backwards, and let each item’s owner speak when it comes up. It takes less time, it surfaces blockers earlier, and it stops being a daily performance review.

The format

Same time daily, same place, under fifteen minutes. If it regularly overruns the problem is almost never the format. It is that a design discussion belonging to two people is being held in front of nine.

Walk the board, not the room

Start at the item closest to done and move backwards. Going around the people produces a status report each; going along the work produces a conversation about the work. The difference is obvious within two days and the second one finishes faster.

Per item, three things

[Item] — [owner] — is it moving, and does anything need to change today? If it is moving and nothing needs to change, that is four seconds and you move on. Most items are four seconds, which is what buys the time for the two that are not.

The blocker sentence

I am blocked on [what] and I need [who] to [do what]. A blocker with no named person and no ask is a complaint, and standups fill with those. Insisting on the full sentence is what turns a standup from a report into something that unblocks people.

The parking rule

That is a conversation for two of us — [names], stay behind. Say it early and say it often. The standup that becomes a design discussion holds nine people hostage to a conversation two of them needed, and it is the main reason people stop coming.

The end

Anything that changed overnight that nobody has said? One sentence, once, at the close. It catches the production incident, the customer escalation and the thing someone assumed everyone had seen.

When it should not be a meeting

If the team is distributed across more than about five hours of time zones, or if three days running produce no blockers, write it instead. A threaded message that people post to by a fixed time, with one person responsible for reading it and chasing, does the same work and costs less.

When the standup is really a status meeting

If the answers are addressed to one person, if that person asks follow-ups nobody else needs, or if people report on days they were on leave — it has become a daily report. It is a legitimate thing to want, but it should be asked for directly rather than run in disguise, because everyone already knows.

Questions

What are the three standup questions?

What did you do yesterday, what are you doing today, what is blocking you. They are the traditional format and are worth replacing: two of the three are already in the tracker, so answering them aloud is a performance rather than information.

How long should a daily standup be?

Fifteen minutes as a hard stop, and most days it should finish early. A standup that reliably takes thirty minutes has a design discussion inside it that belongs to two people rather than nine.

Should standups be daily?

Daily works when the work changes daily and people genuinely depend on each other. Where dependencies are looser, three times a week is often better and the meeting stays useful rather than becoming ritual.

Do standups work for remote teams?

They work across a shared few hours and stop working once the spread gets wide. Beyond about five hours of time zones, a written standup with a posting deadline and one named person reading it does the same job without asking someone to attend at seven in the morning.

Who should run the standup?

Ideally nobody in particular — rotate it, or let the board order carry it. A permanent facilitator, especially a manager, pulls the meeting towards being a report to that person, whatever anyone intends.

What if nobody has blockers?

Then it is thirty seconds long and everyone goes back to work, which is a success. If it happens three days running, the meeting is probably not needed at that frequency and can move to written.

Nothing here needs tooling. A standup is a meeting where a written record has almost no value: the useful output is a handful of people changing what they do that day, and that is visible in the work by lunchtime.