Nobody is a zero. I have never managed anybody who brought nothing. Everyone is good at something, and usually at something the organization genuinely needs.
That is a generous thing to believe and it happens to be true. It is also the most effective excuse in performance management.
Why “good at X” is never an argument
Watch what happens in a talent review when somebody’s name comes up and the room goes quiet for a second too long. Someone will rescue it. He is fantastic with customers. She is the only one who understands the legacy system. Nobody works harder.
All of those are probably true. That is the problem.
Because nobody is a zero, that sentence is always available. You can say it about your strongest performer and about the person you should have moved two years ago, and it is accurate both times. A fact that is true of everyone cannot distinguish between anyone.
It feels like a defense. It is only a description.
There is a version of this that is worse, and it is the one nobody will say. Sometimes the rescue is not about capability at all. Everybody just really likes the person.
That is not nothing. Morale is real, and a team that enjoys being around somebody is better off than one that does not. But when it is the whole case, what you have is not a valuable team member. It is a mascot: somebody everyone is glad is there, and nobody can quite say what they deliver.
The question that cuts through it
Knowing what you know now, would you hire this person into this role today?
Not generically would you hire them. Nobody is a zero, so the answer to that is usually yes somewhere. Into this role. Today. With everything you have learned since the day you actually did hire them, or became their manager.
The question works because of what it removes. It strips out the money and time already invested. It strips out tenure, and the fact that they were here before you. It strips out the hiring decision somebody is defending, which is sometimes yours. And it strips out the thing doing most of the work: how much you do not want to have the conversation.
What is left is a clean comparison. This person, this role, today, with full information.
The hesitation is the answer
A clear yes is easy and you will know it immediately.
A clear no is rarer than people think, and when it comes you already knew.
The common response is neither. It is a pause. A well… followed by a reason. And the pause is the finding, because you are not calculating during it. You are searching for something that will let you avoid saying the thing you already know.
Leaders do this for reasons that are not cowardice. The conversation is genuinely unpleasant, and postponing it costs nothing today. The person is often likeable, frequently loyal, sometimes has been in the building longer than you have. And answering honestly means conceding that somebody’s judgment was wrong, which is uncomfortable when the somebody is you.
So a case gets built instead. And because nobody is a zero, the case is always available, never false, and never sufficient.
Leaving them there is not kindness
This is the part that gets the ethics backwards.
The instinct to wait feels humane. It is not, and the person on the other end of it usually knows something is wrong long before anybody says so. Not the details. The shape of it. That they are working harder than their peers for less credit. That they are not in the conversations they used to be in. That a story has formed about them somewhere they cannot hear it.
They are accumulating a reputation they cannot see and therefore cannot correct. And every month you wait makes their next move harder: internally, because the story has set, and externally, because the unexplained stretch on the résumé grows.
You are not protecting them. You are spending their time, and time is the one thing you cannot give back.
What a hesitation actually obligates you to do
None of which means the answer is the door. A hesitation is not a termination decision. It is a decision that you now owe them a real answer, and there are three.
The gap is closeable. Name it precisely, not “needs to be more strategic,” which is not a gap, but the actual capability that is missing. Then resource it, with a plan and a date, and tell them plainly what has to be different by when. This is why development plans exist, and it is by a wide margin the cheapest of the three options. You already have somebody who knows the business, the people and the history. Replacing all of that to fix one thing is an expensive way to solve a narrow problem.
The gap is closeable, but not in this role. Underused, and often the right answer. The person who is wrong for the job they are in can be exactly right for one two doors down. Most organizations treat a sideways move as a demotion, so it never gets offered, and a solvable problem becomes an exit.
The gap is not closeable here. Then say so, and say it quickly, because the alternative is the slow version above. Partner with Human Resources and follow your company’s process for performance management. What you do not do is use the process as the reason to delay.
You are not protecting them. You are spending their time, and time is the one thing you cannot give back.
A starter, not a finisher
Somebody who worked for me owned our marketing collateral, the finished material that reached customers, prospects and editors. In that job the quality of the artifact is the message. Perception was the product.
She did not have great attention to detail. Other people caught the mistakes, and too often nobody caught them and they went out. The sheer volume of work she produced was impressive, which made her easy to defend, and I defended her for a while.
I would not have hired her into that role. Once I let myself answer that plainly, the rest moved quickly.
What she was exceptional at was starting things. She could take an initiative that had been stuck in a slide deck for two quarters and have it moving inside a month, and we had a queue of those, things everybody agreed mattered and nobody had got off the ground. She was a starter, not a finisher.
There was a cost I had not admitted to either. She felt over-coached, and she was right. I was correcting her constantly, and not because it was making her better. I was doing it because I was embarrassed by the mistakes that reached customers.
There were three ways to go and two of them were easier. I could have kept justifying the mistakes on the strength of the volume: the case was right there, and it was not false. Or I could have let her go, which would have been clean and would have cost the company somebody who was genuinely good at something it needed.
I took the middle one. I moved her into a role where getting something started mattered far more than finishing it cleanly. She has since been promoted several times into roles that suit her. We no longer work together, but I see her on LinkedIn. She got the chance to race her strengths and damn are those strengths valuable.
Nobody is a zero
Take that seriously and it stops being a reason to keep somebody. It becomes a reason to find out where they would be a strong yes.
The question was never whether this person is valuable. They are. It is whether they are valuable here, in this role, doing this, and whether you are willing to find out rather than to keep describing what they are good at.