Coordinate decisions across time zones

A practical reference for global collaborators

Northstar Services is a fictional example. Its teams work across Singapore, Berlin, and Toronto. Make decisions asynchronously when people do not need to be online together; use shared overlap for discussion that benefits from live exchange; and make the decision owner, deadline, and outcome visible.

Start by identifying who is affected and what input is needed. Compare those colleagues’ working hours before proposing a meeting, and state each deadline with its time zone. Do not treat one region’s workday as the default.

Find a usable overlap window

Compare the working hours of the people whose input or decision is necessary—not just the project lead’s calendar. When proposing a slot, state the date, time, and time zone; local dates and times can shift with daylight-saving changes.

If no reasonable overlap exists, use an asynchronous decision rather than repeatedly assigning the same region an early or late meeting. Reserve live time for resolving a genuine disagreement, exploring trade-offs, or building shared understanding.

Choose a coordination method

A fictional decision deadline shows how asynchronous input can reduce the need for a shared meeting window.

Choose a coordination method
Situation Coordination method What to record
Several regions need to contribute, but no practical shared window exists. Request written input asynchronously; name an owner and a deadline with a time zone. Decision question, options, affected regions, owner, deadline, outcome, rationale, and unresolved concerns.
The team must compare trade-offs that are hard to resolve in writing. Hold a focused discussion in a fairly chosen shared window; send the question and options beforehand. Purpose, proposed local times, ways to contribute, decision owner, and written outcome.
Worked example: Northstar’s fictional team must choose one of two release-note formats. Its Singapore, Berlin, and Toronto colleagues have limited overlap. The decision owner posts both formats on Monday and requests comments by Wednesday at 16:00 UTC. Each participant checks the local date and time for that specific deadline; a calendar date is needed to account for seasonal clock changes. After the deadline, the owner records the selected format, why it was chosen, the input considered, and any unresolved concern. Verify time-zone conversions and local dates for the actual decision.

Make asynchronous decisions clear

A written decision request should let colleagues contribute without being online together. The decision owner should:

  1. State the decision and why it matters now.
  2. Describe the options and practical trade-offs.
  3. Name the affected regions or roles and the input each can provide.
  4. Set a response deadline with its time zone and identify the decision owner.
  5. After the deadline, record the decision, rationale, input considered, and unresolved concerns where the team can find them.

Worked example: “Which release-note format should we use for the next update: concise bullets or a short narrative? Please comment on readability for your audience by Wednesday, 16:00 UTC. I’ll record the decision and rationale after reviewing the input.”

Live discussion

Rotate meeting times fairly

When live discussion is necessary, compare proposed times across the affected regions before sending an invitation. Alternate inconvenient meeting slots across recurring cycles rather than repeatedly placing the burden on the same location. Publish the upcoming rotation early enough for people to plan.

Anyone who cannot attend should have an equivalent written way to contribute: share the context and questions beforehand, accept input before the decision deadline, and record the outcome afterward. Attendance at a particular hour should not be the only way to make a relevant point.

Questions and answers

Use the team’s agreed decision owner and established escalation route.

What if there is no reasonable overlap?

Use an asynchronous decision when written input is sufficient. Name the owner, options, affected contributors, and a deadline with a time zone. Schedule a live discussion only when it adds value that written input cannot provide.

Does silence before the deadline mean agreement?

Do not assume that silence is approval. The decision owner should record which input was received, identify remaining concerns, and follow the team’s agreed decision practice before finalizing an outcome.

What if I cannot attend a rotated meeting?

Share your input in writing before the stated deadline. Ask the organizer to include the decision and relevant discussion in the written outcome so you can follow what was decided.

What counts as an urgent exception?

Use the team’s established, approved escalation route for urgent work. This page does not establish a new route or contact. If you are unsure which approved route applies, ask the responsible team or manager through your organization’s existing channels.