What asynchronous means in practice
Working asynchronously means that people do not need to respond at the same moment. A message is sent, and the recipient answers when their working hours begin or when they finish their current task. This is the opposite of synchronous communication, such as a live call or a quick back-and-forth that requires both people to be online together.
For teams whose members live in different time zones, asynchronous habits are often the only realistic option. If two colleagues have few or no overlapping working hours, waiting for each other to be online can add a full day to every exchange. The aim of good habits is to reduce those round trips, so that work continues without anyone being on call around the clock.
Make each message complete
The biggest source of delay is a message that cannot be acted on. Suppose a colleague in one region writes, “Can you check the report?” and then goes offline. The recipient has to ask which report, what to check and by when, and each question costs another day.
A complete message usually answers:
- What is the request or the information?
- Why does it matter, and what is it for?
- What does a finished answer look like?
- When is it needed, in a time zone everyone can understand?
- Where are the relevant files or links?
Writing this way takes more effort up front but saves the wait. The principles of message clarity apply even more strongly when a reply may be a day away. It can help to anticipate the most likely follow-up question and answer it in advance.
Also think about wording on times. “Tomorrow morning” depends on whose morning. Name the date and the time zone, or say “by the end of your day”.
Write down handoffs
When one person finishes for the day and another begins, a short written handoff keeps work flowing. Teams often use a regular post, or a note in a tracker, covering:
- What was done.
- What is blocked and why.
- What the next person should do first.
- Anything urgent or risky to watch.
This also avoids relying on memory or on one person who knows everything. Over time, the written trail becomes a useful record. Where discussions end in agreements, make them easy to find; the guidance on decision records applies strongly in distributed teams, because colleagues who were asleep cannot ask what happened.
Use the right tool for the question
Not everything fits in chat. Quick questions and updates suit chat, while complex topics may be better as a short document or a recorded explanation that people can read or watch at their convenience. Live calls are best saved for discussions that need real-time exchange, such as sensitive feedback or a tangled disagreement. A simple way to choose is explained in the guide to communication choice.
Voice notes and short recordings can add warmth and nuance without requiring simultaneous presence, though not everyone likes them, and they are harder to search. Some teams find that voice messages work well for explanations that would take a long time to type, provided there is a written summary too.
Agree on overlap and availability
Asynchronous does not mean never speaking live. Many teams find a small overlap window useful, perhaps an hour or two when most people are available, for questions that benefit from conversation. Where there is no overlap at all, one or two flexible meetings a month may be worthwhile, rotating the inconvenient hours.
Share working hours openly:
- Put time zone and typical hours in profiles or a shared team page.
- Use status messages for time off and focus periods.
- State response expectations in the team’s chat policy, for example that replies come within one working day of the recipient.
- Agree what counts as urgent and how to reach someone in a true emergency.
Fairness matters. If one region always has to join meetings very early or very late, resentment tends to build. Rotating the awkward times, or recording meetings and sharing notes so that people can contribute in writing, spreads the burden. Tools that show each person’s local time can prevent accidental scheduling errors.
Protect people’s off hours
Because the chat tool is always open somewhere in the world, it is easy to send messages at any hour. The sender’s convenient time may be the recipient’s middle of the night. A few courtesies help:
- Schedule messages to send at the start of the recipient’s working day, if the tool supports it.
- Do not expect a reply outside someone’s normal hours.
- Respect quiet hours and do-not-disturb settings; see the advice on handling notification overload.
- Avoid using mentions at times when they will trigger alerts for people who are asleep, unless it is urgent.
Leaders set the example. If a manager is seen replying at all hours, others may feel they must, even if no one asked.
Build trust and connection
Distributed work carries a risk of isolation. Long delays and text-only communication can create distance, and misunderstandings are easier when you cannot see someone’s face; see the discussion of written tone. Ways to keep a sense of connection include:
- A casual channel for non-work conversation.
- Short, friendly check-ins in addition to task messages.
- Occasional live sessions that are optional, with notes shared afterward.
- Thanking people explicitly in writing.
- Careful attention to newcomers, who may feel adrift; the guidance on team onboarding covers this.
Also be generous when reading replies. A late answer is typically a sign of a different clock, not of neglect.
Watch for the downsides
Asynchronous work is not a cure-all. It can slow down urgent decisions, hide confusion for a long time, and lead to long written threads that few people read. Some tasks, such as brainstorming, may be easier together in real time. Teams usually find a mix that suits them, and revisit it as members and projects change. If it is not working, ask the team what is slowing them down, and adjust.
For people who work across languages and borders, simple wording helps too; the points raised for cross-border messaging are relevant, particularly the value of plain, unambiguous sentences.