Asynchronous Work as Default

Definition

The transition from synchronous to asynchronous work is central to enabling remote work. Synchronous collaboration requires everyone working at the same time in the same place; asynchronous collaboration means the work happens across time zones and disconnected sessions. Rather than meetings and real-time problem-solving, async work relies on written communication, batched updates, and intentional handoffs that don't require immediate response.

In the Book

Fried and Hansson describe this as one of the core benefits of distributed work: "Not only do we not have to be in the same spot to work together, we also don't have to work at the same time to work together." This shift is born from necessity—when collaborating across seven-hour time differences (Chicago to Copenhagen, as 37signals does), synchronous work is simply unworkable.

The book describes specific practices: at 37signals, they use a weekly "What have you been working on?" discussion thread where everyone writes a few lines about their week and plans. There are no real-time reviews or status calls. Instead, they structurally require people to document progress.

The authors also describe how at IT Collective (a film production company), editors switch to nocturnal mode during intensive work. The team overlaps just long enough the next day to review progress and receive direction. The schedule is built around async handoffs, not constant sync presence.

Async communication also accommodates different chronotypes: early birds, night owls, and parents with midday school pickup schedules can all contribute meaningfully because the work doesn't require everyone awake at the same hour.

Why It Matters

This concept inverts the traditional assumption that coordination requires togetherness. It enables flexibility, protects deep work time, and scales across geographies that synchronous work cannot. Async-first structures require better documentation and clarity (you can't mumble in writing), which has second-order benefits for onboarding and institutional memory. The mechanism applies beyond remote work: any organization with knowledge workers competing for focus and flexibility benefits from designing work to tolerate async handoffs.