How to run a daily standup that isn't a waste of time
Most standups fail the same way: they become a status report to the manager. Here's the format that keeps them short, and what to do when yours has drifted.
A daily standup is supposed to take fifteen minutes and surface blockers. In a lot of teams it takes thirty and surfaces nothing, because it has quietly turned into everyone reading their to-do list to the most senior person in the room.
The point of a standup
A standup exists so the team can re-plan the next day together. That's it. It is not a status report, not a progress audit, and not the place to solve the problem someone just raised. If your standup produces no changes to who's doing what, it isn't doing its job.
The format that works
Each person answers three questions, briefly:
- What did I finish since yesterday? Finished, not "worked on".
- What am I picking up today?
- What's in my way?
Two rules keep it to fifteen minutes. First, speak to the team, not the manager. Second, anything that needs discussion gets parked and taken by the two or three people who care — after the standup, not during it.
Five ways standups go wrong
- It becomes a status report. The tell is everyone facing the same person. Fix it by having someone else run it each day.
- People reconstruct yesterday live. Ten people × 45 seconds of "what did I do yesterday…" is most of your meeting. This one is a tooling problem: the answer is already in your tracker.
- Blockers get mentioned but not owned. Every blocker should leave the meeting with a name attached.
- It solves problems in the room. Park and move on.
- It's held at 9am for people who start at 10. Hold it when the team is actually present, or run it asynchronously.
Asynchronous standups
If your team spans time zones, a written standup in a shared channel beats a call nobody's awake for. It works if you keep two things: a fixed cutoff time, and a person responsible for reading the entries and chasing the blockers. An async standup with nobody reading it is just a diary.
Let the tool write the first draft
The "what did I do yesterday" question has an objective answer: it's the tickets you moved, closed and commented on. Any tracker holding that data can assemble the Did / Doing / Blocked list for each person before the meeting starts.
That's how VectorKan's standup page works — it builds the list per person from real activity, so the meeting starts from a written summary instead of ten people recalling their day. The conversation moves straight to what's blocked, which is the only part that needed a meeting.
How to tell if yours is working
Healthy standups are short, and something changes as a result: work gets reassigned, a blocker gets picked up, someone joins someone else. If your standup ends with everyone doing exactly what they'd have done anyway, cancel it for a week and see if anyone notices.
Frequently asked questions
How long should a daily standup be?
Fifteen minutes or less for a team of up to ten. If it regularly runs longer, the usual cause is problem-solving in the meeting or people reporting status rather than surfacing blockers.
What are the three standup questions?
What did I finish since yesterday, what am I working on today, and what is blocking me. The third question is the one that matters — the first two mainly provide context for it.
Should standups be daily?
Daily works for teams with shared, fast-moving work. Teams working on separate long-running tasks often do better with two or three a week — the meeting should match how often plans actually change.
Can you run a standup asynchronously?
Yes, and it's usually better for distributed teams. Post written updates to a shared channel with a fixed cutoff, and make one person responsible for reading them and chasing blockers.