Posts

Why Daily Standups Are Dying (And What's Replacing Them)

Remote workers in different locations checking their phones and laptops at different times of day, representing async communication across time zones

Matt Lewandowski

Last updated 14/02/20268 min read

The daily standup was born in 1993. Software teams sat in the same office, worked the same hours, and could literally stand in a circle each morning. The Agile Manifesto popularized it in 2001, and the 15-minute morning meeting became sacred ritual for two decades. Then remote work happened. The cracks started showing.

The numbers tell the story

Microsoft's 2024 Work Trend Index found that 78% of developers consider "meeting overload" their biggest productivity challenge. Stack Overflow's 2024 Developer Survey reports that 72% of developers now work remotely at least three days per week. GitLab's 2025 Remote Work Report puts 63% of engineering teams across three or more time zones. When your team is scattered across San Francisco, London, and Singapore, that 9am standup becomes someone's lunch break and someone else's midnight. The meeting that was supposed to take 15 minutes now requires calendar gymnastics, and someone always gets the short end of the timezone stick.

The Real Cost

A 2025 study by Linear found that engineering teams lose an average of 4.2 hours weekly to poorly coordinated meetings. At an average developer salary, that's over $15,000 per engineer annually going to meeting overhead.

World map showing multiple time zones with clock icons indicating different times across cities like San Francisco, London, and Singapore, illustrating the challenge of scheduling meetings across distributed teams

Why traditional standups break down

The problems go deeper than timezones.

They interrupt deep work

Software development requires sustained concentration. Research on context switching shows developers need an average of 23 minutes to regain focus after an interruption. A standup scheduled mid-morning doesn't just take 15 minutes; it fragments the entire morning into unusable chunks. One of remote work's biggest benefits is the freedom to structure your day around when you do your best work. Forcing everyone onto a call at the same time kills that flexibility.

They become attendance checks

In remote settings, managers often misuse standups to verify that people are at their computers. Qatalog and GitLab's study "Killing Time at Work" found that this "digital presenteeism" is the number one barrier to async communication. It adds 67 minutes to the average remote worker's day while actively hurting productivity. Standups should surface blockers and keep teams aligned. Not serve as roll call.

They don't scale

With five developers, a standup works. With fifteen, it becomes a lecture. People zone out waiting for their turn, side conversations derail the meeting, and what was supposed to be 15 minutes stretches to 45. Research from meeting analytics firm Otter.ai found companies lose about $283 per employee monthly from standups that run overtime. Multiply that across a 50-person engineering org and you're looking at $170,000 in annual waste from one recurring meeting. Developer at home office looking frustrated at a laptop screen showing a video call grid with too many participants, some with cameras off, depicting meeting fatigue

Developer at home office looking frustrated at a laptop screen showing a video call grid with too many participants, some with cameras off, depicting meeting fatigue

What's actually working instead

The solution isn't to abandon daily check-ins. Teams still need to know who's blocked, what's shipping, and where projects stand. The solution is to separate those benefits from the synchronous meeting format.

📝Async written updates

Team members share what they accomplished, what they're working on, and blockers when it fits their schedule. No coordination required.

🚪Persistent daily rooms

One shared space per day that everyone can access whenever they're ready. No meeting creation, no calendar invites.

🤖AI-generated summaries

Automated digests pull out blockers and patterns so managers don't have to read every update manually.

💬Threaded comments

Questions and follow-ups happen asynchronously in context. Conversations stay focused and searchable.

GitLab documented their async-first approach in their All-Remote Handbook. Their internal metrics show async standups reduced meeting hours by 37% while projects completed faster. Clean interface showing a standup tool with written updates from team members in different time zones, with timestamps showing morning, afternoon, and evening submissions

Clean interface showing a standup tool with written updates from team members in different time zones, with timestamps showing morning, afternoon, and evening submissions

How async standups actually work

The mechanics are simple. Instead of gathering everyone at a set time, each team member posts their update when they start their work day:

Submit your update

Answer your team's standup questions (what you did, what you're doing, any blockers) through a shared tool. Include screenshots or videos when helpful.

Review team updates

Check what your teammates shared. This takes 5 minutes instead of 15+ because you can skim text faster than listening to spoken updates.

Engage where needed

Comment on blockers you can help with. React to wins. Ask clarifying questions. All async, all in context.

Get the summary

AI-generated summaries surface patterns and blockers automatically, so leadership stays informed without reading every update.

Everyone contributes at their optimal time. No one sits through a meeting listening to updates that don't affect them.

Making the transition

Switching from sync to async standups requires more than a new tool. It requires a mindset shift.

Write updates that stand alone (assume readers lack context)

Be specific about blockers and what would unblock you

Use screenshots and screen recordings for visual work

Check teammate updates at least once daily

Engage through comments instead of saving questions for sync meetings

Trust output over presence

The last point matters most. Async standups only work when leadership evaluates people on what they ship, not when they're online. If your organization still expects butts in seats, async won't stick. Writing quality also matters more than you'd expect; the difference between updates people act on and updates people ignore comes down to a few writing habits.

Start small

Don't flip the switch overnight. Run async standups in parallel with your sync meeting for two weeks. Most teams find the sync meeting becomes redundant once they're reading async updates consistently.

What to look for in an async standup tool

Not all tools support async standups well. Here's what separates the good ones:

Capability	Why it matters
Persistent daily rooms	No overhead of creating meetings. Each day just works.
Rich media support	Screenshots, videos, and formatted text make async communication as clear as talking in person.
AI summaries	Surfaces patterns and blockers automatically. Managers get the highlights without reading every update.
Comments and reactions	Enables conversation without pulling people into sync calls.
Timezone-aware reminders	Nudges team members who haven't submitted, respecting their local time.
Data export	Your standup data shouldn't be trapped in a walled garden.

Kollabe's standup tool was built for distributed teams doing async standups. Persistent daily rooms mean zero setup. AI summaries pull out the signal. Rich media support makes async updates as detailed as in-person conversations. Split screen showing a team doing async written updates on the left side and the same team in a focused video call discussion on the right side, representing the hybrid approach

Split screen showing a team doing async written updates on the left side and the same team in a focused video call discussion on the right side, representing the hybrid approach

The hybrid approach

Some teams find a middle ground works well: async standups daily with a weekly sync for longer discussions. The async standups handle the routine stuff. What did you do? What are you working on? Any blockers? None of that requires real-time discussion. The weekly sync handles what does need back-and-forth: technical decisions, architecture discussions, hard problems. Because you're not burning everyone's time on status updates, you can afford to have a real conversation.

When sync still makes sense

Async handles information sharing. Sync handles complex collaboration. Use each for what it does best. Sprint planning, retrospectives, and technical deep-dives often benefit from real-time discussion. Daily status updates rarely do.

The bottom line

Daily standups aren't dying because they're bad. They're dying because they were designed for a world that no longer exists: teams in the same office, working the same hours, building software the same way. Distributed teams need distributed communication. Async standups give you the alignment benefits without the timezone gymnastics, the deep work interruption, or the meeting fatigue. The teams that figure this out first will attract better talent, because they're offering something rare: the ability to do focused work without constant interruption. Ready to try async standups? Start with Kollabe's free standup tool and see how your team communicates without the morning meeting.

For daily status updates, async is often more effective. Written updates are scannable, searchable, and don't require everyone to be available simultaneously. The trade-off is less spontaneous conversation, which is why many teams pair async standups with a weekly sync for deeper discussions.

Urgent blockers shouldn't wait for any standup, sync or async. Flag them immediately through your team's primary communication channel (Slack, Teams, etc.). Async standups are for daily alignment, not emergency response.

Good async tools include reminder systems that nudge people who haven't submitted. More importantly, when async updates are genuinely useful (good AI summaries, engaged teammates), people want to participate. If people skip updates, the problem is usually the format, not the async nature.

Five minutes or less. If updates take longer, you're probably over-reporting. Focus on what's actionable: what you finished, what you're working on, what's blocking you. Save the details for project documentation.

You lose the forced small talk before meetings start. But you can build connection more effectively through dedicated channels for non-work chat, virtual coffee matching, and optional social calls. Trying to cram team bonding into a standup meeting usually makes both the standup and the bonding worse.