Hard Lessons From the Worst Performance Review I've Ever Received

Published August 6, 2026

Years of strong ratings and back-to-back promotions came before the review that blindsided me. Nothing about my role or my responsibilities had changed enough in the final year to explain what came next.

That year, the ground had already started shifting under me. I'd been strung along on a new title and a new role — always close, never final. I'd also been pulled off workshops and design work I used to run, the kind of work with visible impact, and shifted onto busywork instead: slide decks I built and revised that, as far as I could tell, nobody ever actually looked at or used. My autonomy kept narrowing instead of growing the way years of strong ratings should have earned it.

Part of what fed the review, I learned afterward, was one colleague: a newer, inexperienced Business Analyst who had rejected my mentoring and complained about me behind my back all year. He was quietly relaying that complaint to my manager, who was also fairly new and inexperienced in the role. Nobody raised any of it with me directly while it was happening. I only found out afterward, once it was too late to respond to any of it in real time.

The rating that came back was “Inconsistently Met Expectations,” with a performance improvement plan attached. It didn't square with a year of positive feedback in every one-on-one, and it didn't square with the years of ratings that said the opposite. My manager opened the conversation by talking about how hard this was for him to deliver, which meant the first few minutes of my own review were spent on his discomfort instead of my performance.

By the time that review landed, I had already accepted a new job. I'd been watching the promotion promises slide and the real work drain out of my role for months, and I'd made my decision before I ever sat down in that room.

I gave one week of notice, and I didn't feel guilty about it. The same company that expected two to four weeks from departing employees had laid people off with none. If the notice period only runs one direction, I don't owe the longer version of it.

My manager asked, not long after, whether I was leaving because of the review. The timeline alone made the question absurd: it would have meant landing a new job in the three days between the review and my notice. I told him no, it wasn't because of the review, which was true. What I didn't say was the fuller truth: that the review certainly made the decision easier.

Before I left, I put together a large knowledge-transfer effort — documentation and handoffs, enough to leave the team in a good place. Nobody acknowledged it. I never heard from my manager or the director again after I walked out: not a call, not an email, nothing. If I'd known the year was going to end the way it did, I would have started looking for the next job much earlier than I did.

What I took from that year is mostly about what a review should never be — and why it matters if you're the one running reviews for other people. There should be no surprises in a performance review, ever. If feedback only shows up once a year in a room with a rating attached, it's already too late for the person to act on it; give it while there's still time to matter. A manager should never seek comfort from the person they're delivering hard feedback to. The instant that happens, the conversation stops being about the other person's performance and becomes about the manager's own. And a manager shouldn't weigh one new, single-source complaint over years of trust a team has already built with someone, without checking it against anyone else first. If you're leading people, that's the discipline: get more than one perspective before you let one loud voice set the story.

There's a lesson for the person on the receiving end too. Even feedback that's mostly wrong or delivered badly is usually worth mining for whatever's true in it, because there's normally something. Put yourself first in these moments, because your company and your manager generally won't do it for you. And if any part of this sounds like something you've done as a manager, take it seriously enough to actually change it.

I don't think either of the managers in these two stories were bad people. I think they were undertrained and under-supported for the job of managing people, and companies hand out that responsibility constantly without preparing anyone for it — that part is on the organization. But it's also on the individual: developing yourself as a leader doesn't happen by accident, and choosing not to do that work is still a choice.

This is one of two stories about learning leadership from the wrong side of it. The other, about a manager, a trip called Chairman's Club, and a call that turned into a performance conversation, is worth reading too: Hard Lessons From the Worst Manager I've Ever Had.

If you've been the one delivering a review like this, or the one sitting across the desk receiving it, I'd welcome the conversation: https://clients.agile-ideation.com/public/fit-conversation

Back to Field Notes