How can a team choose overlap hours fairly across time zones?
Quick answer
List the work that genuinely needs live discussion, then ask each person for their usual local working window and relevant boundaries. Compare only slots that meet the work need, using each person’s local time. If an inconvenient slot is unavoidable, track who bears the burden and rotate it where possible. Provide an asynchronous way to contribute, record the decision and rationale, and set a date to review the arrangement.
The question, the details, the next step.
Our team spans several time zones, and every proposed meeting seems unfair to somebody. How should we choose overlap hours?
Separate two questions: what genuinely needs shared live time, and how to distribute the inconvenience when live time is necessary. Start with the work, not “When is everyone free?” List the decisions or coordination that need discussion, and identify who must participate. Some items may need a smaller group or no meeting at all.
Ask each person to provide their usual working window in their own local time, along with any boundaries they want considered. Treat this as planning information, not a promise of constant availability. Compare windows only to find overlap that serves a stated work need. Choose the shortest useful slot rather than filling every available hour.
Can you show me a worksheet we could use to compare options without making one person’s local time the default?
Use one row per person and keep working windows in local time. These placeholders are not suggested hours:
Person | Usual work window | Boundaries | Can attend live? | Notes
[A] | [local start–end] | [times or days] | [yes / sometimes / no] | [optional]
[B] | [local start–end] | [times or days] | [yes / sometimes / no] | [optional]
Then list candidate slots and show each in everyone’s local time. Use a shared calendar or ask participants to verify conversions; don’t assume a fixed offset. Compare options using the same questions: Do the necessary participants fit? Does the slot respect their stated boundaries? How often would each person attend at an inconvenient time? What work would be delayed if someone could not join?
Record the chosen slot, why it meets the need, and a review date. That makes the decision easier to revisit than an unexplained calendar invite.
What if the only common time is very early or late for some people? Is rotating meetings actually fair?
Rotation can share an unavoidable burden, but it is not automatically fair. First consider whether the meeting can be shorter, less frequent, split among smaller groups, or replaced with written input and a focused live discussion. If a difficult slot remains necessary, publish a rotation over a defined period and compare how often each affected person gets the inconvenient time. Consider the constraints people have identified, not just whose name appears on the schedule.
For example, a team might rotate a monthly decision meeting among three candidate times across successive meetings, then review the pattern after a few cycles. Choose the cadence and options as a team. Share the agenda in advance and provide a way for people who cannot attend to contribute. If one person still carries most of the inconvenience, change the arrangement rather than calling it fair because it rotates on paper.
We have almost no overlap. How can we make decisions without leaving someone out?
Use an asynchronous process for decisions and reserve live time for unresolved points. Name a decision owner, state the question and deadline, share the options and trade-offs in writing, and give affected people a clear way to comment within their working hours. The owner can summarize what was considered, what remains uncertain, and the decision with its rationale. If discussion is still needed, meet with the smallest group that can resolve it and share the outcome.
A reusable planning note:
Work needing live discussion: [item and reason]
People needed: [roles or names]
Candidate slots in local time: [options]
Chosen slot and reason: [slot; why it meets the need]
Inconvenient-time burden: [who and how often]
Async input method and deadline: [where and when]
Decision owner and review date: [placeholders]
If no slot respects stated boundaries, say so plainly and change the process instead of treating one person’s repeated sacrifice as necessary overlap.
A practical checklist
List the work that truly needs live discussion and who must participate.
Collect usual local working windows and stated boundaries.
Compare candidate slots in each person’s local time and verify conversions.
Choose the smallest useful live slot; use written input or smaller discussions for the rest.
If an inconvenient slot is unavoidable, track and rotate the burden transparently.
Record the rationale, async contribution route, decision owner, and review date.
A few more useful answers
Should the team use one fixed overlap slot or rotate it?
Use a fixed slot if it respects stated boundaries without repeatedly burdening the same people. Rotate when an unavoidable inconvenient time would otherwise fall disproportionately on particular teammates, and review the actual pattern.
What if someone cannot attend the chosen meeting?
Share the question, options, and deadline in advance, and provide a clear way to contribute asynchronously. Send a decision summary afterward so the person can see what was decided and why.
When should we revisit the schedule?
Set a review date when choosing the arrangement, and revisit sooner if team membership, work needs, or stated availability changes. Check whether the slot still serves its purpose and distributes inconvenience reasonably.