Managing Across Time Zones

Map time and work dependencies

Document each person's normal local working pattern, relevant holidays, customer coverage, and critical dependencies, respecting privacy and organizational policy. Then map where work truly needs interaction: decisions, incidents, creative discussion, coaching, handoffs, or access to a specialist. Do not assume every recurring meeting requires everyone.

Examine where delay accumulates. A request that arrives without context near another region's end of day can lose a full work cycle, while a well-prepared handoff can continue. Identify decisions or approvals concentrated in one location. The goal is not constant motion; it is predictable, responsible flow with humane boundaries.

Design for asynchronous progress

Write requests with the purpose, current state, evidence, decision needed, owner, and relevant timing. Keep plans and decisions in shared systems rather than private chat history. A receiving colleague should be able to advance the work without reconstructing context from several unavailable people or guessing which version is authoritative.

Define handoff states such as ready for review, blocked pending a named answer, or approved for the next action. Provide examples suited to the team's work. Avoid creating so much documentation that maintaining it displaces the task. The test is whether the next person can make a sound move with less synchronous recovery.

Use synchronous time fairly

Reserve overlap for decisions, relationship-sensitive topics, ambiguous problems, and collaboration that materially benefits from live exchange. Send context beforehand and record the outcome. If someone cannot attend, state how their input can enter before the decision and how they will learn the result rather than treating attendance as the only path to influence.

When an off-hours meeting is genuinely necessary, rotate the inconvenience where feasible and give notice. Consider role, accessibility, caring responsibilities, and employment policy with qualified support. Rotation is not automatically fair if the burden affects people differently. Managers should inspect impact and alternatives rather than count exceptions mechanically.

Set boundaries and inspect equity

Agree on channels for ordinary requests, urgent incidents, unavailable owners, and expected acknowledgement based on actual work needs. State that delayed response outside normal hours is expected unless a role has a formally established coverage responsibility. Do not invent universal availability standards or rely on employees to signal exhaustion before design changes.

Review decision participation, meeting burden, handoff failures, advancement opportunities, and access to managers across locations. Ask distributed members for specific examples of exclusion or delay. Adjust ownership, records, rotations, and meeting design from that evidence. A remote-friendly statement is not proof that everyday work offers comparable access.

Repair a cross-region handoff

A product team in one region sends late-day review requests to an operations team elsewhere, but missing context causes repeated clarification cycles.

1. Map the handoff and identify the decision, evidence, version, owner, and deadline information that recipients repeatedly need.
2. Create a concise request format and a shared state showing whether work is ready, blocked, or decided.
3. Use the team's limited overlap for disputed cases and process learning rather than reading every request aloud.
4. Review actual handoffs and local-time burden, then revise the format and ownership from the team's own evidence.

Distributed work map

Build this map with the team to make time, authority, handoffs, and participation visible without requiring constant availability.

• Coverage context: local work patterns, holidays, customer needs, formal responsibilities, and privacy or policy constraints.
• Dependency map: work, sender, receiver, decision, required evidence, authoritative location, and unavailable-owner route.
• Interaction design: asynchronous default, shared record, overlap purpose, input route, recording, and off-hours rotation.
• Equity review: local-time burden, access to decisions and managers, handoff delays, opportunities, exceptions, and changes.

Common mistakes

• Treating personal off-hours availability as the main solution to a poorly designed handoff.
• Making important decisions in one region's meeting without a route for absent experts to contribute.
• Declaring a fixed overlap or response rule fair without examining roles, policy, impact, and team evidence.

Try one

Sources

• Atlassian working agreements playA facilitated method for agreeing how a team will communicate, decide, and work together.
• CIPD line management factsheetProfessional guidance on the people-management responsibilities and support needs of line managers.