The Real Cost of Status-Update Meetings

An 8-person team running a 15-minute daily standup spends 2 hours a day in that room — 10 hours a week, 40+ hours a month. That's a full engineer-week, every month, before anyone writes a line of code. Most teams never do this math, because no single standup feels expensive. It's the accumulation that costs.

It's not just the clock time

The direct cost is easy to calculate. The indirect cost is bigger and harder to see:

• Context-switch tax. Standup rarely lands at a natural break. Every engineer pulled out of a debugging session loses the 10–20 minutes it takes to get back into flow — often more than the meeting itself.
• Waiting for your turn. In a round-robin format, most of the room is passively listening to updates that don't apply to them, waiting for their two minutes.
• The update nobody needed live. "Finished the migration script, starting on tests today" doesn't need eight people in a room to hear it in real time. It needs to be written down somewhere anyone can check.

Where the time should go instead

The fix isn't "cancel standup" — teams that go fully async often lose the two or three moments a week where a live conversation genuinely unblocks something faster than a thread would. The fix is separating the two jobs a standup is trying to do at once:

1. Status — what happened, what's next. This is naturally asynchronous. Write it, read it when convenient, done in under a minute either way.
2. Coordination — the handful of items that need two people to actually talk. This is the only part that benefits from being live, and it's usually a fraction of what a standup covers.

Once status moves to writing, the live portion — if you keep one at all — shrinks to the size of the problems that actually need it. Most teams find that's five minutes, not fifteen, and it's five minutes people show up for instead of tolerate.

That's the whole premise behind Strova's async daily updates: collect the status in writing, structure it automatically, and surface only the blockers that need a person's attention. The meeting gets smaller because the noise around it disappears first.