DISTRIBUTED TEAMS, STANDUPS, AND THE ONE PERSON WHO ALWAYS DIALS IN AT DAWN
Somebody on this team is always taking the call at 6am
The standup was set when everyone was in two zones. There are five now, and the same person keeps eating the bad hour without anyone deciding that.
The meeting time was reasonable when it was chosen. Two offices, three hours apart, 9:30am in the eastern one. Nobody minded.
Then someone moved to Lisbon. Then you hired in Bengaluru. Then the west coast office opened. Nobody revisited the time, because revisiting it would mean admitting that there is no time that works, and the meeting already exists.
So it stays at 9:30 Eastern. Which is 6:30am in California and 7pm in India.
The default is not a decision
This is the part worth naming: nobody chose to give one person the 6am slot. The slot was chosen when it was nobody's 6am, and the team grew around it. The cost landed on whoever joined last and had least standing to object.
That is why it persists. It never gets discussed, because it was never proposed.
What the overlap actually looks like
Before you can fix it you have to see the constraint honestly. With normal waking hours on each side, a US-east-to-India pair shares roughly four and a half hours — and they sit at the very start of the American day and the very end of the Indian one. Add California and the shared window with India collapses to almost nothing.
The useful exercise is not "what time suits everyone." It is "how many hours do these people genuinely share, and which of them are humane on both ends?" Once you can see the window, the conversation changes from a scheduling debate into a resource-allocation one — because that is what it always was.
Three fixes that actually hold
Rotate the pain. If the overlap is genuinely narrow, the bad hour is real and someone has to take it. Rotating it monthly spreads the cost and, more usefully, makes it visible to people who were previously insulated from it.
Split the meeting. Two regional standups plus a written handover is often strictly better than one call where a third of the participants are barely awake. The synchronous meeting was never the goal; the information transfer was.
Move it to the honest middle. Sometimes the meeting sits at 9:30 because of history rather than constraint, and shifting it two hours costs the original office very little and rescues someone else's morning entirely.
Anti-fix: rotating it weekly. Everybody's sleep is disrupted, nobody adapts, and it produces more complaints than the original problem.
Check it twice a year
Whatever you land on, the clocks will move underneath it. The US and Europe do not change on the same weekends, so for a couple of weeks each spring and autumn your carefully chosen slot shifts by an hour for part of the team. India does not change at all, which means its gap to everyone else moves without India doing anything.
Mid-March and late October are the two moments a recurring cross-zone meeting can silently break. See Eastern Time to GMT for what happens in those weeks.
Related: The handoff window nobody can agree on · IST to EST
Timezone: World Clock Widget
A world clock, converter and live day/night map for iPhone — 325 cities, offline, no account.
Figures on this page are computed from the IANA time zone database. Last generated 2026-08-18.