One-on-Ones Across Time Zones: A Manager's Playbook

Every manager I have spoken to who runs a globally distributed team has the same graveyard: a Google Calendar full of recurring 1:1s that exist on paper but stop happening. The Tuesday 6 PM slot with the engineer in Berlin keeps getting bumped because she has a 4 PM design review that runs long. The Thursday 7 AM with the designer in Sydney quietly gets cancelled when the manager has a hard week.

The 1:1 is the most important meeting on a manager's calendar. It is also the most fragile across time zones, because both sides usually have a buffet of "good reasons" to skip it. Here is how to build a 1:1 cadence that survives.

The problem is structural, not personal

If your 1:1 with a teammate keeps slipping, the answer is almost never "we both need to try harder." The answer is one of three structural problems:

1. The slot is in someone's red zone (their pre-work, dinner, or kid bedtime hours). Anything that happens at the edge of the day gets sacrificed when the day runs long.
2. The cadence is wrong for the time-zone gap. Weekly is too much when every meeting requires one of you to show up early or stay late.
3. The format is wrong. A 30-minute synchronous chat across nine time zones with no agenda is a bad use of expensive overlap.

Fix the structure first. Coaching, mentoring, and trust-building can only happen on top of a slot that actually holds.

Pick a fair anchor

The first decision is who absorbs the inconvenience. There is no version of a 1:1 across, say, San Francisco and Berlin where both sides are inside their 9-to-5. One of you is on the edge.

Three reasonable rules, in order of fairness:

1. Alternate by week. Odd weeks at 8 AM SF / 5 PM Berlin. Even weeks at 9 AM SF / 6 PM Berlin. Both sides absorb a little.
2. The manager absorbs. If the gap is small, the more senior person takes the awkward edge of their day.
3. The teammate absorbs, with explicit acknowledgment. Sometimes the math only works one way. Name it. "I know 7 AM your time is brutal. We will keep these to 30 minutes and you can cancel without guilt."

The wrong rule is "whatever Calendly says." Calendly does not know who has kids, who has a long commute to a coworking space, or who has an immutable 6 PM gym class.

Cadence: the 90 / 30 rule

For 1:1s across more than four time zones of separation, weekly 30-minute meetings are overkill, and they collapse the moment either side has a busy week.

A better default for distant time zones:

• 90 minutes every two weeks for direct reports.
• 30 minutes weekly for skip-levels and stretch mentees.
• Async written check-ins on the off weeks for direct reports.

A fortnightly 90 has a few quirks that work in your favor across time zones:

• It is more important, so it is harder to bump.
• It is less frequent, so the calendar Tetris is less aggressive.
• It is long enough to actually go past the surface ("how was your week?") into real career and project conversations.

The async check-in on the off weeks fills the gap. Two paragraphs from the report, two paragraphs from the manager, in a shared doc. No live time at all.

The doc-first 1:1

The single highest-leverage habit you can build: write the agenda before the meeting, and write it together.

Each report has one running 1:1 doc. Both of you can append to it any time. The night before the meeting, both sides skim the doc, add to it, and arrive already aligned on what matters.

Why this is especially good across time zones:

• The reporter can fill it in during their working hours, the manager responds during theirs. No live time burned on context-setting.
• It captures decisions in the moment, in writing, in the document itself. Across time zones, "I will follow up tomorrow" often turns into "I will follow up next week," and decisions get lost. The doc anchors them.
• Promotion and performance conversations need a paper trail. The doc is the trail.

A simple structure that works:

## Date
- Updates from <report>:
- Updates from <manager>:
- Decisions / asks:
- Action items (with owner and due date):

Make the report own the doc. They drive the agenda. The manager comes with two or three additions. If you, the manager, are filling in the agenda alone the morning of the 1:1, the dynamic is already wrong.

Hybrid format: 30 minutes async, 30 minutes live

For longer 1:1s with bigger time gaps, split the format:

• Days before: 10 to 15 minutes of async writing in the doc from both sides.
• 30 minutes live: focused only on the items that genuinely need conversation. Career stuff, ambiguous feedback, tough interpersonal stuff.
• Days after: 5 to 10 minutes of async follow-up in the doc.

This gives you the bandwidth of a 90-minute meeting in 30 minutes of live time. The expensive part of the day stays expensive but small.

Show the report when the slot is hurting them

A subtle dynamic across time zones: reports often say a 7 AM slot is "fine" because they want to be a good teammate. Six months later they are burned out.

The fix is not to ask. Look. If the recurring slot consistently lives at the very start or end of their humane working window, name it. "I see we have been doing 7 AM your time for four months. I want to move it. What works better?"

A live overlap board makes this obvious. On a Timezoners board with each report's actual working hours, you can see at a glance which 1:1 slots sit in green zones for both of you and which sit on red edges. Run through the board once a quarter and rebuild the slots.

Skip-levels: keep them in humane hours, always

Skip-levels are different from direct 1:1s in two ways. First, they are voluntary on the report's side. Second, they are about psychological safety.

Forcing a skip-level into someone's 7 AM slot kills both. They will not be candid in their first hour of the day, before coffee, talking to their manager's manager. Move skip-levels to the most humane slot you can find, even if it makes them less frequent. Once a quarter at 10 AM their time is better than monthly at 7 AM.

When the report is in your red zone

Sometimes the math only works if you, the manager, take the awkward slot. Two pieces of advice if you are the absorber:

1. Cap it at one per day. If you have three reports across distant zones, do not stack three early-morning 1:1s on a Wednesday. You will become resentful, and your reports will feel it.
2. Block the hour before and after. A 7 AM 1:1 is a worse meeting if you finish it and immediately go into a 7:30 standup. Give yourself 30 minutes to wake up properly and 30 minutes to write up notes afterwards.

Where to go next

• Time zone fatigue: 5 signs and the cure
• The perfect async handoff
• Friday meeting etiquette across time zones

TL;DR

• The structural problem is usually the slot, not the people. Fix the slot first.
• Default to fortnightly 90-minute 1:1s with async check-ins on the off weeks for distant time zones.
• Run every 1:1 from a shared running doc, owned by the report.
• Rotate or alternate who absorbs the awkward slot. Be explicit about it.
• Audit slots quarterly using a Timezoners board to spot the ones that have drifted into red zones.