Fair Promotions on Distributed Teams

Two engineers came up in the same promotion round. One sat in the same city as the VP who ran calibration and had presented at the last two all-hands. The other was in Bangalore, ten and a half hours ahead, and had quietly carried the payments rewrite that quarter, mostly during hours when the American side of the team was asleep. When the room debated the two of them, the first name landed with a nod. Everyone had a specific memory of him being sharp in a meeting. The second name got a pause. "Remind me what she's been working on?" She got the promotion the next cycle, once someone made a case for her. He got it that day, because he didn't need one.

Nothing in that room was malicious. Nobody said "let's favor the person we can see." They just did, because promotion decisions run on memory, and memory is built from the moments you were both in the same place at the same time. On a distributed team, those moments are handed out unevenly by the clock. That's the whole problem, and almost nobody names it.

Promotion runs on a picture in someone's head

Here's what actually happens when a team decides who moves up. A few people sit in a room, physical or virtual, and try to recall each candidate's year. Not their commits, not their tickets, the impression of them. Did they seem like they were operating at the next level? Were they in the rooms where the hard things got decided?

That picture gets built from exposure. Every time you present to leadership, argue a point in a live meeting, or catch the CTO in a hallway and say something smart, you deposit a little into the account that gets read out at promotion time. In a co-located office that exposure is roughly fair; everyone shares the same building. Remote doesn't remove the account, it just makes the deposits wildly unequal and hands the biggest balance to whoever shares working hours with the people who decide.

The far timezone is where the picture never forms

Think about who gets face time with leadership on a distributed team. The live strategy meeting is scheduled for when the head office is awake. The all-hands runs at 10am Pacific. The impromptu "hop on a call" that turns into someone impressing a senior leader happens during the overlap window, which is midday for headquarters and, for the person twelve hours away, either their late evening or a slot they can't make.

So the engineer in Manila or Lisbon or Nairobi does excellent work, ships it, documents it, and is asleep for every single moment when that work would have turned into a personal impression on the people who promote. They become a name attached to good output rather than a person leadership can picture operating at the next level. And when the room tries to recall them, it comes up a little blank, and a little blank is enough to lose a promotion to someone the room can see clearly. This is the same invisibility that makes isolation on remote teams so easy to miss, except the cost here isn't loneliness. It's a career that stalls for reasons nobody in the decision ever says out loud.

Output is visible. The person producing it is not.

Good distributed managers already learned to judge the work by output instead of the green Slack dot. That fixes the daily version of this problem. It does not fix the promotion version, and it's worth being clear about why.

Judging by output tells you whether someone is doing their job well. It's a check you run on your own reports, from close range, with full context on what they shipped. Promotion is a different court. It's decided a level up, by people who don't have that context, working from a much thinner picture than you have. You can know for certain that your engineer in Bangalore is your strongest performer and still watch her lose the room, because the room isn't running your careful output-based evaluation. It's running on impressions, and hers never had a chance to form. The manager did the right thing at the desk and the system undid it a level up.

Write the growth criteria down, or proximity fills the gap

The first fix is the least glamorous and the most effective. Write down what each level actually requires, in concrete terms, before the promotion conversation happens. Not "operates at a senior level," which is exactly the kind of vague bar that gets filled in with whoever the room remembers. Specific things: leads a project of this size, is the person others go to for this class of problem, ships work that holds up without supervision.

The reason this matters on a distributed team is that vague criteria are proximity criteria. When the bar is a feeling, the feeling gets sourced from face time, and face time is exactly what your far-timezone people are structurally denied. A written, evidence-based bar lets you argue for the person in Bangalore using the payments rewrite she led, instead of hoping the room happens to remember her. It moves the decision off memory and onto record, and record is the one field where the sleeping timezone competes evenly.

This is also where durable written documentation stops being a hygiene chore and becomes a career equalizer. The person whose impact lives in shipped, documented work has evidence that survives them being offline. The person whose impact lived in impressive meetings has nothing to show a room they weren't in.

Someone has to carry the story upward

Written criteria get you an honest evaluation. They don't get you into the room. For that, the far-timezone person needs a manager who does the thing an office used to do by accident: make their work visible to the people above.

In a co-located company this happens on its own. Your skip-level sees your report present and notices them in the mix. Remote deletes that for anyone outside the headquarters timezone, which means the manager has to do it on purpose. That's not politics. It's the job. If you manage someone eleven hours away, part of what you owe them is to be the bridge their timezone won't build for them: to say their name in the rooms they can't attend, and to make sure the VP who runs calibration has a specific, recent reason to picture them at the next level.

The recurring one-on-one you keep synchronous is where you find out what to carry. Ask directly what they're proud of and what they want next, because you cannot advocate for a story you don't know, and the person in the far timezone is the least likely to broadcast it unprompted into a channel nobody in leadership reads at their hour.

Rotate the spotlight, don't just wait for volunteers

The last piece is structural, and managers underuse it. The chances to be visible to leadership, presenting at the all-hands, running the incident review, tend to fall to whoever is awake and available when those events are scheduled. Left alone, that means the same headquarters-timezone people get the spotlight over and over, and the same far-timezone people never touch it.

Treat those visible slots as a resource you allocate, not a thing people opt into. Rotate who presents. Record the all-hands and let someone give their piece async when live is impossible, so being asleep at 10am Pacific stops disqualifying them from being seen. When you're deciding who fronts the demo to the executive team, deliberately pass it to the person whose good work has been invisible, not the one who's already fluent in that room. None of this is charity. It's correcting for a bias the schedule introduced, so that the person doing the best work has the same shot at being known for it as the person who merely shares your clock.

The uncomfortable truth is that on a distributed team, being talented and shipping constantly is not enough to get promoted, and pretending otherwise mostly protects the people who don't need protecting. Visibility is a resource, the timezone gap distributes it unfairly, and if a manager doesn't actively rebalance it, the org will keep promoting proximity and calling it merit. The people you'll lose to that are exactly the ones you least wanted to lose, doing their best work in the hours you were asleep, waiting for a room they were never invited into to finally remember their name.

Make the Far Timezone Easier to Include

Half of what keeps distant teammates out of the rooms that matter is the friction of the clock itself, starting with everyone reading a proposed time differently and someone quietly getting left out. Timely converts every time mentioned in Slack to each person's own clock automatically, so when you schedule the review or the demo or the growth conversation, the person eleven hours away sees exactly when it lands for them and can actually show up to be seen.

Add Timely to Slack — Free · See how it works