The Cost of Standup Meetings: What 15 Minutes Really Costs Your Team
Ask anyone to defend the daily standup and you'll hear the same number. It's only 15 minutes. That number is accurate. It's also the smallest part of what the meeting costs. A live standup takes time before it starts and after it ends, and that time doesn't show up on anyone's calendar.
Here's how to count the real cost of standup meetings, using numbers you can swap for your own.
Start with the minutes on the calendar
The visible cost is the easy part. A 15-minute standup with eight people is two hours of combined team time every day.
In practice it's usually more. Standups run long. Someone shares a screen, two people start solving a problem that should have been a follow-up, and 15 minutes becomes 20. If your standup regularly runs over, use the real length, not the scheduled one.
So far: 20 minutes per person, per day.
Add the time before the meeting
Nobody starts hard work at 9:40 when they know they have to stop at 10:00.
Paul Graham described this in his 2009 essay "Maker's Schedule, Manager's Schedule." For someone who needs long stretches to build things, a single meeting doesn't just take its own slot. It breaks the time around it into pieces too small to use. The half hour before a fixed meeting tends to go to email and small tasks.
Be conservative here. Call it 10 minutes per person of time that would have been focused work and wasn't.
Running total: 30 minutes.
Add the time after the meeting
When the standup ends, people don't snap straight back into the problem they were working on. They check the messages that piled up, then reread where they left off.
You've probably seen the claim that it takes 23 minutes to refocus after an interruption. It's worth knowing that this exact figure comes from an interview, not a published paper.
Gloria Mark's peer-reviewed research at UC Irvine found something related: in a 2005 study of information workers, interrupted tasks took an average of about 25 minutes to resume, often with a couple of other tasks in between.
You don't need either number to see the effect. Watch your own morning after a meeting. Call it another 10 minutes per person, which is well below what the research suggests.
Running total: 40 minutes per person, per day.
Now multiply
Here's the math for an eight-person team, using the conservative estimates above:
Per person | Team of 8 | |
Per day | 40 minutes | 5 hours 20 minutes |
Per week (5 days) | 3 hours 20 minutes | 26 hours 40 minutes |
That's the cost of standup meetings for a single team: more than half of a full-time person's week, every week, spent on one meeting and the time around it.
These are estimates, and yours will differ. Plug in your own team size, your standup's real length, and your honest guess at the time on either side. The total is almost always bigger than people expect.
See what your team gets back. Standup Alice replaces the live meeting with a two-minute written update in Slack, Teams, Google Chat, or Webex. Start your free trial
The cost isn't spread evenly
The people who pay the most for a live standup are the ones doing the deepest work. Engineers and designers lose the most to a fragmented morning, because their work needs long uninterrupted stretches.
Research on developers backs this up. 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 large 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, and they sat in fewer daily meetings overall.
That's a correlation, not proof that standups cause lost coding time. It does match what most teams feel: the meeting costs the most for the people whose time is hardest to replace.
How to cut the cost of standup meetings
Some of the cost is worth paying. Teams need to know what everyone is working on, and blockers need to surface early. (If your updates feel thin, start with the best questions to ask in a daily standup.) Keep the updates. Stop paying for the parts that don't need a meeting.
Look back at the math. The minutes on the calendar are the smallest line. The time before and after is where most of the cost lives, and that cost exists only because everyone has to stop at the same moment.
Take away the fixed time and most of that cost goes with it. An async standup lets each person write their update when it fits their day, usually in two or three minutes, at a natural break instead of in the middle of focused work. Nobody holds back from starting a task at 9:40. Nobody spends 10 minutes finding their place again at 10:20.
Standup Alice runs this inside Slack, Microsoft Teams, Google Chat, or Webex. It reminds each person to post, collects the answers, and sends a summary to the team at a set time. Teams spread across time zones get their reminders in their own working hours. For the rest of an async setup, see async tools that actually save you time.
You keep the visibility. You give back most of the hour around it.
Run the numbers on your own team
Before you change anything, measure the cost of standup meetings on your own team. For one week, note three things for your standup:
How long it actually runs.
Roughly when people start focused work before it.
How long it takes to get back into real work after it.
Multiply by your team size and by five. If the total surprises you, try an async standup for two weeks and compare.
The 15 minutes was never the real cost. Now you'll know what is.
Comments