Why Daily Standups Fail (and How to Fix Them)

Ask ten engineering managers what their standup is for, and you'll get ten different answers. Status update. Blocker check. Team sync. Ritual nobody wants to kill but nobody defends either. That confusion is usually the first sign a standup has stopped working.

The pattern is always the same

A standup starts tight — three questions, five minutes, done. Six months later it's twenty minutes of people reading their Jira board out loud to a room that's only half listening. Nobody planned for this. It just accretes, one "quick addition" at a time, until the meeting is serving everyone's curiosity except the person talking.

The tell isn't length. Plenty of teams run a productive fifteen-minute standup. The tell is whether anyone changes what they do because of it. If the answer is "no, we just note it and move on," the meeting has become a report, not a coordination tool.

What it's supposed to do

A standup has exactly one job: surface the two or three things that need a human decision today — a blocker someone can unstick, a dependency that changed, a scope call that can't wait for planning. Everything else is status, and status doesn't need a live audience.

That's a hard needle to thread verbally. People default to narrating their day because it's the safe, low-effort answer to "what did you do." Getting to the sharper version — what's actually stuck — takes either a skilled facilitator pushing back in real time, or a format that asks for it directly.

What actually helps

A few things move the needle more reliably than "let's keep it shorter":

• Ask for blockers first, work second. Flip the default order and the blocker doesn't get buried under five minutes of task narration.
• Take status async. If someone genuinely wants to know what you did yesterday, a written update they can skim in ten seconds beats you saying it out loud to twelve people.
• Make the live time about the two things that need a decision, not a roll call.

That's the shift Strova is built around — structure the write-up so the AI does the narration, and the DSM board surfaces blockers automatically, so the time your team spends talking is the time actually worth having.

Standups aren't broken because meetings are bad. They're broken because we ask a synchronous format to do an asynchronous job.