The daily standup: 15 minutes every morning. Three questions: What did you do yesterday? What are you doing today? Any blockers?
Simple. Ritualistic. Established.
Also: 15 minutes × 5 people × 5 days = 6+ person-hours per week.
For information that could have been shared in a two-minute written update. Read in 30 seconds. Async. No meeting.
Why are we still doing this?
The Original Justification
Standups emerged for reasons:
**Visibility.** With 8-10 people working in parallel, it was easy to lose track of what everyone was doing. Daily sync provided visibility.
**Coordination for large teams.** Eight people working on interdependent code needed synchronization. Dependencies, blockers, priority shifts — without a sync point, chaos.
**Accountability rhythm.** Saying what you'll do today, in front of peers, creates mild accountability pressure.
These were real benefits for traditional teams.
What Changed
**Work is visible faster.** With AI-assisted development and continuous integration, work becomes visible quickly. You can see what happened. You don't need verbal reports.
**Teams are smaller.** Two people with AI can do what eight did before. Two people don't need daily synchronization ceremonies. They can just talk when needed.
**Async works.** Slack, Teams, shared documents — async communication tools are good enough now that sync meetings are optional, not required.
**Context switches are expensive.** Every meeting breaks flow. For focused work, uninterrupted time matters. Daily interruptions at fixed times harm productivity.
The Async Alternative
Replace the daily standup with:
**Written daily update.** Each person posts what they did, what they're doing, any blockers. Async. People read when it fits their flow.
**On-demand sync.** When real-time communication is needed — a blocker, a decision, a coordination need — just call. Don't wait for the scheduled standup.
**Weekly sync.** A longer, less frequent check-in for the things that benefit from synchronous discussion. Strategy, planning, retrospective.
This gives you the information benefits of standups without the daily overhead.
When Standups Still Work
Not every team should drop standups:
**Large teams** with complex interdependencies may need daily sync.
**Teams with unreliable async communication** — if people don't read written updates, standups force the communication.
**Teams that value the social ritual** — standups can be a bonding moment. If your team values that, keep it.
**Remote teams struggling with isolation** — daily face time might help with connection.
The question isn't "are standups bad?" It's "are standups earning their cost for your specific team?"
Making the Shift
If you suspect standups are overhead:
1. Try async updates for a week. See if information still flows. 2. Keep on-demand sync available. See if blockers still get resolved. 3. Note whether anything was lost. Real problems, not theoretical concerns. 4. If nothing was lost, make it permanent.
If things break — people didn't post updates, blockers festered, coordination failed — bring standups back. No harm done.
But don't assume standups are necessary because "that's Agile." Test it. Many teams find async is better.
The Bigger Point
Standups are one example of ceremony that may have outlived its justification.
The practice: question every recurring meeting.
- What problem does this solve?
- Does that problem still exist?
- Is there a lighter-weight solution?
Apply this to standups, sprint planning, retros, all of it. Keep what earns its place. Cut what doesn't.