How to Build an Async Meeting Culture — Lessons from GitLab, Amazon, and Basecamp
GitLab runs a 2,000+ person fully remote company generating hundreds of millions in annual revenue. Their most repeated mantra: "Create an issue before you schedule a meeting." Jeff Bezos starts every Amazon meeting with 30 minutes of silent reading of a 6-page memo. Basecamp's Shape Up methodology handles most decisions through async documents.
The common thread: async communication is the default. Synchronous meetings happen only when truly necessary.
A 2023 Harvard Business Review study found that teams shifting to async-first saved an average of 8.2 hours of meeting time per week and saw a 23% increase in employee satisfaction. Meanwhile, teams that didn't reduce meetings had 71% of employees reporting meeting fatigue.
This post covers what async actually means, four strategies for transitioning, a readiness checklist, and a week-by-week adoption guide.
What Is Async Communication?
It means communication that doesn't require everyone to be in the same place at the same time. Email, document comments, recorded presentations, messages — people consume and respond on their own schedule.
Let's clear up three common misconceptions first.
Misconception 1: "Async = slow." Removing unnecessary meetings often makes decisions faster. GitLab reported that decisions made through their async issue tracker were 1.5 days faster on average than decisions made in meetings.
Misconception 2: "Async = communication breakdown." Written communication actually increases transparency. Everyone accesses the same information. "I wasn't in that meeting so I didn't know" stops happening.
Misconception 3: "Async = zero meetings." The goal isn't to eliminate meetings. It's to raise the bar for when a meeting is worth holding. When you only meet for discussions that genuinely need real-time interaction, density and satisfaction both go up.
The core shift: change the default from "let's schedule a meeting" to "is a document enough, or do we actually need to gather?"
What Can Go Async — and What Can't
Not everything should be async.
| Activity | Keep Synchronous | Move to Async | Reasoning |
|---|---|---|---|
| Creative brainstorming | Yes | Spontaneous idea-building needs live energy | |
| Conflict resolution | Yes | Non-verbal cues and emotional tone matter | |
| 1:1 coaching / mentoring | Yes | Real-time conversation builds trust | |
| Crisis response | Yes | Immediate judgment and action required | |
| Team building | Yes | Social bonding needs presence | |
| Information sharing / announcements | Yes | One-way; questions can be handled async | |
| Status updates (standups) | Yes | Text updates work just as well | |
| Simple decisions | Yes | Clear options can be resolved via poll or comment | |
| Document / code review | Yes | Async comments are often more thorough | |
| Training / onboarding materials | Yes | Recordings + docs enable self-paced learning | |
| Project kickoff | Yes | Aligning direction needs live discussion | |
| Retrospectives | Yes | Honest conversation and emotional sharing needed |
The test is simple: "Could someone skip this meeting and still keep up?" If yes, it can go async.
Additional questions to ask: Does emotional nuance matter? Is spontaneous idea exchange the point? Does it only work if everyone is present at the same time? If any answer is yes, keep it synchronous.
Strategy 1: Identify What to Convert
Why Start Here
Most teams that fail at async transition never defined what should change. Declaring "let's have fewer meetings" without agreeing on which meetings to cut means you'll be back to the old schedule within a month.
The 3-Filter Framework
Run every meeting on your calendar through these filters:
- Purpose filter: Is the primary goal "information sharing," "discussion/decision," or "relationship building"?
- Participation filter: Do more than 50% of attendees actually speak?
- Urgency filter: Will work stop if this isn't decided within 24 hours?
Meetings that pass all three as "async-eligible" are your first conversion targets. Typically 30-40% of recurring meetings qualify.
How to Execute
- List all recurring meetings from the past two weeks.
- Apply the 3-filter framework. Sort into "keep synchronous" / "convert to async" / "eliminate."
- Pick the 1-2 easiest from the "convert" list and experiment next week.
- Collect team feedback after two weeks and adjust.
Common Mistakes
- Converting everything at once. Start with 1-2 meetings. Gradual change reduces pushback.
- Leader decides alone, ignoring the team. Get buy-in from everyone or the change won't last.
- Removing meetings without providing alternatives. Async isn't about deleting meetings — it's about changing the format. Always set up replacement channels: documents, recordings, or message threads.
Strategy 2: Design Your Async Tool Stack
Why Tools Matter
In synchronous meetings, "being in the room" equals information access. In async, information must be recorded, searchable, and accessible to everyone.
Document-Based Decisions
Amazon's 6-pager works because writing forces clear thinking, and people can absorb it at their own pace.
- Create a decision document template: background, options, pros/cons, recommendation, decision deadline.
- Use whatever your team already knows — Notion, Confluence, Google Docs.
- Try the "Silence as Agreement" rule: if no objections come in by the deadline, the proposal is approved.
Recording-Based Sharing
- Share 5-minute screen recordings for progress updates, design reviews, and technical walkthroughs.
- If a meeting did happen, share the auto-generated summary so absent members get the key points.
- Keep recordings under 10 minutes. Longer than that and people won't watch them.
Async Feedback Loops
- Always set a feedback deadline when sharing documents or recordings.
- Create a dedicated async channel in Slack or Teams — separate from real-time chat.
- Review async communication health once a week.
Common Mistakes
- Introducing tools without usage rules. Without answering "what goes where, who responds by when," you'll create chaos.
- Using too many tools. One doc tool, one messaging tool, one recording/notes tool — keep it to 3 or fewer core tools.
Strategy 3: Set Async Ground Rules
Why Rules Are Non-Negotiable
The most common complaint in async is "nobody responds." In meetings, you get answers on the spot. In async, you don't even know if the other person read your message.
Rules to Agree On
- Response time commitment: Acknowledge within 24 business hours minimum (even just "read it" or "reviewing").
- Urgency tags: Use labels like [Urgent], [Normal], [FYI] to signal priority.
- Respect async hours: Explicitly state that "you don't need to respond to after-hours messages immediately."
- Escalation path: No response in 24 hours = reminder. After 48 hours = switch to a live call.
Common Mistakes
- Agreeing verbally but not writing it down. Put it in your team wiki or handbook.
- Rules that are too strict. "Respond to every message within 1 hour" defeats the purpose of async. The point is giving people uninterrupted time for deep work.
- Leaders breaking their own rules. If the manager sends late-night messages expecting fast replies, the entire async culture crumbles.
Strategy 4: Balance Sync and Async
Finding the Right Mix
The most productive teams spend 60-70% of their time in async mode and 30-40% in synchronous mode.
How to Execute
- Keep one sync meeting per week, but only for items that couldn't be resolved async.
- "Async first" principle: Every agenda item starts as async. Only unresolved items move to the sync meeting.
- Define sync escalation triggers: a comment thread exceeds 5 back-and-forths with no agreement, emotional tension is rising, or a deadline is less than 24 hours away.
- Always leave an async record after a sync meeting. This ensures absent members have the same information.
Common Mistakes
- The "if it doesn't work, let's just meet" safety-net mindset. The right approach: "Discuss fully in async first. Use sync only for the final decision."
- Not recording sync meetings. An unrecorded synchronous meeting is the biggest enemy of async culture.
Async Readiness Checklist
Score your team on these 10 items. 7+ yes = ready to transition. 4-6 = start with partial conversion. 3 or fewer = build the foundation first.
| # | Item | Yes/No |
|---|---|---|
| 1 | Team has a shared doc tool (Notion, Confluence, etc.) used by 80%+ of members | |
| 2 | Meeting notes are consistently created and accessible to everyone | |
| 3 | Async messages (Slack, Teams) get responses within 24 hours as a norm | |
| 4 | Work progress is transparently shared via tools (Jira, Asana, etc.) | |
| 5 | Information-sharing meetings make up 30%+ of all meetings | |
| 6 | Leadership is open to — or actively prefers — async communication | |
| 7 | Team members share the belief that "we have too many unnecessary meetings" | |
| 8 | Team has experience with remote or hybrid work | |
| 9 | Team members can effectively communicate opinions in writing | |
| 10 | Team is 5+ people, making the cost of gathering everyone tangible |
This checklist covers three dimensions: tool readiness (1-4), transition motivation (5-7), and environmental fit (8-10).
4-Week Adoption Guide
Week 1: Assess and Align
- Categorize recurring meetings by purpose (information sharing / discussion / decision / relationship building).
- Run the readiness checklist. Pick 1-2 meetings to convert.
Week 2: First Async Experiment
- Replace selected meetings with document summaries or recorded updates.
- Document team rules: response times, urgency tags, escalation triggers.
Week 3: Iterate and Expand
- Incorporate Week 2 feedback. Refine the process. Convert 1-2 more meetings.
Week 4: Solidify and Measure
- Measure results with data. Run a team retro. Add the rules to your team handbook.
Measuring Success
| Metric | How to Measure | Pre-Transition | 4-Week Target | 12-Week Target |
|---|---|---|---|---|
| Weekly meeting hours | Calendar total | Current | 20% reduction | 30-40% reduction |
| Decision turnaround | Request to decision | Current | Same or better | 20% faster |
| Async response rate | % responded within 24h | Start tracking | 70%+ | 85%+ |
| Team satisfaction | Monthly survey (1-5) | Current score | +0.3 points | +0.5 points |
| Info accessibility | "Can you find last meeting's notes?" | Start tracking | 60%+ yes | 80%+ yes |
| Deep work blocks | 2+ hour uninterrupted blocks/week | 2-3x | 4x | 5x+ |
When Async Doesn't Work
Async has real limits. Be honest about them.
- Urgent crises: Service outages, customer emergencies — you need real-time judgment.
- Emotional conflicts: Text can't convey tone. Switch to face-to-face before misunderstandings pile up.
- Creative brainstorming: The energy of ideas sparking other ideas works better live.
- New team member onboarding: Fresh hires need real-time conversation for psychological safety.
- Writing skill gaps: If there's a wide gap in writing ability, async can create information asymmetry.
Async transition is a culture problem, not a tool problem. What should be async goes async. What needs to be synchronous stays synchronous. The key is having the whole team share that judgment framework — and staying flexible. Start small, experiment, and find the balance that fits your team.