Asynchronous Communication: When to Work Async and How

When to use asynchronous communication instead of meetings, how to write messages that stand on their own, and the team norms that keep async from becoming always-on.

Collaboration Center · Last reviewed October 23, 2026 · 6 min read

Remote and hybrid teams quickly discover that recreating the office on video does not work well. A day of back-to-back calls leaves little time to do the work the calls were about, and a steady stream of chat pings makes it hard to finish anything that needs concentration.

Asynchronous communication, or "async," is the main alternative: people share information and make progress without needing to be online at the same moment. Done well, it protects focus time and helps teams that span schedules or time zones. Done carelessly, it slows decisions and leaves people out of the loop. This guide covers when async fits, when it doesn't, and how to make it work.

Synchronous vs. asynchronous, in plain terms

Synchronous communication happens in real time: meetings, phone calls, video calls and a quick back-and-forth in chat when both people are watching. Asynchronous communication lets each person respond when it suits their work: email, comments in a shared document, updates in a project tool, recorded video walkthroughs and threaded messages that nobody expects answered right away.

The tool does not decide which mode you are in; the expectation does. A chat message becomes synchronous the moment the sender expects an instant reply.

Why async matters: the cost of interruptions

An experiment by Gloria Mark, Daniela Gudith and Ulrich Klocke, presented at the CHI 2008 conference, had 48 participants complete an email-based work task while being interrupted by phone or instant message. Interrupted participants actually finished faster, with no difference in quality. The researchers concluded that people compensate by working faster, but "this comes at a price": more stress, higher frustration, time pressure and effort.

That is the case for async in one finding. Constant real-time demands may not show up as lower output right away, but they make the work harder on the people doing it. Batching questions and updates into channels that people check on their own schedule gives everyone longer stretches to think.

The trade-off: async can isolate teams

Async is not free. A 2021 study in Nature Human Behaviour by Longqi Yang and colleagues analyzed the emails, calendars, instant messages, calls and work hours of 61,182 U.S. Microsoft employees during the first half of 2020. Firm-wide remote work led to a decrease in synchronous communication and an increase in asynchronous communication, and the collaboration network became more static and siloed. The authors suggest these effects may make it harder for employees to acquire and share new information across the network.

The lesson is balance. Use async to protect focus and handle routine coordination, and deliberately keep some real-time contact, especially across team boundaries.

Deciding when to go async and when to meet

A simple rule of thumb: if the work needs fast back-and-forth, emotional nuance or shared discovery, meet. If it needs careful thought, a record or input from people on different schedules, go async.

Good candidates for async:

Status updates and progress reports.
Announcements and "for your information" news.
Reviewing a draft, design or plan, with comments in the document.
Decisions with clear options, where people need time to weigh in.
Questions that are not blocking anyone today.

Better handled live:

Sensitive conversations, such as feedback, performance or conflict.
Early brainstorming, when ideas build on each other quickly.
A discussion that has gone back and forth several times without resolution.
Urgent problems where minutes matter.
Getting to know new teammates.

A useful signal: if an async thread passes three or four rounds of replies without converging, switch to a short call, then post the outcome back in the thread so the record stays complete.

How to write async messages that work

Async depends on writing. Because the reader cannot interrupt to ask what you meant, each message has to stand on its own. The federal plain language guidance on Digital.gov recommends active voice because it "makes it clear who should do what," along with short sections and direct verbs. Those habits matter even more when a reply may be hours away.

A dependable structure for a request:

Context: one or two sentences on what this is about and why it matters.
The ask: exactly what you need, from whom.
The deadline: when you need it, and what happens if you don't get it.
Links: the document, ticket or data the reader needs, so they don't have to hunt.

For example, imagine a project lead posting: "We need to choose a print vendor for the spring catalog by Thursday at noon. I've compared three quotes in the linked sheet. Maria and Dev, please add a comment with your pick and any concerns. If I don't hear by Thursday, I'll go with the lowest quote." Anyone reading it later understands the decision, the options and the deadline.

Other habits that help:

One topic per thread, with a clear subject line.
Put the decision or summary at the top when a thread wraps up.
Record decisions in a shared place, such as a decision log in your project tool, so they don't disappear into chat history.
Prefer a short written summary or a brief recorded walkthrough over "let's hop on a call" for explaining something once to many people.

Set team norms so async doesn't become "always on"

Async only reduces pressure if people trust that a slower reply is acceptable. Agree on a few norms and write them down:

Expected response time per channel, for example same business day for chat, two business days for document reviews.
A clearly separate path for real emergencies, such as a phone call, so other channels can stay calm.
Core overlap hours, if any, when people are generally reachable for live conversation.
Where reference information lives, so questions get answered by documentation instead of interruptions.
Whether anyone is expected to respond outside working hours. Usually the answer should be no.

That last point has a legal side for hourly employees. The U.S. Department of Labor's Fact Sheet 22 states that "work not requested but suffered or permitted to be performed is work time." If a nonexempt employee answers messages after hours and the employer knows or has reason to know, that time generally counts as hours worked. Setting quiet hours protects people and keeps time records accurate.

Keep the meetings you have, but make them better

Async does not mean no meetings. It means meetings are reserved for what needs them. Send an agenda and any reading in advance so the meeting can go straight to discussion. Capture decisions and next steps in writing afterward and share them with anyone who could not attend. Over time, a team that runs this way usually finds that some recurring meetings, such as status check-ins, can move to written updates entirely.

Key takeaways

Async means communicating without expecting an immediate response; the expectation, not the tool, defines it.
In a CHI 2008 experiment, interruptions came with more stress, frustration and time pressure even when output held steady.
Research at Microsoft found that remote work shifted communication toward async and made networks more siloed, so keep some live contact.
Write async messages with context, a clear ask, a deadline and links.
Agree on response times, an emergency path and quiet hours, especially for hourly staff.

Sources

Spotted something out of date? Let us know.