Treat time-zone friction as a team problem
A meeting at a comfortable hour for headquarters may fall at breakfast, dinner or bedtime for someone elsewhere. Scheduling software can show the overlap, but it cannot decide whose time matters. When the same people repeatedly join outside their usual hours, the team has made an operating choice, whether or not anyone intended to.
Start by making working hours visible and asking people which parts of their day they can occasionally shift, if any. Do not assume that a person can move their schedule because they work from home. Care responsibilities, access needs, commuting arrangements and the need for uninterrupted rest all affect what is workable. A fair approach does not promise that nobody will ever be inconvenienced; it prevents convenience for one group from becoming a standing cost for another.
Decide what actually needs a meeting
Before sending an invitation, name the decision or activity that requires people to be present together. A difficult disagreement, a collaborative design session or a sensitive conversation may benefit from live discussion. A status update often does not. Move routine updates into a shared document or project space where people can read, ask questions and respond during their own working hours.
For necessary meetings, use a few agreed overlap windows rather than filling every available gap. Rotate times when no window is reasonable for everyone, and record who bears the early or late slot. Rotation should be meaningful: moving a meeting by thirty minutes may not help a colleague whose workday has already ended. Invite only the people needed for the discussion, then share the outcome with others. Someone should not have to attend at night simply to learn what was decided.
If a meeting falls outside a participant’s usual hours, make declining or contributing in advance a genuine option when their live presence is not essential. Send the agenda and decision questions early enough for that option to work. Afterwards, publish the decision, its owner and any open questions in a place the whole team can find.
Build handoffs that do not require instant replies
Consider an illustrative product team with colleagues in three regions. One group finishes work as another begins, and a third has only a short overlap with either. If every question waits for a call, progress slows and people begin checking messages after hours. Instead, the team can leave a handoff note at the end of each workday: what changed, what is blocked, what decision is needed and where the relevant files are.
Good handoffs make the next action clear. A request such as “Please review this” leaves too much to guess. “Please check whether the proposed wording matches the agreed requirements, and comment by your Thursday afternoon” gives the recipient a task and a local working-hours deadline. Agree on which channel holds the authoritative decision so that people do not have to reconstruct it from scattered chats.
Set response expectations by urgency. Most questions can wait until the recipient’s next working day. A small number of genuine incidents may need a separate escalation path with a named person who is scheduled to respond. An urgent label should not turn every request into an exception. If after-hours coverage is part of the job, plan and share it explicitly rather than relying on whoever happens to be awake.
Make participation possible for people who miss the call
Asynchronous work is only fair if it gives people influence, not just information. Circulate proposals before decisions are made, leave time for comments across regions and state when the discussion will close. For a substantial change, identify who can decide, who needs to be consulted and how objections will be handled. Otherwise, the people online together may settle the issue before distant colleagues have started work.
Written notes also help people who process information better at their own pace or cannot reliably use live audio. Keep them concise but complete: capture the options considered, the reason for the choice and the next step. If the team uses recordings, do not make watching a long video the only way to catch up. A written summary is easier to search and quicker to use.
Check whether the burden is really shared
Review the pattern periodically, not just the calendar for next week. Who attends outside normal hours? Who gets uninterrupted focus time? Whose feedback arrives too late to affect a decision? Ask people privately as well as in group discussions, since a colleague may hesitate to object to a schedule that suits most of the team.
Then change the practice, not merely the wording of the policy. That might mean alternating a recurring meeting, replacing it with written updates, moving a decision deadline or handing meeting ownership to another region. Distributed work becomes more sustainable when people can contribute without demonstrating commitment through constant availability.
