Asynchronous communication norms for distributed teams

What it is

Asynchronous communication, as the Twist guide (cited) defines it, is sending a message without expecting an immediate response. Norms for it are a short written agreement covering four things: which channel carries which kind of message, the expected reply window per channel, what may interrupt someone and how, and where the outcome of a discussion is recorded. Basecamp's internal guide (cited) states the underlying stance: real-time sometimes, asynchronous most of the time; writing solidifies, chat dissolves; speaking helps only who is in the room, writing helps everyone, including people who join later.

Why it matters

A distributed team has no shared office hours. Without norms, the fastest channel wins by default, every message becomes an interruption, decisions are made by whoever was awake, and the record of why something was decided lives in a chat scroll that nobody can search a year later. The same applies to automated agents that read a team's history: what was written down completely is what they can use.

How to apply

• Publish a channel table: decisions and proposals go in a document or issue; questions that can wait go in a thread; only production incidents may page. Say for each channel how quickly a reply is expected, for example within one working day for threads.
• Lead with the ask. The first line names what is needed, from whom, by when; context and links follow. A greeting with the question in a later message costs a round trip across time zones.
• Make each message self-contained: link the document, quote the relevant line, state what was already tried. The reader should not need to ask "which one?".
• Give discussions time, as the Basecamp guide argues; set a decision date instead of demanding immediate replies, and close the thread with the decision written where the work is tracked, not in the chat.
• Meetings need an agenda and produce notes; people who were absent read the notes and can still object within a stated window.
• Publish working hours and hand-over notes at the end of a day so the next time zone can continue.

Pitfalls

Asynchronous as an excuse for silence: reply windows must be honoured. Everything to everyone: broadcasts train readers to ignore the channel. Decisions in direct messages that never reach the record. Tool sprawl that makes the channel table longer than anyone remembers.