The all-hands meeting started at 4 PM on a Tuesday and Rahul almost didn't notice anything was wrong until the third slide. Restructuring. A small number of roles affected. Names would follow in individual calls over the next 48 hours. He closed his laptop, made tea, and didn't think much more about it — not because he was careless, but because by every measure he could see, there was no version of that list with his name on it.
He had topped the quarterly performance rankings for two consecutive years running. His client satisfaction scores were the highest in the entire department, not just his team. He had shipped three projects ahead of schedule in eight months — something nobody else on the team had managed even once. When the calls started going out the next morning, he kept working, genuinely unbothered, right up until his own calendar invite landed at 11:40 AM.
His was the first name on the list.
The call lasted fourteen minutes. His manager read from something — not unkindly, but clearly scripted — and when Rahul asked the only question that mattered, the answer came back short enough that he wrote it down afterward, word for word, on a sticky note that he kept for weeks.
"Low organisational visibility. I had the best numbers on the team and they let me go because half the people in that decision had no idea what I looked like."
Rahul had been fully remote since the day he joined, almost three years earlier. He had met maybe four colleagues in person, ever, at a single offsite that ran for two days. He showed up to every meeting, delivered every project, answered every message — and otherwise kept almost entirely to himself in the digital spaces where the rest of the team's culture quietly got built. He wasn't rude or withdrawn exactly. He just didn't see the point of chatting in the general Slack channel when there was actual work to do.
When the people in that restructuring room sat down to figure out which roles could go, his name came up early. Not because the work was weak. Because nobody in that specific room felt they knew him well enough to push back on his behalf.
The Bias That Followed Everyone Home
What happened to Rahul has a name researchers have been studying for years, well before remote work became the norm: proximity bias. It's the well-documented tendency for managers to favour the people they see, chat with informally, and personally associate with the rhythm of a team — regardless of what the actual output looks like on paper.
The assumption going into the pandemic-era shift to remote work was that this bias would simply fade, since nobody was physically near anybody else anymore. What happened instead is that it relocated. Physical proximity got replaced by digital presence — how often someone's name shows up in conversations, how visibly they contribute outside their narrow lane, how known they are to the people sitting one or two levels above their direct manager.
A Microsoft WorkLab study found that remote employees were over twice as likely to report feeling overlooked for promotions and opportunities compared to in-office peers, even when their performance was measurably equal or better. The gap doesn't stay flat either — it widens sharply during layoffs and restructuring, when decisions get made fast and personal familiarity quietly becomes a stand-in for actual value.
Rahul had optimised entirely for output and not at all for presence. In a stable year, that trade-off is invisible — nobody notices, nobody asks. In a restructuring, where decisions get made under time pressure inside a room he was never going to be in, it cost him the entire job.
What "Low Visibility" Actually Looked Like, Specifically
The phrase his manager used sounds like the kind of corporate language designed to soften something. It isn't, really. It's a fairly precise description of a pattern that had been building for three years without anyone naming it.
Rahul never posted in the company-wide Slack. He skipped every optional town hall and virtual social hour without exception. He gave updates only when someone asked him directly, never proactively. He had no working relationship with anyone above his direct manager — not because he'd been excluded, but because he'd never tried to build one. His LinkedIn hadn't been touched in close to three years.
No presence in cross-team conversations. No relationship with anyone beyond your direct manager. Never volunteering for anything outside your core scope, even small things. Strong work that nobody outside your immediate team could describe if asked. A LinkedIn profile that hasn't moved in years, signaling — fairly or not — disengagement.
None of this appears in any job description anywhere. All of it, in practice, quietly shapes how dispensable a person looks the moment a room full of decision-makers needs to shorten a list.
The Conversation That Came After
A week later, once the initial numbness had worn off enough to think clearly, Rahul called his manager and asked the question directly: if his performance had genuinely been the best on the team, how was his role the one that got cut? His manager's answer was careful, but honest in a way Rahul later said he respected, even through the anger.
The decision hadn't been his manager's alone. It had gone through a small group, most of whom knew Rahul only as a name on a roster and a number in a dashboard. When the question of who could be cut came up, his manager had pushed back on his behalf — but without anyone else in that room who actually knew Rahul or his work, one voice wasn't enough to outweigh a spreadsheet.
"He told me straight out he couldn't fight for me alone," Rahul said to a former colleague afterward. "He needed someone else in the room to back him up. There was nobody."
The Response Was Immediate and Pretty Divided
Rahul found a new role within six weeks. The new company is also fully remote, which he chose on purpose — he wanted to test whether the problem had really been remote work itself, or just how he'd shown up inside it. This time, he spends a deliberate thirty minutes a week doing nothing but being visible: commenting on internal posts, weighing in on discussions slightly outside his lane, sending short updates to stakeholders who never asked for one.
His output hasn't changed at all. His presence is almost unrecognisable from before.
He hasn't had a formal performance review yet at the new place. But three people on the leadership team already know his name on sight, not just from a directory search. He made sure of that in the first month, on purpose, in a way he never once thought to do in three years at the last job.
"In a room full of people deciding who stays, the person protected is rarely the best performer on paper. It's the one someone in that room knows well enough to actually defend."