Remote work is a location policy. Async-first is a documentation discipline: the operating model that determines whether distributed teams produce coherent output or just synchronized chaos. In UC Irvine field research, interrupted work was resumed 23 minutes and 15 seconds later on average.
Remote work answers the question of where. Async-first answers the question of how. Treating them as interchangeable is the reason most distributed teams end up with the inconveniences of remote work and none of the productivity advantages.
A fully co-located team can be async-first. A fully distributed team can be synchronous-by-default, just with longer lag times and more Zoom fatigue. The operating model and the location policy are separate levers, and conflating them produces neither effective in-person collaboration nor effective distributed work.
The short version: async-first means the written record is the default place where work happens: proposals, decisions, status and handoffs are written first, and meetings are kept for the conversations that truly need people at the same time. You can be async-first in one office or across six time zones. Interruptions are the cost it cuts: Microsoft's 2025 Work Trend Index found that the most-pinged fifth of Microsoft 365 users are interrupted every 2 minutes during core work hours.
Write a one-page proposal before any decision that affects more than one person.
Keep status in a shared system that anyone can read without asking.
Use meetings for negotiation and disagreement, then write down what was decided.
Agree on response windows for each channel, and define "urgent" in writing.
Async-first leaders go first: their decisions are written where everyone can see them.
Mycelium networks transmit signals across distributed nodes without any central coordinator. Async-first teams operate on the same principle: information travels on its own schedule, not synchronized by a meeting calendar.
What async-first actually means
Async-first still has meetings. What it means is that decisions, context, and institutional knowledge exist in written form by default, because the work itself produces written artifacts as its primary output rather than because someone documented them after the fact.
In a synchronous-by-default organization, a decision gets made in a meeting. The meeting participants leave with shared context. Everyone else doesn't have it. The decision may get captured in meeting notes if someone remembered to take them, or it may live entirely in the memories of the people who were in the room. Future decisions that build on that context require access to those people, which creates bottlenecks that scale poorly as the organization grows.
In an async-first organization, the decision-making process itself is written. The proposal, the constraints, the options considered, the reasoning behind the chosen path: all of it is visible before the decision is final. Stakeholders can weigh in on their own schedule. The decision record exists permanently. New team members inherit context without requiring anyone to narrate history.
The overhead of writing well is real. It's also an investment with compounding returns: the same document that informed one decision informs the ten decisions that build on it.
Async-first vs remote work, side by side
Remote work and async-first get blurred because they arrived together for most companies, so it helps to put them next to each other. Remote work is a policy about place. Async-first is a set of habits about how information moves. Either can exist without the other.
Remote work
Async-first
The question it answers
Where do people work?
How do decisions and information move?
What you change
Office, equipment, hiring radius
Proposals, status, meetings, response windows
Where a decision lives
Wherever it was made: a call, a chat, a hallway
In a written record anyone on the team can find
How a new hire catches up
Asks the people who were there
Reads the decision log
Typical failure
Back-to-back video calls replace the office
Documents nobody reads, or side deals made in private messages
A team that went remote in a hurry usually kept the synchronous habits and moved them to video. That is the version with the most meetings and the least written down. An async-first team that sits in one room still writes the proposal first, so the person who was out sick on Tuesday can catch up from the record.
The difference between a team that scales and one that doesn't is often the difference between knowledge that lives in documents and knowledge that lives in people's heads.GitLab's 2020 Remote Work Report found that 50% of the 3,000 professionals it surveyed default to shared documents and rely on meetings only as a last resort. The async-first shift is toward defaulting to written, time-stamped communication that does not require simultaneous presence to move decisions forward.
The three shifts that make it work
Written proposals replace verbal pitches. Before any decision is made (on tooling, architecture, process, scope), the proposer writes it down. Keep it to one page: the problem, the proposed solution, the alternatives considered, the criteria used to choose. The act of writing forces precision that conversation doesn't require. Vague proposals become obvious in writing in a way they rarely do in real time.
Status is pulled from a shared system instead of pushed through check-ins. In synchronous environments, status travels through check-ins, standups, and informal desk conversations. The person with the most pull (the most persistent asker, the most senior title) gets the most current information. In async-first teams, status is visible in the project management system by default. Anyone can check the state of any project at any time without requiring another human to transmit it. This is the organizational equivalent of observability: replace manual reporting with instrumentation.
Meetings are for decisions that require real-time negotiation, not information transfer. If the purpose of a meeting is to share information that could have been written and read, it's a synchronous tax on everyone's calendar. Meetings are valuable when real-time back-and-forth is the mechanism: negotiating scope, working through a disagreement, collaborative problem-solving where the exchange itself produces insight. Everything else is a document.
The cognitive cost of context-switching is materially lower in async-first environments because deep work blocks don't get interrupted by synchronization requirements. The meeting that "could have been an email" costs more than annoyance: in Gloria Mark's University of California, Irvine field research, interrupted work was resumed, on average, 23 minutes and 15 seconds later.
Every decision made in a written document instead of a meeting compounds: the same record that informed one choice informs the ten decisions that build on it.
What the interruption research says about async-first work
The 23-minute figure gets quoted loosely in async-first writing, so it is worth being exact about it. In a June 8, 2006 Gallup interview, Gloria Mark described shadowing office workers and timing every switch. She reported that 81.9 percent of interrupted work was resumed on the same day, and that it was resumed, on average, "in 23 minutes and 15 seconds," usually after other tasks in between. That is the time until people got back to the work, which is a different thing from how long it took them to refocus once they did.
Two decades later the interruptions are more frequent. Microsoft's June 2025 Work Trend Index report, built on anonymized Microsoft 365 data, found that among the top fifth of users by volume of pings, people are interrupted every two minutes during core work hours, 275 times a day, by meetings, emails or chats. The same report counts 153 Teams messages per weekday for the average worker, and meetings starting after 8 pm up 16% year over year.
Async-first changes who decides when interruptions happen. In an async-first team, a question posted to a shared thread waits until the person finishes the block they are in; a tap on the shoulder or a call does not. Over a week, that difference is most of what people mean when they say an async-first team gets more done with the same hours. For more on the switching cost itself, see the real cost of context switching.
What it requires from leadership
Async-first doesn't happen by announcing it. It requires leaders to model it: to write their own decisions in public, to ask for written proposals instead of verbal presentations, and to resist the pull toward synchronous resolution when the topic is uncomfortable or complex.
The most common failure mode is leaders who endorse async-first publicly but resolve ambiguity in private conversations. Every time a decision gets made in a hallway or a DM instead of a written document, the organization learns that the written process is for appearances and the real decisions happen elsewhere. Trust in the system collapses quickly once that pattern is established.
The second failure mode is mistaking documentation for bureaucracy. Async-first documentation is meant to be lightweight and functional: a decision record, not a policy manual. The question is always "what does someone need to know to understand or build on this?" not "how do we create a record for its own sake?"
GitLab, which has run as an all-remote company since 2014 and published the 2020 Remote Work Report quoted above, puts the leadership point bluntly in its guide to asynchronous and non-linear working: "The company must embrace asynchronous workflows (including tools like GitLab as well as processes) in a deliberate, intentional, and thorough way." An async-first policy memo is not enough on its own. People copy what the person at the top does with a hard decision.
How to write an async-first decision record
The decision record is the basic unit of async-first work. An async-first record does not need special software; a shared document or a ticket works. What matters is that every async-first record has the same parts, so anyone can read one in two minutes.
Title and date. What was decided, in one line, and when.
Owner. The one person who made the call.
The problem. Two or three sentences on what prompted the decision.
Options considered. Including "do nothing," with one line on each.
The decision and the reasons. Which option, and the criteria that picked it.
Who was consulted. Names, so a later reader knows whom to ask.
What would change it. The signal that should reopen the question.
Illustrative example: picture a twelve-person accounting office that works async-first, choosing a new phone system. The office manager posts a one-page proposal on Monday with three options and the criteria: call recording, a mobile app, and a monthly cost ceiling. Partners comment by Wednesday at their own pace. One raises a concern about call recording consent in Massachusetts, which the manager checks and notes. The decision record goes up Thursday, naming the choice, the reasons and the condition that would reopen it. Nobody sat through a meeting, and the new hire who starts in March can read exactly why the office picked that system.
That last point is the async-first payoff. The async-first record outlives the people who made it, which is the protection against the key-person risk described in the bus factor. When a decision is easy to reverse, the record can be short; the heavier version is for the decisions described in one-way and two-way doors. Kief Studio's knowledge systems work is built around making records like this easy to find later.
An async-first communication contract for a small team
An async-first team runs on agreed response windows. Without them, people on an async-first team either answer everything at once to be safe or let things sit, and both undo the point. A one-page async-first contract settles it. Here is a starting async-first version to adjust:
Channel
Use it for
Expected response
Phone call or text
True urgencies only: a system down, a legal deadline today, a client emergency
Scheduled, with a written agenda and a written outcome
The windows here are a template to adjust; what matters is that they are written down and everyone agreed to them. When an async-first team does meet, the outcome goes in writing the same day. Qurtoo's meeting notes prompt for decisions and action items turns a transcript into decisions, owners and dates that you then check, which keeps the meeting from becoming the only record.
The same async-first habit is spreading to AI tools at work. When an AI assistant drafts a customer email or a post, an async-first team wants the draft and the approval in writing too, so there is a record of who said yes. That is the reason LTFI keeps AI staff work in an approval queue with an activity log rather than in a chat window that scrolls away.
Where async-first breaks down
Async-first has real costs, and a team should know them before it commits to async-first. The first is speed on contested questions. A disagreement that two people could settle in a ten-minute call can stretch across three days of comments. The async-first answer is a simple rule: if a written thread goes back and forth more than twice without movement, the owner books a short call and writes the outcome afterward.
The second cost is the writing itself. People who think out loud find a one-page proposal slow at first, and some never enjoy it. Templates help, and so does accepting that an async-first record can be rough as long as it is clear. A decision record with typos that answers the seven questions is worth more than a polished one that never gets written.
The third is connection. A team that only ever writes to each other can feel lonely, especially when it is distributed. Async-first teams that last keep some time together on purpose: a weekly call with no status in it, a lunch, a working session on a hard problem. The async-first meetings that remain are better because they are no longer carrying the status updates.
Finally, async-first depends on one shared place. If decisions are spread across email, three chat tools and a whiteboard photo, writing them down does not help much, because nobody can find them. Picking that place is the first async-first step, and it is often the moment a team notices how many tools it is paying for, the problem behind vendor consolidation for regulated industries.
How to move a team to async-first in 30 days
Most teams can make the async-first shift in a month without a big announcement. The order matters more than the speed.
Week 1: write down how decisions get made now. List the last five real decisions and where each one happened. Most teams find that the majority happened in a call or a private message.
Week 2: start decision records. Every decision that affects more than one person gets an async-first decision record in one shared place, using the seven parts above. Leaders write theirs first.
Week 3: move status out of meetings. Status updates go into the project tool by a set time. The standing status meeting becomes optional, then gets cancelled if nobody misses it.
Week 4: write the communication contract. Agree on channels, response windows and the definition of urgent, and post it where everyone can see it.
Then review the async-first trial after a month. Count how many decisions have records, how many meetings were cancelled, and whether anyone was blocked waiting on an answer. Adjust the async-first windows rather than abandoning the idea. A distributed team will feel the change first, but a team that shares an office benefits from the same async-first records, which is the point Brian makes from the client side in the client who wanted a dashboard actually wanted a decision. Building the habit early is the theme of building systems before you need them.
Frequently asked questions about async-first work culture
Does async-first work for client-facing teams?
Yes, with a clear communication contract. Clients need to know the expected response time, what channels to use for what types of communication, and what constitutes an escalation. Most clients don't actually need instant responses; they need reliable responses within a defined window. A clear SLA lets an async-first team give that reliability, and the replies tend to be more considered because the context is written down and preserved.
How do you handle urgent issues in an async-first environment?
By defining "urgent" explicitly before you need to. Most things that feel urgent are immediate rather than urgent by any operational definition, which is different. True urgencies (production down, legal deadline, client emergency) warrant synchronous escalation. Everything else follows async protocols. The definition has to exist in writing before the moment of apparent urgency, or the exception becomes the rule.
What tools support async-first effectively?
The tool is less important than the discipline. Linear, Notion, GitHub Issues, Basecamp: any system where work and decisions are visible by default works. The usual failure comes from the team continuing to route context through private messages and verbal exchanges while nominally using the system.
Is async-first appropriate for early-stage startups?
It requires more investment upfront than ad-hoc verbal coordination, which can feel slow when the team is two or three people in the same room. The payoff is in the 10-50 person phase, where verbal-only organizations hit communication walls that require expensive restructuring. Building the documentation habit early costs less than retrofitting it later.
Is async-first the same as remote work?
No. Remote work decides where people sit. Async-first decides how information moves: written proposals, visible status and meetings kept for negotiation. An office team can be async-first, and a remote team can still run on back-to-back calls.
Does async-first mean no meetings?
No. Async-first teams still meet to negotiate, resolve disagreements and handle sensitive conversations. The difference is that the meeting has a written agenda and a written outcome, and routine status moves to a shared system.
How fast should people respond in an async-first team?
As fast as the async-first team's written contract says for that channel. A common starting point is the same working day for chat, one working day for tasks, and right away only for agreed urgencies like a system outage.
What is an async-first decision record?
A short written note of one decision: title and date, owner, the problem, options considered, the decision and reasons, who was consulted, and what would reopen it. It lets anyone catch up without a meeting.
What are the downsides of async-first work?
Contested decisions can take longer, writing takes effort, and a team that only writes can feel disconnected. Async-first teams handle this with a rule for when a thread moves to a call and with some regular time together that carries no status updates.
How do you start async-first with a small team?
Start with decision records, then move status into a shared tool, then write a communication contract with response windows. A small team can make the async-first shift in about a month, with leaders writing their own decisions first.
How to audit AI spending without buying a tool first. Zylo's 2026 index found ChatGPT is now the most expensed app, so the audit starts in card statements and expense reports, then moves to API keys, owners and a monthly review.
62% of large organizations were building, deploying or developing AI agents in September 2026, KPMG found. After a year and a half of agentic AI in production on LTFI, our lessons are about approval lines, logs, written rules, cost, drift and people.
Website maintenance cost depends on which of three jobs you buy: hosting, plugin updates or real website operations. Patchstack counted 11,334 new WordPress vulnerabilities in 2025. Published 2026 ranges, Worcester labor figures and the drivers that move the price.