Skip to content
Playbook
IntermediateCEOFounderManager

The Async-First Operating Model: What Works in 2026

Async-first is no longer a remote-work pitch — it is a productivity discipline that distributed companies have spent five years debugging.

10 min read
On this page
60-Second Summary
  • Async-first works. Async-only fails — humans need some real-time connection.
  • Document defaults, decision logs, and writing standards are non-negotiable.
  • The 60/30/10 rule: 60% deep work, 30% async collaboration, 10% real-time.
  • Manager skill that breaks teams in async: cannot write clearly.

Async-first as a fashion peaked in 2022, got declared dead in 2024, and quietly became standard operating procedure in 2026 for any company that hires across more than two time zones. The teams that made it work look nothing like the original GitLab handbook fantasy — but they also look nothing like the always-online Zoom culture that replaced it for a while.

Five-year verdict

Async-first is a real productivity model when applied to knowledge work with measurable output. It fails in functions that depend on rapid iteration with customers (early-stage sales, executive crisis response, live operations). It also fails when the company uses 'async' as a euphemism for 'we will not invest in management'.

What works

  • A written handbook everyone trusts and edits — not a wiki graveyard.
  • Decision logs: every significant decision documented with context, owner, and date.
  • A shared writing standard (one-pager, RFC, decision doc) so writing quality is consistent.
  • Two to four hours of guaranteed overlap per day for cross-timezone teams.
  • One in-person offsite per quarter for teams that work together daily.

What fails

  • Async as a synonym for 'do not message me' — collapses team coordination.
  • Meetings replaced by ten Slack threads with no decision recorded.
  • Performance management by activity signals (online green dot, typing indicator).
  • Hiring junior people into a fully-async culture without a structured ramp.
The 60/30/10 operating model
  1. 1
    60% deep work
    Protected focus time. Calendar held, notifications off. The output of a knowledge worker.
  2. 2
    30% async collaboration
    Written work — docs, code review, threads, decision logs. The connective tissue.
  3. 3
    10% real-time
    1:1s, team rituals, live problem-solving. Small, intentional, well-prepared.
The hiring filter

If a manager cannot write a clear one-pager, they cannot run an async team. This belongs in the interview loop.

Written by Pawan Joshi.Sources cited inline.
First published 23 Jun 2026See site changelog →