Async-first for small teams: what changes, what breaks, what to write down
"Async-first" has moved from a remote-work niche into mainstream advice. The idea is simple: default to written, asynchronous communication, and use live meetings only when they genuinely help. Companies like GitLab have documented their async practices publicly in the GitLab Handbook, and many small remote and hybrid teams have followed.
Async-first can give small teams more focus time and fewer interruptions. It can also slow everything down if it is adopted as "nobody talks anymore".
What changes
- Default channel: written updates, documents and comments instead of calls
- Response expectations: hours, not minutes, for most things
- Meetings: fewer, shorter, with a clear purpose
- Documentation: decisions and status written down where everyone can find them
What breaks if you are not careful
Decisions slow down. A decision that took five minutes on a call can take three days of back-and-forth messages. Fix: name a decision owner and a deadline for input.
Context gets lost. Information scattered across chat threads is as bad as information in someone's head. Fix: one place for status, one for decisions.
Waiting becomes invisible. In async teams, more work waits on someone else's reply. If nobody tracks that waiting, things stall quietly. Fix: make waiting a visible state, with a name and a date.
People feel isolated. Fix: keep some synchronous time for connection, not status.
What to write down
- What each person is working on, visible without asking
- What is waiting, on whom, and since when
- Decisions, with the reasoning and the date
- How the team works: response times, what counts as urgent, when to call
Async status without a meeting
The weekly status meeting is the easiest meeting to replace, if the status is visible somewhere. A board where every action shows who has the ball does most of the job. In Axtio, projects are rows and columns are Mine, Other, Next Steps and Done; anything waiting on someone else shows how long it has waited and gets flagged after a week. Teammates in different time zones can open the board and see exactly where things stand. See how to run async standups and kanban for remote teams.
When to go synchronous
- Conflict or sensitive conversations
- Brainstorming early ideas
- Decisions stuck after two rounds of written discussion
- Onboarding new people
- Celebrating
Async-first is not async-only. It is a default, with deliberate exceptions.
See remote work has settled and meeting-free days.