Coordinating Time Off Across a Global Team

A product manager I worked with set a launch for a Tuesday. Everything was staged, the checklist was green, and by 10am her time the launch channel was silent. Her two engineers, both in Bangalore, weren't behind. They were off. It was Diwali, and neither had thought to flag it, because to them it was as obvious as her not working on Thanksgiving. She'd built an entire launch around a day when a third of the people who had to run it were home with their families, phones face down.

Nothing broke. The launch slipped two days. But she spent those two days feeling faintly stupid, and her engineers spent them quietly wondering why anyone would schedule something big on a day the whole country has off. Both were right. Neither had the piece of information the other took for granted.

That's the strange thing about time off on a distributed team. It's the most predictable disruption you'll ever face, holidays are literally on a calendar years in advance, and somehow it keeps ambushing people.

An office makes absence loud

Walk into an office on the day before a long weekend and you can feel it. Half the desks are empty, someone's got a suitcase parked by their chair, the person you needed left at noon and told three people on the way out. Absence in a shared room is impossible to miss. You plan around it without thinking, because the empty chairs do the planning for you.

Distributed teams delete that signal completely. When your teammate in Osaka takes the whole of Golden Week off, nothing on your screen changes. No empty desk, no suitcase, no overheard "see you next Thursday." Their Slack avatar sits there looking exactly as available as always. So you send the message, you wait, and somewhere around hour eighteen of no reply you start to wonder if you said something wrong, when the real answer is that they told you a week ago in a channel you'd already scrolled past.

The absence is just as real. It's the visibility that's gone. And on a team spread across countries, you're not tracking one holiday calendar but five or six, most of which you've never had to think about in your life.

Public holidays are capacity gaps you didn't schedule

Here's the fact that trips up almost every new distributed team: the four countries your team sits in probably share almost no public holidays. The US, Germany, India, and Australia barely overlap on a single date across the whole year. American Thanksgiving means nothing in Berlin. Australia Day means nothing in Bangalore. Lunar New Year can take a chunk of your team offline for the better part of a week while the other half doesn't even notice the date.

Treat those days as what they are: capacity gaps you didn't put on the plan. If a fifth of your team is out for a national holiday, that's not a footnote, it's the same as a fifth of the team being on vacation, and you'd never schedule a launch into that on purpose. The mistake isn't that people take holidays. The mistake is planning as if everyone shares yours.

This is also why your timezone footprint is an architecture decision rather than an accident. Hire across four continents and you've bought yourself four holiday calendars to reconcile, which is fine, as long as you actually do the reconciling instead of being surprised by it twice a quarter.

Put every holiday on one calendar nobody has to remember

The fix for the invisible-holiday problem is boring and it works: one shared calendar that shows every country's public holidays and every person's booked time off, visible to the whole team.

Not a wiki page someone updates twice a year. A live calendar you look at before you schedule anything that matters. Most calendar tools can subscribe to a country's public holidays as a feed, so the dates populate themselves and you're not relying on the person in Tokyo to remember to warn you about a holiday that, to them, needs no warning. Layer everyone's personal PTO on the same view. Now when you go to pick a launch date, the empty desks are back. You can see them.

This is the same instinct behind making time itself unambiguous. The cost of a bare "3pm" and the cost of an unmarked national holiday are the same kind of cost: a small piece of missing context that quietly wastes a day and makes someone feel foolish. You close both gaps the same way, by putting the information where people will see it instead of hoping they carry it in their heads.

Personal time off needs a louder signal

Public holidays at least live on a fixed calendar. Personal vacation is worse, because it's unpredictable and, remotely, close to invisible unless the person going away makes it visible on purpose.

In an office you take a day off and it's self-announcing. Remote, you have to broadcast it, and most people under-broadcast because it feels like bragging or like nobody cares. So the norm has to come from the team, not the individual. Booking time off should mean three concrete things happen: it goes on the shared calendar, it gets a heads-up in the relevant channel a few days before, and the person sets a Slack status with their return date so the message stays visible while they're gone. "Back Monday" on an avatar does more to prevent a stalled thread than any policy document.

The part people skip is the handoff. Leaving for a week without saying where your in-progress work stands is how you become the reason a project freezes while you're on a beach with no signal. Before you log off for real time away, leave the same kind of note you'd leave for a clean handoff across timezones: what's in flight, what's blocked, who to ask instead of you. Vacation shouldn't turn one person into a single point of failure any more than a normal Friday should.

Cover the gap, don't be a hero about it

When someone's out, the work they normally catch doesn't stop needing to be caught. On a distributed team this bites hardest when the person who's off is the only one awake during a certain window. Your one engineer whose afternoon overlaps with the Americas takes a week in Bali, and suddenly there's a six-hour stretch every day where a customer question can land and nobody's around to answer it for half a day.

The answer is to name coverage before the person leaves, not to quietly hope it works out. Who's watching that channel while they're gone? Who's the backup reviewer? It doesn't have to be heavy. It has to be assigned to a specific human, because work that belongs to everyone belongs to nobody, and "the team will keep an eye on it" is how a customer waits two days for a reply during someone's vacation. Spreading the coverage around also keeps you from leaning on the same reliable person every single time, which is its own slow way of burning someone out.

The unlimited-PTO trap

I'll say the unpopular thing. "Unlimited PTO" usually makes the problem worse on a distributed team, and I'd think hard before adopting it.

The pitch sounds generous. In practice, when there's no defined amount, most people take less, not more, because they've got no number telling them what's normal and they're privately afraid of looking like the one who slacks off. That fear is sharper when you're remote, where your output is the main thing colleagues see of you and logging off for two weeks feels like disappearing. So people quietly grind, skip the break they needed, and the team loses the recovery that keeps good work sustainable.

If you want people to actually rest, give them a real floor and push them to hit it. A stated minimum, "everyone takes at least four weeks, and yes we mean it," does more than an unlimited policy ever will, because it replaces a vague permission with a concrete expectation. This is the kind of norm that has to be written down and modeled from the top, not left to each person to negotiate with their own guilt. When the founder visibly takes three weeks and hands off cleanly, everyone else exhales and does the same.

Time off on a global team isn't a scheduling nuisance to be tolerated. It's a real, recurring input to how much your team can do in any given week, and the teams that treat it that way stop getting ambushed by a holiday they could have seen coming for a year. Make absence visible again. The empty desks were doing more work than anyone realized.

Stop Getting Ambushed by a Holiday You Never Saw

The first place a distributed team loses track of each other is time, and that's before anyone leaves for vacation. Timely converts every time mention in Slack to each reader's own timezone automatically, so "let's regroup at 2pm when Priya's back" reads correctly for everyone and one less thing depends on people doing the math in their heads.

Add Timely to Slack — Free · See how it works