Why This Matters

Ever sit through a meeting that should've been an email? Yeah. We all have.

Remote work freed us from commutes. But now we've replaced in-person interruptions with digital ones. Endless Slack pings. Back-to-back Zooms. The unspoken rule that you must respond immediately.

Async flips this. You communicate without everyone being online at the same time. It's not just about time zones. It's about protecting focus time and actually getting work done.

GitLab, Zapier, Automattic. Billion-dollar companies, all async-first. It works.

What's Async, Actually?

Simple: communication where people don't need to be present simultaneously. You send a message. They respond when available.

Sync (real-time)

  • Video calls, phone, chat expecting instant replies

Async (time-shifted)

  • Email, Loom videos, project comments, chat when you get to it

The tool doesn't matter. Slack can be async or sync. It's about expectations. The question: does everyone need to be available RIGHT NOW?

Why It's Better

Deep work happens. Research shows it takes an average of 23 minutes to fully refocus after an interruption according to UC Irvine studies on workplace attention. In a ping-heavy culture, actual focused work is nearly impossible. Async lets you batch communication. Respond on your schedule.

Time zones don't matter. San Francisco to Singapore? Works fine when nobody needs to be online simultaneously.

Better decisions. Real-time meetings favor whoever talks fastest. Async gives everyone time to think. Introverts get equal voice.

Built-in documentation. Everything's written down. Decisions documented. New hires can read history instead of asking.

Actually flexible schedules. Parents work around school. Night owls work at 2 AM. Real flexibility, not "remote but online 9-5."

When to Use Which

Async isn't everything. Some things need real-time.

Go async for:

  • Status updates
  • Information sharing
  • Non-urgent feedback
  • Decisions that can wait
  • Complex explanations (record a Loom)
  • Weekly updates

Go sync for:

  • True emergencies
  • Building relationships
  • Sensitive conversations
  • Rapid-fire decisions
  • Initial onboarding

The 1-day rule: If waiting 24 hours would seriously hurt outcomes, go sync. Otherwise? Async.

Tools That Work

A few things worth knowing before you pick. Loom's free plan caps you at 25 videos per person and 5 minutes per recording, which is fine for trying it out and annoying once the whole team is hooked. Paid plans start at $18 a month. Twist is still around and still built around threads instead of a live chat stream, which is the whole point if you want people to stop expecting instant replies.

Slack's free plan only keeps 90 days of message history. That's a problem for async teams specifically, because the whole idea is that decisions live in writing. If you're on free Slack, put anything that matters in your docs tool, not in a thread that disappears in three months.

How to Do It Right

Write clearly. Context included. Ask stated upfront. Options provided, not just "what should we do?" Anticipate follow-up questions.

Use the right channel. Project updates in the PM tool. Announcements in dedicated channels. Questions to specific people via DM.

Set response expectations. Define as a team: standard response times, how to signal urgency, what's a real emergency.

Use video. Text strips tone. Complex topic? Record a Loom. Three minutes beats 500 words.

Document decisions. What, why, who, when, where to find more. Future you will thank present you.

Batch your comms. Check messages at set times. Morning, after lunch, end of day. Not continuously.

Quick Templates

Daily update: Done, Doing, Blocked, Need

Decision request: Context, Options with pros/cons, My recommendation, What I need from you, Deadline

Project update: Status (green/yellow/red), Summary, Progress, Next up, Risks

Templates look boring on a page, so here's what a decision request actually looks like filled in:

Context: Our onboarding emails go out from three different tools and customers are getting duplicates.

Options: (A) Move everything to the CRM. Cheapest, but we lose the nicer templates. (B) Keep the email tool, kill the other two. Costs a bit more, less migration work.

My pick: B. We can do it in a week.

What I need: A yes or no from Dana on the budget.

Deadline: Thursday 5pm CET, so it's done before the next batch of signups.

Notice what's missing. No "thoughts?" No meeting request. Anyone can read it cold and answer in two minutes.

Where Async Goes Wrong

Async fails in a few predictable ways. Most teams hit at least one.

Everything becomes "urgent." If people start tagging half their messages as urgent, you've just rebuilt the ping culture with extra steps. Keep one channel for real emergencies and guard it.

Nobody closes the loop. A thread gets 14 replies and no decision. Someone has to own it, write "Decision: we're going with B," and move on.

Silence gets read as agreement. Or as rudeness. Neither is fair. If you need a reply, say who and by when.

People feel alone. Pure async can get lonely. That's why the sync list above includes relationship stuff. A casual video call every week or two does more than any tool.

Spread across very different time zones? Our time zones guide covers overlap hours and how to share out the bad meeting slots.

Frequently Asked Questions

For chat, sure. For history, no. The free plan only keeps 90 days of messages, so anything you need later belongs in a doc.

Track metrics. Meeting time before vs. after. Start with one recurring meeting. Show results.

Counterintuitively, no. People respond with complete info. Work continues while waiting. Total time is often shorter.

Virtual coffee chats. Social channels. Video messages instead of text. Occasional in-person if possible.

DMs: 4-8 hours. Mentions: 24 hours. General posts: 24-48 hours. Emergencies: separate channel.

Define "urgent" explicitly. Separate channel for emergencies. On-call rotation if needed. Phone for true crises.

Everyone adds ideas independently, then comments, then votes. Often better than sync. No groupthink.

Use video for tone. Lead with context. Be specific. Invite their perspective.

Pre-recorded videos, written guides, assigned buddy for sync questions. More real-time at first, then gradually shift.

Getting Started

  • Week 1: Audit your meetings. What could be async?
  • Week 2: Convert one recurring meeting. Set expectations.
  • Week 3+: Expand based on what works.

Bottom Line

The goal isn't zero meetings. It's being intentional about when real-time actually adds value.

Your best working hours shouldn't be spent in meetings about meetings. Async gives that time back.