The PIP Was Already Decided Before Anyone Opened the Doc — Here's the Tell

Day 14: The Honest PIP Test

A PIP can torch trust in a single meeting — not because performance gaps are ugly to talk about, but because most PIPs lie about their own purpose, and the person sitting across from you has usually clocked the lie before you finish your opening sentence.

The tell

There's a specific moment in a PIP kickoff where the employee's face changes. It's not when you read out the success criteria. It's earlier — the second they see who's in the room, or notice the invite came from HR's calendar instead of yours, or clock that the doc has some clinical title instead of whatever you'd normally call it. They've done the math before you've said anything real: who scheduled this, how long the doc runs, how formal the room feels. Anyone who's been managed for a few years can smell a decision that's already been made. At that point the actual conversation is almost beside it — you're just confirming what their pattern-matching told them the moment they sat down.

The thing managers won't say out loud

Here's the part nobody puts in the manager training deck: most PIPs get written backward. The manager has already landed on a conclusion — this isn't working, this person needs to go — and the PIP gets built as documentation for that outcome, not as a genuine attempt to answer "can this actually be fixed." HR isn't lying to you when they say a PIP exists to help someone improve. But in practice it's routinely used as a legal and procedural artifact: a paper trail that makes an already-decided termination defensible. The dishonesty isn't in reaching that conclusion — sometimes it's the right one. The dishonesty is running a 30- or 60-day theater production and calling it a fair shot.

My story: legible in the first 60 seconds

I've sat on both sides of this table. One sits with me still — I knew it was a script before the manager finished the opening line. Four things gave it away. First, HR had scheduled the meeting, not the manager — the manager's own calendar showed nothing until HR's invite dropped two days earlier, which meant Legal had already been looped in before the employee had any idea something was wrong. Second, the doc's language was hedge-everything passive voice — "expectations were not consistently met" instead of one specific, falsifiable claim. Vague language in a PIP isn't sloppy drafting; it's built that way on purpose so it can't be argued with, because arguing was never on the agenda. Third, the window was 30 days for a gap that was, honestly, about judgment and system-design instinct — a skill that takes a couple of quarters to build even with real mentorship and heavy AI-assisted pairing to speed up the mechanical parts. Thirty days was never enough, and everyone in that room who'd actually built that skill themselves knew it. Fourth, HR was there from minute one — not as an escalation resource, as a witness. Real coaching conversations don't need a witness on day one.

The tell-tale signatures of a fake PIP

• ▹A window that doesn't match how long the skill actually takes to build — 30 or 60 days for judgment, architecture sense, or leadership presence, none of which compress just because an AI coding assistant can crank out the boilerplate faster
• ▹Success criteria the employee is seeing for the first time in the document, not criteria they helped shape or push back on
• ▹The manager can't say "we want you to succeed" while making eye contact — the line gets said because it has to be said, not because anyone in the room believes it
• ▹Legal or HR present from the very first conversation, framed as support but functioning as documentation
• ▹No real mechanism for the plan to change mid-flight — check-ins are status theater confirming a story already written, not gathering signal that could move the outcome
• ▹Goals only measurable in hindsight ("show more ownership," "communicate proactively") instead of instrumented, checkable weekly deltas
• ▹On AI-first teams specifically: the plan still measures old-world output — PR count, lines shipped, tickets closed — numbers that went noisy or inflated the moment agents started writing a chunk of the code, instead of the judgment and review-quality gap that's the real issue now

What a real PIP looks like

I've seen exactly one PIP where the outcome was genuinely up in the air going in, and it looked structurally different from the first minute. The goals were co-authored — the employee pushed back on one metric as unfair given their team's context, and it actually changed in the doc. The manager had already spent real political capital defending this person before the PIP even opened — extended a deadline for them in a leadership review, argued to keep headcount on the team when it was on the chopping block. That's what skin in the game looks like; a manager who's already burned capital on someone has a real reason to want them to succeed, not just a rehearsed line about it. And critically, the plan was willing to move: it ended three weeks early because the signal was unambiguous and good, not because a calendar said 60 days. That willingness to shorten it, extend it, or scrap it entirely based on what actually happened is the clearest proof the outcome wasn't fixed at the start.

The actual decision point

Sit with this one for a second: the PIP is not where you decide someone isn't working out. If you're honest with yourself, that call got made weeks earlier — quietly, in the pattern you'd already been watching, in the gap between what the role needs and what you're actually seeing. The PIP isn't the decision point. It's the point where you choose whether to be honest with the person about a decision you've already, privately, made. Writing a "fair-looking" PIP to launder a conclusion you've already reached — that's the real harm, not the fact that someone was underperforming. And it's gotten more common, not less, on AI-first teams: agent-driven workflows let a team absorb more throughput with fewer people, so redundancy calls now get made faster and quieter than they used to, and it's tempting to dress up a headcount decision as a performance narrative because it feels less blunt to deliver. It isn't kinder. It's the same dishonesty wearing a different excuse.

Day 14 operating rule

Before you open a PIP doc, answer one question honestly — to yourself, not to HR: if this person exceeds every metric on this plan, do they keep their job? If the answer is yes, genuinely yes, write the PIP and run it like it matters: co-author the goals, set a timeline that matches how the skill actually gets built, and mean it when you say the outcome isn't decided. If the answer is no, or you're not sure, or you already know you'd find another reason anyway — don't write a PIP. Have the harder conversation instead: a direct talk about fit, an exit conversation, or, if it's really a redundancy call, say that plainly instead of hiding it behind a performance narrative. A PIP you don't intend to honor isn't a second chance. It's cover.

Extend your knowledge

• ▹Kim Scott's Radical Candor — the section on "ruinous empathy" is the clearest explanation of why avoiding the hard conversation early is exactly what forces the dishonest PIP later.
• ▹Camille Fournier's The Manager's Path — the section on managing someone out pairs well with today's lesson: what an honest exit conversation looks like when a PIP isn't the right tool.
• ▹Google's re:Work performance management guides — a solid baseline for what a well-designed, criteria-driven improvement plan is supposed to look like structurally, to compare against what you've actually seen run.
• ▹Next time you're handed (or about to write) a PIP, run the Day 14 test on it explicitly before the first conversation — write down your honest answer, not the one you'd say out loud in the room.