Remote One-on-Ones Across Timezones

A manager I coached had a standing 1:1 with a report in Lisbon while he sat in Chicago. Their only shared hour was his 8am, her 2pm. Fine on paper. In practice, his 8am was also school drop-off, the occasional dentist, the morning his calendar got raided first when something urgent landed. So the 1:1 moved. Pushed to Thursday, then skipped, then "let's just catch up async this week," then a month went by where they hadn't actually talked.

He thought things were fine. Her updates landed in the channel, her work shipped, no fires. Then she resigned, and in the conversation that followed she mentioned three things that had been bothering her for two months. None of them were in a Slack message. All of them were exactly the kind of thing a person says out loud in a 1:1 and never types into a public channel. He'd had a venue for hearing them and had quietly let it dissolve, one reschedule at a time.

That's the trap with 1:1s on a distributed team. They're the easiest meeting to cancel and the most expensive one to lose.

Why the 1:1 is the wrong meeting to make async

A lot of distributed-team advice, including plenty I've written, pushes you toward async by default. Drop the standup, post updates in a channel, stop making people wake up for a call. That's right for most things. The 1:1 is the exception, and it's worth being clear about why.

A team standup is about sharing information, and information moves fine in writing. A 1:1 is about the stuff that doesn't survive contact with a public channel. The half-formed worry. The "I'm not sure I'm doing this right." The frustration with a teammate that a person will say to your face but would never put in writing where it lives forever and could be screenshotted. The career question they're a little embarrassed to ask. None of that shows up in an async update, because the entire reason it's a 1:1 topic is that it's not safe to broadcast.

So when you turn a 1:1 into "just send me your updates," you don't get an async 1:1. You get no 1:1, plus a status report you already had. The conversation that mattered doesn't move to text. It just stops happening, and you don't notice, because what you stop receiving is invisible by definition. The manager in Chicago didn't see two months of silence as a problem. Silence felt like everything was fine.

Anchor it in your real overlap, then protect that slot

The first practical move is to put the 1:1 inside the hours you and your report genuinely share, and then treat that slot as close to immovable.

If you have a four-hour overlap, easy. If you have ninety minutes, the 1:1 has a serious claim on it. This is the one meeting I'll argue should outrank deep-work protection on the calendar, even though I'm usually the person telling people to guard their focus blocks. A canceled focus block costs you a few hours of output you can recover tomorrow. A 1:1 that quietly dies costs you the only channel where you'd have heard a problem before it became a resignation.

The discipline that actually keeps it alive is boring: don't reschedule it casually. If something urgent collides with it, move the urgent thing or move the 1:1 to later the same day, not to "next week." The moment a 1:1 becomes the meeting you sacrifice when you're busy, your report learns it's optional, and they stop bringing the things that need the room. They'll save those for a meeting that feels solid, and on a distributed team there often isn't another one.

Don't make the same person eat the bad hour forever

When your only overlap is someone's early morning or late evening, the 1:1 lands at a bad hour for one of you. Usually the report, because managers tend to schedule for their own convenience without quite realizing it.

A weekly call at someone's 8pm, every week, indefinitely, is a slow tax on a person who's already isolated by distance. It's the same dynamic that makes a stranded solo hire drift to the edge of the team: the schedule keeps taking from the same person, and no amount of being nice in the meeting offsets the fact that you've made them give up dinner for it fifty times a year.

You can't always fix it, but you can share it. If the overlap genuinely forces a bad hour, take turns eating it. Some weeks you do the early call on your side, some weeks they do the late one on theirs. Treating the inconvenience as something to distribute fairly rather than dump on the lower-status person is most of what a timezone-aware culture actually means in practice. Your report notices who absorbs the cost. They always notice.

Run it off a shared doc, not your memory

The thing that makes a remote 1:1 work across a wide gap is a running shared document, one per report, that both of you add to between meetings.

It solves a specific problem. When you only overlap for ninety minutes and you're both holding things for the next sync, stuff gets forgotten, or it spills into Slack at a bad hour and arrives as a wall of text the other person reads half-asleep. A shared doc gives those thoughts a home. Your report drops in the topic that came up Tuesday while you were offline. You add the feedback you'd otherwise forget by the time you're both awake. By the time the call starts, you both know what it's for, and you spend the scarce live minutes talking instead of reconstructing the week.

This is the same async-first habit of writing things down applied to a meeting that stays synchronous. The doc isn't a replacement for the conversation. It's the thing that makes ninety minutes of conversation a month feel like enough, because nothing gets lost in the eight-hour gaps between your waking hours.

One rule for the doc: it's theirs, not yours. The agenda should be mostly the report's topics, not your status questions. If every 1:1 is you asking what they got done, you've rebuilt the standup and skipped the part that was worth keeping.

Cadence beats duration

Given how hard it is to find the slot, a tempting move is to make the 1:1 monthly and long. Resist that. A 25-minute conversation every week does more than a 90-minute one every month, and it's not close.

The reason is that the small stuff is time-sensitive. The mild frustration that's easy to talk through this week has, four weeks later, either festered into something real or been buried as not worth raising. A weekly rhythm catches things while they're small. A monthly one mostly receives the things that already grew large enough to survive a month of the report deciding whether to mention them, which is exactly the wrong filter. The frustration with a teammate, the quiet "am I doing okay," the early wobble in motivation all decay if there's no near-term venue for them.

If a true weekly is impossible, every two weeks is a reasonable floor. Below that, you're not really running 1:1s. You're running occasional check-ins and hoping nothing important happens in between, which is the same hope that blindsided the manager in Chicago.

The new-hire exception

One case deserves more than the steady-state cadence: someone in their first month. A brand-new remote hire needs more contact, not less, because everything an office onboards for free has to be rebuilt on purpose, and a lot of that rebuilding happens in the 1:1. Daily for week one, tapering as they find their feet. Then settle into the weekly rhythm once they're not drowning. Front-load the contact when the risk of silent drift is highest, then ease off.

The shape is the same everywhere though. The 1:1 is the one recurring meeting where a distributed report can be a whole person instead of a row of green checkmarks in a channel. Protect the slot, share the bad hour, run it off a doc, and keep it frequent. Lose it, and you lose the only place you'd have heard the thing that matters while you could still do something about it.

Keep the 1:1 About the Person, Not the Time Math

The one meeting you can't afford to fumble is the one where someone's deciding whether to bring up something hard. The last thing you want is to open it by working out whose 2pm is whose. Timely converts every time mention in Slack to each reader's own timezone automatically, so "let's keep our 1:1 at 2pm your time" is already clear to both of you, and the conversation starts where it should.

Add Timely to Slack — Free · See how it works