The Hardest Thing, No. 6. Expanded from the Oct 13, 2026 Tuesday post.
You are twenty minutes into delivering a performance improvement plan. The document is on the table, you have walked through the first two concerns, and the employee looks up and says, quietly, “This is because I’m over 40, isn’t it.”
That sentence stops managers cold, and almost nobody has rehearsed for it.
The untrained move comes in two flavors, and both go wrong. The first is defense. “That has nothing to do with it.” It comes out fast and a little sharp, because the manager feels accused, and now two people are arguing about motive instead of talking about the work. The second is retreat. The manager panics, softens everything, and ends the meeting without finishing the plan. That one feels kinder in the moment. It isn’t. It tells the employee the accusation worked, and it tells anyone who reads the file later that the manager stopped the second someone named something he had reason to hide.
Here is what I coach instead. You stop. You take it seriously. And you separate the two things, out loud, so the employee hears that both are real.
“I hear you, and I want to be clear that I take that seriously. Age has nothing to do with this plan, and if you believe it does, I want you to raise that with HR today, and I will make sure it’s looked at properly. Separately, the performance concerns in this document are real, they’re specific, and we’re going to walk through them. Both of those things can be true at the same time.”
Then you finish the PIP. Every item, same tone, same pace. And before you leave for the day, you send HR a short note in writing: what the employee said, what you said back, and when. Two or three sentences. Not your opinion of whether the concern is fair. Just the record.
Why does this work? Because a protected-class flag is not a trapdoor. It is a second conversation, and it belongs to HR, not to the manager in the room. The manager’s job is not to win the argument about whether age played a part. He can’t win it, and trying makes it worse. His job is to make sure the concern gets heard by someone who can look at it fairly, and to keep the first conversation intact.
That second conversation matters more than most managers realize. When HR follows up, the questions are real ones. Were these same expectations applied to everyone in the role? Were the concerns raised before today, in writing, with dates? Is there anything in the file, a comment in a review or a joke in a team chat, that would make the employee’s worry reasonable? Sometimes the honest answer turns something up, and you want to find it now, not in a deposition. Most of the time the file holds, and the employee still gets something that matters: proof that when they raised a concern, the company took it seriously instead of taking it personally.
One more thing. Once an employee raises a concern like this, everything that happens next will be read in its light. Raising a discrimination concern is protected, and a decision that looks like payback is its own claim. So the plan stays exactly as written. Same check-ins, same standards, no new items quietly added in week two. Clean and consistent protects everyone.
This is one of the moments I built my agents to catch, because it happens fast and nobody practices it. The words are short. The discipline is the hard part: don’t get defensive, don’t fold, and don’t decide alone.
Treat it that way and you protect the employee, the manager, and the company at the same time. Almost nothing else in this job does all three.
The hardest parts of HR, handled.