Being the Only One in Your Timezone

Mei works in Auckland. Her team is in San Francisco and Berlin. Most mornings she opens Slack to sixty unread messages, and buried in them is a decision made overnight: a schema change she'd have flagged a real problem with, now four replies deep and basically settled. The daily standup is 6am her time. The "quick sync, won't take long" someone booked yesterday lands at 11pm. On the org chart she's a full member of the team. In lived experience she's running a week permanently out of phase with everyone she works with.

There's a version of remote work that's much harder than the rest. It's being the one person who sits many hours out from wherever everybody else clusters. Most advice about distributed teams quietly assumes a group that's spread but overlapping, a few Europeans and a few Americans who can all make a 4pm London call feel bearable. Being the outlier is a different job. Nobody warns you about it, and if you're the manager, you usually can't feel it at all.

The team has a center of gravity, and it isn't you

Distributed teams are rarely smeared evenly around the planet. They clump. You get a knot of people in US Pacific and Mountain, maybe a couple in New York, one or two in Western Europe. That mass becomes the center of gravity, and every default settles around it without anyone deciding: the meeting times, the hours the channel is loud, the window when decisions actually happen. If you live inside that mass, the defaults fit you like they were made for you, because they were.

If you're the single person in GMT+12 while the team's weight sits at GMT-8, every one of those defaults is set against you, and no one did it on purpose. There's no villain to argue with. It's just gravity. The standup landed at 9am because 9am works for the eight people who picked it, and it happens to be your bedtime. That's what makes it hard to name. Complain and you sound like you're blaming people for a decision nobody consciously made.

What it actually costs you

Start with meetings, the most obvious one. Every live meeting is at your bad hour. Not now and then. Structurally, forever. The usual fix is to rotate the awkward slot so one person doesn't always eat it, which is good advice for a team with two or three clusters. It falls apart when you're the sole outlier, because there's nothing to rotate into. Move the call an hour and it's still the middle of your night. The pain can't be shared around a table of one. So the honest answer here is usually not rotation. It's cutting the meeting or having the majority occasionally move their own hours, and most teams reach for neither.

Then there's the decision drift. A thread catches fire during the team's afternoon, someone floats a plan, four people react, and by the time you wake it reads as agreed. The async decision ritual is supposed to protect against this: write a short proposal, put a deadline on input, treat silence as consent. But "silence as consent" has a failure mode nobody talks about, which is that the person asleep for the whole window counts as silent. You didn't consent. You were unconscious. You inherited a decision you'd have changed, and unwinding it now costs political capital you'd rather spend elsewhere.

The quietest cost is that you drift out of sight. Leadership builds its picture of you from the moments they witness, and the outlier gives them the fewest. You ship excellent work into hours when nobody who matters to your career is awake to see it. This is how the far-timezone person gets overlooked at promotion time despite a track record that would be obvious if anyone had been in the room. Your output is real. It's just landing in a timezone with no audience.

Be honest about the one real upside

It isn't all tax. The outlier gets something the people in the cluster would kill for: the cleanest stretch of uninterrupted hours on the whole team. For most of Mei's day, no one who could ping her is even conscious. That's the setup every productivity book begs you to engineer, handed to you for free. If you learn to treat those silent hours as your best deep-work block instead of a lonely void, being the outlier can make you the most focused person on the team. I've seen people out-ship an entire cluster on the back of five undisturbed morning hours. The gap that costs you meetings pays you back in concentration, if you let it.

If you're the outlier: refuse the second tier

The trap is drifting into a role where you're technically on the team but functionally a contractor who happens to have a company laptop. Fighting that is mostly on you, because the people who could fix it can't feel the problem.

Make your work loud in writing, louder than feels natural. You've lost the ambient visibility of being seen online, so manufacture it deliberately: the weekly update people actually read, the PR description that explains itself, the decision doc with your name on it. Lean hard on the async-first habits that let work speak without you being awake. If you rely on being seen live, you'll be invisible, because live is the one thing your schedule can't offer.

Push back, politely and by name, when a decision that affects you got made in your sleep. Not to relitigate everything, but to set a norm: anything touching your work gets a proposal with an input window that includes one of your working days. Say it calmly the first few times, and most reasonable teams adjust.

Guard your one or two overlap hours like they're made of gold, because they are. Don't let a status meeting a document could replace colonize the only time you can talk to a teammate in real time. Spend that window on the things that genuinely need a live person.

And say the cost out loud. This is the one most outliers skip, out of some misplaced worry about seeming difficult. Your manager in Denver has no bodily sense that your 9am is his 2pm. "That standup is midnight for me" is new information to him, not a complaint, and most people fix it the moment they understand. Silence gets read as "it's working fine." It isn't, and only you know that.

If you manage an outlier: the load is yours

If someone on your team is the lone person in a far zone, stop expecting them to absorb the whole gap quietly. Rotation won't save them, so sometimes the right call is to kill a recurring sync they can never make and run it async, or to move your own hours a couple of times a quarter so they aren't the only one ever paying in sleep. You'd never ask that of yourself. Ask why.

Watch for the drift on their behalf. The outlier is the person your leadership forms the weakest picture of, so carry their story into the calibration room yourself instead of assuming the work speaks for itself into an empty timezone. And treat "silence equals consent" with suspicion whenever the silent party was asleep for the window. If it affects them, the window includes their day.

The deeper fix might be structural: one outlier is fragile and lonely in a way two people in the same zone simply aren't. If you keep hiring solo people into far-flung timezones one at a time, you're not building a global team, you're building a collection of isolated individuals who each feel like an afterthought. That's a hiring pattern, and you can change it.

The part that stays hard

Some of this doesn't fully resolve, and pretending otherwise helps no one. If you're twelve hours out, you'll always wake into conversations that are half over, carrying a low hum of being behind the beat. This is the operational cousin of the isolation that quietly builds when someone sits far from everyone else. The goal isn't to erase the gap, which you can't. It's to keep it from hardening into a permanent second tier where the outlier does great work, gets thinner recognition, makes every hard call at a worse hour, and eventually just leaves.

You took the outlier seat for a reason. A life you wanted, a family you're near, a job worth the odd hours. It can absolutely work. But it only works if someone actively decides it will, because if you leave it to gravity, gravity has already picked a center, and you're not standing on it.

Let a Bot Handle the Clock

Being the outlier is hard enough without also doing timezone arithmetic in your head every time someone drops a "let's talk at 3" into the channel. Timely reads each person's Slack timezone and converts every time mentioned into their own local clock automatically, so a message written in San Francisco lands in Auckland already saying what it means. It won't move a meeting off your midnight, but it removes one more small tax on the person the defaults forgot.

Add Timely to Slack — Free · See how it works