Follow-the-sun handoffs: making decisions without waiting for the next overlap window

A distributed product team across CET, EST, and SGT has roughly forty-five minutes a day when everyone is awake at the same time. That window, in practice, is when the team in Singapore is finishing dinner and the team in San Francisco is finishing the morning standup. It's the seam of the calendar.

Every decision the team needs to make collectively gets queued for that window. Roadmap prioritization. Incident reviews. Hiring debriefs. The seam becomes a bottleneck, and the bottleneck becomes a delay, and the delay shows up as the thing teams in one timezone are doing right now that won't be agreed on until tomorrow's seam opens up.

The temptation is to schedule more meetings inside the seam. It doesn't scale. The seam is forty-five minutes. There aren't that many forty-five minutes in a week.

The teams that have been distributed longest don't fight the seam. They route around it.

Routing around the seam means treating the meeting as the synthesis of decisions, not the venue of them. The Singapore team weighs in on the roadmap during their afternoon. The CET team picks it up during their morning, layers in their context, hands off. By the time SF logs on, three timezones of input are already on the table, and the seam meeting becomes the place where the open questions get closed, not where the conversation starts.

This works only when the input collection is structured. A Slack thread won't do it, too easy to miss, too easy to reply to selectively, too easy for the loudest voice in any one timezone to dominate. A document with a fixed prompt and a deadline that respects every contributor's sleep does the job. Every voice gets the same space. Notifications fire when the contributor wakes up, not at 3am.

A distributed PM we know runs every cross-functional roadmap review like this. The async window opens Thursday afternoon CET. Each contributor records a voice note or writes a paragraph within their working hours. By Tuesday morning CET, four timezones have weighed in, the overview is synthesized, and the synchronous slot, which is forty-five minutes long because that's all there is, opens with the trade-offs already named.

The meeting becomes optional for the people who couldn't have been there anyway. The decision still gets made. The seam is no longer the bottleneck; it's the closing argument.

If your team is distributed and the seam is the limiting factor, the test is simple: which of this week's decisions could have been made without the seam, if the inputs had been gathered first? Those are the decisions that don't need to wait for the next overlap window. They need to wait for the next async cycle, which closes faster.