Async-First Is an Accessibility Feature

Defaulting to async is how distributed teams stop punishing different nervous systems.

Defaulting to async is how distributed teams stop punishing different nervous systems. The synchronous meeting assumes a body that can context-switch on demand, parse spoken language in real time, mask its affect under social pressure, and recall decisions made out loud with no written record. That body is a minority of bodies. The rest of us have been quietly compensating for an interface that was never designed with us in mind.

The first time I noticed how much the office was costing me, I was on a video call where five people debated the same architectural question for forty minutes, reached a decision I could not have repeated under oath, and then asked me to ship the work. I asked, that evening, whether anyone could send the decision in writing. No one had taken notes. The decision lived in five different heads, in five subtly different shapes. By the end of the week it had drifted into a sixth shape, in mine.

What synchronous defaults actually assume

The synchronous meeting assumes that the cost of participation is uniform. It is not. For people with AuDHD, sensory processing differences, anxiety, hearing impairment, English as a second language, caregiving responsibilities, or simply a different time zone, the cost of being ‘on’ for a one-hour call is enormous compared to the cost of writing the same content out in a doc. The output looks similar. The input cost is wildly different. Sync-first teams optimize for the wrong axis.

It also assumes that the loudest voice in the room is the best signal in the room. Often it is not. The strongest engineer on the team may be the one who needed forty-five minutes and a quiet kitchen to formulate the objection that would have saved the project. They do not get those forty-five minutes in a meeting. The decision ships without their input. The org calls this ‘velocity’ and is surprised when it has to be reversed three sprints later.

Async-first as legible decision-making

Async-first writes the meeting down. The decision exists in a document. The reasoning exists in a thread. The dissent exists in a comment with a timestamp and a name attached to it. Six months later, when someone asks why the system looks the way it does, the answer is retrievable in twenty seconds instead of being reconstructed from competing memories of who said what in a room that has since dispersed.

This is not a tooling problem. Notion, Linear, GitHub discussions, Loom, Slack channels with permalinks — the substrate has been adequate for years. The blocker is cultural. Teams default to meetings because meetings feel productive in real time. They are mostly productive in the way that pacing the floor feels productive: motion confused with progress. The first weeks of an async-first transition feel slower because they are honest about how slow synchronous thinking actually was.

The accessibility frame is the load-bearing one

When I call async-first an accessibility feature, I do not mean it as a compliance argument. I mean it as systems design. The teams that succeed with neurodivergent contributors, contributors across time zones, parents on the second shift of childcare, and engineers who do their best thinking before 7am are the teams that already had to write things down. They did not retrofit access. They built the substrate that made access incidental.

It is the same pattern as captioning. Captions were added for the Deaf and hard-of-hearing community. The benefit cascaded — second-language viewers, viewers in loud environments, viewers who want to watch while a baby naps, search indexers that can now find a moment inside a video. The accommodation became the affordance. Async-first is captions for collaboration.

What async-first is not

Async-first is not slow. Decisions can still close in hours when the question is well-formed. Async-first is not no meetings. Meetings still happen — for synchronous decisions that genuinely require a real-time conversation, for relationship-building, for the rare crisis where parallel writing would be too slow. Async-first is not asocial. The teams that do it well often have richer social rituals because they are no longer using calendar slots to manufacture connection.

What async-first refuses is the assumption that being in a meeting is the proof of work. It demands an artifact instead — a document, a PR, a decision log, something a reader can audit. The artifact is the deliverable. The meeting, if there even was one, is a side effect.

How async-first fails when it fails

Async fails when teams treat it as a license to write less, not more. The whole substrate depends on writing — clear, well-structured, generous-with-context writing. A team that goes async and writes one-liners has just made themselves less legible than they were when they spoke out loud. The cost moves from real-time participation to opaque writing, which is worse, because at least the meeting had a witness.

Async also fails when there is no decision protocol. Documents pile up. Comments pile up on documents. Nothing gets closed. The team feels busy and ships nothing. The fix is not to return to meetings. The fix is to add a small piece of governance — every thread has an owner, a deadline, and a clear definition of done. The accessibility feature still works. It just needs the rails.

What changes when you build this way

The team that can think on paper together is the team that can include people who think differently. It is also the team that can hire across continents without optimizing for who can stomach the most calls. It is the team whose institutional memory survives turnover, because the reasoning is in the substrate and not in the heads of the people who happen to still work there.

These are not soft benefits. They are recruitment, retention, and operational continuity. The case for async-first is not ‘be kind to your colleagues.’ It is: design the team for the bodies and minds and time zones you actually have, instead of the imaginary uniform participant the meeting culture was built around.

Treat async as the accessibility feature it is. The team that writes down its thinking is the team that gets to keep its thinking. Everyone benefits — the people the meeting was already failing, and the people the meeting was working for who never knew the alternative existed. // JV, from the orchid dark.