For three months, our team had a daily standup that looked like this: eight people in a room, each saying what they did yesterday, what they're doing today, and whether they have blockers.
Total time: 30 minutes. Every single day.
That's 10 hours per week. 40 hours per month. In a year, that's two full work weeks spent exclusively in standup meetings.
So we stopped.
Here's what happened.
The Experiment
We replaced daily standups with two things:
- A shared async update doc — everyone writes what they did, what they're doing, and blockers by 10am
- A weekly 30-minute sync for actual discussion, decisions, and relationship-building
That's it. No daily synchronous meeting.
Week One: The Anxiety
Week one was uncomfortable. People kept asking "when's the standup?" out of habit. Some felt like they weren't connected to the team. A few worried that without the daily check-in, work would fall through the cracks.
The async doc got filled out, but mostly as a box-checking exercise. Half the updates were "working on X, no blockers." Not useful.
Week Two: The Adjustment
By week two, people started using the async doc more thoughtfully. Instead of "working on feature Y," someone would write "Feature Y is blocked because we need API access from the backend team — I've pinged them twice."
The weekly sync was shorter because we'd already read what everyone was doing. We used the time for actual problem-solving instead of status reports.
Month One: The Numbers
We tracked our output for month one against the previous month:
- Features shipped: 7 (up from 5)
- Average time to unblock a developer: 4 hours (down from 1.2 days)
- Team satisfaction with meetings (survey): 6.2/10 (up from 4.1/10)
What We Learned
Async works for updates, not decisions
The daily standup was good for updates. The async doc actually worked better — people had time to think and write clearly.
But the standup was also handling decisions and discussions. Those don't work async. So we kept the weekly sync specifically for things that need back-and-forth.
Visibility isn't the same as alignment
Daily standups made people feel visible. But visibility isn't the same as knowing what's actually happening.
The async doc gave more context. You could see the full picture of what everyone was working on, not just the three-minute summary in the standup.
Some people need more structure
Two developers hated it. They missed the predictability of the daily rhythm. They requested additional 1:1s to compensate.
We granted them. Not everyone thrives with the same structure.
The Honest Downsides
This isn't all positive:
- The spontaneous hallway conversation is gone. Some of the best ideas came from those unscripted moments.
- Junior team members felt more adrift without daily presence of senior people.
- Building team culture takes longer when you don't see each other every day.
Would We Go Back?
No. The time savings alone are worth it. We get back 8 hours per week per person — that's 32 hours of engineering time per week across the team.
But we'd do it differently from the start. We'd be more intentional about the async format. We'd build in more unstructured social time. We'd check in more on junior team members.
The meeting-free week isn't magic. It's just a better trade-off for our team.
Top comments (0)