What asynchronous means
Asynchronous communication is any exchange where the people involved do not need to be present at the same moment. You write a message, record a clip or leave a comment, and the other person responds when they are ready. Email is the classic example, and so are comments on a shared file or a note left on a task.
The opposite is synchronous communication: a phone call, a live video call or a rapid chat conversation where both sides are expected to respond right away. Most working days use a mix of both. The useful question is which one fits a particular job.
Why teams choose it
Async tends to be attractive for a few reasons.
- Different schedules. When colleagues are in different time zones or keep different hours, waiting for everyone to be online at once is slow and tiring.
- Protected concentration. A message that can wait does not break someone’s train of thought.
- A written record. Decisions and reasoning sit in one place, so people who join later can catch up.
- More thoughtful replies. People have time to think before answering, which can lead to better answers, particularly for those who do not like speaking up on the spot.
It is not automatically better, though. Async can feel slow when a question genuinely is urgent, and a long thread can grow confusing.
Writing a message that works on its own
The core skill is writing something the reader can act on without asking you anything. Before sending, imagine the reader opening it hours later with no background.
A simple structure helps:
- The point first. Say what you need or what has changed in the opening line.
- Context. Give only the background needed to understand the point.
- The ask. State exactly what you want, whether it is a decision, feedback or just awareness.
- A deadline, if there is one. “By Thursday afternoon” is clearer than “soon.”
- Links or attachments. Include what the reader needs, so they do not have to search for it.
Compare two versions of the same message. The first: “Can we talk about the schedule?” The second: “The delivery date may slip by a week because the review took longer than planned. I would like to either move the launch or drop one feature. Could you tell me which you prefer by Wednesday? Details are in the attached notes.” The second can be answered in one line without a call.
Setting expectations for replies
Async only works when people agree how fast replies are expected. Without that, some people wait anxiously and others feel pressured to answer instantly, which defeats the point. Teams often settle on something like “within one working day for normal messages” and a separate way to flag something urgent. The exact timing matters less than everyone knowing it. Good online etiquette includes respecting those expectations rather than following up after an hour.
Choosing where messages go also matters. Using sensible communication channels, such as a team chat for quick notes and email or a longer document for detailed matters, keeps important items from getting buried.
Keeping discussions from sprawling
Written threads can become tangled. A few habits keep them readable:
- Keep one topic per thread.
- Name the decision-maker so the discussion can end.
- Summarize the outcome at the end in a sentence or two.
- Move to shared documents when a discussion needs several people editing a single draft.
- Write a clear subject or opening line so people can tell whether a message concerns them.
Short, regular status updates are a natural async habit. They replace many “where are we on this?” interruptions.
When a live call is better
Async is not a rule to follow at all costs. A live conversation often works better when:
- The topic is sensitive or emotional, and tone is easily misread in text.
- There is real disagreement that written exchanges are not resolving.
- You are brainstorming and need quick back-and-forth.
- A written discussion has gone through several rounds without progress.
- Someone is new and building relationships.
A reasonable pattern is to try writing first and escalate to a call if confusion remains. When you do call, keep the meeting short, set an agenda and follow with a written summary so that the people who were absent are included. Planning well-run video meetings helps keep those live moments useful.
Common pitfalls
Too little detail. Messages that force a string of clarifying questions are slower than a call.
Too much detail. A wall of text hides the request. Put the key point at the top.
Silence. If someone never acknowledges messages, work stalls. A quick “got it, will reply tomorrow” avoids uncertainty.
Notification pressure. If every message triggers a ping, the benefits of async disappear. Muting alerts outside agreed hours and managing notification overload makes it genuinely calmer.
A small way to start
If your team mostly relies on live calls, you do not need to change everything. Pick one recurring meeting that mainly shares information and try replacing it with a written update for a few weeks. Ask people afterward whether anything was lost. Results vary by team and by type of work, so adjust based on what you observe rather than on a fixed rule.