Synchronous or Asynchronous: Choosing the Channel and Writing Clearly

The biggest source of fatigue and inefficiency in remote teams is not technology: it's the wrong choice of channel. We put in a meeting what should have been a message; we drown in chat what deserved a call; we wait for an immediate reply on something that could have waited. Communicating remotely means first deciding how to communicate.

Synchronous vs asynchronous

Two broad families of communication:

• Synchronous: everyone is present at the same time (video, call, meeting). Fast for deciding, discussing, building connection — but costly: you have to align calendars and mobilize everyone's attention at once.
• Asynchronous: each person contributes when they can (email, message, shared document, recorded video note). Slower, but respectful of focus time, traceable, and suited to different time zones.

The practical rule: asynchronous by default; synchronous only when real-time interaction adds real value (deciding, debating, feeling, connecting). This discipline drastically reduces the number of useless meetings.

Choosing the channel: a decision tree

graph TD
    A[I have something to communicate] --> B{Is it urgent?}
    B -->|Yes| C{Sensitive or emotional?}
    B -->|No| D{Need a real-time exchange?}
    C -->|Yes| E[Call or video]
    C -->|No| F[Direct message + mention]
    D -->|Yes| G[Short scheduled meeting]
    D -->|No| H[Clear async message or email]

Writing an async message that doesn't get lost

Async writing is the heart of remote work, and it's where everything plays out: a vague message generates ten clarification messages. A few principles for effective writing:

• The subject / first line states the essential. The reader should know in one line what it's about and what's expected of them.
• An explicit request. Specify the expected action and the deadline: "Can you approve X before Thursday noon?" rather than "Let me know what you think."
• Context first, detail second. Give the "why" before the "how."
• One message = one topic. Don't stack three requests in a single block.
• Visual structure helps. Short paragraphs, bold on the essentials, lists for steps.
• Tone compensates for the absent voice. In writing, neutral is often perceived as cold or curt. A courteous phrase, a warm word, sometimes an emoji suited to the team's culture, defuses misunderstandings.

The test of a good async message: the recipient can act without needing to reply to ask for clarification.

The "answer me right now" trap

Treating every async channel as if it were synchronous (expecting an immediate reply to an email, getting annoyed at an unread message after ten minutes) destroys everyone's focus. Setting clear timing expectations ("not urgent, by end of week") is part of good written communication.

What to say / what not to say

Practical exercise

Take the last three meetings you attended. For each, ask yourself honestly: could it have been a clear async message? For the ones where the answer is yes, draft the message that would have replaced it. You've just reclaimed time — and trained your judgment on channel choice.

Summary

Remotely, the first decision is the choice of channel. Synchronous (video, call) is for deciding, debating, handling emotion and building connection; asynchronous (message, email, document) is for informing, documenting and respecting focus. The rule: asynchronous by default, synchronous only when real time adds real value. A good async message states the essential in the first line, makes an explicit request with a deadline, handles a single topic, is visually structured, and tends to its tone. The success criterion: the recipient can act without having to ask for clarification.