Over the last two years I’ve worked with eight different remote teams. Some of them were meeting monsters, Zoom all day, two hours of real work left. The others had one synchronous meeting a week and everything else in writing. The gap in productivity, work quality, and stress levels was huge. Async is a skill you can learn and strengthen like a muscle. Here’s what I’ve taken from those teams.
The core assumption of async
Decisions and information don’t have to travel instantly. A few hours is fine. This assumption exists so the team can spend most of its time in deep work.
Synchronous culture is the opposite: answer every Slack question now, respond to every ping immediately, hop on a half-hour “quick call”. Focus is impossible.
The practices that make async possible
- Written decision documents. RFCs, ADRs, design docs. Important decisions are written down first, the team comments, then the call is made. No meeting required, there’s a record.
- Daily status updates, written. No standup call, everyone writes what they did, what they’re doing, and their blockers in a Slack thread. Reading for 15 minutes beats a 30-minute call.
- Documentation discipline. Wiki, Notion, GitHub README, all kept current. Instead of telling a new hire “go ask so-and-so”, you point them at the doc.
- Public cross-team channels. Decisions happen in public Slack, not DMs. Everyone can see the conversation.
- Response SLAs. “Important messages get a reply within 4 hours. Critical within 1. Normal by end of day.” Everyone knows the rules, expectations are clear.
- Loom, Granola, async video. If you need to show something, record a 3-minute video instead of booking a call. Watchers can run it at 2x.
- Meetings require an agenda up front and notes after. If there’s a meeting, the agenda comes before and the notes come after. Anyone who missed it can catch up by reading.
Habits that break async
- DMing “are you free?” for every question.
- Meeting invites without agendas.
- The “let’s hop on a call” trap, pulling a written conversation onto audio.
- Decisions made in private channels.
- Answering a written question with “jump on a call now”.
- Fake urgency like “I need this in an hour” when it isn’t actually urgent.
Timezone management
My team was spread across Istanbul, Berlin, and Toronto. Three timezones, 8-hour spread. We had to narrow synchronous windows to 2 hours a day. That forced async culture.
Only genuinely synchronous things happened in the window: the weekly team meeting, urgent incidents. Everything else was written.
When the Toronto teammate started in the morning, they worked through Istanbul’s messages, PR reviews, decision threads. When they closed out in the evening, Berlin picked up. Continuous progress.
The solo mental model
People on async teams develop one key habit. Before panicking about a problem, they ask: “does this really need to happen now, or will it work itself out in 4 hours?”. Most things wait. Teams without that muscle constantly escalate non-fires into fires.
Tool choices
- Slack: discussion and daily updates only. Not where decisions live.
- GitHub Issues/PRs: code-level discussion.
- Notion: documentation, RFCs.
- Loom: long explanations as video.
- Linear: task tracking.
- Cal.com: when a meeting is unavoidable, easy scheduling.
They’re all connected, but each one stays in its lane. You don’t try to write an RFC in Slack.
Where async falls short
Let’s be honest, some things are hard in async. Creative brand sessions, the first-week bonding for a new hire, someone deep in a mental slump who needs a breather, conflict resolution. Synchronous wins those.
The rule is: async by default, sync when needed. It’s not “everyone always writes”, it’s “decidable things go in writing, empathy goes in voice”.
Closing thought
The best team I worked with was an Estonia-based startup, 14 people across 9 timezones. One hour of demo call a week, one hour all-hands a month. Everything else written. The product moved fast, people looked unstressed. When I asked “what are you doing differently?” the founders said “we built a written culture from day one and never changed it”. Culture doesn’t show up on its own, it gets designed.