Minimal Overlap Coordination

Definition

Distributed teams don't require everyone working the same hours. A small window of overlap—roughly 4 hours per day—is sufficient for real-time coordination, collaborative decisions, and synchronous problem-solving. The rest of the day can be asynchronous. This principle enables teams to span multiple time zones without sacrificing collaboration, and it allows individuals to optimize their own work schedules within the overlap window.

In the Book

The authors share 37signals' own experience spanning Chicago and Copenhagen—a seven-hour time difference. They determined that "we need a good four hours of overlap to avoid collaboration delays and feel like a team." To achieve this, Copenhagen works 11 AM–7 PM (local time) and Chicago works 8 AM–5 PM, creating exactly the key four-hour intersection.

Fried and Hansson note that this constraint, born from necessity, benefits everyone: "You'd be surprised at how many people prefer unconventional work schedules. Maybe it gives them extra time for their family or hobbies, or they simply do their best work at night or crazy-early in the morning."

The authors describe IT Collective's approach: editors sometimes switch to nocturnal mode during intensive film production. They "overlap with the rest of the team just long enough to review progress and get direction for the next night. Who cares if they slept way past noon to make that schedule work?" The overlap is purposeful, not constant.

They also acknowledge the exception: if time zones make even 4 hours impossible (Shanghai to LA), "you're probably going to have to work without a lot of real-time collaboration. That's not ideal; in fact, in most cases we think it's more of a challenge than it's worth—but some companies still manage to get it right when the payoff is big enough."

Why It Matters

This concept challenges the assumption that distributed work requires constant availability. By quantifying the minimum viable overlap, it opens a design space: you can expand teams geographically without proportionally sacrificing collaboration. It also exposes a hidden benefit of partial remote work: when only part of the day is synchronous, the rest becomes protected deep-work time. The mechanism generalizes: any system that requires coordination can calculate its minimum synchronization cost and structure the rest asynchronously.