The phrase "async-first" has become a buzzword, which means it's now mostly empty. Everyone says they're async-first. Almost nobody is. Most teams have a Slack channel they treat as a 24/7 chat room, a calendar full of recurring meetings, and a vague sense that they should probably be writing more documents.
This piece is for people who want to actually decide which mode their team should be operating in, and what changes that decision requires.
The short version: it's not a binary. Most healthy distributed teams are sync for some kinds of work and async for others, on purpose, with the boundary written down. The teams that struggle are usually the ones who never made the decision deliberately.
What "async" and "sync" actually mean
Sync — short for synchronous — means real-time. Everyone is present at the same time. The communication is a conversation. Meetings, phone calls, live chat back-and-forth, pair programming sessions.
Async — asynchronous — means time-shifted. The sender posts and then leaves. The receiver picks it up later. The communication is a record. Documents, emails, recorded video, code reviews, GitHub issues, comments on a doc.
The distinction matters because the two modes have completely different cognitive costs, social signals, and failure modes.
Sync communication is high-bandwidth and emotionally rich. You see facial expressions, you hear tone, you can resolve ambiguity in seconds. The cost is that you have to be there at the same time, which creates calendar tax, time-zone tax, and interruption tax.
Async communication is structured and durable. The document still exists tomorrow. The comment thread can be re-read by a new team member six months from now. The cost is that ambiguity takes longer to resolve, social warmth is harder to convey, and unwritten rules become invisible.
Neither is universally better. The question is which one fits the work.
When sync wins
Synchronous work is the right choice when at least one of these is true:
The conversation is exploratory. You don't know where it's going. You'll find out together. Brainstorming, architecture discussions, creative review, customer discovery. Things where the back-and-forth is the value.
Trust is fragile or new. Onboarding conversations, performance feedback, conflict resolution, disagreement. Anything where tone matters more than the literal content. Written feedback can be re-read out of context and re-injure. Spoken feedback fades faster.
The decision needs immediate action. Production incidents, customer escalations, time-bounded negotiations. Anything where the time cost of a 6-hour async loop is greater than the time cost of getting people on a call.
The relationship matters more than the output. Team rituals, social check-ins, the conversation after the meeting. These are where the human bonds get built that make the async work possible.
If your team has stopped doing any of these synchronously, your culture is probably more fragile than you think.
When async wins
Asynchronous work is the right choice when at least one of these is true:
The work product is itself a document. Code review, design review, spec review, plan review. The artifact is the conversation.
The participants are in different time zones. Above any other factor, geography forces async. Trying to maintain sync defaults across 8+ hour gaps is a losing game.
You need a durable record. Decisions that future team members will need to understand. Onboarding documents. Process changes. Anything where "we discussed this on a call three months ago" becomes a problem in retrospect.
Deep work is at stake. Synchronous meetings shatter focus. A team operating sync-first will lose half its productive thinking hours to meeting fragmentation. Knowledge workers need three to four hour uninterrupted blocks to do their best work. Sync defaults make those blocks impossible.
Different people need different time to process. Sync conversations privilege fast thinkers and confident speakers. Async conversations privilege careful thinkers and good writers. Most teams have both. Async gives the careful ones a fair seat.
The default question
A useful frame: what's your default? When something comes up that needs discussion, does the team's instinct go to "let's get on a call" or "let me write this up"?
Most teams have a sync default because that's how every previous workplace operated and nobody noticed when it stopped serving them. The way to shift is small and slow:
- Start each new conversation with a written first draft. Even a paragraph. Post it where the team can see it.
- If it provokes a response, that response also lives in writing.
- A live conversation only gets scheduled when the written exchange has reached a clear impasse or when someone explicitly asks for one.
This sounds bureaucratic. After a few weeks, it stops feeling bureaucratic and starts feeling like normal work. The amount of stuff that resolves itself in writing is surprising.
The decision matrix
A simple way to think about any specific conversation or piece of work:
| Low ambiguity | High ambiguity | |
|---|---|---|
| Low relational stakes | Async (it's just status) | Async with optional sync (write first, talk if needed) |
| High relational stakes | Sync with async follow-up (talk first, document the decision) | Sync (you need the bandwidth) |
The mistake teams make is putting everything in the bottom-right box ("high stakes, let's just get on a call") even when it doesn't belong there.
Three team archetypes, three different mixes
Here's what the right balance looks like in different team types.
Archetype 1: Small fast-moving startup, all in one city
Team of 5–10. One location or two adjacent ones. Working on early product, lots of unknowns.
Right mix: Sync 60%, async 40%.
These teams should bias sync. They benefit from fast iteration, exploratory conversation, and the social glue of being in the same space (or same time zone). Writing too much too early is a tax. The risk: as the team grows, the sync defaults stop scaling.
Schedule template:
- Daily 15-minute standup, in person or live.
- Weekly hour-long team meeting.
- 2–3 ad-hoc sync conversations per day per person.
- Async: shared planning doc updated weekly, code review in PRs, decision log for things worth recording.
Archetype 2: Globally distributed engineering team
20–100 people across 4+ continents. Mature product, lots of process.
Right mix: Async 80%, sync 20%.
These teams have to be async-first. The cost of sync default is too high. Reserve sync time for the highest-leverage real-time activities (incident response, design reviews on novel problems, 1:1s). Everything else is in writing.
Schedule template:
- No daily standup. Use written daily updates or weekly summaries.
- One weekly all-hands, recorded.
- 1:1s with managers, sync.
- Project work entirely in writing: design docs, RFCs, PR reviews, decision logs.
- A "decision window" of 60 minutes per day where ad-hoc sync conversations can happen if needed.
Archetype 3: Sales-led distributed team
Account executives, customer success, sales engineering, distributed across regions.
Right mix: Sync 70%, async 30%.
These teams are sync-heavy because the customer-facing work is itself sync. Most of the meetings can't be moved. Internal coordination should still be async-first to protect the time that's available for external work.
Schedule template:
- Daily sync customer-facing time blocks.
- Weekly sync regional team meeting.
- Internal coordination async: account notes, deal logs, written handoffs.
- A weekly written summary from each rep replacing the "what happened this week" sync meeting.
The four pitfalls
Watching teams shift between modes, four traps are predictable.
Pitfall 1: Slack as a sync substitute
Teams say they've gone async, but they treat Slack as a 24/7 chat room. Pings get answered in minutes. People feel guilty going offline. The expectations are sync; only the medium changed.
Fix: explicit response time expectations. "Slack response is best-effort within four working hours during your day. Async means we don't expect immediacy. Use email or a tagged doc for things that need a fixed response window."
Pitfall 2: Meeting hangover
Teams cut meetings to be async-first, but then someone schedules a "quick chat" three times a week with the same three people. The meetings come back through the side door.
Fix: every recurring meeting needs an explicit charter (what decision does this produce?) and a six-month review. Standing meetings without a charter get cancelled by default.
Pitfall 3: Vague writing
The team writes more, but the writing is unstructured paragraphs ending in "let me know what you think." Async only works if the writing is actionable.
Fix: a written-update template. Decision, context, options, deadline, default action if no response. Use it for everything.
Pitfall 4: Loss of social texture
The async-first team gets the work done but starts feeling like a series of strangers. People stop trusting each other. Conflict becomes harder.
Fix: explicit social rituals. A regular sync block that is just for hanging out (not status). Quarterly or annual in-person team time, if budget allows. A culture where 10 minutes at the start of every meeting is small talk, not pre-meeting work.
What to do this week
Three small experiments:
- Pick one recurring meeting and convert it to a written update for two weeks. See if anyone misses the live version.
- Write your team's overlap window on a sticky note. Look at how many of your current sync practices fit inside it. The ones that don't are quietly costing someone.
- Adopt a written-update template. Use it once. See how the conversation that follows changes.
The goal isn't to be more async or more sync. The goal is to be deliberate. Teams that decide on purpose tend to find their way to a stable mix. Teams that drift end up wherever the loudest person's preference takes them.