When a Teammate Changes Timezones

Priya was the London one. For two years her name sat in everyone's head next to "GMT, replies before New York has lunch." Then she spent three weeks in Bali visiting family, kept her calendar exactly as it had always been, and the team kept pinging her at what they thought was her early afternoon. It was her late evening. Work that used to clear in a day started taking two. Nobody had done anything different. The map in their heads just quietly went wrong, and no one corrected it, because on a distributed team there is no doorway to watch someone walk through carrying a suitcase.

That is the odd little gap this opens up. In an office, a colleague leaving for a month is impossible to miss. The desk sits empty, or they mention the trip at standup, or you notice the tan when they get back. Remote, a person can move a third of the way around the planet and, unless they say so out loud, nothing in your daily experience of them changes except that their replies turn slow and start landing at strange hours. You feel the effect for days before you ever learn the cause.

A person's timezone is data other people run on

We treat where someone is as a private fact, theirs to know and mostly none of our business. On a distributed team it is neither private nor irrelevant. Where a teammate sits decides when your message reaches them awake, where the one hour you can both make a call actually falls, and how long a question will really take to come back. It is a shared input the same way a bare "3pm" dropped into a channel is a shared input everyone silently converts wrong. When it changes and the change is invisible, everyone downstream keeps doing their arithmetic on a stale number.

This is the cousin of the daylight saving problem, where the clocks move under a meeting nobody touched, flipped around. There the clocks move and the people stay put. Here the people move and the clocks stay put. Same result either way: the offset you built your week on is briefly, silently false. The one mercy of daylight saving is that it runs on a published schedule. A teammate's sudden three weeks in Lagos does not.

The two ways the traveler makes it worse

Left to instinct, the person who moved tends to pick one of two bad options, and both make things harder than just saying something would have.

The first is to keep home hours. The traveler decides to hold their normal schedule so nothing changes for the team, which sounds considerate right up until you do the math. Holding London hours from Bali means working 4pm to midnight local, eating dinner at one in the morning, sleeping at three, and doing that for three weeks. I have watched people torch a real vacation this way, half-there at the family dinner and half-there in Slack, no good at either. It is the same trap as never finding your evening's off switch, just relocated somewhere with better weather.

The second is to quietly flip to local hours and disappear. Shifting to the new zone is the humane thing to do for your own sleep, but if you tell no one, the overlap window the team leaned on to reach you simply evaporates. The 9am call you always shared is now 4am for you, so you are not in it, and the colleague waiting on your sign-off sits blocked for a full extra day with no idea why. You did the right thing for yourself and left everyone else guessing.

Both are avoidable with one move. Say the thing, in their clock, before you go.

Make the change loud

The fix is almost embarrassingly simple, and hardly anyone does it cleanly. Announce the shift the way you would announce time off, because operationally that is close to what it is: your usual hours are gone, and different ones have taken their place. It runs on the same instinct as making an absence visible on a shared calendar instead of letting people discover it by ping. A zone change is a partial absence. Treat it like one.

In practice that means posting in the team channel before you leave, written in each affected cluster's own clock. Something as plain as: "From the 3rd to the 24th I'm in Manila. My hours will roughly be 9am to 5pm there, which is late evening in New York and early morning in London. For anything urgent during your day, expect me the next morning mine." Update your Slack timezone to where you actually are rather than where you usually live, so your profile clock and every tool that reads it tell the truth. Slide your calendar working-hours block to match. If you have a standing 1:1 or a team sync, flag that it needs rescheduling for the trip instead of assuming it still lands where it always did, the same fairness you would bring to any meeting you are asking people to cross a timezone for.

Then choose your hours on purpose instead of drifting into them. There is a genuine decision here and it turns on the trip. A one-week conference in a neighboring zone? Keep your home hours; it is short and the drift is small. A month with family eleven zones out? Shift to local, guard your sleep, accept that you will fall outside the usual overlap, and build the handoffs around that. The only wrong answer is to not decide, let whatever happens happen, and leave the team to figure it out by watching your reply times get weird.

What managers should watch for

If you run the team, two things land on you. First, make announcing a zone change the normal, expected thing, so nobody feels high-maintenance for posting "I'll be in Portugal for a fortnight, here are my hours." The people who most need to say it, the junior folks who worry that any wrinkle makes them look flaky, are exactly the ones who will stay quiet unless you have made it plainly ordinary. Model it yourself the next time you travel.

Second, watch for the silent version. When someone's replies have gone nocturnal and their messages keep landing at 3am their supposed time, resist reading it as heroic dedication. Ask. They may be traveling and quietly grinding themselves down on option one, and a manager saying "shift to local hours, we'll manage" is often the permission they were waiting for. This is a piece of managing by output rather than by the green presence dot: where a person physically sits matters far less than whether their work is visible and moving, and a traveling teammate on decent sleep will beat a stationary one running on fumes every week.

The permanent version

Everything above gets sharper when the move is not a trip but a life change. Someone relocates from Toronto to Lisbon, and now the team's whole overlap arithmetic has changed for good rather than for three weeks. That deserves more than a channel post. It is worth a short, deliberate conversation about which meetings still work, which handoffs now cross a night that used to fit inside one day, and whether the move has quietly turned a comfortable four-hour overlap into a painful one. Far better to redraw the map on purpose than to notice six weeks later that the two people who need to talk every day now share ninety usable minutes.

It all comes down to refusing to let an assumption stand in for a checked fact. Everyone on a distributed team walks around with a mental map of who is where and when they can be reached. The moment you move, for a week or forever, you have made everyone's map wrong and you are the only person who knows it. So say so, in their time, before they find out the slow and expensive way.

Keep the Map Honest When Someone Moves

Half the battle is making sure a time still means what you meant once a teammate's location shifts. Timely reads each person's Slack timezone and converts every time mentioned in the channel into their current local zone, so the moment a traveler updates their profile to where they actually are, everyone's messages start landing at the right hour for them automatically. One less thing to track when a teammate is somewhere new.

Add Timely to Slack — Free · See how it works