asynchronous communication
Also called: async communication, async work
Work communication that doesn't need people to be present at the same time: written updates, comments, recorded explanations. It suits teams across time zones and outages, and works when messages are complete enough to act on without a follow-up call.
Asynchronous communication is work communication that doesn't need people to be present at the same time: written updates, ticket comments, shared documents, recorded walkthroughs. The opposite, synchronous communication, is a call, a meeting or a chat that expects a reply now.
For teams spread across time zones, shifts and unreliable power or connection, async is the sensible default, and calls are for what really needs back-and-forth. Two questions pick the channel: how urgent is it, and does it need a conversation? Urgent and tangled: a call. Urgent and simple: a tagged message in the team chat. Not urgent: the ticket thread or a written update.
Async works only with a few habits. A message must be complete enough to act on without a follow-up: context, what you tried, what you need, and by when. Each channel needs an agreed response time, so "async" doesn't turn into "whenever". And people need quiet hours: a message sent at night is fine, a reply expected at night is not. Many status rounds and announcements can move from a meeting to a written update, which frees the meeting for decisions and blockers.
Example
Klasna's Support team works from Kyiv, Lviv and abroad; two coordinators are two hours behind Kyiv, so a 09:00 stand-up starts at 07:00 for them. The lead audits two weeks of the daily stand-up (seven people, 10 working days):
The working: 298 + 89 = 387; 387 / 900 = 43.00%. With seven people in the room, the written-up part costs 387 × 7 = 2,709 person-minutes, or about 22.58 person-hours a week (2,709 / 60 / 2), before anyone spends a few minutes reading it.
The async version: each coordinator posts a three-line status in the team thread by 8:45 Kyiv time (or the evening before), announcements go into a weekly written update, and the call keeps the blockers. One complete message replaces a late-night chain of "hi", "got a sec?": "Family X, refund for 3 lessons lost to a tutor no-show. Policy covers 2. Can I approve the third? Tomorrow 10:00 is fine."
Common mistakes
- Bare messages. "Hi" or "got a sec?" forces a round trip; write the context, the ask and the deadline in one message.
- Async as "whenever". Without agreed response times per channel, a family's question can wait two days in a thread.
- Expecting replies outside someone's shift. Send or schedule messages any time; expect answers during working hours.
- Leaving inconvenient hours to the same people. Rotate early and late slots across time zones.
- Putting conflict or bad news about a person in writing first. Hard conversations go to a call or a one-to-one; the written summary comes after.
Learn it in the course
- Channels and async work · When to talk live and when to write, messages people can act on, time zones and outages, and what to hand to a tool.
- Case: the 90-minute stand-up · Two weeks of meeting-audit data show where the daily stand-up's 90 minutes go. Redesign it for a team across two time zones.