Skip to main content

Performance Improvement Plans: When They Work, When They Don't

Performance Improvement Plans: When They Work, When They Don’t

Half the Performance Improvement Plans written in British workplaces are, in private, called something less polite. Managers know the rhythm: HR sends through a template, you fill in 90 days of objectives that no one will revisit until day 89, and three months later the employee leaves with a handshake and a settlement. The other half — the ones where the employee genuinely turns things around — get talked about much less often, and that is precisely where the useful lessons sit.

This guide is for the working manager who has been handed a PIP template, or is contemplating starting one, and would like an honest read on what they are actually for, when they help, and when they cause more trouble than the original problem.

What a PIP is actually for

A Performance Improvement Plan is a documented, time-bound, structured attempt to close a specific gap between someone’s current performance and what the role reasonably requires. That is the polite definition, and it is also the accurate one. Everything that goes wrong with PIPs goes wrong because someone has quietly substituted a different definition.

There are two legitimate uses:

  • Genuine remediation. The employee can do the job, has not been doing the job, and a focused plan with clear expectations and regular feedback gives them a fair chance to put things right.
  • A defensible exit route. The employee almost certainly cannot, or will not, meet the standard, but the organisation owes them — and itself — a process that is fair, documented, and capable of withstanding a tribunal panel reading it back in eighteen months.

Both are defensible. The reason PIPs have such a poor reputation is the third, unwritten use case: as a substitute for a conversation that should have happened six months ago. If you are starting a PIP because you have run out of other options to avoid having a difficult conversation, the plan is unlikely to fix anything.

When a PIP is the right tool

There are four conditions worth checking before you draft the document. The more of them you can answer honestly with “yes”, the more likely the PIP is to do useful work.

  1. The gap is specific and behavioural or output-based. “Quality of work” is not a gap. “Three of the last five client briefs went out with calculation errors that the client flagged” is a gap. If you cannot describe the problem in two concrete sentences, you are not ready to write a plan.
  2. You have already given clear, direct feedback informally. A PIP should never be the first time the employee hears that there is a problem. If it is, you have a management issue rather than a performance one, and the document will rightly carry no weight with the employee.
  3. The person has shown the capability and the willingness. Capability without willingness is an attitude problem and needs a different conversation. Willingness without capability is a development problem and may need a different role rather than a tighter version of the current one. PIPs work best where both are present, and something has gone wrong in how they are being applied.
  4. The role and the expectations are reasonable. Workload, scope, resources, and the standard you are holding them to all need to pass a “would a competent peer agree this is fair?” test.

If those four hold, you have a chance of writing a plan that actually changes something.

When a PIP is the wrong tool

A PIP is the wrong tool more often than it gets used. Some honest examples:

  • The problem is a relationship, not a performance gap. Two people who have stopped communicating cannot be fixed with a document about output quality. Mediation, a manager change, or a frank conversation will go further.
  • The role itself is broken. Scope has crept, headcount has shrunk, the brief is unclear, the tooling does not work, and the previous incumbent left for similar reasons. Writing a PIP here is asking one person to compensate for a structural problem. The tribunal panel mentioned earlier will spot this immediately.
  • The manager has not actually communicated the expectation. “I assumed they knew” is one of the most common openings to a failed plan. If the standard was implicit, the gap is not the employee’s.
  • The organisation wants someone gone and is using performance as the route. Sometimes this is unavoidable — a redundancy that cannot be made out, for example — but it tends to be obvious in the writing. The objectives are vague, the timeline is short, and the support promised in the plan never quite materialises. If this is the situation, talk to HR about whether a settlement conversation is more honest, kinder, and quicker.
  • You are using it because someone has annoyed you. This is rarer than it sounds, but worth a moment of self-honesty before drafting anything.

Designing a plan that might actually work

If the situation passes the “right tool” test, the design of the plan matters more than most managers expect. Three principles do most of the heavy lifting.

Apply SMART objectives properly, not decoratively

Most failed PIPs collapse on the M and the A — measurable and achievable. “Improve stakeholder communication” is not measurable. “Send a written summary within 24 hours of every external meeting, for the next eight weeks” is. Two or three objectives written this tightly will outperform nine objectives written loosely. If you cannot tell at the end of any given week whether the objective was met, neither can the employee, and the plan will quietly drift.

Set the cadence before the content

Most PIPs fail on cadence rather than content. A 30-minute weekly check-in, in the diary for the full duration, with the same agenda each time (what went well, what didn’t, what’s blocking, what’s next), is worth more than a perfectly drafted objective set discussed twice. The point of the plan is to create enough feedback loops that improvement, if it is possible, has a chance to happen. Without cadence the plan is just a piece of paper.

Borrow from “fair process”

The fair-process principle — well established in organisational research and most cleanly summarised by Kim and Mauborgne — has three components: engagement (the person has had a chance to give their view of the situation), explanation (they understand why decisions have been made the way they have), and expectation clarity (they know exactly what is expected and what will happen if they meet or miss it). PIPs that score well on all three tend to either succeed in remediation or end cleanly. PIPs that score badly on any one of them tend to drag on, end in dispute, and damage the team’s confidence in the manager regardless of the outcome.

The conversation that opens the plan

The opening meeting sets the tone for everything that follows. A few practical points:

  • Be serious, not punitive. This is a formal process and should feel like one, but the goal is the person’s success in the role. If you cannot say that and mean it, ask yourself whether you should be doing this at all.
  • Lead with the specific facts. Not “your work hasn’t been good enough” but “in the last six weeks, three deliverables have gone out with errors that the client flagged in writing.” Specifics give the person something to engage with; generalities give them only something to defend against.
  • Invite their view, and actually listen. You may learn something that changes the plan — a hidden caring responsibility, a process problem, a personal situation. Do not skip past this step because you have already decided the outcome.
  • Avoid the three classic opening lines. “This isn’t personal” (it is, to them). “I’m doing this for your own good” (you aren’t, or shouldn’t be). “I’ve had no choice” (you have, and pretending otherwise tells them the plan is not honest).
  • Document what was said. Not as a weapon, but because in three months’ time neither of you will remember the conversation accurately, and the written record protects both of you.

Running the 30/60/90

A standard PIP runs for either 30, 60, or 90 days. Ninety is the most common in UK practice and usually the right length: enough time for behaviour to actually change, short enough that drift is visible. The shape of a well-run 90-day plan tends to look something like this:

  • Weeks 1–2: scaffolding. Tighter than usual oversight. The employee may need help working out how to meet the objectives, not just being told to meet them. This is where you discover whether the gap is capability or motivation. Expect some early dips as people overthink the work.
  • Weeks 3–6: rhythm. The weekly check-in becomes routine. You start to see whether the trajectory is moving. By the mid-point, an honest manager can usually tell which way this is going to end. Resist the temptation to be either falsely optimistic or prematurely resigned.
  • The mid-point review. A more substantial conversation, ideally with HR present. Acknowledge what has improved, name what has not, and re-clarify what success looks like in the remaining time. If the plan is failing, this is the conversation that fairly warns the employee of that — and gives them the second half to respond.
  • Weeks 7–12: the honest call. By the final fortnight, the outcome is usually clear. If improvement is real and sustained, end the plan with a written confirmation, and mean it. If not, move into the next step (final written warning, dismissal, settlement, redeployment) with the same documented care the plan itself was given.

When to end the plan early

Most plans run their full length, but there are three situations where ending early is the right call.

  • Genuine, sustained improvement before the deadline. If the objectives are being met cleanly by week six and the underlying behaviours have changed, prolonging the plan is theatre rather than management. Close it out, in writing, and resume normal supervision.
  • Clear non-engagement. If the employee refuses the check-ins, doesn’t engage with the objectives, or makes clear they have no intention of trying, the plan is not the right document any more. Pause, take HR advice, and move to the appropriate disciplinary step.
  • Material new information. Disclosed illness, a safeguarding issue, a grievance against the manager, a bereavement, evidence of bullying — any of these change what kind of process you should be running, and the PIP needs to stop while that is dealt with separately. Carrying on regardless is both unkind and legally risky.

The honest test before you start

A useful sanity check, before drafting any plan, is to ask yourself one question: if this person met every objective on this plan, exactly as written, would I genuinely be pleased and want to keep them? If the answer is no, you are not writing a Performance Improvement Plan. You are writing the opening pages of an exit, and you and HR should be honest with yourselves about that, even if you cannot be honest with the employee for legal reasons. The plan can still be the right process — exits sometimes need to be defensible — but the framing in your own head matters. It changes how you write the objectives, how you run the check-ins, and how you feel walking out of the final meeting.

The best-run PIPs sit on a foundation of ordinary, regular management: clear expectations, frequent feedback, fair treatment, and difficult conversations had early rather than late. A PIP cannot retrofit any of those things. It can only formalise the conversation that, in a well-managed team, would have happened months ago, in a quieter form, over a coffee.

For managers who want to build the underlying skills — giving feedback, running difficult conversations, designing fair performance processes — SkillsCircle offers structured CPD pathways with real-world case studies and accredited assessment.

Advertisement