Async & Remote

Distributed and async-first teams require different norms and structures than co-located synchronous ones. This section covers frameworks for communication that works across time zones, that scales to many readers, and that doesn't require everyone to be in the same room at the same time. The shift from "show up to a meeting" to "read this carefully" changes what good communication looks like.

Async communication forces clarity: you can't rely on body language, immediate clarification, or group energy. But it also creates space for deeper thinking, broader participation, and better-documented decisions. These frameworks help teams move fast asynchronously without creating bottlenecks, ensuring the right people have the right information at the right time.

Frameworks Covered

• GitLab Async-First Handbook Principles - Cultural and operational guidelines for making async the default, with synchronous meetings as exceptions
• DRI (Directly Responsible Individual, Apple) - One person owns each decision and outcome; clarity about who decides prevents endless discussion
• Shape Up Communication Norms (Basecamp) - Pitch-based decision making, time-boxed cycles, and carefully chosen synchronous moments

When to Reach for This

• Your team spans multiple time zones and sync meetings create burden
• You want to scale decision-making and reduce meeting load
• Documentation and written communication keep getting deprioritized
• You need to involve many people in decisions but can't get them all together
• Preventing decisions that require "alignment meetings" after the fact

Prerequisites

Foundations, Writing & Structure: the ability to write clearly and organize information for scanning and reference