When Decisiveness Turns to Liability

The Commander is the schema you appoint in a crisis. It is also the one you have to watch once the crisis has passed.

There is a phrase you hear in big organisations when nothing is moving.

"It's just how things get done here."

Say it out loud and it sounds like culture. Listen properly and it is something sharper. It means someone at the top is commanding, and everyone below has quietly learned to wait.

I have placed leaders into rooms just like that. Sometimes I have placed the very person doing the commanding. And the Commander is, more often than not, exactly who you want. Right up until they aren't.

If you have been keeping up with this newsletter series, you will know what comes next.

A couple weeks ago I introduced the "Four", the four behavioural patterns I see repeat in senior leaders, again and again, whatever the sector or the job title. Commander.

Architect. Servant. Visionary. I said then that I would take each one in turn, look at how it behaves on a good day, and name what it means when the pressure is on.

We start with the Commander. Partly because it is the one most people picture the moment they hear the word leader. But, mostly because its pressure-state default does the most damage before anyone thinks to look for it.

The schema you appoint in a crisis

The Commander takes charge. They set direction and hold it. They cut through noise and get a team moving while everyone else is still forming a committee. When a business is on fire, when the clock is the enemy and someone has to own the call, the Commander is the hire needed.

I have watched Commanders rescue businesses that a more consensual leader would have talked into a state of near death.

There is a reason the schema exists. It works.

The instinct that says "someone has to be in charge, and it may as well be me" is the instinct that turns a stalled situation into a moving one.

And, boards love it in the interview.

It reads as decisiveness, conviction, grip.

That is the strength. Now the part the interview never shows you.

What pressure does to it

Every schema has a default that fires under pressure. Ian Stewart, whose framework sits behind this series, calls it "the schema tightening." Under schema tightening the Commander's is the most recognisable of the four.

Under real pressure the Commander does not change tactics.

They do more of what already made them effective.

The directives sharpen.

The tolerance for debate shrinks.

Dissent starts to get read as disloyalty, and the people who used to push back learn that pushing back costs them in their ability to be heard. The room keeps moving, because the Commander keeps it moving. It just stops thinking.

That is the trap. The behaviour that looked like strength on a good day becomes the thing that hollows out the team on a bad one. And because the business is still visibly moving, nobody catches it until something jams.

The leader everyone learned to wait for

Let me give you a real one, anonymised.

A while ago I placed one of the most effective leaders I have ever worked with into a business that was on its knees. A genuine turnaround, the kind most people look at once and walk away from. He took hold of it, and within months it was “stable”. Decisions that had been stuck for a year were getting made in a week.

The board exhaled.

On every measure that mattered, the appointment was a triumph.

Then the crisis passed, and the command did not.

The same grip that rescued the business stayed clamped on long after the emergency was over. Every decision of any size still ran through him. The capable people he had inherited, and the good ones he went on to hire, slowly stopped offering a view, because a view that differed from his had stopped being worth the friction.

Meetings turned into briefings.

The questions dried up.

Eighteen months in, two of his strongest people had gone. He was working fourteen-hour days because, by then, nothing moved unless he moved it. He had become the single point the whole business turned on.

The board still saw a safe pair of hands. What they actually had was one person thinking for the entire organisation, and a team that had quietly forgotten how to think for themselves.

What it costs, and why boards miss it

The cost of this never lands in one place.

It builds quietly.

Good people stop raising risks, because raising risks is exhausting. Information stops flowing upward, so the Commander makes the next call with less of the picture than they think they have. Work that depends on two functions cooperating without a memo simply does not happen.

By the time it shows in the numbers, it has been true in the behaviour for a year.

This is why I am wary of assessing a Commander on track record alone.

The track record is usually superb.

It was built in the exact conditions where the schema shines: pressure, ambiguity, a clear mandate to take charge. Drop the same leader into an organisation that needs collaboration more than command, or leave them in post long after the crisis has passed, and the very pattern that delivered the wins starts to manufacture the losses.

The Commander who can see it

None of this is a case against hiring Commanders. I place them deliberately, and often. It is a case for hiring the ones who can see their own default.

Remember we are talking about a schema, not a personality type. When a person knows their default schema they can often manage it to be more effective in different scenarios.

The Commander worth backing is the one who knows what they do under pressure and has the ability and awareness to act against it. They put someone in the room whose job is to disagree, and they actually listen. They notice when the team has gone quiet and treat the silence as information, not agreement.

They ask the question they would normally just answer themselves. That is the line between a schema that drives a business forward and one that slowly teaches everyone around it to stop thinking.

A Commander rarely needs to become someone else.

They need to know which version of themselves the moment is asking for. In a crisis, command. When the crisis passes, ease off the throttle before the team forgets how to move on its own.

Before your next senior conversation

If you lead, here is the uncomfortable test.

When was the last time someone genuinely disagreed with you in a meeting, and you changed your mind?

If you can name it, you are probably regulating the default well. If you have to think hard, the room may already have learned to wait.

Next in the series: the Architect, the leader who builds beautiful systems and sometimes forgets to ship them.

Chris Underwood

Adastrum Consulting

chris.underwood@adastrumconsulting.com