How to Run a Daily Standup

Done well, a standup is a 15-minute sync that surfaces blockers and keeps the team aligned. Done badly, it's a status meeting everyone dreads. Here's how to keep it the former.

What a standup is for

A daily standup (or daily scrum) exists to coordinate and surface blockers — not to report status to a manager. The whole team gets a quick shared picture of where things stand and where someone is stuck, so help can be arranged. If it feels like a roll-call of updates, it has drifted from its purpose.

The classic format

Keep it short, literally standing if you're co-located, and give each person a moment to answer three questions:

Some teams replace this with "walk the board" — reviewing the work items themselves rather than going person by person, which keeps focus on the work instead of individuals.

That daily 15 minutes adds up

A standup runs ~260 times a year. See what yours costs across the team.

Open the Standup Cost Calculator →

Timebox it ruthlessly

Fifteen minutes, maximum. The fastest way to ruin a standup is to let it slide into problem-solving. When a real discussion surfaces, "take it offline" — note it and have the two or three people who care meet after.

Common mistakes

When to go async

For distributed or multi-timezone teams, a live standup is often the wrong tool. An async written standup — each person posts their update to a channel at the start of their day — removes the scheduling problem and leaves a searchable trail. See async vs meetings and meetings across time zones.

Frequently Asked Questions

No more than 15 minutes. If it regularly runs longer, it's drifting into problem-solving — park those discussions and have the few relevant people continue after the standup.

What did I do since the last standup, what will I do before the next one, and what's blocking me? Many teams now prefer to 'walk the board' instead, reviewing work items rather than going person by person.

Daily suits fast-moving teams, but the right cadence depends on how often coordination is actually needed. Some teams do well with two or three a week, or with async written updates that remove the scheduling problem entirely.