Async Communication: How to Reduce Meetings Without Losing Alignment

Automattic — the company behind WordPress.com — has over 1,900 employees across 90+ countries. They have almost no recurring meetings. Their CEO, Matt Mullenweg, has described their communication culture as "async by default, sync by exception." Company decisions happen in written posts. Team updates happen in P2 blogs. Even hiring interviews are conducted over text chat.

They're not anti-meeting. They're anti-unnecessary meeting. And when you examine how most companies spend their meeting time, the waste is staggering.

A 2022 study by Otter.ai found that the average employee spends 18 hours per week in meetings, and considers 5.6 of those hours to be unproductive. For a team of 10, that's 56 wasted hours per week — more than a full-time employee's worth of lost productivity.

Async communication isn't about eliminating meetings entirely. It's about doing asynchronously everything that can be done asynchronously, so your remaining meetings are high-value and high-energy.

Why Async Works Better Than You Think

The default assumption is that real-time communication is faster and more effective than async. For simple questions, that's sometimes true. For complex decisions, collaboration, and knowledge sharing, async is often superior.

The Quality Advantage

When you write a proposal asynchronously, you think before you communicate. You organize your argument. You anticipate objections. You include supporting data. Compare that to the same proposal delivered verbally in a meeting — half-formed, interrupted by tangential questions, and never documented.

Jeff Bezos banned PowerPoint at Amazon in favor of six-page narrative memos precisely for this reason. Writing forces clarity. "When you have to write your ideas out in complete sentences, complete paragraphs," Bezos told CBS, "it forces a deeper clarity."

The Inclusion Advantage

In a synchronous meeting, extroverts dominate. The person who speaks fastest and loudest gets heard. Introverts, non-native English speakers, and people who need processing time get marginalized — even when they have the best ideas.

Async levels this playing field. Everyone gets the same amount of time to compose their thoughts. A thoughtful response posted 4 hours after the question is given equal weight to an immediate reply. This is especially critical for building a diverse team culture.

The Timezone Advantage

If your team spans more than two time zones, synchronous meetings become a logistics nightmare. Someone is always attending at 7 AM or 9 PM. Async communication works at any time, from any timezone, without anyone sacrificing their sleep schedule.

The Documentation Advantage

Meetings produce memories, which are unreliable. Async communication produces records. Every decision, every discussion, every piece of context is searchable and quotable. Six months from now, you can trace exactly how and why a decision was made. With meetings, you're relying on someone's recollection — or hoping someone took decent notes.

What to Move Async (And What Stays Synchronous)

Not everything should be async. The key is matching the communication format to the purpose.

Move These Async

Status updates. "What did you work on this week?" should never be a meeting. Written standups (daily or bi-weekly) take 5 minutes to write and 10 minutes to read, replacing a 30-minute meeting.

Information sharing. Product updates, company announcements, process changes — all of these are better as written posts where people can read at their own pace and ask questions in comments.

Decision-making (non-urgent). Share the proposal in writing. Give people 24-48 hours to review and comment. Synthesize the feedback. Make the decision. Document the outcome. This produces better decisions than a 60-minute meeting where half the attendees haven't thought about the topic beforehand.

Feedback and reviews. Code reviews, design reviews, and document reviews are inherently async. Reviewing in real-time adds time pressure that degrades quality.

Training and onboarding. Recorded videos and written guides that new hires can consume at their own pace. They can pause, rewatch, and reference the material months later. A live training session evaporates the moment it ends.

Keep These Synchronous

Conflict resolution. Tone and nuance matter too much for text. When emotions are involved, get on a call.

Brainstorming. Real-time creative energy, building on each other's ideas, the electricity of a good brainstorm — this is genuinely better synchronous. Keep it to 30-45 minutes with a clear prompt.

Relationship building. One-on-ones, team social time, and new hire introductions benefit from the human connection of face-to-face (or camera-to-camera) interaction.

Crisis response. When the server is down or a major customer is about to churn, you need real-time coordination. Everyone on a call. Fix it. Then document what happened asynchronously.

Complex, multi-party negotiations. When multiple stakeholders need to reach consensus quickly and positions are far apart, a facilitated discussion is more efficient than a 47-message Slack thread.

Async Formats That Work

Written Standups

Replace the daily standup meeting with a written post. Each team member shares three things at a consistent time daily:

1. What I completed yesterday
2. What I'm working on today
3. Any blockers I need help with

Post these in a dedicated Slack channel or a recurring Notion page. Teammates read when convenient. Blockers get addressed via thread replies or direct messages. Total time: 5 minutes to write, 5-10 minutes to read all updates. Versus: 15-30 minutes for a synchronous standup, longer if discussions go off track.

Tools: Geekbot ($2.50/user/month) automates standup collection in Slack. Standuply does the same for Teams. Or just use a recurring Slack reminder with a template.

Loom Videos for Complex Updates

When written text isn't enough — you need to walk through a design, demo a feature, or explain a nuanced situation — record a Loom video (or any screen recording tool). A 5-minute Loom replaces a 30-minute meeting because:

• The presenter organizes their thoughts before recording (better quality)
• Viewers watch at 1.5-2x speed (time savings)
• The video can be rewatched, shared with absent team members, and referenced later
• Comments are timestamped, creating async discussion on specific moments

Basecamp's team uses recorded walkthroughs extensively. Shape Up, their product development methodology, includes video "pitches" where the person proposing a project records their case rather than presenting it live.

RFCs (Request for Comments) for Decisions

For significant decisions, write an RFC document:

Context: What's the situation? What problem are we solving?

Proposal: What do you recommend and why?

Alternatives considered: What else did you evaluate and why was it rejected?

Risks and mitigations: What could go wrong?

Decision deadline: When do we need to decide by?

Share the RFC with relevant stakeholders. Set a comment deadline (typically 48-72 hours). People add their input asynchronously. The author synthesizes the feedback, updates the proposal, and either makes the call or escalates if there's unresolved disagreement.

Amazon, GitLab, and Stripe all use RFC-style processes for significant decisions. The format varies, but the principle is universal: write the thinking down, let people react thoughtfully, then decide.

Weekly Digest Posts

Replace the weekly all-hands with a written digest. Each team or function posts a weekly summary:

• Key accomplishments
• Metrics update (with context, not just numbers)
• Upcoming priorities
• Decisions needed from other teams

Compile these into a single weekly post that everyone reads. Add a "questions and discussion" section where people can comment asynchronously. For a 20-person company, this saves 20 person-hours per week compared to a one-hour all-hands.

The Transition Plan: From Meeting-Heavy to Async-First

You can't flip a switch from synchronous to async culture. Teams accustomed to meetings will feel anxious without them — not because the meetings were productive, but because the meetings were familiar.

Week 1-2: Audit and Baseline

Count every recurring meeting on your team's calendar. For each, document: attendees, duration, purpose, and stated output. You'll likely find that 30-50% of recurring meetings produce no documented decisions or action items.

Week 3-4: Eliminate the Obvious

Cancel meetings that have no clear purpose, no agenda, or where the output could be an email. "Status update" meetings are the first to go. Replace with written standups.

Week 5-8: Convert the Convertible

For each remaining meeting, ask: "Could this be an async document with a comment period?" If yes, convert it. The weekly team sync becomes a written digest. The design review becomes a Loom video with async feedback. The project kickoff becomes an RFC.

Week 9-12: Optimize the Remainder

The meetings that survive should be genuinely high-value: brainstorms, one-on-ones, conflict resolution, and celebrations. For these, invest in making them excellent — clear agendas, tight timeboxes, and documented outcomes.

Ongoing: Protect the Culture

Async culture erodes when leadership backtracks during stressful periods. "Let's just hop on a call" is the gateway phrase. Sometimes a call is warranted. But if it becomes the default response to any complex question, you're drifting back to sync-first.

Create a norm: before scheduling a meeting, write the question or proposal as an async post. If async discussion doesn't resolve it within 48 hours, then schedule a meeting. This simple gate dramatically reduces unnecessary meetings.

Measuring Success

Track these metrics monthly to verify your async transition is working:

• Total meeting hours per person per week. This should decline by 30-50%.
• Written decisions documented. This should increase as more decisions happen asynchronously.
• Response time to async requests. Should stabilize at 4-8 hours for normal priority items.
• Employee satisfaction with communication. Survey quarterly. If people feel less informed or more isolated, the async implementation needs adjustment.
• Output per person. With fewer meetings and more deep work time, individual output should measurably increase.

Common Pushback and Responses

"Async is slower." For individual exchanges, yes. For organizational throughput, no. A 30-minute meeting that blocks 8 people costs 4 person-hours. An async thread that takes 6 hours wall-clock time but 20 minutes of each person's attention costs 2.7 person-hours. Async is slower in latency but cheaper in total time.

"I can't read tone in text." This is real. Train your team to use explicit emotional signaling. "I'm not frustrated, genuinely curious:" before a challenging question. Emoji for tone (a well-placed thumbs up conveys approval faster than a paragraph). And default to video call when text threads become tense.

"Some people don't respond to async messages." This is a management problem, not a format problem. Set clear response time expectations and hold people accountable. If someone consistently ignores async requests, address it in their one-on-one, just as you would address someone who consistently shows up late to meetings.

Conclusion

Async communication isn't about banning meetings or forcing everything into Slack threads. It's about using the right communication format for each purpose and recognizing that most of what we put in meetings doesn't belong there.

Start by replacing one recurring meeting with an async alternative this week. Measure the time saved. Scale from there. Within three months, your team will wonder how they ever tolerated a calendar full of status updates disguised as collaboration.