An employee misses a deadline. Two reminders went unanswered, a customer is frustrated, and someone else has to clean up the problem. The manager has every reason to address it. Instead of having a direct conversation, though, the manager calls the employee out in front of the team and adds a sarcastic comment about whether anyone understands what a deadline is.
When someone later questions the approach, the manager offers a familiar defense: “But I was right.”
Yes. About the deadline.
That does not settle the question of how it was handled.
This is an uncomfortable distinction because being right feels like it should count for more. We identified the problem. We understood the consequences. Maybe we even warned everyone before it happened. Surely that earns us some latitude in how we respond.
It may explain our frustration. It does not give us unlimited permission to express it.
You can be correct about what happened and unfair in how you address it. You can have a legitimate complaint and deliver it with unnecessary cruelty. You can defend an important standard while behaving in a way that undermines another one.
The original problem and your response are separate things. Both deserve an honest evaluation.
When Being Right Becomes Permission
One of the risks of being certain is that we may stop examining ourselves. Once we have decided the other person is wrong, our attention shifts almost entirely toward what they need to understand, admit, or change. How we behave becomes secondary because, in our minds, they created the situation.
They missed the deadline. They broke the agreement. They failed to listen. They made the decision we warned them not to make.
All of that may be true. None of it makes every possible response reasonable.
There is a difference between explaining the consequences of someone’s behavior and trying to make them feel small. There is a difference between documenting a repeated problem and copying people into an email because we want an audience. There is a difference between holding someone accountable and continuing to press after they have acknowledged the mistake because we have not yet finished being angry.
At that point, we may no longer be trying to solve the problem. We may be trying to collect something from the person who caused it: embarrassment, submission, or the satisfaction of watching them admit how right we were.
I think that is a question worth asking ourselves in a difficult conversation: What would be enough here? An explanation? A correction? A clear commitment that the behavior will change? Or am I looking for a particular degree of discomfort before I will consider the matter settled?
Accountability needs a purpose beyond making someone pay emotionally for frustrating us.
Leadership Makes the Responsibility Larger
For a leader, this distinction matters because authority changes the weight of a response. A sarcastic remark from a peer and a sarcastic remark from the person who controls your responsibilities, compensation, or future are not the same interaction.
A manager may consider an exchange a brief expression of frustration. An employee may leave it wondering whether they are respected, whether their job is secure, or whether speaking up next time is worth the risk.
That does not mean leaders should avoid uncomfortable conversations. Quite the opposite. Addressing poor performance clearly is part of the job. Letting a problem continue because confrontation feels unpleasant is not especially kind to the employee, the customer, or the teammates carrying the extra work.
But the conversation should make the expectation clearer, not merely make the leader’s anger more visible.
In the missed-deadline example, a productive discussion would establish what was expected, what happened, why the reminders went unanswered, and what needs to change. Depending on the circumstances, consequences may be appropriate. None of that requires sarcasm or an attack on the employee’s character.
Sometimes an issue must be addressed immediately or in front of others. A leader should not allow an unsafe action to continue while searching for a private room. A team may need a public correction to information everyone heard. The question is not whether correction must always be gentle or private. It is whether the response serves a legitimate purpose and stays proportionate to it.
Leadership requires more than noticing when someone else has fallen below the standard. It requires remaining accountable to a standard while addressing it.
The People Closest to Us Are Not Exceptions
The same responsibility follows us home.
Suppose your partner agrees to call when plans change and does not. You are left waiting, rearranging your evening, and wondering what happened. That is a reasonable concern to raise.
“We agreed that you would call, and I was left waiting” addresses the broken agreement. “You never think about anyone but yourself” turns that event into a judgment about the whole person.
The second statement may feel more satisfying when you are angry. It also asks the conversation to carry much more than the original problem. Now you are arguing about whether they are selfish, whether “never” is fair, and whether the last ten years support your accusation. The agreement that actually needs attention can disappear beneath the argument you built around it.
This does not mean every conflict should be treated as an isolated incident. Repeated behavior matters, and patterns deserve to be named. But naming a pattern requires specific examples and a clear explanation of its impact, not an unlimited license to reach for whatever will hurt most.
Knowing someone well gives us insight into how to communicate with them. It also gives us access to their insecurities. Those are not interchangeable tools.
There is something particularly troubling about demanding care from another person while choosing language designed to wound them. The need underneath the complaint may be completely legitimate. The method still needs to change.
Neither Truth Nor Tone Gets a Free Pass
This principle can also be misused, especially in workplaces and public life. Someone raises a valid concern, and instead of answering it, the person responsible focuses entirely on how the concern was expressed.
Suddenly, the unanswered question, broken commitment, or poor decision disappears. The discussion becomes a lecture about being respectful.
I do not buy the idea that a problem only deserves attention when it is presented pleasantly enough.
An employee should not have to deliver a flawless speech before a manager takes a concern seriously. A resident should not have to sound agreeable before a public body answers a reasonable question. Someone who has been repeatedly ignored may have good reason to be angry.
Discomfort is not evidence that the speaker handled it wrong. Firmness is not cruelty, and a refusal to accept another vague answer is not automatically disrespect.
Public decisions also deserve public scrutiny. If the issue affects the community, bringing it before the community may be entirely appropriate. “Handle it privately” should not become a convenient way to keep legitimate problems out of view.
But public accountability does not require personal contempt. A resident can challenge a project’s cost, question its priorities, and demand a clear explanation without ridiculing the people who support it. Those responsible can object to a personal insult without using that insult as an excuse to avoid the underlying question.
The standard has to work in both directions: having a valid concern does not excuse every behavior, and behaving imperfectly does not invalidate every concern.
These are separate judgments, not a requirement to divide the blame equally.
An Apology Is Not a Surrender
Perhaps the most useful part of this distinction is what it makes possible after a conversation goes badly.
We often resist apologizing because we think it will concede the entire argument. If we admit we handled something poorly, the other person might conclude that their behavior was acceptable. So we defend our response as aggressively as we defended our original point.
That leaves us protecting behavior we might otherwise recognize as wrong.
There is another option.
“I should not have made that comment in front of the team. It was disrespectful, and I apologize. We still need to address the missed deadline and agree on how this will be handled going forward.”
That is not a contradiction. It is an example of applying accountability to both people.
The apology does not need a “but” attached to it. The original issue does not need to be withdrawn. Each can stand on its own.
The same is true on the receiving end. Someone who raises a concern badly may owe you an apology. You may still owe them an answer. Waiting for them to handle everything perfectly before examining your own behavior is another way of avoiding responsibility.
The more demanding version of maturity is being able to say, “My point was valid, and my behavior was not.” It requires giving up the comfort of being entirely justified without giving up what actually matters.
Before the next difficult conversation, it is worth deciding what a good outcome would look like. What needs to be understood? What needs to change? What consequence or boundary is necessary? Then consider whether your planned response moves toward that outcome or simply expresses how angry you are.
You cannot control whether someone listens, agrees, apologizes, or changes. Handling a conflict well does not guarantee a satisfying result. It does mean you have not made their poor judgment the excuse for abandoning your own.
You do not have to choose between standing your ground and taking responsibility for your conduct.
A valid point deserves to be handled well.