PIPs and paper trails: performance intervention done fairly

A fair plan is a ladder someone can actually climb — not a countdown to an exit you’ve already decided.

The idea

By the time you write a performance improvement plan, the case is mostly already made — or already broken. What separates a winnable, defensible plan from a paper trail to a foregone exit is what happened in the weeks before it: specific, dated notes on real misses; feedback the person actually heard; and support attached to measurable goals.

You climb an escalation ladder one rung at a time: informal feedback, documented expectations, a formal warning, then a PIP. Skip rungs and the record hollows out. Log vague labels like “attitude problem” and they bounce — they aren’t documentable, so they don’t hold weight.

How it works

The ladder is a sequence, not a menu. Each rung needs the one below it plus its own evidence, all dated as it happened:

Rung 1  Informal feedback        needs: 1 specific, dated observation
Rung 2  Documented expectations  needs: rung 1 + a 2nd observation + a logged 1:1
Rung 3  Formal written warning   needs: rung 2 + 3 observations + 2 feedback talks
Rung 4  PIP with milestones      needs: rung 3 + support attached + a measurable goal
Rung 5  Fair decision            needs: rung 4 + 2 milestones + ≥8 weeks elapsed
                                     + fairness ≥ 60 + defensibility ≥ 60

Two things quietly decide the outcome. Support (coaching, clearer goals, training) is what turns a plan the person can pass from one designed to fail. And time — each undocumented stretch is a hole a reviewer will find, and rushing the whole ladder into a month reads as a decision made before the process started.

When to use it

Watch out for

• Vague, subjective labels. “Attitude problem,” “not a team player,” “low energy” can’t be measured, coached, or defended. Translate each into a specific, dated behavior and its impact.
• Back-filling the record. Writing up three months of misses the day before the PIP is transparent and undermines the whole file. Document contemporaneously — the same week it happens.
• A plan with no support. Milestones without coaching, tools, or clearer goals isn’t improvement — it’s a trap. Attach real help to every goal.
• Unmeasurable milestones. “Improve communication” can’t be passed or failed. “Post a written status by 10am each Monday” can.
• Inconsistency. Holding one person to a standard others miss is where bias claims live. Apply the same bar and document that you did.

General management practice, not legal advice — specific requirements vary by company policy and jurisdiction.

Worked example

An interviewer asks: “An engineer keeps missing deadlines. Walk me through putting them on a PIP.” The weak answer jumps straight to the plan. The strong answer starts earlier: “First I’d check what’s documented. If it’s just my impression, I have no case yet.” They’d log two or three specific, dated misses (“sprint 14: committed to the API cutover, shipped 9 days late with no heads-up”), have and document a direct feedback conversation, then — if the gap holds — open a PIP with two measurable milestones, coaching attached, and a realistic window. Crucially they’d say they want the person to pass, and they’d apply the same standard they hold everyone to. That answer signals fairness and a record that survives scrutiny.