Async Work

Async work (asynchronous work) is an operating model where collaboration happens primarily through written communication and structured documentation rather than synchronous meetings. It enables teams to make decisions, share information, and coordinate work without requiring all participants to be available at the same time. The model is particularly valuable for distributed teams across time zones and for deep-work-heavy roles where uninterrupted time matters more than constant availability. It is a structural shift in how work gets done and a discipline that requires intentional culture-building, tooling investment, and behavior change.

The components of async work:

Written-first communication:

• Important decisions documented in writing.
• Status updates, project plans, and decisions written down rather than just discussed.
• Meeting summaries documented for absent participants.
• Decisions are "decision records" with explicit rationale, owner, and timing.

Structured documentation:

• Wiki or documentation system (Notion, Confluence, GitBook) where information lives.
• Meeting notes, project briefs, decision logs, and process documentation all in writing.
• Searchable; new employees can ramp up by reading rather than asking.

Async-friendly meeting practices:

• Meetings have written agendas distributed in advance.
• Pre-reads (documents to read before meetings) replace in-meeting context-setting.
• Meeting notes published after for absent participants.
• Some companies do "memo culture" (Amazon-style 6-page memos read silently at meeting start).

Communication tool norms:

• Chat (Slack/Teams): real-time but not expected to be real-time. Responses can take hours.
• Email: longer-form, asynchronous by default. Multi-day response times acceptable.
• Video updates (Loom, etc.): async video replaces synchronous meetings for status updates.
• Documents: long-form thinking captured in collaborative documents.
• Synchronous meetings: reserved for genuinely interactive discussions (brainstorming, hard decisions, sensitive conversations).

Time-zone awareness:

• Meeting schedules respect time-zone differences; no expectation of late-night attendance from off-cycle participants.
• Some teams have "overlap hours" when most members are available; outside that, async only.
• Decisions can wait for the next overlap window rather than requiring everyone to be present immediately.

Where async work shines:

• Distributed teams: across time zones, async is the only practical operating model.
• Deep-work roles: engineering, design, writing benefit from uninterrupted blocks of time.
• Knowledge-intensive work: thinking benefits from written articulation.
• Inclusive cultures: async gives quieter team members voice (writing) that synchronous meetings (talking) often miss.

Where async work struggles:

• Crisis response: production incidents, customer escalations, urgent decisions need synchronous response.
• Brainstorming and creative work: real-time collaboration often produces better ideas.
• Difficult conversations: feedback, conflict resolution, sensitive topics benefit from synchronous video at minimum.
• Onboarding: new hires often need real-time guidance until they have enough context.

The discipline that makes async work:

• Strong writing culture: team members invest in clear written communication.
• Default-to-document: writing things down is a habit, not a chore.
• Patience with response times: not expecting immediate response.
• Async-friendly tools: Notion, Linear, Loom, Slack threads, async standups via Geekbot.
• Clear escalation paths: when something truly is urgent, there's a way to escalate (paging, urgent Slack channels) without making everything urgent.

What founders get wrong: Trying to operate distributed or large teams synchronously, exhausting everyone with meeting load and time-zone scheduling without recognizing that async culture is the discipline that unlocks distributed-team scale. The right discipline: at any company operating distributed (or at any growing co-located company with deep-work-heavy roles), invest in async culture deliberately: documentation system, written decision records, async-friendly meeting practices, time-zone-aware scheduling, deep-work protection. The cultural investment is significant but the operational leverage compounds significantly.

Related: Remote Team · Distributed Team · Company Culture · Core Values · Performance Review

FAQ

What is async work?
An operating model where collaboration happens primarily through written communication and structured documentation rather than synchronous meetings. Enables teams to make decisions, share information, and coordinate work without requiring all participants to be available at the same time.

Where does async work shine?
At distributed teams across time zones (where synchronous meetings are difficult), for deep-work-heavy roles (engineering, design, writing benefit from uninterrupted time), for knowledge-intensive work (thinking benefits from written articulation), and for inclusive cultures (async gives quieter team members voice through writing).

What disciplines make async work work?
Strong writing culture, default-to-document habit, patience with response times, async-friendly tools (Notion, Linear, Loom, async standups), structured meeting practices (written agendas, pre-reads, post-meeting summaries), clear escalation paths for truly urgent matters, and time-zone-aware scheduling. The investments compound to enable distributed-team scale.