Scheduling Meetings Across Time Zones Without Burning Out One Region
Every globally distributed team has a meeting-time problem, and most solve it the same silent way: the region with the least organizational power takes the 6am and 10pm slots, permanently. The fairer alternatives cost slightly more coordination and buy substantially more retention.
The workable patterns
- Rotate the pain: alternate the recurring meeting between times that are bad for different regions. The US takes the early call one month, APAC the next. Fairness is visible on the calendar.
- Find the golden hours and guard them: most three-region teams have a narrow daily window that is tolerable everywhere (often 7-9am US Eastern for US/Europe/India). Reserve it for the meetings that genuinely need everyone, and refuse to fill it with meetings that do not.
- Split the meeting: run the same session twice for two regional cohorts, with a shared document carrying context between them. Costs the organizer double; costs everyone else nothing.
- Go async by default: the strongest fix is needing fewer all-region meetings at all — written proposals with objection windows replace most of them.
The recording-and-recap pattern
For meetings that cannot include everyone, the recording plus a structured recap is what keeps excluded regions from becoming excluded people. The critical detail is recap quality: a 60-minute recording nobody watches does not transfer context; a two-minute structured summary with decisions and action items does. MeetOye's Oya generates that recap automatically and emails it to all invitees — including the ones who were asleep — the moment the meeting ends. Someone in Singapore wakes up to the decisions, not to a calendar entry they missed.
Small mechanics that reduce friction
- Always write times with zone labels, or use calendar invites that localize automatically — never 'at 3pm' in a global channel.
- Check the other region's holidays before scheduling; a fair rotation that lands on Diwali or Thanksgiving is not fair.
- Put working-hours blocks in shared calendars so schedulers see them at booking time, not in the decline message.