Rotating Meetings Across Time Zones Treats the Symptom

The short version

Rotating an unfriendly meeting slot spreads the cost evenly. It does not reduce it, and evenly distributed pain is easier to ignore.
Rotation also makes attendance worse: a slot that moves cannot be planned around, so people miss it in turn and the meeting repeats itself.
Before you rotate, ask what the meeting is for. Most rotated meetings are status meetings, and status does not need a meeting.
Keep and protect the meetings where the outcome depends on live argument. Retire the ones where people take turns reading their updates.

Rotation is a fairness mechanism applied to a design problem. If a meeting has to happen at an hour that is unkind to someone, rotating who suffers is more equitable than always choosing the same victim. But the meeting still costs the same number of unkind hours per month, and the team has now agreed to stop complaining about it.

"We rotate the pain so nobody complains and everybody is tired."

Why teams start rotating

Rotation usually arrives after someone points out that the weekly all-hands is always at 22:00 for the Singapore team. The observation is fair, the response is proportionate, and the outcome is a rota.

It is a genuine improvement in fairness, and that is exactly why it is dangerous. It converts a loud, specific grievance into a quiet, shared inconvenience. The Singapore team stops raising it, because now everyone takes a turn, and the underlying question, whether that hour needs to exist at all, never gets asked.

What rotation actually costs

Unplannable weeks. A fixed bad slot can be built around: a school run rearranged permanently, a standing arrangement at home. A moving bad slot means everyone keeps a wide window mentally reserved every week.
Worse attendance, more repetition. People miss the rotation that falls badly for them, so content gets repeated for whoever was absent, which is the same content being delivered twice.
Diffused accountability for the hour. When everyone pays sometimes, nobody owns reducing it. A permanently bad slot has an advocate for change. A rotating one does not.
Timing errors. Rotating slots plus clock changes plus regional holidays produce a steady trickle of people joining an hour late or not at all.

Which meetings to cut first

Before rotating anything, sort the recurring cross-zone meetings by what they produce. The test is simple: what came out of the last three instances that could not have been written down?

Meeting type	Needs everyone live?	Verdict
Round-robin status update	No	Retire it
Information broadcast, one speaker	No	Record it, or write it
Decision review with trade-offs	Yes	Keep, and protect the slot
Disagreement or escalation	Yes	Keep, and hold it sooner
Team connection and social	Yes, occasionally	Keep, make it rarer and better

The first two rows are usually the majority of rotated hours. That is the finding that matters: most rotated meetings are status meetings, and status can be answered instead of held. Each person spends ninety seconds at the end of their day on a brief, and while they are off, their StandIn answers questions from it in their words, with a source under every answer. Anyone in any zone can ask what moved, what is blocked, and who owns the call, during their own working day.

The hour you were rotating disappears rather than moving. What remains is a short decision slot that genuinely needs people awake, which is a much easier thing to schedule fairly. More on retiring the status half in replace the status meeting, keep the status, and on the wider seam in working across time zones.

What to keep, and how to protect it

Once the status hours are gone, you are left with a small number of genuinely synchronous meetings. Give them a fixed slot in the least bad shared window, publish it in every relevant local time, and defend it from creep. A protected weekly decision slot is worth more than four rotating calls and costs a quarter as much.

Keep the agenda strict: decisions with named owners and a pre-read. If there is nothing to decide, cancel it that week without negotiation. A recurring slot that survives empty weeks will refill with status.

If you do rotate, rotate properly

Some meetings really do need everyone and really have no kind hour. For those, rotate with discipline: publish the rota a quarter ahead, cap how often any zone takes the bad slot, count a late or early slot as working time with a compensating adjustment the same week, and always record the session with written notes so the person who cannot make it never has to attend a repeat performance.

And review it quarterly against one question: what did we decide in this meeting that we could not have decided in writing? If the answer is nothing for two quarters, the rota is protecting a habit.

Common Questions

Is rotating meeting times better than a fixed bad time?

It is fairer and it is less plannable. For a meeting that must exist, rotation is the right call, published well in advance and capped per zone. For a meeting whose content could be written, rotation is a way of keeping it alive by making it slightly less objectionable to everyone.

How do we decide which meetings genuinely need everyone?

Ask what the last three instances produced that could not have been produced in writing. Decisions and resolved disagreements pass. Updates, broadcasts, and read-alouds do not. Run the test on real instances rather than on the meeting's stated purpose.

What about time zones that simply cannot be included?

Then do not pretend the meeting includes them. Make the decision in the zones that can meet, name the decider, and publish the outcome in a form the excluded zone can question during their own working day. A meeting somebody cannot attend is not inclusive because it was recorded.

Should we pay people for out-of-hours meetings?

Either compensate the time or give it back the same week. What you should not do is treat 22:00 attendance as a neutral part of the role. Unpriced out-of-hours time is how a rota becomes a shift pattern nobody agreed to.