The meeting was about a person. A new hire was approaching the end of probation, and someone had to decide whether to confirm the hire.
The company had grown past a hundred people. There were no written criteria for the decision. Nothing that said what this person should be able to do by now, or what the role even required beyond its title.
So the call was about to be made the way these calls usually get made. Whoever felt most strongly in the room would win.
I have sat in a lot of rooms like that. The conversation sounds like an evaluation. It is actually an argument about taste.
The debt nobody sees
Here is the belief I keep coming back to, and I will state it plainly.
Most companies do not have a performance problem. They have definition debt.
Nobody ever wrote down what good means in the role. Not when the role was created, not when the job was posted, not when the person started. So every evaluation, formal or hallway, runs on private standards, and private standards cannot be taught, cannot be met on purpose, and cannot be judged fairly.
The probation decision is simply the first place the debt becomes visible. It also sits under every review cycle, every one-on-one, every quiet story about who is not working out.
When the debt comes due, the bill goes to the person. The hire was a mistake. Someone needs to step up.
The people conversation feels rigorous. It is mostly a way of not noticing that the standard never existed.
The person is rarely the problem.
One sheet, written late
We did not run a workshop or redesign hiring. We built a simple go or no-go evaluation for this one conversion decision.
To fill it in, the manager had to write down, for the first time, what good actually looks like in that role. Which behaviors. Which outputs. What must be true after ninety days.
That is the whole intervention. A sheet that forces a definition.
Two things happened.
First, the decision itself got easier and calmer. With a definition on paper, the room was comparing a person to a standard instead of comparing impressions to impressions. Nobody had to win an argument, and nobody had to carry the verdict alone.
Second, and this is the part worth remembering: the manager changed more than the new hire did.
Writing the definition down exposed something uncomfortable. Half of the ambiguity the hire had been struggling with was not a gap in ability. It was the manager’s unwritten expectations, standards that lived in one head and were graded as if they had been announced.
The hire had been failing a test nobody had shown them.
That is not a performance problem. That is a setup problem wearing a performance costume.
Write it down before you judge by it
The sheet did one more thing we had not planned. It became the onboarding brief for the next person in that role. The next hire will start with answers this one had to guess at.
Sit with that for a second. The document that made one evaluation fair made the next person’s first ninety days clear from day one. A definition is not evaluation paperwork. It is the raw material of clarity.
This is why I keep saying that enjoyable and high-performing are not two dials pointing in opposite directions. Both broke here for the same reason, and both recovered with the same fix. An undefined role is stressful to hold and impossible to excel in. A defined role is calmer to hold and far easier to be visibly good at.
Change the setup, not the people.
So the principle, and it costs one page. For any role you will ever have to evaluate, write down what good means before the evaluation forces you to. Which behaviors, which outputs, what must be true by a specific date.
If you cannot write it down, you have found the real problem, and it is not the person in the role.
The debt is always paid by whoever holds the role. Pay it yourself, in writing, up front.