What a standup is actually for
A standup exists so that people working on connected pieces of work know what the others are doing, and so that anyone who is stuck gets unstuck today rather than on Thursday.
It is not a status report. This distinction is the whole ballgame. When people are speaking to a manager rather than to each other, they optimise for sounding productive, blockers stop being mentioned, and the meeting becomes a daily performance that everyone privately resents.
The direction test
Watch where people look while they talk. If everyone reports to one person, you have a status meeting with a standup's name on it. If people talk to each other, it is working.
The format
Each person covers three things, in this order, in roughly a minute.
What I finished. Completed since the last standup. Finished, not worked on. "Still on the migration" three days running is itself the useful signal.
What I am doing next. The single next thing, not a list. This is what lets someone else say "I am touching that file too" before both of you waste an afternoon.
What is blocking me. Anything waiting on another person, a decision, an access request, or an answer. Named, with who you think can unblock it.
The order matters more than it appears. Finishing on the blocker means the meeting ends on the actionable part, and the facilitator can assign each one immediately.
Six rules that keep it to 15 minutes
Same time, every day, no exceptions
A standup that moves is a standup people forget. Pick a time that suits the team rather than the manager, and keep it.
Avoid first thing in the morning if anyone has a commute or flexible hours. Mid-morning usually gets better attendance than 9am.
Fixed slotNot 9amBlockers get assigned, not solved
When someone raises a blocker, the only thing that happens in the meeting is naming who will deal with it and when. The actual discussion happens straight after with the two or three people involved.
This single rule is the difference between a nine minute standup and a thirty five minute one.
The most important ruleHold an after-meeting, deliberately
Keep the five minutes immediately after the standup free. Whoever needs to continue a conversation stays, and everyone else leaves.
Without this, the discussion has nowhere to go, so it happens in the standup while six uninvolved people wait.
5 minutesOnly the people involvedOne person facilitates and keeps time
They move it along, cut off problem-solving, and make sure every blocker gets an owner before the meeting ends.
Rotate the role weekly. It stops the standup becoming one person's meeting and it makes everyone better at running it.
Rotate weeklyTalk to the team, not to the manager
If a manager attends, they listen and unblock. They do not respond to each update, and they do not ask follow-up questions in the meeting.
One follow-up question per person is enough to turn the whole thing into a review, and it happens without anyone intending it.
Managers listenStand up, or use the timer
The physical version of this meeting was standing for a reason. Remotely, use a visible timer instead. Fifteen minutes, on screen.
Mild artificial pressure does most of the work of enforcement, and it means the facilitator does not have to be the person cutting colleagues off.
Visible timer15 minutes hard cap
Why standups degrade
Almost every failing standup is one of these five.
It became a status report. Covered above, and the most common by a distance.
Problem-solving leaked in. Two people go deep on a technical question while everyone else waits. The after-meeting rule exists precisely for this.
Too many people. Above eight or nine, a standup cannot stay short and most attendees are listening to updates that do not affect them. Split it by working group.
Nothing ever changes as a result. If the same blocker is raised three days running and nobody has acted, people learn that raising blockers is pointless and stop. This is the failure that quietly kills the meeting.
It runs on a day when nothing has changed. For teams doing week-long independent tasks, a daily standup produces "same as yesterday" from everyone. Reduce the frequency rather than persisting with the ritual.
Running it asynchronously
Async standups work well for distributed teams, and for teams whose work is loosely coupled. Everyone posts the same three items in a shared channel by an agreed time.
What you gain: no time-zone compromise, a written record, and people are not interrupted mid-morning.
What you lose: the immediate unblocking. In a live standup, someone hears a problem and says they will handle it in the next ten minutes. In a channel, a blocker can sit unread for hours.
The compromise most distributed teams settle on is async posts daily, plus one live session a week for the things that need conversation. If you go async, two rules make the difference: someone has to be responsible for reading the posts and picking up unassigned blockers, and the format stays exactly the same three items, or the posts drift into paragraphs nobody finishes reading.
Frequently asked questions
- How long should a standup be?
- Fifteen minutes as a hard cap, and most teams of five to eight finish in under ten. If it consistently runs longer, the cause is almost always problem-solving happening in the meeting rather than being taken offline.
- Should standups be daily?
- Daily works when the team's work is interdependent and changes day to day. Where people work on separate things for a week at a time, two or three times a week is enough, and daily becomes a ritual with no information in it.
- Who should attend a standup?
- The people doing the work. Managers can attend to listen, but a standup with senior observers turns into a performance, and people stop saying they are stuck. If that is happening, the observers should read the async version instead.
- What are the three standup questions?
- What did I finish since the last standup, what am I working on next, and what is blocking me. The third question is the one that carries the value, and it is the one most teams rush.
- Should standups be async?
- Async works well for distributed teams across time zones and for teams where work is loosely coupled. It loses the immediate unblocking that happens when someone hears a problem and says they can help, so decide which of the two matters more for your team.
- Why do people say standups are a waste of time?
- Usually because the standup they attend is a status report to a manager rather than a coordination meeting between peers. The format is identical, the direction of the information is not, and that difference is what makes it feel like surveillance.