How to run a daily stand-up

Running an effective daily stand-up is a facilitation problem, not a format problem. The three questions, the board, the timebox — every team knows the parts. What separates a stand-up worth fifteen minutes from one people quietly skip is whether someone holds the shape: opens on the goal, keeps it moving, refuses to let it become a status report.

This chapter is the how. The rules are few and most of them are about what you don’t do in the meeting.

Start before the meeting starts

The best facilitators don’t walk in cold. A few minutes beforehand, glance at the board: what moved, what’s stuck, what’s been sitting in the same column too long. That short prep is the difference between a facilitator who runs the stand-up and one who merely opens it and hopes.

Cold facilitation is how a stand-up drifts. You open the floor, someone starts narrating, and forty minutes later you’re still going round the room. Two minutes of prep buys you the authority to say “that card’s been in review three days — what’s it waiting on?” instead of waiting for someone to volunteer it.

The rules that keep it fifteen minutes

The timebox holds only because problem-solving is pushed outside it. Anything that needs longer than a sentence leaves the box — that’s the whole trick.

Four rules do almost all the work:

Surface problems; don’t solve them. The single most important rule. The instant two people start debugging, everyone else is paying for a conversation they’re not in. Name it, note who’s needed, park it.
Hold a hard timebox. End on time even mid-sentence. The overrun is a signal, not something to absorb — if you keep letting it run to thirty minutes, thirty minutes becomes the norm.
Aim it at the team, not the front of the room. If updates start drifting toward the manager or Scrum Master, redirect: “tell the team, not me.” Where the updates point decides whether you get problems or performance.
Blockers first. Ask for what’s stuck before what got done, while attention is still fresh.

Handling the hard cases

Most stand-up trouble is one of three people, and each has a structural fix — reach for the format, not the personal callout.

The rambler gives a five-minute answer to a one-line question. Don’t correct them mid-flow; change the format. Walking the board caps rambling naturally, because the conversation is about the card, not the person’s day. If it persists, a private “keep it to your one main thing” lands better than an interruption in front of the team.

The dominator takes more airtime than the format allows, every day. Switch to walking the board so airtime follows the work. If one person still needs more than the meeting can give, that’s a coaching conversation to have privately — not a stand-up to let sprawl.

The silent update — “nothing to report, same as yesterday” — is the one to watch. Sometimes it’s fine. Sometimes it’s a stuck person who doesn’t want to say so. A gentle, specific follow-up (“still on the migration? anything slowing it down?”) surfaces the blocker that “nothing to report” was hiding.

What good looks like

You’ll know the stand-up is working less from what happens in it than from what happens right after. On a healthy team, the meeting ends and two or three useful side-conversations start immediately — the blockers it surfaced getting picked up by the people who can clear them. That’s the meeting doing its job: it’s a router for problems, not a container for solutions.

The opposite tell is a stand-up that ends and everyone just goes back to their desks unchanged. If nothing the meeting produced altered anyone’s day, you ran a status report. The stand-up anti-patterns chapter is the diagnostic for when it’s gone wrong; the format catalogue is where to look when it’s merely gone stale.

For where the stand-up sits among the sprint’s other meetings, see the agile ceremonies guide; to make the daily habit stick, hand the team copy-paste templates; and for the formats and failure modes, work through the rest of the daily stand-up guide.

Frequently asked questions

Who runs the daily stand-up?

The team owns it; someone facilitates it. On a Scrum team the Scrum Master often facilitates early on, but the goal is a team that runs its own stand-up without a designated timekeeper. The facilitator’s job is narrow — open on the goal, keep the board moving, park the deep dives, end on time. It is not to receive updates, which is the fastest way to turn a sync into a status report.

What makes a good daily stand-up?

It’s short, it leads with blockers, and it’s aimed at the team rather than a manager. A good stand-up sends people away knowing what changed, what’s stuck, and what they’re doing about it — and it ends on time. The tell is what happens after: on a good team, useful side-conversations start the moment it ends, because the meeting surfaced the right problems instead of burying them in status.

How do you handle someone who dominates the stand-up?

Name the pattern kindly and structurally, not personally. Switch to walking the board so airtime follows the work rather than the person, hold a hard timebox, and when a deep dive starts, park it: “good one — you and Sam grab five minutes after.” If one person routinely needs more airtime than the format allows, that’s a coaching conversation to have privately, not a stand-up to let run long.

How do you keep a stand-up from running long?

Ban problem-solving in the meeting and route it to a parking lot, hold a hard end time even mid-sentence, and walk the board instead of going person by person. A stand-up that regularly overruns isn’t undisciplined — it’s mis-scoped: the team is trying to do work in a meeting built only to coordinate it. Fix the parking-lot habit before you shorten anyone’s update.