Flocci Projects

Home › Agile answers › How do I run a daily standup that is not a status meeting?

How do I run a daily standup that is not a status meeting?

Run the standup against the board, not around the room: walk the columns right to left, discuss the cards closest to done first, and surface blockers. Fifteen minutes, standing or async. The failure mode is each person reporting to a manager — the meeting is for the team to coordinate, not to report.

Step by step

  1. Open the board, not a list of people. Share the Kanban board and walk it right to left, starting at Review. Work closest to done gets attention first, which is what pulls cards over the line rather than starting new ones.
  2. Talk about cards, not calendars. For each card in flight ask what it needs to move. 'Yesterday I worked on the thing' is a status report; 'this is blocked on the API key' is coordination.
  3. Name blockers explicitly. A blocker with no owner and no date is a wish. Assign the unblocking to a person before the meeting ends, and put it on the card as a comment so it survives the conversation.
  4. Take detail offline. Any discussion involving two people and five minutes moves to after the standup. Protect the fifteen-minute box or attendance quietly erodes.
  5. Go async if time zones fight you. One written check-in per person per day against the board, with the same three questions, gets ninety percent of the value for distributed teams — and leaves a searchable record.

Why the round-robin format fails

Asking each person what they did yesterday optimises for sounding busy. It produces performance rather than coordination, takes longer as the team grows, and teaches junior members that visible effort matters more than finished work. Walking the board inverts all three incentives.

The async alternative

For distributed teams, a written daily note per person — what moved, what is blocked, what I am pulling next — attached to the board gives the same coordination without a scheduling compromise, and it accumulates into a record that the activity history alone cannot express.

Try it on a free Flocci Projects board

Related questions

How long should a standup be?

Fifteen minutes, hard. If it consistently runs longer, the cause is usually detailed problem-solving that belongs in a follow-up conversation with the two people who actually need it.

Should managers attend?

They can, but should not run it or be the person everyone addresses. The moment answers are directed at a manager, it becomes a status meeting and the coordination value evaporates.

Do we still need a standup if we have a realtime board?

A realtime board removes the need to report status, which is most of the meeting. What remains — surfacing blockers and agreeing who helps — is real, and many teams keep a short async version for exactly that.

More agile answers