The Cost of Live Standup Meetings: Why Your 15-Minute Standup Takes 30
Updated: Oct 5
Every team that runs a live standup has said it at some point: it's only 15 minutes.
Then it runs 25. Then 30. Nobody planned for that and nobody tracks it, so the extra time never shows up anywhere except in the work that didn't get done.
The cost of live standup meetings is bigger than the calendar shows. A live standup asks everyone to stop at the same moment and then do their prep work out loud while the rest of the team waits. Here's where the time goes and how to get it back.
Where a live standup loses its time
Watch a live standup closely and you'll see the same leaks almost every day.
Waiting to start
The meeting is at 10:00. The last person joins at 10:03, and the next minute goes to "can everyone hear me?" It's small, and it happens every single day.
Updates pieced together from memory
Most people walk into a live standup without having written anything down. So they rebuild yesterday on the spot, scrolling through tickets and correcting themselves halfway through. An update that takes 30 seconds to read takes two minutes to say.
Status that wasn't meant for you
In a round-robin, everyone listens to everyone. The designer sits through the database migration details. The backend engineer sits through the copy review. Most of what's said matters to one or two people in the room.
Problems solved in front of everyone
Someone mentions a blocker. The two people who can fix it start fixing it, right there, while six others wait. It's a useful conversation. It just didn't need an audience.
Questions that could have been answered earlier
"Did the deploy go out?" "Who's reviewing my PR?" These have one-line answers, but they get asked live because the meeting is the only place everyone is together.
None of this is anyone's fault. It's what happens when a live meeting has no prep step.
What a live standup really costs
Here's an example for a team of eight whose live 15-minute standup regularly runs 30:
Scheduled | Actual | |
Per person, per day | 15 minutes | 30 minutes |
Team of 8, per day | 2 hours | 4 hours |
Team of 8, per week | 10 hours | 20 hours |
That's the cost of live standup meetings for one team: 20 hours a week, half of a full-time person's week. Ten of those hours are overrun that nobody booked.
Your numbers will differ. Time your standup for a week and compare it with the calendar invite. Most teams are surprised by the gap.
Get the status out of the meeting. Standup Alice collects everyone's answers before the standup starts, in Slack, Teams, Google Chat, or Webex. Start your free trial
Who pays the most
The bigger the team, the more of each live meeting is status that has nothing to do with you.
Research on developers points the same way. A 2017 study by Viktoria Stray, Nils Brede Moe, and Gunnar Bergersen surveyed 221 developers about daily stand-ups. Only 44.7% were positive about them. Satisfaction was lowest on teams of 12 or more and among senior developers, who often already know what's going on. The developers who were positive also reported spending more time each day on programming.
That's a correlation, not proof. It does match what most teams feel: in a live standup, everyone pays for every update.
How to cut the cost of live standup meetings
Every leak above has the same root cause. In a live standup, the prep work happens in the meeting, while everyone waits.
Move that work out of the meeting and most of the overrun goes with it.
This is what Standup Alice does. Before the standup, Alice reminds each person to post their answers in Slack, Microsoft Teams, Google Chat, or Webex. People write their update when it suits them, with their tickets open, so nobody rebuilds yesterday from memory. You can set different questions for each team (if you're rethinking yours, start with the best questions to ask in a daily standup).
Alice collects the answers and sends a summary to the team at a set time, with replies threaded under each update. By the time anyone would meet, the status is already shared and the simple questions have already been answered in the thread. What's left is the part that needs a real conversation.
From there, teams usually take one of two paths:
Go fully async. The summary is the standup, and there's no meeting at all. If that's new for your team, here's how asynchronous standups work.
Keep a short live check-in, but only for the blockers flagged in the summary. With status already read, it can stay well under the original 15 minutes.
Either way, nobody waits through updates that weren't meant for them. For the rest of an async setup, see async tools that actually save you time.
Run the numbers on your own team
Before you change anything, measure the cost of live standup meetings on your own team. For one week, track:
When the standup actually starts and ends.
How much of it is status and how much is real discussion.
How often a side conversation takes over.
Multiply the overrun by your team size and by five. Then run two weeks with Alice collecting answers ahead of time, and compare.
Try it for two weeks
Your standup can go back to being 15 minutes, or less. Setup takes about five minutes, and your team keeps the tools they already use.
Works in Slack, Microsoft Teams, Google Chat, and Webex.
Comments