The short answer
Asynchronous working means people can contribute without responding at the same moment. It depends on written context, clear ownership, accessible decisions and agreed response times. An async culture is not a rule against meetings. It is an agreement about which work can progress independently, when a real-time conversation helps and how urgent issues are escalated.
Asynchronous versus synchronous work
| Situation | Useful asynchronous approach | When to switch to a live conversation |
|---|---|---|
| Routine update | A short written update with blockers and next steps | A blocker needs a fast shared decision |
| Proposal | A document with the recommendation and response deadline | The group is interpreting the problem differently |
| Handoff | A record of status, owner and the next action | An unresolved exception puts the deadline at risk |
| Feedback | Clear comments on a piece of work | The topic is sensitive or needs a two-way discussion |
| Incident | A written record alongside the response | Immediate coordination is needed |
Choose the format around the task. Sending a vague message and waiting longer for a reply does not make a process asynchronous; it simply delays the clarification.
Six rules for an async team agreement
- Put the context with the request: explain the problem, evidence and decision needed.
- Name one owner for moving the work to the next step.
- Give a response window in a shared time zone or with an explicit deadline.
- Keep the decision in an accessible record rather than only in a chat thread.
- Define an urgent route and what qualifies for it.
- Use live discussion when it resolves uncertainty faster, then record the outcome.
Ask the team where work most often waits. Write the agreement around those moments. You may need different response windows for a customer incident, a weekly report and a proposal that needs considered review.
An asynchronous request template
| Field | What to include |
|---|---|
| Context | The situation and why it matters |
| Decision or action | The specific response you need |
| Recommendation | Your proposed next step and its reasoning |
| Evidence | Links to the relevant source material |
| Owner and deadline | Who moves it forward and when a response is needed |
| Escalation | What happens if the deadline or situation changes |
| Decision record | Where the final outcome will be written |
Write enough for a colleague to respond without asking for a meeting to establish the basics. Keep optional background separate from the information needed to make the decision.
Example: a handoff across time zones
A colleague finishes a vendor evaluation before another colleague begins their working day. The handoff includes the comparison document, two unresolved questions, a recommendation and a deadline for a decision. The next person can check the evidence and respond without waiting for an overlap meeting.
If the second colleague finds a material contradiction, they use the agreed escalation route. After a short live conversation, the decision owner updates the shared record. The process combines independent work with real-time discussion where it adds value.
Which meetings should stay?
Keep a meeting when the work requires rapid interaction, a sensitive conversation, relationship building or exploration that is difficult to handle through written comments. Give the meeting a clear purpose and let people prepare with the relevant context.
Afterwards, write down the decision, owner and next action. Colleagues who were not present should be able to understand the result without watching a recording of the entire discussion. A written outcome is often more useful than a large recording archive.
How to introduce asynchronous working
Choose one recurring workflow, such as a weekly update or an approval request. Record how long it currently waits and where clarification is needed. Agree a template, response window and owner, then test it for a few cycles before extending the approach.
Review the clarity of decisions, unresolved questions and the amount of after-hours checking. If people feel they must monitor messages continuously, the boundaries are not working. GitLab’s public handbook offers an example of a company documenting asynchronous communication practices; adapt principles to your own work rather than copying another company’s operating model.
Common questions
Does asynchronous working mean no meetings?
No. It means the team does not require simultaneous availability for every task. Use meetings for work that benefits from immediate interaction, then record the result so other colleagues can continue independently.
How do we handle urgent work in an async team?
Define what counts as urgent, which channel reaches the responsible person and who provides backup. Keep the urgent route distinct from routine updates so employees do not have to treat every message as an interruption.
Which tools are needed for an async culture?
Start with an accessible place for documents, tasks and decisions plus a clear communication agreement. More tools will not solve unclear ownership or missing context. Improve the workflow before expanding the software stack.