Most stand-ups start with good intentions: quick updates, blockers, and alignment. Fifteen minutes, then back to work.
Then it slowly changes. More people join, updates get longer, and it starts feeling like a daily report instead of a team conversation.
The Slow Takeover
At some point, someone invited the project manager. Then another PM. Then a stakeholder who "just wants to listen." Before you know it, the stand-up has twelve people in it, and only four of them are actually building things.
Here's what happened next: the developers started talking to the project managers instead of to each other. Every update became a status report. "I worked on the API yesterday. Today I'll finish the API. No blockers." Repeat times eight.
Nobody was learning anything. The developers already knew what each other was working on. The PMs were getting status they could have read in the ticket system. But the meeting kept happening because that's what you do.
The Real Cost
A 15-minute meeting doesn't cost 15 minutes. It costs the context switch before it and the ramp-up time after it. For a developer in the middle of solving a hard problem, that interruption can cost an hour of productive work.
Multiply that by every developer, every day, and you're looking at hundreds of hours per month — spent reciting information that already exists in your ticket system.
The Question Nobody Asks
Here's a question that should be asked more often: "If the tickets already show our status — which is the entire point of the tickets — why are we spending 30 minutes every morning reciting it out loud?"
Nobody can answer that question. So we keep doing it.
The alternative isn't "no communication." It's better communication. Written updates that people can read when they're ready. Questions asked asynchronously so people can respond thoughtfully. Meetings reserved for things that actually need real-time discussion.
Not every sync needs a meeting. Most of them just need a message.