When Your Manager Just Doesn't Like You: A Workplace Case Study

Vertika joined a Pune-based MNC at 23, fresh out of college, with the kind of energy that makes managers look good in team meetings. She was sharp, completed her work ahead of deadlines, never escalated problems unnecessarily, and got along well with her colleagues. By every measurable standard, she was a good employee.

Two years in, she had not grown in her role. She had not been given a single high-visibility project. Her performance reviews were average, filled with vague feedback like "needs to show more initiative" and "could communicate more effectively." When she asked her manager for specifics, the conversation would end quickly with something like "just keep doing what you're doing."

Vertika assumed she was the problem. She started second-guessing her work, over-explaining her decisions in emails, volunteering for tasks outside her role just to be seen. She was working harder than she ever had and feeling worse than she ever had.

What Vertika did not know was that her manager, Raghav, had decided she was not "the right fit" within her first three months. She had, unknowingly, corrected him during a client call. Politely, professionally, with full context. But she had made him look uninformed in front of people who mattered to him. He never forgot it.

The Bias That Has No Official Name

What happened to Vertika has a name in organizational psychology: affinity bias in performance evaluation. It refers to the tendency of managers to rate employees higher when they feel a personal connection with them, and lower when they do not, regardless of actual output.

A study published in the Journal of Applied Psychology found that the relationship quality between a manager and an employee, often called Leader-Member Exchange or LMX, predicted performance ratings far more strongly than objective performance metrics. Employees in low-LMX relationships received fewer developmental opportunities, lower ratings, and less access to senior leadership, even when their work quality was comparable to high-LMX peers.

In simpler terms: how much your manager likes you personally shapes your career trajectory in ways that have nothing to do with how well you actually work.

This is not a rare edge case. Research from McKinsey and Lean In consistently shows that access to sponsorship, stretch assignments, and internal advocacy is heavily skewed toward employees who have informal warmth with their direct manager. The formal system, the job description, the performance framework, the HR process, exists alongside an informal system. And the informal system usually wins.

What Raghav Was Actually Doing

Raghav was not dramatically cruel. He did not shout at Vertika or give her false information or sabotage her work visibly. What he did was quieter and, in many ways, harder to fight.

He stopped mentioning her name in rooms she was not in. When a new project came up that would have given her visibility with senior stakeholders, he gave it to Sameer, who had joined six months after her. When Vertika asked to attend an external training program, Raghav said the budget was tight, then approved the same program for another team member two weeks later.

He gave her feedback that was impossible to act on. "Be more confident." "Show more leadership." These are not instructions. They are impressions. And impressions, unlike tasks, cannot be completed.

In performance review cycles, he rated her as "meets expectations" across the board. Which sounds neutral until you understand that in most MNCs, "meets expectations" is the rating that keeps you exactly where you are. It is a ceiling dressed as an assessment.

Vertika had no proof of any of this. She just had the slow accumulation of being passed over, and the growing suspicion that something was wrong that she could not name.

Why Employees Blame Themselves First

When organizational systems appear fair on paper, the natural conclusion for someone inside them is that the problem must be personal. The performance framework exists. HR exists. The appraisal process exists. If the outcome is bad, it must be because of something the employee did or did not do.

This is exactly how biased systems survive. They look neutral from the outside, which means the person being harmed by them carries the weight of the harm as a personal failure.

Vertika spent eight months believing she lacked something. Confidence, communication skills, strategic thinking. She signed up for a public speaking course. She started documenting her work more obsessively. She asked for feedback more frequently, which only made Raghav more distant, since frequent check-ins from her now felt like pressure rather than curiosity.

Psychologists call this self-blame in ambiguous situations an attribution error. When outcomes are bad and causes are unclear, people, especially people who have been socialized to take responsibility, tend to attribute the outcome to internal factors. "I am not good enough" feels more controllable than "the system is working against me," even though the second option is far more actionable.

The self-blame was not weakness. It was a rational response to an irrational situation. But it was also costing Vertika months of energy that could have gone toward solving the actual problem.

When She Finally Saw It Clearly

The shift happened accidentally. Vertika was having lunch with a colleague from a different team, Priya, who mentioned offhandedly that Raghav had described Vertika as "a bit difficult to manage" in a cross-functional meeting. Priya assumed Vertika knew. She did not.

"Difficult to manage" is a phrase that travels fast in corporate environments. It attaches to people and changes how others read them before those people ever walk into a room. Vertika had been carrying that label without knowing it existed.

She went back through two years of interactions with fresh eyes. The training program that was approved for someone else. The project she was never considered for. The feedback that was never specific enough to act on. The pattern was suddenly visible. It had always been there. She had just been looking for her own flaws instead.

What She Did Next

Vertika did three things.

She started building relationships outside her immediate team. She volunteered for cross-functional projects that gave her visibility with managers other than Raghav. Within four months, a senior leader in a different vertical had noticed her work and asked Raghav directly about her growth plans. The question alone changed the dynamic. Raghav could no longer afford to keep her invisible.

She documented everything. Every project, every outcome, every piece of positive feedback from stakeholders. She stopped relying on Raghav to represent her work and started letting the work speak through channels he did not control.

She also had one direct conversation with Raghav, not accusatory, but clear. She told him she wanted to understand what specific behaviors or outcomes would need to change for her to grow in her role. She asked him to put it in writing. He could not. And that inability said more than any performance review had.

What This Case Reveals About Workplaces

Across industries, across cities, there are people sitting in "meets expectations" boxes because the person evaluating them never gave them a fair read. The solution is rarely a single confrontation. It is visibility through multiple channels, documentation as a professional habit, and the gradual understanding that your manager is one data point about your career, not the final word.

Performance reviews are supposed to be about performance. In practice, they are also about relationships, memory, ego, and the very human tendency to reward people who make us feel comfortable. Knowing this does not make it acceptable. It makes it navigable.

How It Actually Ended

Thirteen months later, Vertika left. She had no offer lined up. She had just reached the point where staying cost more than the uncertainty of leaving. Two years of good work, invisible to the one person whose job it was to see it. She decided that was enough data.

Her colleagues were surprised. Raghav told people she had "always seemed a little unhappy here." The label followed her out the door, even as she walked through it herself.

She spent three weeks feeling like she had failed. Then she started interviewing, and the first hiring manager who spoke to her for forty minutes told her she was exactly what his team needed. She had not changed. The room had.

Vertika's story does not end with justice inside the company that failed her. It ends with her making a decision that the company was not going to make for her. That is not a defeat. It is the only move left when the system has already made up its mind.