You Decided to Fight Your PIP. Here's What to Do in the First Week.
Fighting your PIP?
Get a week-by-week plan for exactly what to do.
The decision is behind you. You looked at the situation, weighed the factors, and decided to fight your Performance Improvement Plan (PIP). Good.
Now stop thinking about whether it was the right call. The people who survive PIPs are the ones who switch into execution mode immediately. Not the ones who spend two weeks second-guessing the decision they already made. There are real moves to make in the first week, and most of them are time-sensitive. This article covers those moves in order.
One note on scope: this is not a guide to deciding whether to fight. That decision is covered in depth in the fight-or-leave framework. It's also not about the psychological experience of receiving a PIP, which is its own piece. This guide starts the moment the decision is made and covers what to do next, practically and in sequence.
The problem your brain is about to create
Before getting to the moves, there's a failure mode worth naming because it will feel like the right instinct.
The natural response to being formally evaluated is to work harder. Put your head down, produce more output, be visibly busy, and prove through sheer effort that the PIP was wrong about you. This feels right. It is usually wrong.
Staw, Sandelands, and Dutton (1981), writing in Administrative Science Quarterly, identified what they called the threat-rigidity effect: under threat, people restrict their information processing, narrow their attention, and default to familiar responses, even when those responses are suboptimal. You stop asking questions. You stop gathering information about what's actually wanted. You produce more of what you already know how to produce.
The problem is that PIPs are often triggered by misalignment, not raw output. If your manager thinks you're not demonstrating ownership, and you respond to that by shipping more features without demonstrating ownership, you've added work but not addressed the criterion. One engineer who survived two separate Amazon PIPs described the root cause of his first one this way: "My manager wanted long-term projects tackled, but I didn't realize this was expected until I saw the PIP document." More work would not have fixed that. Clarity would have.
There's also a cognitive cost. Beilock and Carr (2005) found that performance pressure impairs working memory most severely in the highest-performing individuals, the ones with the most capacity to lose. A 2016 study in Cerebral Cortex found that social evaluative threat produces measurable reductions in prefrontal cortex activation, specifically in the areas responsible for complex reasoning and planning. The formal scrutiny of a PIP creates real cognitive drag on the work you're being evaluated on.
Building a process that doesn't depend on your judgment staying clear is the only reliable answer. That's what the rest of this guide is.
Are You at Risk of a PIP?
Find out if you're missing the warning signs — before it's too late.
1 of 7
Has the tone of your 1:1s with your manager changed in the last few months?
Day 1: Read before you execute
The instinct is to prove you're already working on it. Resist this.
Day one is for reading the PIP document with a specific question: are any of these goals actually measurable?
Go through each criterion listed. For each one, ask:
- Is there a specific, observable outcome I can point to when this is done?
- Is there a number, a date, a deliverable, or an agreed definition that will tell both me and my manager when this goal is met?
- Or is this a phrase that could mean anything?
Vague criteria create a structural disadvantage. They give the evaluator sole discretion over whether you've succeeded. HR platforms like Retorio and Engagedly describe phrases like "show more initiative" and "improve communication" as among the clearest indicators of a poorly designed plan, one that will be hard to pass regardless of effort because success is subjective.
If any of your criteria are vague, your first move is to request written clarification before the PIP period fully starts. Email your manager (CC HR, matter-of-factly) with something like:
I want to make sure I'm aligned on what success looks like for each criterion in the plan. For [vague criterion], could you help me understand what a successful demonstration would look like, specifically what you'd expect to see at the end of the PIP period that would confirm this goal has been met?
This is not pushback. It's alignment. Most managers, when asked directly, will give you something more concrete. Some will not, and that refusal is itself evidence worth having on record.
District Employment Law, an employment firm with extensive PIP case history, advises: "Politely demand clarification... don't stop until your employer either amends the PIP or directs you to stop. If you are directed verbally to stop pushing back, confirm it in an email to your employer to create a written record."
On Team Blind, engineers who survived PIPs consistently reported that those with quantifiable criteria had more control over the outcome. One thread on how to fight a shady PIP reached this community consensus: the first week is for forcing clarity, not execution. If the company agrees to rewrite the criteria, you're in a better position. If they refuse, you have documentation of the refusal.
Also on day one: sign the PIP, but add language. You do not have to agree with the document's contents to acknowledge you received it. Write directly on the document or in an accompanying email: "Signing to acknowledge receipt only. I do not agree with the contents of this document." This keeps your employment intact while preserving your factual record.
Day 2-3: Build your documentation infrastructure
Before you produce a single deliverable under the PIP, build the infrastructure for capturing what you produce. This is the parallel record you'll need if the process turns adversarial.
The recap email habit
After every meeting with your manager or HR, send a brief email within an hour: what was discussed, any decisions made, any points of disagreement you want on record. Not elaborate. Just the facts.
Romano Law advises: "Email regular reports to both your supervisor and HR documenting your achievement of each PIP goal." The recap email creates a contemporaneous record that is very difficult to contradict later. If goalposts start to move (if a criterion gets reinterpreted partway through, or a completed item gets reclassified as incomplete), you have a timestamped record of what was agreed.
Spitz, The Employee's Law Firm notes that "if your employer... changes success criteria mid-PIP, document these failures; they undermine the PIP's legitimacy and could support a wrongful termination claim."
The prior evidence file
Pull your past performance reviews, commendation emails from managers or skip-levels, project feedback, anything that establishes your track record before this PIP. Save this file somewhere you control, not just on company systems.
If the PIP claims you have never demonstrated ownership, and you have a chain of emails praising exactly that, you have a rebuttal. Matthew Ruggles, a Sacramento employment attorney, is direct: take notes during every meeting "so you can refer back to the specifics." This matters both for passing the PIP and for protecting yourself if the matter escalates.
Your work artifact log
Keep a running document in personal storage of your deliverables: closed tickets, shipped features, documents authored, PRs merged, test coverage improved. Add to it each week with dates, descriptions, and links or screenshots where possible. This becomes your evidence base.
You are not copying confidential company data. You are collecting evidence of your own output, the kind of thing that would appear on a resume or in a performance review. That distinction matters legally.
What vague language actually means
At some point in the first week you will stare at a criterion like "demonstrates leadership presence" and have no idea what to produce. Here is how to translate the most common ones:
"Demonstrates ownership" means you identify problems and close them without being asked. You don't report obstacles; you resolve them and report the resolution. The behavioral signal your manager is looking for is the ratio of "I found a problem and fixed it" to "there's a problem."
"Shows initiative" means you act before being directed. You see the gap, close it, and document what you did. The distinction between initiative and ordinary work is that the action was your idea, not a response to a request.
"Improves communication" usually means one of two specific things: you need to communicate your status more proactively (your manager doesn't know what you're working on without asking), or your communication style in meetings or written form is creating friction somewhere. Ask your manager which one they mean. Force the answer to be specific.
"Demonstrates leadership" at most tech companies means operating above your current level in some dimension: influencing without authority, unblocking others, making architectural or process decisions that get adopted. Ask which dimension your manager has in mind.
Once you've gotten clarification, write it back: "Just confirming our conversation. My understanding of [criterion] is [specific behavioral definition]. Let me know if that doesn't match your expectation." This creates an aligned definition that protects you from goalpost movement.
Day 3-5: How to approach your manager
There's a trap in the manager relationship during a PIP that catches engineers in two opposite directions. One group treats every interaction as adversarial (everything is being used against them). Another group treats the manager the same as before (oversharing, assuming goodwill). Both are wrong.
The right position: professional, cooperative, and documented.
You want to be engaged, ask questions about priorities, and be visibly working on the PIP criteria. You also want a written record of everything and eyes open to whether criteria are shifting. These aren't contradictory. You can collaborate fully on the work while keeping your own contemporaneous record of what that work was.
What your manager is actually writing
Here's what's useful to know about the other side of the check-in.
Enterprise HR platforms like HR Acuity, which is widely used for PIP documentation at large tech companies, ask managers to record: goal progress against each criterion, behavioral observations, deliverable status, and any obstacles mentioned. Managers log "milestones and check-ins throughout the PIP period," tracking whether improvement is happening week by week.
That tracking record is what you're shaping. If you produce specific behavioral evidence mapped to each PIP criterion before the check-in, your manager's note that week reflects it. If you work hard but produce nothing citable, the note will read as vague. Vague manager notes, at the end of a PIP evaluation, tend to resolve against you.
PeopleGoal, an HR management platform, describes the structure of a manager's check-in note as: document wins with specifics, flag setbacks with data, update progress numbers. The goal is to create a "narrative of whether improvement happened." You want to be the one supplying the data points that narrative gets built from.
Day 6-7: Lock in the weekly rhythm
By the end of week one, put two recurring structures in place.
The proactive status email
Before each check-in meeting, send your manager a written update: here is what I've done this week against each PIP criterion, here is the evidence, here is what's next. Do not wait to be asked for a status update. Engineers who have survived Amazon PIPs consistently cited this as one of the highest-leverage moves: presenting your own account first, before your manager writes their assessment.
One engineer who documented surviving Amazon's PIP process put it this way: "Be vocal, get all your work done, and don't be afraid to hold the people who control your fate accountable to do their part too."
That last clause matters. Your manager has commitments in the PIP as well: assigned support, scheduled check-ins, agreed criteria. If they miss those, document it the same way you'd document your own progress.
The check-in meeting itself
Come in with your status update already prepared. Walk through each criterion, cite specific evidence, and flag anything you need from them. End with: "Can you confirm in writing whether you see this week's work as progress toward the goal?"
PerformYard's check-in guidance describes the structure as: review progress against each goal, address obstacles, confirm next steps in writing. You're not inventing a process. You're using the process the company is supposed to be running, and making sure it actually runs.
One more thing: the job search
Running a parallel job search during a PIP is not conceding defeat. It's risk management. The engineers who navigate PIPs most effectively (whether they survive or not) treat the search as a parallel track from day one. You can fight the PIP with full effort and interview at the same time. One does not cancel the other.
The engineers who tend to come out worst are the ones who fight the PIP hard, lose, and then start a job search with a recent termination and no pipeline. That outcome is avoidable. If you reach a point where you decide to stop fighting and negotiate your way out instead, exiting on your terms covers how to protect your record and severance.
The weeks past the first week bring their own challenge: sustaining performance under sustained scrutiny is harder than the first week, and it's worth knowing what to expect.
How the PIP resolves depends on factors partly outside your control. What you can build in this first week is your record: how clearly you understood the criteria, how consistently you mapped your work to them, and how thoroughly you documented the process. That record protects you whether you survive or not.
CareerClimb helps you log your work and keep your evidence current throughout, so whatever evaluation you face, you have the strongest possible case. Download CareerClimb
