How to respond to a performance improvement plan

You got the meeting invite, or you got the document, and since then you've been running the same loop: is this real, or have they already decided? You've read a dozen articles that all say the same reassuring thing, and none of them told you what you actually want to know, which is what your manager and their boss say about you when you're not there.

This article covers what a PIP signals, what your manager was coached to do before this point, and how to tell a genuine improvement plan from a documented exit. It also covers what to negotiate before you agree to anything, how to run the weeks that follow, and what to say in your next interview. Read the section on what your manager was told to do first, because most of your decisions get easier once you know what this looks like from where they're sitting.

The management thinking here comes from the people who train managers to run these plans: Alisa Cohn, an executive coach who scripts these conversations for founders; Kim Scott, who managed teams at Google and Apple and wrote Radical Candor; Elizabeth Stone, chief technology officer at Netflix; Molly Graham, who led teams at Facebook, Google, Quip, and the Chan Zuckerberg Initiative; and the Mochary Method curriculum used by founders at Coinbase, OpenAI, and Reddit. The employee side comes from Kenneth Berger, an executive coach who was the first product manager at Slack and was fired from it three times, and Aakash Gupta, who has run these plans as a manager.

What a PIP actually signals

A performance improvement plan means two things are now true. Someone senior enough to start a formal process believes your work isn't meeting the bar, and that belief has moved from a private opinion into a written record that HR is tracking. Both matter, and people usually only react to the first one.

The existence of a plan won't tell you whether the decision has already been made. That varies enormously by company, by manager, and by why you're on it. At some companies a plan is a real last attempt to keep someone. At others it's a required step before a termination that leadership already agreed on. What's inside the document will tell you which one you have, and so will the answers you get when you start asking questions.

Before you conclude anything about your own ability, look at the most common cause of performance problems. Molly Graham has run teams through fast growth at four companies and starts every performance conversation in the same place.

If you're on a plan and the honest answer to "did anyone ever tell me clearly what good looked like here" is no, say that in the first meeting. You're not defending yourself or accusing anyone by saying it. You're asking for the thing that has to be fixed before the clock starts, because a plan built on an expectation nobody ever stated is a plan you can't pass.

What your manager was probably told to do

Almost every article about PIPs is written for the person on the plan. Your manager got trained on this from the other direction, and what that training says is worth knowing.

Above everything else, every manager training says the same thing: don't let this be the first you're hearing of it. Kim Scott tells a story about a direct report she calls Bob, whose work wasn't good enough for months while she said nothing, because she liked him and didn't want to knock his confidence. By the time she sat down with him it was ten months too late.

Alisa Cohn, who coaches founders through exactly these conversations, puts the responsibility on the manager in plainer terms.

Cohn then scripts the conversation she thinks should happen well before any formal plan. Read it as the conversation you were owed, and check it against what you were actually told.

That script contains a specific behavior, the fact that it's been raised before, how long it's been going on, a deadline, the consequence, and two sentences of genuine belief in the person. A manager who gave you all of that is running the process properly. A manager who gave you the deadline and the consequence with no specific behavior attached has told you something as well.

The Mochary Method curriculum, which many startup managers train on, tells managers to diagnose before they escalate. It splits the cause of any performance problem three ways: clarity, meaning your manager never made the ask specific; capability, meaning you don't yet have the skill, time, or support; and caring, meaning motivation. Each one gets a different response. The curriculum's test for clarity is that a video camera should be able to record the behavior being asked for. "Show more ownership" fails that test. "Post the sprint update by Monday noon" passes it. Run every line of your plan through it, because any line a camera couldn't film is a line you and your manager will argue about at the end.

Our playbook for managers in this situation lays out the whole process they're being asked to run, including the escalation steps and the firing conversation. It's uncomfortable reading, and it's the clearest picture you'll get of what your manager has been coached to do next.

Telling a genuine plan from a documented exit

Here's the honest answer: sometimes a PIP is recoverable and sometimes it's paperwork on a decision already made. The difference is usually visible in the document and in how people behave in the first week.

Some companies don't use plans at all, and it helps to recognize that model when you see it. Elizabeth Stone, Netflix's chief technology officer, describes the question their managers ask themselves instead.

Stone says employees ask her the question back, in the form of "am I passing your keeper test?", and she treats it as another way of asking how they're doing (33:43). That phrasing works at any company. Ask your manager some version of it and pay attention to how long the pause is before the answer.

One more thing to hold onto while you assess all this. Molly Graham is blunt about how often hiring simply misses.

If half of all hires don't work out, then a job going wrong is frequently a match problem rather than a verdict on what you're capable of. That isn't meant to make you feel better, but it should change how you talk to yourself about this. Ask whether the role changed under you after a reorg, whether you were promoted into work that's different from what you're good at, or whether the job you were hired to do stopped existing.

Questions to ask in the first meeting

You'll be tempted to defend yourself line by line in this meeting. Don't. Your only job in the first conversation is to leave with information you didn't walk in with. Take notes, ask these, and say almost nothing else.

Then ask for time. You don't have to respond to the plan in the meeting where you receive it, and you shouldn't. Say something like: "I want to take this seriously, so I'd like a couple of days to read it properly and come back with questions." That buys you time to get advice, and it keeps you well clear of the reaction that gets people fired in a week.

Negotiating the terms before you agree to them

Most people treat a PIP as a document handed down. A lot of it is negotiable, especially the parts that decide whether you can pass, and asking to change them makes you look like you're taking the plan seriously. It's what your manager was supposed to do when they wrote it.

Send your requested changes in writing, calmly, framed as wanting to get this right. "I want to make sure I'm working on the same thing you're measuring, so here's how I'd suggest wording items two and three." Whatever the outcome, you now have a written record of someone engaging seriously with the plan, and that record helps you in every direction this can go.

The reaction that ends it in a day

There's one move that reliably turns a survivable plan into an immediate exit, and it comes from a completely understandable place. Aakash Gupta describes putting someone on a plan six weeks into a new job, having already spent an hour a day trying to improve that person's work.

So this was a real plan, written by the one person in the building arguing to keep the employee. Here's what happened next.

Over one evening, the employee gathered screenshots of Gupta's late-night Slack messages, built a case that he was a toxic manager, and circulated it. Gupta's account is that they were let go the same day. The person had a genuine plan and a manager fighting for them, and they never found out, because they went to war in the first twelve hours.

Kenneth Berger, who was the first product manager at Slack and was fired from it three times over a single year, describes the same instinct from the inside.

Berger is also clear about what he skipped at the start. He went into Slack overconfident and never asked what success looked like there or what the expectations of him were, so he made his best guess and went for it (46:32). None of this means you should accept an assessment you believe is wrong. It means you separate the two jobs. Disputing a specific factual claim in writing, once, calmly, is fine and sometimes necessary. Building a case against your manager is a different activity, and it ends the conversation about your performance permanently.

The weekly routine to run while you're on it

Your manager decides this in the check-ins, not at the end date. Most people sit through them quietly and wait for a grade. Take charge of them instead.

Written updates do a specific job here. They give the person deciding your future something to look at other than an impression, and they stop the final meeting turning into an argument about what was agreed.

Also, tell one person outside your reporting line who can vouch for your work. You're not building a coalition. You just want someone senior who watched the last three months and will say so on a reference call.

Looking after yourself through it

A PIP hits sleep, appetite, and your sense of whether you're any good at your job, and it does that to competent people. Berger, ten years on and now coaching executives, is direct about which part is actually the hard part.

Things that help while you're in it:

• Give this a time box. An hour a day of thinking about the plan, and the rest of the day doing the work. Otherwise it takes the whole day.
• Tell two or three people you trust, and pick at least one who won't only tell you you're wonderful.
• Keep the parts of your life that tell you who you are when work isn't answering: exercise, friends, anything you're competent at that has nothing to do with this job.
• Separate "this job isn't working" from "I'm not good at this." The first is a fact about how well you and this role fit. The second is what stress does to your thinking, and it isn't reliable.
• If your company has an employee assistance program or covered therapy, use it now rather than after.
• Don't make big decisions at 11pm. Write the angry email, save it as a draft, read it in the morning.

If this ends with you leaving, our playbook on staying confident after a rejection covers the recovery part in more detail.

Running a job search at the same time

Start looking, whichever way you read the plan. A search takes months and a plan takes weeks, and the version of you who's already interviewing makes better decisions at work than the version who has nowhere else to go. If you are running that search while still employed, our job search while employed playbook covers the time budget and the discretion.

There's a real strategic choice here, and it's worth making deliberately rather than drifting into it. Fighting for the role makes sense when you believe the criteria are fair, you can see how to meet them, and you'd want this job if you did. A dignified exit while collecting a paycheck makes sense when you've read the plan honestly and concluded it can't be passed, or when you've realized you don't want to pass it. Both are legitimate. What fails is doing neither, half-committing to the plan while half-searching, and arriving at the end date with no new job and a bad record.

How to talk about this in your next interview

Almost nobody will ask "were you on a performance plan." What they will ask is why you left, and what you'd do differently in a role that went badly. Kim Scott says the story of a career is her favorite interview question for a specific reason.

Scott adds that if someone tells the story of their career with no mistakes in it, that itself is information. So don't plan to hide this period. Aim to describe it in ninety seconds without blaming anyone and without falling apart.

Say it out loud until it's boring to you, because delivery is most of it here. The same words sound completely different coming from someone who's settled about what happened than from someone who's still arguing about it. Our behavioral interview playbook covers the structure for answers like this, and the career story playbook covers where to place it in your narrative.

Frequently asked questions

Does a PIP always mean I'm being fired?

No, and anyone who tells you otherwise is guessing about your company. People do come off plans and go on to be promoted. People also get plans that were paperwork on a decision made weeks earlier. The difference shows up in whether the criteria are specific, whether support is attached, whether the timeline fits your work, and what answer you get to "if I do all of this, do I keep my job."

Should I sign it?

Signing usually acknowledges that you received the plan rather than that you agree with it, but that varies by company and by jurisdiction, and some documents bundle in things that matter far more than acknowledgment. Read what you're signing, ask what the signature means, and if there's a release or a severance offer attached, get advice from an employment lawyer where you live before you sign.

Can I ask to skip the plan and take a severance package instead?

You can ask, and people do. Frame it as wanting the best outcome for both sides. "I've read the plan carefully and I'm not sure this role is the right match anymore. Is there a version of this where we agree an exit instead?" Understand that asking signals you're leaving, so decide first, and find out what you'd be giving up before you open that conversation.

Should I go to HR about my manager?

HR works for the company. That doesn't make them dishonest, and they're genuinely useful for process questions like what the plan requires and what the timeline is. If you believe something unlawful is happening, like discrimination or retaliation, that's a different situation. Document it and get outside legal advice rather than treating an internal complaint as your only route.

What if the plan is genuinely unfair?

Respond to it once, in writing, calmly and factually. State the specific claims you dispute and the evidence, accept the parts you do accept, and ask for the plan to be amended where it's wrong. Then work the plan anyway while you also look. A calm written rebuttal is worth having whatever happens next. A campaign will only cost you.

Should I tell my team?

Generally no. It changes how people work with you and it rarely helps. One or two trusted colleagues outside your reporting line is a different question, and worth having.

The checklist

If part of what got you here was a promotion conversation that went badly, our playbook on what to ask after a promotion is denied covers that conversation. And if you want to understand exactly what your manager is being coached to do next, read the manager's version of this situation.