DEV Community

Kinetic Goods
Kinetic Goods

Posted on

I Ran Every Meeting Async for 30 Days. Here's What Actually Happened.

For 30 days, I replaced all team meetings with async updates. No standups, no planning sessions, no "quick syncs." Here's what I learned.

The Setup

My team was three people, distributed across two time zones. We had:

  • Daily standup: 15-20 minutes
  • Weekly planning: 45 minutes
  • Biweekly review: 30 minutes
  • Various "quick calls" that were never quick

Total: roughly 5-7 hours per week in meetings.

I proposed a 30-day experiment: what if we replaced all of it with written async updates?

The System

Each morning, each team member posts:

**Yesterday:** What I accomplished
**Today:** What I'm working on  
**Blockers:** Anything preventing progress
**Help needed:** If I need input from someone specific
Enter fullscreen mode Exit fullscreen mode

Updates are posted by 10 AM in a shared channel. Team leads read by 11 AM. If a discussion is needed, we schedule a 15-minute focused call - but only for the people who need to be there.

What Worked

Time zone flexibility improved immediately. No one had to be online at 9 AM for a standup. People posted when their day started.

Written thinking is clearer thinking. When you have to write what you did instead of saying it, you naturally focus on outcomes rather than activities. "Built the login API" becomes "Completed and tested the login API endpoint, ready for review."

Fewer interruptions. Knowledge workers report that they need 2-3 hours of uninterrupted time for deep work. Meetings are interruption triggers. Removing them meant people actually had time to think.

Documentation happened naturally. Instead of decisions living in someone's memory, they lived in the channel. New team members could read back and understand why things were built a certain way.

What Didn't Work

Complex technical discussions are harder async. When you need to whiteboard something or hash out architecture decisions, text doesn't cut it. We still had 2-3 video calls per week for genuinely complex topics.

Some things need synchronous alignment. Vision,ไปทๅ€ผ่ง‚, culture - these are hard to transmit in written updates. We added a monthly 30-minute video "hangout" that wasn't about work.

Social connection suffers. The casual "how was your weekend" moments don't happen async. We had to be intentional about adding them back.

Not everyone writes well. Some team members struggled to communicate clearly in writing. This became a coaching opportunity, but it took time.

The Numbers

After 30 days:

  • Meetings: down 80%
  • Tasks completed: up 15%
  • Team satisfaction (survey): 8.2/10 vs 6.1/10 before
  • Time in deep work: up from ~2 hours/day to ~4 hours/day

The Meeting System That Made This Work

I didn't go in blind - I used a Meeting Mastery System that includes templates for:

  • Daily async standup format
  • Decision documentation template
  • Blockers-only meeting agenda (for when we do need synchronous time)
  • End-of-week summary template

It's not anti-meeting. It's pro-meetings-that-actually-have-a-purpose.

[Link to Meeting Mastery System in bio]

The goal isn't to eliminate all meetings. It's to make every meeting one that justifies the time it takes.

Top comments (0)