How async-first teams actually work

Every distributed team says it is asynchronous. Very few are. The difference is not the calendar — it is what happens to a decision between someone thinking of it and it being made.

The written default

In an async-first team, the first move is always to write. A question becomes a document with context, options and a recommendation. People respond in threads over hours, not in a meeting over thirty minutes.

This feels slower at first and is dramatically faster in aggregate, because the context survives. Six months later the reasoning is still there, and the person who joined last week can read it.

Meetings have a narrow job

Async teams still meet. They meet for things that genuinely need live conversation: conflict, negotiation, brainstorming where the energy matters, and relationships.

What they stop doing is using meetings to broadcast information. If the purpose of a meeting could be served by a document that people read first, the meeting is a sign the document was never written.

Decision rights are explicit

A distributed team cannot rely on who was in the room. Every significant decision has a named owner, a deadline and a place where the outcome is recorded. Anyone can disagree in the thread; once a decision is made, it is written down and it stands until someone reopens it with an argument.

This is the part that most new joiners underestimate. In an async team, silence in a discussion means agreement, not absence. If you have a view, you have to write it before the deadline.

Response windows instead of replies

Nobody is expected to answer instantly. Most async-first teams publish a response expectation — often within one working day — and treat any faster behaviour as a bonus, not a norm.

That expectation is what makes deep work possible. It also means that urgency has to be signalled explicitly, which is why good async teams have a separate channel or tag for things that genuinely cannot wait.

How to tell if it is real

Ask four questions of any team that claims to be async-first:

• Where would I find the decision about the last significant change?
• What is the expected response time to a message?
• Which meetings are mandatory, and what happens in them?
• When was the last time a meeting was cancelled in favour of a document?

If they can answer all four without hesitating, the culture is real. If the answers are principles rather than facts, it is a distributed team with a long calendar.

What it asks of you

Async work rewards people who write clearly, decide without permission, and follow through without being chased. It punishes people who need to be in the room to feel informed.

If that trade sounds good, ask about it explicitly in your interviews. The best signal is whether the person answering reaches for examples — a specific document, a specific decision, a specific disagreement resolved in writing.