Why defensible decisions still cost you: The difference between protecting the organization and actually leading it
There is a phrase that keeps surfacing in my coaching work with fire service leaders.
They don't say it out loud. But it lives in the subtext of almost every difficult situation I sit with them inside.
The phrase is: I did everything right — and it still went wrong.
Not wrong legally. Not wrong procedurally. The process was followed. The documentation was solid. HR signed off. The chief's action was defensible in every way that matters to the organization's legal posture.
And the culture still paid for it.
I want to talk about why that happens. Because until you understand the gap between defensibility and leadership credibility, you will keep making technically correct decisions that quietly cost you the thing you need most — the trust of the people in the stations.
Process protects the organization. Leadership shapes it.
When a difficult situation lands on a chief's desk — a discipline issue, a contested promotion, a complaint that implicates a senior member — the instinct is to manage it. Find the right policy. Follow the right steps. Protect the department from legal and political exposure.
That's appropriate. It's also insufficient.
Because the people in the stations aren't evaluating your decision by the same rubric HR uses. They're watching something different. They're watching what your decision signals.
What does this tell me about what matters here?
Whose side does the organization protect when it costs something?
What happens to people who do the right thing — and people who don't?
Is the standard real, or is it negotiable depending on who you are?
Those questions don't get answered in the memo. They get answered by what you do. And once the organization has an answer, it's very hard to change.
The defensible call that destabilized a culture
Here's a pattern I've seen more than once — the names and departments are different, but the structure is almost identical.
A senior member is producing strong operational results. He's also creating problems the organization has been managing around for years — not formally, but informally. The exceptions have accumulated. The look-the-other-way moments have added up. Everyone at the station level knows the score.
Then something happens that forces the chief's hand. Documentation is assembled. Progressive discipline is applied. The process unfolds exactly as it should.
And the culture still doesn't move.
The chief did everything right. The discipline was defensible. And the people in the stations read it as: you only acted because you had to. You already knew. You chose to manage this quietly for as long as you could. This action is about protecting the department, not about standards.
They weren't wrong.
The action was correct. The preparation behind it — the cultural groundwork, the conversations that should have happened earlier, the standard that should have been stated plainly before it was tested — wasn't there. So the action landed without the credibility it needed to actually change anything.
What the people in the stations know
Here's the hard truth about fire service leadership: your people are excellent observers.
They notice what you enforce and what you let slide. They notice who gets held to the standard and who gets the exception. They notice whether your actions are consistent or situational. They notice the gap between what you say matters and what your decisions reveal actually matters.
And they draw conclusions. Those conclusions become the real culture of your organization — not the mission statement on the wall, not the values listed in the strategic plan. The culture that lives in the kitchen at 0200, in the conversations that happen when you're not in the room.
That culture is built one signal at a time.
Every decision you make teaches your organization something. The question is whether you're aware of the lesson you're sending.
Second-order effects are almost always more important than the original decision
Most leaders think about the immediate outcome. Did we resolve the situation? Did we stay out of legal jeopardy? Did the issue go away?
The more important questions are downstream.
What behavior will increase because you enforced that standard? What behavior will decrease — or disappear entirely — because you looked the other way?
Who stopped reaching because of what that promotion signaled? Who started speaking up because you protected the person who filed the report?
Who decided they can trust this organization — and who decided they can't?
Those are the questions that separate leaders who manage situations from leaders who shape organizations. And they only get asked by leaders who are willing to look past the immediate relief of a resolved situation and ask: what did I just teach everyone who was watching?
What this requires of you
It requires getting out ahead of the problems you can see coming.
It requires stating the standard clearly before it's tested — not after.
It requires being consistent when it's inconvenient, enforcing accountability with people who deliver operationally, and protecting the people who do the right thing even when it creates friction above you or around you.
It requires carrying decisions long after the meeting ends.
That's not comfortable work. It's not always recognized work. But it's the work that determines whether your organization is functional or actually healthy — whether your best people stay, reach, and trust the institution they're serving.
Defensibility and leadership credibility are not the same thing.
The people in the stations know the difference.
I've spent the last year building something around this exact problem. More on that July 1.
— Chief Chris Armstrong The Thinking Chief Leadership Group, LLC TheThinkingChief.com