Why Angry Leadership Works, Until It Doesn't

Last week, we looked at anxiety and the idea that feelings are information, not instructions.

The same is true of anger. But anger is tricky because sometimes it works.

A leader tells me:

“I know I come down too hard on my team. I raise my voice, threaten consequences, and tell them if they can’t get the job done, I’ll find someone who can.”

Then comes the justification:

“But what am I supposed to do? Nothing happens unless I get angry.”

There may be some truth in that. People respond when the boss gets angry. Deadlines suddenly matter, emails get answered, people stay late, and mistakes get corrected.

So the leader learns: Anger gets results. At least in the short term.

What Anger Is Trying to Accomplish

I ask: “What do you actually want from your team?”

Usually the answer isn’t that they want the team to be afraid of them.

It’s some version of:

“I want them to take responsibility and to follow through.”

“I want to know I can count on them. I’m tired of carrying everything myself.”

Now we’re getting somewhere. The goal isn’t anger. It's actually accountability, reliability, and cooperation.

Anger has simply become the strategy for getting it.

The High Cost of Anger

The team may comply when the boss gets angry, but they also learn:

• Not to bring bad news too early
• Not to admit mistakes.
• To wait to be told what to do rather than risk making the wrong decision.

The leader gets obedience while gradually losing honesty, initiative, and trust. That’s a high price for short-term compliance.

Calm Doesn’t Mean Permissive

Here’s where many frustrated leaders get stuck. They’ve tried saying:

“This deadline was missed twice. I need to understand why, and we need a clear plan to prevent it from happening again.”

And then it happens again. So they conclude: See? Being calm doesn’t work.

But the alternative to anger isn’t endless patience. It’s firmer accountability.

If expectations have been made clear and performance still doesn’t change, the leader needs to escalate without exploding.

They need to ask what's getting in the way. Is it ability, clarity, resources, or willingness?

Then make the expectation unmistakable: “This needs to be completed by Thursday at 3 p.m. If something threatens that deadline, I need to know by Wednesday.”

And put ownership back where it belongs: “What will you do differently this time?”

If the pattern continues, calmly state and follow through on the consequence: “If this happens again, we’ll need to address it as a performance issue.”

That may mean changing responsibilities, formal performance management, or eventually deciding the person isn’t right for the role.

But here's the interesting thing: None of that requires anger.

The leader doesn’t have to choose between being nice and tolerating poor performance or becoming threatening enough to force compliance.

There's a third option: Be calm and consequential.

Feelings Are Information, Not Instructions

Anger contains useful information: something important isn’t happening; a boundary may have been crossed; or you're growing frustrated because you don’t feel supported.

Listen to that information but not to anger’s instruction, which might be: Make them afraid enough to do what you want.

Instead, ask:

1. What is my anger telling me matters here?
2. What do I actually need from this person or team?
3. What response is most likely to create that result over time?

The goal isn’t to get rid of your anger. You can't control your feelings.

It’s to understand what the anger is asking for and choose a response that creates accountability without destroying trust.

Next week, we’ll look at guilt and how the desire to avoid disappointing people can quietly turn into overcommitting, people-pleasing, and taking responsibility for far more than is ours.

Let’s keep doing this together.

Jo-Aynne Von Born, Leadership/Executive Coach

​READYSETMORE​