The Team Member Everyone Had Written Off

When I first joined the company, I inherited a team member with a history of negative performance evaluations. The record made the concern seem clear: low ratings and a perception of difficult peer relationships that previous managers described as persistent.

What the record didn’t capture was the scope of the social damage. Working relationships weren’t just strained. They’d been damaged across most of the teams in the org.

Japan’s employment protections make involuntary separation a slow and contested process, and with a performance record this mixed, that route wasn’t available. Some managers in that position just wait it out instead, hoping the friction builds until the person decides to leave. I didn’t want to manage that way.

What I found when I looked

I reviewed the past evaluations, spoke with their former managers, and gathered peer feedback. When I asked their teammates how they felt working with the team, without naming anyone specifically, they brought them up on their own. What they said didn’t match the record.

They described them as a strong team member with solid technical judgment, someone the team trusted.

The pattern that emerged was different from what the evaluations suggested. Their friction with management came from a tendency to push back hard on decisions they disagreed with. Over time, that conflict had eclipsed everything else they’d done.

The ratings were documented. The reason behind them was more complicated.

I decided to form my own view rather than inherit the one I’d been handed. I spent time with their work and concluded that technical capability was not the issue.

How I approached the coaching

I focused the coaching on how they responded under pressure. When tension surfaced in discussions, they escalated rather than stepped back. I coached them in real time, in those moments, rather than waiting for review cycles.

If they dismissed a teammate’s point in a discussion, I’d pull them aside right after and name it. Not in a formal setting. Just a direct word before the next thing started.

I also gave them the lead on a meaningful technical project, matched to what I’d heard from 1:1s they wanted to work on. That required some groundwork: I had to position the assignment carefully and run interference with stakeholders who had prior impressions of them. The goal was to give them enough room for the work to speak before the relationship history could get in the way.

Their next performance rating came back positive. Working relationships improved, not purely because their behavior changed in meetings, but because delivering well shifted how others perceived them.

A reputation built on friction started to compete with a record of delivery.

What this taught me about inherited situations

Performance problems are often context problems. When someone is struggling, my first question is about the environment they’re operating in, and whether I’m part of the problem.

The harder lesson is about situations where structural constraints remove the easy exits. When you can’t manage someone out, diagnostic rigor stops being optional. Forming your own view matters most precisely when the standard moves aren’t available.

If someone on my team gets a poor evaluation, I carry some responsibility for that. Either I missed the signals or I didn’t create the conditions for them to succeed. That belief is what pushes me to ask harder questions in 1:1s, not just take the surface answer.

---

Choosing not to give up on someone costs something. You absorb the doubt from the people who’ve already decided. You advocate in rooms they’re not in, hold the belief before there’s evidence to justify it, and do the quiet work of keeping the door open when everyone else has closed theirs.

That team member is a friend now. Turns out that’s what the door was for.