How do you replace meetings with async communication?

Replace status update meetings with written standup posts (3 bullets: what I did, what I am doing, blockers). Replace brainstorms with shared documents where people contribute on their own schedule. Replace 1-on-1 check-ins with weekly written updates plus a monthly video call. Keep only meetings that require real-time discussion: complex decisions, conflict resolution, and relationship building. In my experience, this eliminates 70 to 80% of recurring meetings.

What tools work best for async communication?

Slack or Teams for quick async messages (treat as async, not instant messaging). Notion or Confluence for documentation and decision records. Loom for async video updates that replace meetings. Linear or Asana for project tracking. The tool matters less than the norm: the team must agree that async is the default and synchronous meetings are the exception.

Do async teams communicate less than teams that meet constantly?

No. They communicate more, but differently. Async teams produce more written documentation, more structured updates, and more searchable records. The communication is higher quality because people think before writing instead of speaking off the cuff in a meeting. The tradeoff is that spontaneous conversation happens less, which is why the best async teams still schedule 2 to 3 hours per week of synchronous social time.

I Replaced 80% of My Meetings With Async Updates. Here Is Exactly How.

At my second remote company, I spent 28 hours per week in meetings. Twenty-eight. Out of a 40 hour work week.

I was in daily standups, weekly team syncs, biweekly sprint reviews, monthly all-hands, 1-on-1s with my manager, 1-on-1s with my reports, cross-functional alignment meetings, project kick-offs, project retrospectives, and something called a "vibe check" that I still do not fully understand.

Every meeting was on Zoom. Every meeting could have been a message, a document, or a short video.

When I moved to my third company (a fully distributed team across 13 countries), they did not have a single recurring meeting on the calendar. Zero. Everything was async by default. Meetings happened only when someone explicitly requested one and could articulate why async would not work.

I was skeptical. I thought it would be chaos. It was the most productive I have ever been.

Over the next two years, I refined their system and brought elements of it to my current company. Here is exactly what I did.

The Async Audit: Categorizing Your Meetings

Before eliminating anything, I categorized every recurring meeting by purpose. Every meeting falls into one of four categories:

Status updates. "What are you working on? What did you finish? Any blockers?" This is information transfer. It does not require real-time discussion. It requires a shared format for reporting progress.

Brainstorms and input sessions. "We need ideas for X" or "What do people think about Y?" This feels like it needs a meeting, but in practice, people think better when they have time to consider. Real-time brainstorms favor the loudest voices, not the best ideas.

Decision meetings. "We need to decide between A and B, and there are legitimate disagreements." This actually benefits from real-time discussion. Nuance, tone, and the ability to build on each other's arguments matter here.

Relationship and culture. Team bonding, 1-on-1 rapport, casual connection. This is the human glue that keeps remote teams from becoming transactional. It needs to be synchronous because human connection requires presence.

After auditing my calendar, I found that roughly 80% of my meetings were in the first two categories. Status updates and brainstorms. Both of which work better async.

What Replaced Each Meeting Type

Daily Standups became Written Posts

The daily standup is the most common meeting in remote work and the most wasteful. Fifteen minutes times ten people is 2.5 hours of collective time per day, spent listening to updates that are relevant to maybe two of the ten people.

I replaced it with a written standup in Slack, posted by each team member before 10 AM in their local timezone. Three bullets:

What I completed since last update
What I am working on today
Blockers (if any)

A thread under each post for questions. No meeting. No Zoom. No fifteen minutes of everyone sitting on mute while one person talks.

The result: updates that people can read in 2 minutes instead of 15. A searchable record of what everyone did. And people who are blocked get help faster because the blocker is visible the moment it is posted, not at the next day's standup.

Weekly Team Syncs became Shared Documents

The weekly team sync was 60 minutes of going around the room (screen) and sharing what each person was working on. It was the daily standup but longer and less frequent.

I replaced it with a weekly written summary document. Each team member adds their section by end of day Friday. It contains: accomplishments this week, priorities next week, decisions needed, and one thing I learned. The document is shared Monday morning. Comments and questions happen in the document itself.

Total time investment: 15 minutes per person to write their section, 10 minutes per person to read everyone else's. Compare that to 60 minutes in a meeting where you are actively listening for maybe 10 of those minutes.

Brainstorms became Async Contribution Windows

This was the hardest shift. People love brainstorm meetings because they feel collaborative and energizing.

But here is what actually happens in a brainstorm meeting: 2 or 3 people dominate the conversation. The introverts stay quiet. The person in the most inconvenient timezone is half asleep. And the ideas that surface are the ones that sound good in the moment, not the ones that survive scrutiny.

I replaced brainstorms with a 48-hour async contribution window. Someone creates a document describing the problem and opens it for input. Team members add their ideas, comments, and questions over two days. Then, if needed, we hold a 30-minute synchronous meeting to discuss the top ideas and make a decision.

The quality of ideas improved dramatically. People had time to think. Introverts contributed equally. And the synchronous meeting (when it happened) was focused on evaluating ideas, not generating them.

1-on-1s became Written Updates Plus Monthly Video

This is the one people push back on most. "You cannot replace 1-on-1s. The relationship is too important."

I agree that the relationship is important. I disagree that a weekly 30-minute Zoom call is the best way to maintain it.

What I do now: my reports send me a written weekly update (wins, challenges, things they need from me, career thoughts). I respond in writing within 24 hours. Once a month, we do a 45-minute video call focused entirely on career development, feedback, and the human stuff that writing does not capture.

The weekly written updates are actually more honest than face-to-face check-ins. People write things they would not say out loud. "I am frustrated with X project." "I feel stuck on Y." The written format gives them space to be candid without the social pressure of a video call.

What I Kept as Synchronous

Not everything went async. I kept three types of meetings:

Complex decisions with genuine disagreement. When the team is split on a direction and the tradeoffs are nuanced, a real-time conversation lets people build on each other's arguments and read emotional signals. Async decision-making works when there is rough consensus. It breaks down when there is genuine conflict.

Conflict resolution. If two people are at odds, async communication makes it worse. Written words lack tone. Messages get misread. Tensions escalate. Conflicts need voice-to-voice (or face-to-face) resolution.

Social connection. I schedule 2 hours per week of purely social synchronous time. No agenda. No work topics. Virtual coffee, games, casual conversation. This is non-negotiable. Without it, remote teams become transactional and people feel isolated.

The Results After 2 Years

After running this system for two years across two companies:

My meeting load dropped from 28 hours per week to 6. Those 6 hours include: 2 hours of social time, 2 hours of decision meetings, 1 hour of 1-on-1 video (rotated monthly across reports), and 1 hour of buffer for ad-hoc requests.

The remaining 22 hours went back to actual work. Deep work. The kind of focused, uninterrupted time that remote work is supposed to enable but rarely does when your calendar looks like a Tetris game.

Team output increased. Not because people worked more hours, but because they had uninterrupted blocks to think, build, and write. The quality of decisions improved because people had time to consider options before discussing them.

Documentation quality skyrocketed. When async is the default, everything gets written down. Decisions are documented. Context is captured. New team members can onboard by reading the archive instead of sitting through weeks of "shadow these meetings."

The Tool Stack

The tools matter less than the norms, but here is what works for me:

Slack for quick async messages. Key norm: nobody is expected to respond within minutes. Response time expectation is 4 hours during working hours. Urgent matters get a phone call, not a Slack message.

Notion for documentation, decision records, weekly updates, and brainstorm contribution windows. Everything searchable. Everything linked.

Loom for anything that needs visual explanation. Instead of scheduling a meeting to walk someone through a design or a dashboard, I record a 5-minute Loom and share it. They watch it when convenient, respond async.

Linear for project tracking. Async task management where the status of every project is visible without asking anyone.

The Hard Part Nobody Mentions

The hardest part of going async is not the tools or the process. It is the cultural shift.

People are addicted to meetings. Not because meetings are productive, but because meetings feel like work. Sitting in a meeting for an hour feels busy. It feels collaborative. It feels like something is happening.

Async work does not feel that way. Writing a document in silence does not feel collaborative even when it is. Reading someone's update instead of hearing them say it does not feel connected even when the information transfer is better.

The cultural shift requires leadership buy-in. If the manager still schedules meetings for everything, the team will never go async. It has to start from the top.

I pushed this transition by leading with data. I tracked my team's output before and after reducing meetings by 75%. When the numbers showed higher output, faster decisions, and better documentation, the skeptics came around.

The Connection to Job Search

If you are searching for a remote role right now, here is why this matters: remote companies that run on async are fundamentally better places to work than remote companies that run on Zoom.

When you evaluate a remote company (I wrote a full guide on how to do this), ask about their meeting culture. If the answer is "we try to keep meetings minimal," that is aspirational. If the answer is "we have no recurring meetings and here is our async playbook," that is operational.

The difference determines whether your remote job gives you freedom or just replaces a commute with a camera.

And if you are applying to multiple remote roles, every application needs to demonstrate that you understand async work. Your resume should mention documentation, written communication, and async tools. Your cover letter should reference distributed team experience. Submix can help here: it reads the job description and generates a tailored resume that mirrors the posting's language, including remote-specific terms like "async," "distributed," and the specific tools the team uses. You review and submit. The tailoring is what gets you past the ATS and in front of a human who cares about remote readiness.