Home › Async vs Meetings

Async Communication vs Meetings

When to meet synchronously and when to communicate asynchronously

The Rise of Async-First Culture

The shift to remote and hybrid work forced organizations to rethink how they communicate. Before 2020, most teams defaulted to meetings for anything beyond a quick chat. Now, many of the most productive companies operate on an "async-first" principle: communicate asynchronously by default, and reserve synchronous meetings for situations that genuinely require them.

The logic is straightforward. Asynchronous communication — messages, documents, recorded videos — allows each person to engage on their own schedule, at their own pace. This respects deep work time, accommodates time zone differences, and creates a written record. Synchronous meetings, by contrast, require everyone to be present simultaneously, cost real money in salary, and produce no permanent record unless someone takes notes.

Neither mode is universally superior. The skill is knowing when each one is the right choice.

When to Meet Synchronously

Some situations genuinely benefit from real-time, face-to-face (or screen-to-screen) interaction. Use synchronous meetings when:

The topic requires rapid back-and-forth

Complex problem-solving, architecture discussions, and brainstorming sessions involve building on each other's ideas in real time. The latency of async communication (minutes to hours between messages) makes these conversations painfully slow and fragmented. A 45-minute meeting can accomplish what would take a week of async back-and-forth.

Emotional nuance matters

Giving sensitive feedback, resolving interpersonal conflict, discussing career development, or addressing team morale issues should almost always happen synchronously. Tone, facial expressions, and vocal inflection carry information that text cannot. A message meant to be constructive can read as harsh. A meeting allows you to read reactions and adjust in real time.

Alignment is urgent

When a decision must be made quickly and involves multiple stakeholders with different perspectives, a meeting can reach consensus in 30 minutes that would take days of email threads. Crisis response, incident post-mortems, and time-sensitive product decisions fall into this category.

Relationship building is the goal

Team bonding, one-on-one check-ins, and cross-team introductions are inherently synchronous. The point is the human connection, not the information exchange. These meetings are high-ROI even when they don't produce tangible deliverables.

Multiple complex inputs need synthesis

When you need input from engineering, design, product, and legal on a single decision, a meeting lets you hear all perspectives together and resolve conflicts in real time. Async threads with multiple participants often devolve into parallel conversations that no one can follow.

When to Go Async

Many common meeting types can be replaced with asynchronous alternatives that are faster, cheaper, and produce better outcomes.

Status updates

The classic "standup" or "weekly sync" where each person reports what they've done and what they'll do next is one of the most replaceable meetings. A structured written update — posted to a shared channel or document at a consistent time — takes 5 minutes to write and 2 minutes to read. It's also searchable and permanent, unlike a verbal report.

Cost comparison: A 30-minute standup with 8 people averaging $120,000/year costs about $230 per meeting or $12,000 per year. A daily written check-in costs $0 in meeting time and takes roughly 40 minutes total per day across the team (5 minutes each) versus 4 hours (30 minutes × 8 people simultaneously).

Document reviews

Walking through a document in a meeting is inefficient because reading speed varies widely. Some attendees finish each section in seconds while others need minutes, creating awkward pacing. Instead, share the document asynchronously with a deadline for written comments. Follow up with a short meeting only if comments reveal disagreements that need real-time resolution.

Simple decisions

Binary decisions (yes/no), decisions with a clear recommendation, or decisions where one person has authority don't need a meeting. Present the context and recommendation in writing, give stakeholders 24-48 hours to comment, and proceed unless someone raises a blocker.

Information sharing

Announcements, knowledge transfers, and demonstrations can be delivered via recorded video (tools like Loom or screen recordings), written posts, or documentation. This allows the audience to consume the information at their own pace, rewind and re-watch if needed, and skip content that isn't relevant to them.

Feedback collection

When you need input from a group — opinions on a design, reactions to a proposal, prioritization of a backlog — surveys, polls, and comment threads give everyone time to think before responding. This often produces more thoughtful input than on-the-spot reactions in a meeting, where the loudest voices tend to dominate.

Async Tools That Replace Meetings

The right tooling makes async communication seamless. Here are the categories of tools that most effectively replace meetings:

Lessons from Remote: Office Not Required

Few books have made a stronger case for asynchronous work than Remote: Office Not Required by Jason Fried and David Heinemeier Hansson, the founders of Basecamp (now 37signals). Published in 2013 — years before the pandemic forced the issue — the book argued that most office meetings exist because of habit, not necessity. Fried and Hansson describe how their fully distributed team replaced nearly all recurring meetings with written communication: long-form project pitches instead of brainstorming sessions, asynchronous check-ins instead of standups, and automatic-trust workflows instead of approval meetings. Their core insight is that "overlap hours" — a small window when everyone is online simultaneously — should be treated as a scarce, expensive resource reserved for genuine collaboration, not consumed by status updates.

Several techniques from the book translate directly into meeting cost savings. The authors advocate for a "library rules" culture where uninterrupted focus is the default, and any synchronous interruption (including a meeting) requires justification. They also recommend recording decisions and context in writing so that meetings don't become the only way institutional knowledge moves through a team. For organizations spending thousands per week on meetings — a figure you can verify with our meeting cost calculator — these practices can reclaim significant time and budget.

More than a decade later, the book remains one of the most practical guides to async-first work. If your team is struggling with meeting overload, it's a worthwhile starting point. Get Remote: Office Not Required on Amazon.

Meeting Fatigue: The Hidden Cost of Too Many Meetings

The financial cost of a meeting — salaries multiplied by time — is only part of the picture. Researchers at Stanford identified "Zoom fatigue" as a measurable phenomenon: excessive video calls cause cognitive overload from constant eye contact at close range, the unnatural experience of watching yourself on screen, reduced physical mobility, and the extra mental effort required to interpret non-verbal cues through a camera. A 2021 study published in the journal Technology, Mind, and Behavior confirmed that back-to-back video meetings increase stress and reduce the ability to focus and engage.

This matters for meeting cost calculations because fatigue compounds the expense. A $500 meeting doesn't just consume 60 minutes of salary — it can suppress productivity for the rest of the afternoon as attendees recover their focus. Teams that stack four or five meetings in a row are paying for those meetings twice: once in direct salary cost and again in the deep-work hours lost to mental exhaustion. Factoring in fatigue makes the case for replacing low-value meetings with async alternatives even stronger.

The Rise of Meeting-Free Days

A growing number of companies have adopted meeting-free days as a structural solution to meeting overload. In 2023, Shopify made headlines by cancelling all recurring meetings with more than two people and designating Wednesdays as entirely meeting-free. Asana, Atlassian, and Meta have implemented similar policies. Internal data from these companies consistently shows that employees report higher productivity, deeper focus, and lower stress on days without meetings. One MIT Sloan study found that companies reducing meetings by 40% saw a 71% increase in employee productivity.

Meeting-free days work because they create guaranteed blocks of uninterrupted time — the kind of time required for complex problem-solving, writing, and creative work. They also force teams to become better at asynchronous communication, since anything that would have been a Wednesday meeting now has to be handled via a document, message, or recorded video. For teams considering this approach, start with one meeting-free day per week, protect it aggressively, and measure the cost of the meetings you eliminate to build the case for expanding the policy.

The Hybrid Approach: Async-First with Intentional Sync

The most effective teams don't eliminate meetings entirely — they use a hybrid model where async is the default and meetings are intentional exceptions. This looks like:

  1. Default to writing. Any communication starts as a written message, document, or video. This forces clarity — if you can't write it down, you probably haven't thought it through.
  2. Escalate to sync when async stalls. If an async discussion goes three rounds without resolution, or if you notice tension building in text, switch to a meeting. Async is efficient for clear-cut topics but can be frustrating for ambiguous ones.
  3. Protect meeting slots for high-value interactions. Use your limited synchronous time for the things that truly benefit from real-time presence: creative collaboration, relationship building, and complex decision-making.
  4. Document sync outcomes asynchronously. After every meeting, post a summary with decisions made and action items assigned. This closes the loop for people who weren't in the meeting and creates a searchable record.

Companies like GitLab, Automattic, and Basecamp have built highly successful businesses on async-first cultures. Their experience shows that teams can be more productive, not less, when they reduce synchronous communication — provided they invest in the written communication skills and tooling to make async work well.

Making the Transition

Moving from a meeting-heavy culture to an async-first culture is a gradual process. Start with these steps:

See the cost of meetings you could replace with async

Open the Calculator

Related Reading