One-to-ones across time zones: who moves, and how to rotate it

A recurring one-to-one should move around the clock, or the same person pays for it every month. Ours sat at nine in the evening for the Manila half of the team.

The call that always fell at nine

I worked from Lisbon and my most experienced analyst worked from Manila, seven hours ahead. The only slot that suited my mornings fell at her nine at night.

She agreed without complaint, and for five months the call started at nine. Her answers got shorter in month three and stopped arriving in month five.

I read that as disengagement. It was fatigue, and the schedule had been designed so that only one of us could notice it.

The default hides a subsidy

Every recurring meeting has a default time, and the default is set by whoever holds more power. Nobody decides this, which is why nobody reviews it.

A nine in the evening call looks like a small accommodation from the manager’s side. From the other side it removes the whole evening, twice a month.

The subsidy is invisible because it never appears in a calendar. It appears in the quality of the conversation six weeks later.

Rotate the inconvenience

We changed the pattern rather than the time. Two calls a month now alternate: one at eight her time, one at eight mine, and neither at nine.

Each of us absorbs one awkward slot per month instead of one of us absorbing both. The total inconvenience stays the same and the distribution changes.

The first rotated call was noticeably better. She arrived with a list rather than a polite summary of a week she had already finished.

Anchor the call to the report’s week

Where a rotation is impossible, the call should sit inside the report’s working day. The manager has more control over the rest of their own calendar.

That rule sounds generous and is mostly practical. A person at the end of their day gives you decisions, and a person at the start gives you thinking.

For a one-to-one, thinking is the product. The status update is what the written note is for, and it can travel without either of you awake.

What a call carries that text cannot

Tone, hesitation, and the half-sentence that reveals a problem. None of those survive in a written update, and all of them justify a call.

So the call should be spent on the things text is bad at. Ours now begins with one question about load and ends with one about the next month.

Everything factual moves into a note beforehand. Reading four lines takes her three minutes at a time she chooses, which is the whole point.

The forty-minute limit

A cross-time-zone call has a hard cost at both ends, so it should have a hard limit. We set forty minutes and put the first ten aside for reading.

The limit did more for quality than any agenda. With less room, we stopped covering six topics badly and started settling two properly.

Anything unfinished becomes a written thread the same day. Writing it while both of us still remember why it mattered takes four minutes.

Notes before, not after

She writes four lines the day before: what moved, what stalled, what she needs, what she wants to discuss. I read them before the call starts.

The order matters more than the content. Writing first forces her to decide what the conversation is for, which is usually the hardest part.

After the call I write the decisions, not the discussion. That note is the only thing either of us will still have in eight weeks.

When the gap passes six hours

Beyond six hours of separation the rotation starts to break, because one slot lands outside any reasonable day. At nine hours, overlap disappears entirely.

At that point the one-to-one should become fortnightly and longer, with a written exchange in between. Frequency is the variable to sacrifice, not sleep.

We tried a weekly twenty-minute call across nine hours once. It produced six months of short conversations that neither of us could recall afterwards.

Protecting the worse slot

Whoever takes the inconvenient hour should get something back in the same week. A late start the following morning, or no early meetings for two days.

This is not a perk. It is the only way to keep the arrangement honest over a year, when goodwill has stopped being a reliable currency.

We wrote it into the team’s working agreement. Fairness that depends on a manager remembering it in a busy month is not a policy at all.

Audit the calendar quarterly

Once a quarter I list every recurring meeting and mark who attends outside their normal hours. The list is short and the pattern is always obvious.

Last quarter one person carried four awkward slots and nobody had noticed. Two of those meetings had been mine to move for eight months.

The audit takes fifteen minutes. Without it, the same three people absorb the cost of a globally spread team and nobody says so.

What rotation costs the manager

Rotation costs me two early mornings a month and a small amount of planning. It also removed the most common reason for a resignation I did not see coming.

The harder cost is attention. A rotated schedule cannot be booked once and then forgotten, and that small friction is exactly why it works.

Managers who resist rotation are usually protecting a habit rather than a result. The habit is theirs, and the result belongs to both people.

The test of a fair schedule

Ask each person on the team what time their calls fall in local hours. If the same names keep appearing at the edges, the schedule is not fair.

Fairness here is not equal suffering. It is that no one person systematically spends their evening on a meeting that could have been moved.

Our calls now cost each of us roughly the same, measured in hours that are awkward rather than hours that are convenient. That was the whole design.

A calendar hides the hours it costs, because it shows only the ones the manager keeps. List every recurring meeting by local hour: whose evenings sit in the column you never open?