Performance Improvement Plans: How to Manage the Process Without Making It a Death March


paperwork documents office review

What a PIP Is Really For

A performance improvement plan is a structured process designed to give an underperforming employee a defined path back to acceptable performance. Done right, it protects the employee, the team, and the organization. Done poorly, it becomes a paper trail dressed up as support.

As the manager, your job isn’t just to document the problem. It’s to create the conditions where the employee can genuinely turn things around — and to make a clear-eyed decision if they don’t. Both outcomes are valid. Neither should feel personal.

Before you open a PIP, be honest with yourself about one question: Do I actually want this person to succeed? If the answer is no, you’re not running a PIP — you’re building an exit case. That distinction matters, because employees can feel the difference, and so can HR.

Before the PIP Starts

Make Sure the Problem Is Real and Documented

A PIP should never be a surprise to the employee. If they haven’t already received clear feedback that their performance is below expectations, the PIP will feel like an ambush — and it will be harder to defend if things escalate to HR or legal review.

Before initiating the process, confirm you have:

  • Specific examples of underperformance with dates and details
  • Evidence that the employee was told what was expected
  • A record of prior conversations or warnings
  • Clarity on whether the issue is performance, conduct, or something else

Performance issues (missing targets, quality problems, slow output) and conduct issues (attendance, attitude, policy violations) are handled differently in most organizations. Know which you’re dealing with before you begin.

Loop In HR Early

Don’t write a PIP alone. HR exists partly to protect you from making well-intentioned mistakes that create liability. Bring them in before you draft anything, confirm the process your company uses, and get their sign-off on the language before the employee ever sees it.

This isn’t about covering yourself — it’s about making the process fair and consistent. HR can also tell you whether the issues you’re seeing are serious enough to warrant a PIP or whether a documented verbal warning is the right first step.

Setting Up a PIP That Actually Works

Write Goals That Are Specific and Measurable

Vague goals are the most common reason PIPs fail. “Improve communication” tells an employee almost nothing. “Submit weekly status updates to the team by Friday at 5pm, with no more than one missed deadline per month” gives them something they can actually achieve.

Every goal in a PIP should answer three questions:

  • What does success look like?
  • How will it be measured?
  • By when?

If you can’t answer all three, the goal isn’t ready to go into the document.

Set a Realistic Timeline

Most PIPs run 30, 60, or 90 days. The right length depends on the complexity of the performance gap and the role. A 30-day PIP for a complex skill deficit is almost always too short. A 90-day PIP for a simple attendance issue may be longer than necessary.

The timeline should be long enough for the employee to demonstrate genuine change, but not so long that it drags and becomes demoralizing for everyone involved.

Define the Support You’ll Provide

A PIP is not a one-sided document. It should include what the manager and organization will do to support improvement, not just what the employee must do. This might include:

  • Weekly one-on-one check-ins with specific agenda items
  • Access to training, coaching, or mentoring
  • Clearer communication of priorities from the manager’s side
  • Removal of obstacles that have contributed to the problem

Listing these in the document makes the process feel collaborative rather than punitive — and holds you accountable too.

The Meeting Where You Present the PIP

This is one of the hardest conversations you’ll have as a manager. Here’s how to make it go as well as possible.

Be Direct, Not Harsh

State clearly why you’re having the meeting. Don’t soften the opening so much that the employee doesn’t realize what’s happening. Something like: “I’ve asked you to meet with me today because your performance in [area] has been below what’s required for this role, and I want to put a plan in place so we can work on that together.”

Then walk through the document point by point. Give the employee time to read it, ask questions, and respond. This is not a monologue — it’s a conversation.

Expect an Emotional Reaction

Some employees will be defensive. Some will be upset. Some will be quiet and withdrawn. All of these are normal. Don’t escalate if they push back emotionally. Give them space, acknowledge that this is hard, and return to the facts.

What you should not do is back down from accurate feedback because the conversation gets uncomfortable. Vagueness in this moment is a kindness that backfires later.

End With Clarity

Before the meeting ends, make sure the employee can answer:

  • What specifically do I need to do differently?
  • What does success look like at the end of this process?
  • What happens if I don’t meet the goals?
  • Who can I go to for support?

Don’t leave consequences vague. If failure to meet the PIP goals could result in termination, say so clearly and professionally. Employees deserve to understand what’s at stake.

Managing the Employee During the PIP

Check In Consistently

Your check-in cadence during a PIP should be more frequent than your normal one-on-ones. Weekly is standard. Each check-in should follow the same structure: review progress against goals, identify any obstacles, give specific feedback, and document what was discussed.

Don’t skip check-ins, even when things seem to be going well. Consistency signals that you’re serious about the process and that you’re genuinely invested in the outcome.

Give Real-Time Feedback — Not Just Weekly Updates

If the employee does something well on a Tuesday, tell them Tuesday. If they miss a deadline on Thursday, address it Thursday. Don’t save everything for the weekly check-in. Real-time feedback is how people actually adjust their behavior.

Positive feedback matters here as much as corrective feedback. If you only engage when something is wrong, the employee will become defensive and demoralized. Acknowledge genuine progress explicitly and specifically.

Document Everything

Keep a running log of every relevant interaction during the PIP period. This includes check-in notes, emails, examples of work that did or didn’t meet the standard, and any conversations about the plan. Store these somewhere accessible and consistent — not just in your memory.

If things end in termination, documentation protects the fairness of the process. If things end in success, documentation shows what good coaching looks like.

Don’t Isolate the Employee

One of the most damaging things a manager can do during a PIP is treat the employee as if they’re already gone. Excluding them from team discussions, reducing their responsibilities without explanation, or becoming cold and distant will accelerate failure, not prevent it.

Treat the employee with the same basic respect you give everyone else. They’re still on your team. The PIP is a process, not a verdict.

When Things Aren’t Improving

If you’re two-thirds through the PIP period and the employee isn’t making meaningful progress, don’t wait until day 90 to have an honest conversation. Address the gap directly: “We’re at the halfway mark and I’m not seeing the improvement we agreed to. I want to understand what’s getting in the way and what we can do about it.”

Sometimes this conversation surfaces a genuine obstacle that can be addressed. Sometimes it confirms that the employee isn’t going to get there. Either way, it’s better to have it early than to let the clock run out in silence.

Loop in HR when you see consistent non-improvement. They need to be part of any decision about what happens at the end of the PIP, and they need time to prepare for it.

At the End of the PIP

If the Employee Succeeded

Close the PIP formally. Document that goals were met, acknowledge the employee’s effort, and be clear that the plan is closed. Then do the harder work: figure out what will prevent a relapse. Were there management gaps on your side that contributed to the problem in the first place? Were there role fit issues that are still lurking? A PIP that ends in success but doesn’t address root causes often reopens six months later.

If the Employee Didn’t Succeed

If the employee has not met the goals after a fair process with genuine support, the next steps are typically a conversation about separation — either a managed exit or termination, depending on your organization’s process. This decision should involve HR and, in many cases, your own manager.

Don’t delay this decision out of guilt or discomfort. Keeping someone in a role they’re not performing in isn’t kind — it costs them time they could use to find a better fit elsewhere, and it costs your team.

The Manager’s Mindset

Managing someone on a PIP is emotionally demanding. You’ll second-guess yourself. You’ll wonder if you gave enough feedback earlier, built enough rapport, or set clear enough expectations. Some of that reflection is healthy. Some of it is just the discomfort of a hard situation.

The thing to hold onto is this: a well-run PIP is one of the most respectful things you can do for an underperforming employee. It says: I see a problem, I’m going to name it clearly, I’m going to support you in fixing it, and I’m going to give you a real chance. That’s not punitive. That’s what good management looks like when things get difficult.

The managers who do this well aren’t harder or colder than other managers. They’re just clearer — and that clarity, in the long run, is what people actually need.

Frequently Asked Questions

How do I know if an employee needs a performance improvement plan?

A PIP should never be a surprise to the employee – if they haven’t already received clear feedback about underperformance, you’re not ready yet. You need specific examples with dates, evidence they knew what was expected, and records of prior conversations or warnings. Before initiating a PIP, ask yourself honestly: do I actually want this person to succeed, or am I just building an exit case?

What’s the difference between performance issues and conduct issues in PIPs?

Performance issues involve missing targets, quality problems, or slow output, while conduct issues cover attendance, attitude, or policy violations. These are handled differently in most organizations, so it’s crucial to identify which type you’re dealing with before starting the PIP process. This distinction affects how you structure the plan and what outcomes you measure.

Why do I need to involve HR before writing a performance improvement plan?

HR helps protect you from well-intentioned mistakes that create legal liability and ensures the process is fair and consistent. They can confirm your company’s specific PIP process, review your language before the employee sees it, and determine if the issues are serious enough for a PIP or if a documented verbal warning should come first. Never write a PIP alone.

How do I write effective goals for a performance improvement plan?

Vague goals are the most common reason PIPs fail – saying “improve communication” tells an employee almost nothing actionable. Instead, write specific and measurable goals like “submit weekly status updates to the team by Friday at 5 PM” that give clear direction. The employee should know exactly what success looks like and how it will be measured.

What should I do before starting the PIP process with an underperforming employee?

First, make sure the problem is real and documented with specific examples, dates, and evidence of prior feedback. Confirm you have records showing the employee knew what was expected and had received previous warnings. Loop in HR early to review your approach and ensure you’re following company procedures correctly before drafting anything.

Ty Sutherland

Ty Sutherland is an operations and technology leader with 20+ years of experience. He is Director of IT Operations at SaskTel, founder of Ops Harmony (fractional COO and EOS Integrator), and former COO at WTFast. He writes Management Skills Daily to share practical management frameworks that work in the real world.

Recent Posts