The US–Asia time gap is the hardest scheduling bridge in global business. New York and Tokyo are 13–14 hours apart; Los Angeles and Mumbai are 13.5 hours apart. No comfortable overlap exists — someone is always joining outside of normal working hours.
The Available Windows
The only time that's even minimally tolerable for both sides is the edge of each workday. For US West Coast and Tokyo: 7–8 AM PT = 11 PM–midnight JST. For US East Coast and Singapore or Hong Kong: 8–9 AM ET = 8–9 PM SGT. Neither is ideal. For India (IST = UTC+5:30), US East Coast mornings (9 AM ET = 6:30 PM IST) and US West Coast afternoons (4 PM PT = 5:30 AM IST next day) bracket the gap, with mornings ET being the more workable option.
The Rotating Schedule Strategy
For weekly syncs that span the US and Asia, the fairest approach is a rotating schedule. Week A: US morning / Asia evening (late for Asia). Week B: US evening / Asia morning (late for US). Alternate so neither team is always the one staying late.
Bi-weekly calls are worth considering for US–Japan or US–Southeast Asia bridges. Reducing frequency makes the occasional off-hours call feel less burdensome, while asynchronous updates (written summaries, recorded videos) handle the routine work between calls.
Async-First for US–Asia
Most experienced global teams with a large US–Asia gap default to async communication for day-to-day work. Stand-up updates are written rather than spoken. Decisions are made via comment threads on shared documents. Live meetings are reserved for kickoffs, relationship building, and genuinely complex decisions that require back-and-forth.
Tools like Loom (video messages), Notion (async documents), and Linear (async project tracking) make async workflows practical. The key discipline: over-communicate in writing, set clear response SLAs, and resist the reflex to schedule a meeting when an email or document would do.
