How to Run a Standup Under Fifteen Minutes

The daily standup exists so silence does not become the default. Left alone, teams drift into parallel universes — everyone working hard, nobody working together. The ritual is gravity: brief, reliable, grounding. When it expands past fifteen minutes, it stops being alignment and becomes a meeting wearing standup clothes.

Keep the three questions, enforce the contract

What did you do yesterday? What will you do today? Any blockers? The questions are old because they work. The failure mode is not the script. It is the lack of boundaries around it.

Time box per person. Thirty to sixty seconds is enough if people prepare. If someone needs five minutes, they need a follow-up conversation, not the floor.

Blockers get named, not solved. Standup surfaces dependency. Resolution belongs in a smaller room immediately after. Solving architecture in the circle is how forty-five minutes disappear.

Stand up, literally or figuratively. Posture signals duration. Remote teams can keep cameras optional but should keep the “this is short” norm explicit in the calendar invite.

When standups go wrong

A forty-five-minute standup usually means one of three things:

It is a status report to management. If only the lead speaks, cancel the meeting and send a dashboard.
There is no parking lot. Decisions deferred to “after standup” need a real slot, not an informal drift into lunch.
The team is too large. Fifteen engineers times two minutes is already half an hour. Split by squad or move to async written updates for stable workstreams.

Remote async teams can replace the live standup with a written check-in — same three questions, same deadline, replies only on blockers. The ritual is showing up, not the video tile.

Leaders model brevity. If the tech lead takes eight minutes, everyone else will too. Prepare your update before the call. Skip work that does not change anyone else’s plan.

Rotate facilitation. Ownership of the clock should not live with one person forever. A shared facilitator with permission to interrupt politely keeps the meeting from becoming a lecture series.

What good looks like

By minute twelve, everyone knows who is blocked, who is waiting on whom, and whether today’s plan still matches yesterday’s commit. Nobody rehearsed a performance. Nobody got surprised by work that was invisible.

Schedule the standup at a time that respects time zones when you can. Protect it from being the first meeting dropped when the calendar fills — that is when drift returns.

If the ritual stops working, change the format before you cancel it entirely. Teams that abandon alignment entirely pay in surprise dependencies, not saved minutes.

Keep it short. Keep it honest. Keep showing up.

— JV · Dark Heart Labs.