The PIP that doesn't feel like a trap: scripts, milestones, paper trail
Most PIPs are exit documents in disguise. Here's how to design and deliver one that's actually defensible — 30/60/90 milestones, documented check-ins, and the…
On this page▾
- A PIP without honest belief that improvement is possible is just a constructive dismissal letter. Don't write one you're not willing to celebrate succeeding.
- Three milestones (30/60/90), three measurable outcomes per milestone, written check-ins every two weeks. No moving goalposts.
- The opening conversation is the most important artifact. Script it; don't ad-lib.
- Two outcomes are acceptable: meaningful improvement, or a clean separation. 'Limp along' is a failure of the manager, not the employee.
A PIP isn't a punishment. It's a contract that says: here's what 'good' looks like, here's how we'll measure it, here's the timeline, and here's what happens either way. The reason most PIPs feel like traps is that managers write them when they've already decided — and the employee can smell it from across the room.
When a PIP is the right tool (and when it isn't)
| Situation | PIP? | Better tool |
|---|---|---|
| Clear skill gap, employee willing | Yes | — |
| Behavioral issue, no prior feedback | No | Documented coaching first |
| Role mismatch (great person, wrong job) | No | Internal transfer or honest exit |
| You've already decided to fire them | No | Just separate humanely; don't run theater |
| Repeated misses after 2+ rounds of feedback | Yes | — |
Designing the PIP: 30/60/90 with measurable outcomes
- 1Day 30Three outcomes. Each must be observable by someone other than the manager. Example: 'Ship 2 production PRs that pass code review without rework' — not 'show improved engineering judgment'.
- 2Day 60Three outcomes that build on the first set. Stretch but achievable. Add one outcome that requires collaboration so we can see whether peers want them on the team.
- 3Day 90Three outcomes at the level the role actually requires. If hit, the employee is back to good standing — written confirmation, same day.
Vague outcomes ('demonstrate ownership', 'be more strategic') are the #1 reason PIPs get challenged. If a peer rater couldn't decide whether the outcome was hit, rewrite it.
The opening conversation — script
'I want to be direct with you. Over the last [period], we've talked about [X] in our 1:1s on [dates]. I haven't seen the change we agreed to, and the gap is now at a point where I have to put structure around it. I'm putting you on a Performance Improvement Plan. I want to say this clearly: I am not trying to manage you out. I genuinely believe you can hit this bar — if I didn't, we wouldn't be doing this. Here's what the next 90 days look like, here's exactly what success means, and here's what happens at each checkpoint. I'd like you to take 48 hours to read it, then come back with questions or pushback on any goal you think isn't fair.'
Three things every opening must cover: (1) why now, with specific dates of prior feedback; (2) what 'success' looks like, written down; (3) what happens at day 90, both outcomes explicit.
The bi-weekly check-in cadence
- 30-minute check-in every two weeks. Same agenda every time: progress against each outcome, blockers, what I'm doing to help.
- Written summary within 24 hours — emailed to employee, copied to HR. Three sections: 'On track', 'At risk', 'My commitments to you'.
- Never let a check-in slip. A missed check-in is the employee's first legitimate defense against the whole process.
- If the employee asks for a change to the plan, decide within 5 working days. Either accept in writing or decline in writing with reasoning.
Endgame: success, extension, or separation
- All three day-90 outcomes met or substantially met.
- Written confirmation same day. 'You're off the PIP. Here's what I want to keep seeing.'
- Reset the relationship — don't keep referencing it.
- Extension only if outcomes missed for reasons clearly outside employee's control (illness, scope change). One 30-day extension max.
- Otherwise: separation conversation, scheduled within 5 days. Severance per policy. No surprise.
- Never 'limp along' — it punishes the employee, the team, and the manager.
The paper trail that protects everyone
- Signed PIP document (employee + manager + HR) at day 0.
- Email confirming receipt and 48-hour reading period.
- Bi-weekly written summaries — 6 total over 90 days.
- Any plan adjustments documented in writing within 5 days.
- Day-90 outcome document, signed.
- If separation: termination letter, severance agreement, benefits continuation notice — all dated, all consistent with the bi-weekly summaries.
Read your PIP draft and ask: 'If this person hits every outcome, will I genuinely celebrate it?' If the answer is 'no, I'd be annoyed' — you're not running a PIP, you're running a paper trail. Skip the PIP and run an honest separation conversation instead.
- Performance Reviews People Don’t Dread
- Feedback Frameworks That Land
- Firing someone humanely: the script, the severance math, the reference policy
- Difficult Conversations: A Manager’s Field Guide
- Calibration prep for a manager who's never done it before: a 5-day worksheet
- 1:1 Meetings That Actually Help
- Goal-Setting Frameworks: OKRs vs MBOs vs SMART — Which Fits Your Team
- Continuous Performance vs Annual Ratings: The Honest Trade-Off
Read next
All playbooksThe system around the review matters more than the review itself. A modern approach to goals, feedback, calibration, and the conversation.
Why most feedback fails, and the small set of frameworks that make it useful, specific, and bias-aware.
How to terminate a single employee with dignity and defensibility — the 8-minute conversation script, the severance formula most companies use, what you…