# The Async Leader Playbook

A guide for founders leading a remote team who want fewer meetings, decisions made in writing, and people who can focus without watching chat.


<a id="start-here"></a>

## Start here

Most remote teams still work as if they shared an office. Every question goes to chat, every decision needs a meeting, and the people who answer fastest get the least focused work done.

This playbook is for founders and leaders of remote teams who want to move work into writing. It covers what real-time defaults cost you, when to work async and when to meet, the communication rules I give my teams, and how to build teams that run without you in every thread.

<a id="context"></a>

## Context

<a id="problems"></a>

### Problems

Teams that default to real-time communication pay a steep cost in focus, ownership, and scalability. Below are the symptoms, costs, and risks.

- Remote work requires a different work and communication paradigm.
- Default to real-time communication.
- FOMO: People are encouraged to stay connected in real-time because they fear missing out on discussions and decisions. It drastically hurts well-being and productivity. Interruptions can push people to work faster, increasing stress, pressure, frustration, and effort.
- Priority overload makes them lose track of their highest priorities.
- People fill their days with snacking or quick and low-value tasks to fill their limited time.
- Because everyone is available to help you in real-time, there are fewer constraints on collaboration, leading to loose boundaries and unclear ownership across the organization.
- Knowledge is never documented, as an expert always lies around to help.
- But Slack is an instant messaging tool masquerading as async. It is not suited to host business-critical knowledge.

Costs:

- Disruptions delay a return to focused work.
  - Disruptions are blasting productivity.
  - Collaboration overload
  - Employees toggle all day between chat, email, and work.
  - Constant context switches kill cognitive efficiency.
- Context switches are expensive and create micro-stress.
  - It builds up micro-stress throughout the day that accumulates over weeks.
- Notification fatigue

Risks of the status quo:

- Speed slows down as you hire more people.
- Knowledge silos lead to bus factor risk.
- When the one expert leaves, the blast radius is massive as the organization relies on tribal knowledge to operate.

<a id="practices"></a>

## Practices

<a id="default-to-async"></a>

### Default to async

This section is for leaders who want to transform their organization into an async-first and distributed workforce. The goal is to implement the cultural transformation to allow async work practices to thrive.

The most complex part: adapting the company culture. As a new work paradigm, it requires a mindset shift. People must unbelong from the old work methods to see the value of asynchronous work. Example: asynchronous work is admittedly slower, but outcomes are of higher quality.

Most people will shortly bound "slower" to "less productive." But being fast is worthless if you are not working on the right things. Asynchronous work makes teams surgical precision squads that go straight to where the value lies.

Asynchronous work allows employees to have more freedom to organize their workday. But freedom is a burden without discipline. Individuals must build strong discipline to thrive in this paradigm, as the organization adapts.

Written communication becomes the main way to collaborate and converse. Individuals must master it as a core skill to operate efficiently. [The Documentation as Code Playbook](/playbooks/the-documentation-as-code-playbook) explains how to keep that knowledge in a handbook.

Defaulting to async will allow you to build multi-thread teams.

- Optimize for 4 hours deep work per day.
- Check messages before or after natural context switches.

Make sure to support them in working healthy hours, taking regular breaks, and resting, especially when they don't feel in shape. Leave employees working whenever they want or feel as long as they stay aligned with business expectations and values. Finally, be very conscious of overworking. Plan and prioritize ruthlessly while listening to feedback to understand if you are pushing too much on your employees. Operating efficiently in this mode requires trust, discipline, autonomy, and accountability.

Hire and train consequently. A significant benefit of written communication is that it generates natural documentation. You can search for discussions and refer to them. While it doesn't prevent you from adequately persisting knowledge in documents, it is better than nothing. Asynchronous work gives people time to think and reply with complete thoughts, bringing quality to conversations and leading to more significant outcomes.

<a id="real-time-communication-in-async"></a>

### Real-time communication in async

Defaulting to asynchronous work doesn't mean removing synchronous communication at all. There is still a place for it, but must be used for the right purpose. This section applies for leaders who want to know when to use synchronous work compared to asynchronous work.

Use chat for coordination that doesn't need to outlive the day: a review request, a status ping, a link shared during a call, an incident in progress. Anything someone will need later, a decision, its reason, or a commitment, goes where it's kept: the issue, the pull request, or the document it changes. Prefer a public team channel to a direct message, because it's searchable, but never treat a chat thread as the record. The [Shaped Kanban channel map](/playbooks/the-shaped-kanban-playbook#communicate-and-improve) is one example.

Keep a few chat channels for things that can disappear:

- `#social-watercooler` (memes, life updates)
- `#urgent-alerts` (PagerDuty integrations, live incidents)
- `#voice-chat-text` (links shared during a live call)

Use these rules to choose when to meet:

- Use synchronous communication only for chit-chat, social, casual conversations, or emergencies.
- Synchronous work is mandatory during emergencies like incident resolution.
- The rule is: real-time sometimes, asynchronous most of the time.

Real-time communication overhead makes it difficult to focus, drains employees' mental resources, and makes it more challenging to make meaningful progress on work. It leads to constant interruptions.

In real-time environments, you're incentivized to stay connected and available at all times. If you disconnect, discussions will move on before you even have a chance to respond to or even see them. To avoid missing out on crucial decisions and discussions, people try to always be online and in as many meetings as possible, hurting both their well-being and productivity.

Keep real-time communication the last resort. Respect people's time.

Examples of platforms optimized for synchronous communication:

- Slack
- Google Chat
- Discord

<a id="the-async-communication-blueprint"></a>

## The async communication blueprint

- Be explicit in everything you say.
- Take time to craft complete thoughts.
- Be vulnerable and transparent.
- Avoid DMs and private channels.
- Ask, never assume.
- Listen first, talk last.
- Be clear about the emergency channels.
- Always use threads, except in emergency channels.
- Set deadlines when requesting an action.
- Assume a delay of 24 hours for people to reply.
- Share what it is about in your first message.
- React with emojis to give undisruptive and soft feedback.
- Be clear when there is an action for others to perform.
- Ask naive questions.
- @ mention people only when they must read it.
- Archive unused channels as soon as possible.
- Be concise and use ubiquitous terms.
- Link documentation instead of duplicating content.
- Use simple words.
- Use bold text to emphasize essential info.

<a id="distributed-team-management"></a>

## Distributed team management

[The Empowerment Playbook](/playbooks/the-empowerment-playbook) explains how to give each decision a clear owner.

- Autonomous individuals
- Self-sufficient teams
- Asynchronous communication
- Non-blocking execution and processes
- Authority decentralization
- Supportive leadership
- People-first
- Resilience
- Working from anywhere
- Remote-friendly
- Versatility and full-stack engineering
- Simplicity to support versatility and accessibility
- Self-discipline
- Personal growth
- Management is horizontal and centralized, therefore, individual contributors must become stronger without direct input from leadership.
- Information is in the field. If you bring decision-making to the field, decisions can be fast and well-informed because they don't require long back-and-forth between hierarchy and individual contributors.
- Following Conway's law, distributed teams are well-suited for distributed systems in software engineering.
- Trust
- Social capital
- Decentralized accountability. The more people have impact in decision-making, the more they must accept accountability for the outcome (success or failure) of decisions.
- Eight people maximum
  - More than that, start building a new team by splitting the first one.

<a id="change-benefits"></a>

## Change benefits

- Deep work
  - Recover 20 hours per dev per month for deep work.
  - Increases deep work time by 4 hours per day
  - People can optimize their productive hours to deep work, which produces higher outcomes.
  - Decreases collaboration overload
  - Significantly decreases the need for meetings
- Adapted to personal contexts
  - Differ depending on the person (morning, afternoon, night)
  - Different energy types let you work through bursts or constant effort.
  - Workers can organize their day as they see fit without impacting company operations.
  - Adapted to all personality types
  - Inclusive for workers with personal conditions
    - Physical handicap
    - Mental handicap
    - Extra care for a family member or child
  - People can deal with an emergency without impacting their work.
- Global talent acquisition
  - People win the freedom to work from and live anywhere.
  - Access to the global talent pool
  - They have more options to find a location aligned with their lifestyle.
  - Remote work and async work beat vanity perks any day and cost nothing to provide.
  - Asynchronous work allows working efficiently with people in different timezones.
  - Perk: enables people to travel and work abroad
- Customer success
  - Can build teams that follow the sun
  - Available around the clock to help colleagues, lead incidents, or support customers
- Documentation
  - Default to written communication produces natural documentation.
  - People can provide complete thoughts before a reply.
- Mental health
  - Employees don't feel FOMO anymore.
  - They don't need to be always on to follow conversations and participate in decisions.
- Suited for software engineering
  - Work finely with engineering as async work shines with knowledge work in general.
- Increase collaboration efficiency
  - Explicit on collaboration rules which clarify the ownership structure
- Cost efficiency
  - Cancels the need for an office
- Culture improvements
  - Forces a culture of transparency and trust
  - Builds business resilience and sustainability

<a id="challenges"></a>

## Challenges

- Requires writing skills
- Requires autonomy and authority delegation
- Works better with versatility and cross-skills
- Requires a different leadership style

<a id="start-with-one-meeting"></a>

## Start with one meeting

Choose one recurring meeting and replace it with a written update for 4 weeks. Share the async communication blueprint with your team on day one. Bring the meeting back only if the written version failed, and say why.

If you want to move a remote team to async without losing speed, that's what I do as a part-time Fractional CTO.


Leadership guidance you adapt to your team. It is not HR or legal advice; check working-hours and employment rules where your people live.