Asynchronous communication: working without everyone being online

Asynchronous communication means people exchange information without being available at the same moment: a written message that can be read in an hour, a document that can be commented on tomorrow, a recorded walkthrough watched at a convenient time. It is the default in distributed teams and increasingly in teams that simply want fewer interruptions.

The common mistake is treating it as a tool choice. Adopting chat and expecting replies within minutes is synchronous work with worse ergonomics — all the interruption of a meeting, none of the resolution. The change that matters is behavioural, and it is mostly about how much you write.

What has to change

• Write in full. An async message needs the context, the question and what you need back — because the clarifying round trip costs hours rather than seconds.
• State the deadline and the default. I need an answer by Thursday; if I do not hear, I will proceed with option B. This single sentence removes most async stalling.
• Decisions go in writing, in a findable place. In a synchronous team the decision lives in people's memory of a meeting; async, it lives in the document or it did not happen.
• Nobody is expected to be instantly available. If that expectation survives, people simply watch chat all day and the interruption cost returns.
• One urgent channel that genuinely means urgent, and almost nothing routed to it. Without it, everything creeps back to instant.

Async replaces meetings with writing, and writing is slower for the sender and much faster for everybody else. That trade is the whole idea, and it is also why it feels worse to the person writing — the cost is visible and concentrated, the saving is invisible and distributed. Teams abandon async at precisely this point, usually without noticing that they abandoned it.

What should stay synchronous

Not everything benefits. Anything with strong feelings attached — difficult feedback, a disagreement that has already been misread once, anything about somebody's employment — belongs in a conversation, because text strips tone and people fill the gap with the least generous interpretation. Early creative work benefits from being live, since half-formed ideas are expensive to write and cheap to say. And a genuine emergency is synchronous by definition. The discipline is not making everything async; it is defaulting to async and choosing synchronous deliberately.

Making it work in practice

1. Set response-time expectations per channel, in writing, and honour them: chat within a day, email within two, urgent channel within an hour.
2. Use threads properly. A flat channel is not async — it is a meeting you have to attend continuously.
3. Record decisions in the document, not in the thread where they were made. Threads are conversations; documents are the record.
4. Overlap hours, if the team spans time zones — even two shared hours a day removes most of the friction, and specifying them is kinder than pretending anyone is always available.
5. Write the update rather than holding the status meeting. A short written update read by six people costs less than the meeting and produces a record.

Where it lives

Ettex Chat carries the conversation and Ettex Docs holds the decisions and the longer writing that async depends on — the split matters, because a decision recorded only in a chat thread is a decision nobody will find. The tooling question generally is covered in internal communication tools, and the policy side in remote work policy.

Being direct: no tool makes a team asynchronous. What tools do is make the written record findable; the behaviour — writing in full, stating deadlines, not expecting instant replies — is an agreement, and it is the part that actually fails.