The daily standup is one of agile's best ideas and one of the most commonly ruined meetings in practice. Done well, it surfaces blockers early and keeps a team pointing the same direction. Done badly, it is a 30-minute status report nobody needed delivered in person. The fix is not a new tool — it is respecting the format. Here is exactly how to run one that the team will actually value in 2026.
What changed in 2026
- Fully async teams are now the norm, not an exception. Written standup tools — Geekbot, Slack workflows, Linear updates — are table-stakes. A live standup is a deliberate choice, not a default.
- AI summarization means async standup responses can be auto-summarized and surfaced as a digest, reducing the need to read every update.
- Distributed time zones make synchronous standups impractical for many global teams; the async-first pattern has largely won for those groups.
- Over-meeting fatigue is well-documented — if your standup is not clearly earning its 15 minutes, the team will start multitasking or skipping.
The three-question format
Every standup answer covers exactly three things:
- What did I complete yesterday (that moves the team's goal forward)?
- What am I working on today (specific task, not a domain)?
- What is blocking me (and who needs to know)?
Nothing else belongs in the standup answer. Project updates, decision-making, design debates — those are conversations that happen after the standup, between the relevant people only.
Live vs async: which to use
| Scenario |
Best format |
| Co-located team, same timezone |
Live, 10–15 min |
| Remote team, overlapping hours |
Live OR written async |
| Distributed, >3 hour time gap |
Written async + AI digest |
| Team of 2–3 |
Slack message or brief call |
| Team of 10+ |
Async; live standups at that size are hard to timebox |
How to run a live standup
- Set a fixed time and start the second. Do not wait for latecomers. Respect for the ritual trains punctuality.
- Stand up (if in person) — the physical discomfort enforces brevity.
- Each person gets 2 minutes. Use a timer. Visible timers are not rude; they are a service.
- Capture blockers in writing as they are raised. One person acts as the note-taker for blockers only.
- Close with "take it offline" for anything needing discussion. Name the people who should stay on.
- End under 15 minutes. If you hit 15 regularly, something is wrong with the format, not the team.
How to run an async standup
- Post a shared template in your team's channel: "Yesterday / Today / Blockers."
- Set a window: everyone posts by 10 AM local time.
- Use a bot or AI summary to produce a daily digest by 10:30 AM.
- The team lead reviews blockers and responds within the hour.
- No live call needed unless a blocker requires it.
Common mistakes
Solving problems in the standup. The moment someone says "actually let me explain that issue" you have lost the timebox. Say "let's take that offline" and move on.
Using the standup to report upward. If the standup starts serving management's status needs, the team stops using it for coordination. Keep it team-facing.
No one actually has blockers. If blockers never surface, either the format feels unsafe or the team is sandbagging. Ask "is anyone waiting on anything?" directly.
Rotating facilitators without training them. The facilitator's only job is to timekeep and redirect off-topic threads. New facilitators should know this explicitly.
Async standup with no one reading it. If the team posts updates and nothing happens with the blockers, the async standup will die within two weeks. Someone must act on blockers daily.
What to skip
- Ice-breaker questions before the three questions — they kill the timebox and feel forced after week two.
- Sprint-level planning in the standup — that belongs in a proper planning session.
- Attendance tracking — if someone's not posting, address it directly, not by monitoring.
FAQ
How many people is too many for a live standup?
Roughly eight. Above that, 2 minutes each becomes 16+ minutes without fail. Consider sub-team standups or a full async format.
What do I do with a chronic over-sharer?
After the second sentence, say "got it — blockers?" It is not rude to enforce the format. Do it consistently and the behavior will change.
Should remote participants have cameras on?
Preference varies, but for a 10-minute sync, cameras-on improves engagement. Make it a team norm, not a mandate.
Does the standup replace a sprint review?
No — completely different purpose. Sprint reviews assess completed work; standups coordinate active work. Both are needed.
Where to go next
How to give a presentation in 2026, How to delegate tasks in 2026, and How to run a retrospective in 2026.