I've managed people for eight years and I'd written three Performance Improvement Plans before last year. All three ended in termination. Somewhere along the way I'd started thinking of the PIP as exactly what cynical employees suspect it is: paperwork to document a decision that's already been made, the legal shield you raise right before the inevitable. I'm not proud of that, but it was honestly how I'd come to see the document — a thing you issue when you've given up but need a paper trail.
Then I had a team member whose decline was obviously situational. A hard stretch at home, a project he was genuinely mismatched to, and a communication breakdown with a teammate that had been quietly rotting for months while I told myself it would sort itself out. I didn't want to lose him. He'd been excellent for two years. I wanted to give him a real, honest shot at getting back to the person I knew he could be — and I realized my usual approach to PIPs would actively work against that.
What I did differently
I ran the Performance Improvement Plan Draft — Kind, Specific, and Actually Defensible prompt through GPT-4o. I described the concrete issues — two client deliverables late without notice, inconsistent status updates to the team — and the feedback I'd already given over the prior quarter so it wouldn't read as a surprise ambush. I used GPT-4o specifically because I knew I'd iterate on this five or six times, tightening the wording and reworking the support section until it felt right, and GPT-4o is fast and cheap enough that I never once hesitated to regenerate or tweak. The draft opened with a purpose statement that framed the plan as a structured opportunity rather than a disciplinary action, and that single reframing was unlike any PIP I'd ever written.
The section nobody puts in their PIPs
The part that changed the entire conversation was Support & Resources. The prompt simply won't let you skip it — it requires at least two concrete commitments from the company, not just a list of demands aimed at the employee. So I committed, in writing, to weekly thirty-minute coaching sessions, a pairing with a senior colleague he respected, and a temporarily reduced project load for the first two weeks so he could actually breathe and rebuild some momentum. Writing those commitments down made the plan bilateral instead of a one-sided indictment. When I walked him through it, his first words were, "You actually want this to work." He was right, and the document had proved it before I had to say a word.
- Every concern had a SMART expectation, so he knew exactly what success looked like rather than guessing at a moving target
- Weekly check-ins were structured: fifteen minutes on wins, fifteen minutes on blockers
- Mid-point review at the halfway mark showed real, measurable progress on two of three areas
- Final review: all criteria met, plan closed successfully, and a [LEGAL REVIEW] flag the prompt added on one clause that I did run past HR before issuing
The honest part
He completed the plan and he's been one of my steadiest people since. Can I prove the framing caused the turnaround? No, and I want to be honest about that — maybe he'd have recovered anyway once the situation at home settled. But the process felt genuinely supportive instead of performative, and I can tell you with total certainty that my three prior PIPs did not feel that way to anyone involved, least of all me. The difference wasn't that the prompt wrote a kinder document in some flowery sense. It's that it forced me to put real support commitments in writing, and the act of writing them down is what made them real and made me accountable to them.
A serious caveat
A PIP is a serious legal instrument with real consequences for a real person, and no prompt replaces your HR and legal review. The [LEGAL REVIEW] flags the prompt inserts are a prompt to actually escalate, not a checkbox to clear. I treat the output as a strong, well-structured first draft that I and my HR partner then own. Used that way, it raises the floor on every PIP I write — even the ones that, despite everyone's best effort, don't end in a turnaround. Grab the Performance Improvement Plan Draft — Kind, Specific, and Actually Defensible prompt on Prompt Dock when you have someone worth fighting for. And when the plan works and review season comes around, I run that same person's notes through my Fair Performance Review Summary from Messy Manager Notes prompt to make sure the recovery gets recorded as clearly and fairly as the problem ever was.