What to Do When There's No Usable Time Zone Overlap
Most scheduling advice assumes there’s a workable overlap window somewhere. But some time zone combinations have no shared business hours at all. Auckland and London are 13 hours apart. San Francisco and Singapore are 15–16 hours apart. No amount of creative scheduling finds a window where both sides are in their working day simultaneously.
Forcing synchronous meetings across these gaps means someone is consistently on a 7am or 10pm call every week. That might be acceptable for a monthly all-hands. It’s not a working rhythm.
Confirming the gap is real
Before building an async workflow, check the actual current offset in meetwhen — not a theoretical annual average. DST can open or close a 30–60 minute window depending on the season. Verify.
Common pairs where async is the right default:
| Pair | Standard hours overlap |
|---|---|
| San Francisco ↔ Singapore | None |
| New York ↔ Auckland | None |
| London ↔ Auckland | None |
| London ↔ Los Angeles | 0–1 hour |
The handoff model
The most useful structure for no-overlap time zones is a handoff: each side works their day, completes a defined unit of work, and passes it to the other side to pick up when they start. A London–Auckland team can get 20 hours of active coverage across two working days — better than either side waiting around for an overlap window.
This requires three things that synchronous work doesn’t:
Written context. In a meeting, you ask a quick clarifying question and move on. In a handoff, an ambiguous task sits idle for 12 hours. Written handoffs need more detail: what’s done, what’s pending, what decision is needed, and what specifically unblocks the next step.
Explicit decisions. “We’ll figure it out on the call” is broken in an async workflow. If a decision needs to be made, name it, frame the options, and assign who makes the call — so the other side can act on it without waiting.
A shared status layer. A doc, task board, or thread that both sides can read and update. This replaces the ambient awareness you get from being on the same Slack schedule.
When synchronous is still worth it
Async-first doesn’t mean async-only. Some things work better in real time: first meetings, complex decisions with multiple stakeholders, anything where iteration needs to be fast and unpredictable. For these, schedule occasional synchronous calls at a rotating off-hours slot — but treat them as deliberate exceptions, not the default rhythm.
Buy me a coffe