Best Meeting Times for Global Teams

Direct Answer

The best meeting time for a global team is rarely the mathematically perfect midpoint. It is the shortest overlap that respects business hours, protects deep work, and does not punish the same region every week.

Why This Matters

Teams often optimize for convenience in the current week instead of fairness over time. That creates quiet burnout, bad attendance, and recurring meetings that survive only because nobody wants to renegotiate them.

A Better Ranking System

Priority	What to optimize	Why
1	Business-hours overlap	Prevent burnout and missed calls
2	Rotation fairness	Avoid always pushing pain to the same city
3	Meeting length	Shorter meetings need less overlap perfection

Choose The Slot With A Simple Decision Flow

1. Start with the strongest business-hours overlap.
2. Check whether the same city has been absorbing the pain.
3. Shorten the meeting before you expand the overlap window.
4. Move status work async so the live slot stays reserved for decisions.

When to Rotate the Slot

• When one region keeps taking early mornings or late evenings.
• When DST changes reintroduce the same pain every quarter.
• When the team grows into a third major region.

A US East–West Coast Example

A team split between New York and Los Angeles is only three hours apart, but the burden is real: a New York morning is a Los Angeles dawn. The design is the same as the international case, just with smaller numbers:

1. Keep the slot inside both teams’ work hours — usually a New York mid-morning window that is still an early-but-legal Los Angeles start.
2. Rotate the early side instead of letting the West Coast own every early slot.
3. Reserve the strongest overlap for decisions and move status updates async.

Open the meeting planner with New York and Los Angeles preloaded

Protect the Best Band

Reserve the strongest overlap for decisions, 1:1s, and unblockers. Use async updates for everything else.

Useful TimeNowHub Starting Points

These pages are good starting points when a team regularly coordinates across the same regions:

• Compare New York to London
• Compare London to Sydney
• How to schedule across time zones

Frequently Asked Questions

Is the best meeting time always the midpoint between all cities?

No. The midpoint often ignores business hours and fairness. The better choice is the shortest overlap that solves the problem without repeatedly pushing pain to the same team.

When should a team rotate its recurring meeting hour?

Rotate when one region consistently absorbs early mornings or late evenings, or when DST changes make the current slot noticeably worse.

What work should stay inside the best overlap band?

Keep decisions, unblockers, interviews, and 1:1s in the strongest overlap. Push status reporting and routine updates into async channels.

Three-region example you can actually run

A product triad in New York, London, and Sydney does not have a fair midpoint. The live band is a short morning in Sydney or a late afternoon in New York. The honest design is:

1. One 30-minute decision slot in the strongest overlap.
2. A written async update for everything else.
3. A rotation rule so Sydney does not own 07:00 forever.

Load those three cities, set duration to 30 minutes, and generate the series. If the fairness view shows one city eating every early slot, rotate the anchor week or cut the meeting.

Open the meeting planner with New York, London, and Sydney preloaded

Gulf-weekend roster: if Riyadh is on the call, Friday is not a work day in our engine (Saudi Arabia, Qatar, Kuwait, Oman). Do not “fix” that by inventing a Saturday standup — change the cadence. Riyadh time states the country; the planner states the weekend in words.

DST still moves the band: see Why DST breaks recurring meetings rather than a second “best times” URL.