Automate Your Software Team Management

Most employees view Performance Improvement Plans (PIPs) as bureaucratic theater designed to justify a pre-decided firing. To run an ethical process, you must treat the PIP as a passable contract - one with clear gaps, real support, and a legitimate path to success.

This guide covers how to:

Diagnose the root cause
Write scorable success criteria
Manage the process without lying about the potential outcomes

1. Diagnose the Root Cause First

A PIP should be your second act, not your first. Before you draft legal documents, you must decide what you are actually seeing: a skill gap, a will gap, or a role mismatch.

Write down your hypothesis in plain English.

Skill: They are missing specific technical abilities.
Will: They are not doing the required behaviors.
Fit: This role is simply wrong for them.

Pick the lightest tool that works first, such as coaching or pairing. A PIP is only for when you need a timeboxed, documented agreement on what "improvement" looks like.

2. Eliminate the Element of Surprise

If the first time someone hears "you are not meeting expectations" is in the PIP meeting, you have turned the process into theater. Employees do not interpret surprise PIPs as support; they interpret them as "building a case."

You must build a "pre-PIP trail" that a reasonable person recognizes as feedback.

Use this script to keep yourself honest:

"I want to be direct: this is below the bar because [Reason]."
"Here are two concrete examples from the last two weeks."
"If we don't see improvement by [Date], we will move to a formal plan."

If you are casual in 1:1s but formal in the document, the tone whiplash destroys trust immediately.

3. Write Success Criteria You Can Score

Ethical PIPs have a property that is hard to enforce: someone can reasonably "pass" them. You achieve this by writing criteria you can score mathematically, not based on vibes.

Pick a window based on the work cycle (typically 30–90 days). Then, write goals that do not depend on your opinion.

Good (Scorable): "Ship 3 scoped tickets per sprint with first-pass acceptance >70%."
Good (Scorable): "Reduce escaped defects to <2 per sprint using Checklist A."
Good (Scorable): "Follow the runbook for Sev-2 incidents and escalate within 10 minutes."
Bad (Vibes): "Be more proactive."
Bad (Vibes): "Communicate better."

If you cannot write specific examples, you are likely policing personality, not performance.

4. Invest Real Manager Calories

A PIP that consists only of extra pressure is not an improvement plan; it is a warning letter. If you want it to be ethical, you must spend actual manager calories on support.

Real support looks like:

Reducing scope so they can hit quality targets.
Pairing on risky work until patterns improve.
Adding checkpoints mid-sprint so work doesn't drift.

"Try harder" is not a plan. If you are not willing to invest the time to support them, do not pretend you are offering a fair chance. Remember: An ethical PIP is a passable contract.

5. Stop Lying About the Outcome

Ethical does not mean "nice," and it does not mean "you will keep your job." Ethical means the employee has a fair shot and enough clarity to make their own decisions.

Do not hand-wave away the stigma. Be honest about the uncertainty.

Speak in boundaries:

"I believe improvement is achievable."
"I don't know the outcome; it depends on meeting the criteria."
"The likely outcome is exit if these criteria aren't met."

If you say "this is just to help" while handing them a legal document, they will assume you are lying. Admit the baggage, then run a process that counters it.

6. Operationalize the Cadence

Most ethical failures happen in the messy middle due to inconsistent meetings and undocumented decisions.

Lock the operating cadence immediately. Weekly check-ins are the sane default.

The Weekly Agenda:

Review evidence of progress against criteria.
Review what didn't meet the bar (with examples).
Plan the support for next week.

Involve HR early. If the employee cannot see the notes, they will assume you are building a secret case. Keep it visible.

Closing Thoughts

The closeout is where your intent becomes legible.

You either pass them because they met the math, extend them because they made progress, or exit them because they failed the criteria. Anything else is rewriting history.

If you treat the process as a narrative engineering exercise, you poison the team. If you treat an ethical PIP as a passable contract, you handle the outcome with dignity.

Do This Next: The Pre-PIP Checklist

Before you issue the document, ensure you can check these four boxes.

[ ] The "No Surprise" Test: Have you given this feedback in writing at least twice before?
[ ] The Math Test: Can a neutral third party score the success criteria (Yes/No)?
[ ] The Calendar Test: Have you cleared 2 hours/week on your own schedule to provide the promised mentorship?
[ ] The Honesty Test: Have you explicitly told them that termination is a possible outcome?

🔗 Read Next

Effective 1:1s With Engineering Managers – Building the foundation for hard feedback.
Measure Developer Productivity the Right Way – How to define the "math" for a fair PIP.
Managing a Brilliant Jerk on Your Team – How to address behavioral gaps before they require a formal plan.

Ethical PIP: A Guide for Managers