Most advice about holding people accountable quickly moves to progressive guidance. Set the expectation, document the gap, escalate to discipline. The mechanics are not wrong. They are just second, and when a leader reaches for them first they usually do not work.
They don’t work because accountability is not perceived the same way by everyone. The same conversation, using the same words, can be help for one employee and a threat for another. The difference is whether that employee trusts me, and that needs to happen long before I sit down with potential progressive discipline.
If they do not trust me, accountability is not a correction. It is the first step in getting rid of them, and that is how they will hear it no matter how carefully I say it. Once someone believes I am building a case, nothing useful happens after that. They stop listening for what needs to change and start thinking about their defense.
Why departments let a standard go
There are real reasons departments let a standard go. A hiring freeze or few applicants. A position that takes months to fill, and a team already covering the gap. I understand those pressures, but they cannot be part of the decision, or a reason to ignore a problem.
Accepting poor performance because I am afraid of an open position is weak, and it is a bad decision. I keep the person and lose the standard, and the standard is what the rest of the team is watching.
So the slow approach I take to formal discipline is not hesitation. It is process. There is something that has to come before progressive discipline, and skipping it is what makes progressive discipline fail.
Trust is not built in the accountability conversation
Trust is not built in the accountability conversation. It is built in everything that happened before it, and by this point it either exists or it does not.
The work that builds it is ordinary, and it is mostly recognized by consistency:
- Being where the work happens often enough that my presence is not a signal that something is wrong
- Fixing what I said I would fix, and going back to say so when I could not
- Telling the team what is coming before they hear it from somewhere else
- Making the standard visible, in writing, at the point of work, so nobody is ever corrected against a rule they were never shown
- Backing an employee when they are right, including when backing them is inconvenient for me
None of that is dramatic. It accumulates. And what it buys is the benefit of the doubt, which is the only thing that lets a hard conversation be heard as help.
When an employee trusts that I want them to succeed, I can tell them plainly that the work is not meeting the standard, and they will hear a leader trying to keep them. When they do not trust that, the identical sentence means I am moving them toward the door.
Accountability to the standard is different
Trust also determines what accountability is about, and it should not be about me.
When accountability is personal, it turns into a contest between two people, and the employee always has the option to leave the contest. Compliance with me is a weak thing to ask for, and it disappears the moment I am not standing there.
Accountability to the standard is different. The room gets terminally cleaned to a defined process because the next patient in that bed has no way to protect themselves. The high-touch surfaces get disinfected because that is where transmission happens. The work is not owed to me. It is owed to the patient, and to the person on the next shift who inherits whatever we left behind.
That is a conversation very few people argue with. I am not asking anyone to obey me. I am pointing at something we both already agree matters and asking whether the work met it.
Talk to them or write them up
Ask some frontline leaders what should be done about a performance problem, and the answer is talk to them or write them up. Those are the two ends of a range, and almost everything useful lives in the middle.
Retraining is a consequence. So is a check-in schedule, a change in assignment, a shadowing shift with a strong performer, or a defined date when we look at the same measure again. None of those threaten the person’s job. All of them say the standard is real and I am paying attention.
They also say something the formal steps cannot say, which is that I am still investing. That is the difference between correction and removal, and employees read it accurately.
Reserve the formal steps for what they are built for, which is a behavior that has not changed after real attempts to move it. Reaching for them early spends the most serious tool I have on a problem a job aid would have solved, and it tells the employee exactly what they suspected about my intentions.
A team can carry a demanding standard
A team can carry a demanding standard. What a team cannot carry is watching one person skate while everyone else absorbs the difference.
Every strong employee is doing arithmetic. They see who is producing and who is not, they see what happens to each, and they draw a conclusion about whether effort is worth anything here. When a poor performer faces nothing, the message is not that we are a forgiving department. The message is that the standard is optional, and the extra work is unpaid.
This also destroys the trust I have been building. The people I have been consistent with are watching me be inconsistent about the only thing that costs anything.
The good employees do not complain about this. They leave.
Avoiding accountability produces the loss it was meant to prevent
Avoiding accountability produces the loss it was meant to prevent. It only changes who leaves.
Enforcing the standard risks losing the person who is not meeting it. Refusing to enforce it means losing the people who are. One of those is a loss I can plan for and recover from. The other one hollows out a department slowly enough that it looks like bad luck.
So the question is not whether I can afford to hold people accountable. It is whether I have built the trust that lets accountability mean what I intend it to mean. When that trust is there, when the standard is visible, when it points at the work instead of at me, and when it applies to everyone the same way, most people meet it.