What To Do With A Bad Performance Review
Most advice tells you to document and fight back. Here's why I don't.
A bad review rarely ambushes you. By the time it’s written down, your manager already decided something. The meeting just makes it official. The question that matters isn’t “how do I improve.” It’s “what did my manager actually decide.”
I’ve sat on both sides of that table, as an engineer and later building and running product teams.
Here’s the sequence I’d follow.
1. Figure out the manager’s real intent first. Two very different things produce a bad review: a manager who wants you to succeed and is frustrated you haven’t, and a manager who’s already decided you’re leaving and is building the paper trail to make it stick. Don’t assume it’s the first one just because that’s the more comfortable read.
Some tells of a managed exit: the feedback is vague and trait-based (”not strategic enough”) rather than tied to specific decisions. The timeline for improvement is short and unrealistic. The manager won’t commit to clear, measurable criteria for success. You’re suddenly being CC’d to HR or skip-level on routine things. None of these prove it on their own, but a cluster of them is a pattern, not bad luck.
2. Ask for concrete, actionable items, not adjectives. Whatever the intent, push for specifics: “What exactly would ‘meeting expectations’ look like by next quarter? Give me two or three concrete things.” A manager who genuinely wants you to succeed will usually engage with this. A manager who’s already decided will deflect, stay vague, or hand you a list that quietly keeps moving. That response is itself useful data, going back to point one.
3. Decide if it’s a fixable problem or a fit problem. If it’s fixable, fix it. If it’s not, figure out where the mismatch actually lives. Is it this manager, this team, or this company? That distinction matters because your options shrink fast once you’re formally on a PIP. Plenty of companies won’t let you transfer teams once you’re flagged, even if the problem was clearly about your specific manager and not your work. If a lateral move is on the table, it’s usually only available before the PIP starts, not after.
4. Check whether this is a visibility problem or an alignment problem. These look identical from the outside but need opposite responses. A visibility problem means the work is good but invisible: nobody above your manager knows what you actually did. An alignment problem means the work itself doesn’t match what the team or company needs right now, regardless of how visible it is.
If it’s visibility, the fix is making your work legible: documenting impact, presenting in the right rooms, and yes, seeing if a peer or skip-level will vouch for you with specifics. A peer saying “actually, I saw them solve X” carries more weight than anything you say about yourself. If it’s alignment, no amount of visibility fixes it. You need a different role, team, or company where the work that comes naturally to you is the work that’s valued.
5. Skip the “document everything and challenge your manager through HR” advice. This gets repeated everywhere, and I think it’s mostly wrong. HR exists to manage company risk, not to act as your advocate. They report up through the same leadership your manager answers to. If your manager has been asked to hit an unregretted attrition number, which happens more often than companies admit, HR isn’t a neutral referee. They’re often the mechanism executing that plan.
Building a detailed paper trail to dispute a review can occasionally help if you’re aiming for a severance negotiation or you have a genuinely strong legal claim. As a strategy to keep your job or change your manager’s mind, it rarely works and it burns time you could spend on your next move. Decide which game you’re actually playing before you invest in documentation.
A bad review is one of the few moments someone is forced to tell you, in some form, where they think you stand. Spend your energy figuring out what’s really happening, not on convincing them they’re wrong.