The Department That Kept Ordering Training — And Why Nothing Ever Changed

They weren't failing to learn. They were failing to enforce what they'd already learned. There's a difference, and it matters more than most chiefs want to admit.

I sat across from a fire chief a few years ago who had just finished walking me through the last four years of his department's leadership development history. Two multi-day programs. One outside facilitator. One internal training series built by his deputy. Evaluations that came back strong every time. A command staff that showed up, engaged, and left with the right language.

He slid a legal pad across the table. On it, he'd written out the same three accountability problems he'd been trying to solve since before any of it started.

"None of it moved," he said. "Not permanently."

I've had versions of that conversation more times than I can count. And the thing I've come to understand is that this chief didn't have a training problem. He had a much older, quieter, harder problem — one that no curriculum was ever going to solve on its own.

The first few weeks are always promising

Leadership programs in the fire service tend to follow a recognizable arc. The program runs. People engage in ways they don't always engage in day-to-day operations — there's something about being pulled out of the routine, put in a room with peers, and asked direct questions that surfaces honesty you don't usually see on shift. Battalion chiefs share things. Command staff listens. The energy in the room is real.

And then everyone goes back to work.

For a few weeks, you can see it. The language from the program shows up in conversations. A BC has a hard conversation he'd been avoiding. An officer handles something without kicking it up the chain. The chief notices. Things feel different.

Then they stop feeling different.

Not all at once. Gradually. Someone reverts to an old pattern and nothing happens. Someone else notices that nothing happened, and files that information away. The drift starts at the edges — small things, easy things to overlook. And because each individual instance of drift feels minor, it doesn't get addressed. The moment passes. Then the next moment. Then the next.

"Culture eats strategy for breakfast."— Peter Drucker

Drucker's line gets quoted constantly, usually in the context of organizational change. What it means in a fire department, practically speaking, is this: whatever the training says the standard is, the culture will assert its own standard the moment enforcement goes quiet. And enforcement goes quiet faster than most chiefs expect.

What the middle is actually calculating

Here's what makes this harder in the fire service than in most organizations: the people being asked to hold standards — the battalion chiefs, the company officers — are operating inside a system that has taught them, often repeatedly, that holding the line carries personal risk.

They've watched a grievance get filed on a peer who made a defensible call. They've seen command staff distance themselves when a decision gets challenged, leaving the BC to carry it alone through a process that takes months and costs more than the original issue was worth. They've learned, through experience, that the organization's stated standards and the organization's actual appetite for the fight required to enforce those standards are not the same thing.

So they make a calculation. Not a cynical one — a rational one. They weigh what holding the standard will cost against what letting it go will cost. And in departments where inconsistent enforcement has become the norm, letting it go almost always wins the calculation.

Command staff, looking at this from above, tends to diagnose what they see as a confidence problem. Their battalion chiefs won't own decisions. They avoid the hard conversations. They manage from a distance instead of engaging. The diagnosis isn't wrong about what's happening — it's wrong about why it's happening.

"Leaders must own everything in their world. There is no one else to blame."— Jocko Willink

Willink is right, and most chiefs know he's right. The problem is that owning everything requires an environment where ownership is safe — where a good-faith decision that goes sideways gets backed rather than abandoned. In departments where that environment doesn't consistently exist, asking people to own outcomes is asking them to accept exposure the organization hasn't agreed to share. The training can say all the right things about ownership and accountability. But what the organization actually does when a BC makes a call and it gets challenged is the lesson that sticks.

The question nobody asks after the program ends

Most departments invest significant energy in evaluating training programs. They measure engagement, satisfaction, and immediate application. What they rarely measure — with any rigor or accountability — is what happens six weeks later.

Who is checking whether behavior actually changed? Who recovers the drift when it shows up? Who has the direct conversation with the one officer who went back to the old way and waited to see if anyone noticed?

In most departments, the honest answer is: nobody has been assigned that role. The program ends, the trainer leaves the building, and the organization moves on. The follow-up that would make the training permanent gets absorbed by the next operational priority. Six weeks becomes twelve. Twelve becomes the new baseline. And eventually, someone in command looks around and wonders why the same problems keep surfacing — and orders another program.

The training wasn't the failure. The follow-up was. And the follow-up failed not because people didn't care, but because no one had made it anyone's explicit responsibility to hold the standard after the room cleared out.

What actually changes the pattern

The departments I've seen break this cycle share a few things in common. They don't treat training as a solution — they treat it as a starting point. They come in with a clear, honest read of what's actually happening in the organization, not just what they hope is happening. And they build the follow-up into the structure before the program ever begins — with accountability attached, not left to good intentions.

More importantly, they're honest about what the enforcement pattern communicates. When standards are applied inconsistently — when one person is held to the expectation and another person doing the same thing is not — what gets transmitted through the culture isn't the standard. It's the inconsistency. People learn which rules are real and which ones are negotiable. They learn who they apply to. And that lesson spreads through a department faster than anything you can teach in a program.

"The most dangerous leadership myth is that leaders are born — that there is a genetic factor to leadership. That's nonsense; in fact, the opposite is true. Leaders are made rather than born." — Vince Lombardi

Lombardi's point cuts both ways. Leaders are made by what they're taught — but they're also made by what they're shown. What gets modeled, permitted, and consistently enforced in an organization shapes its leaders far more durably than any program ever will. The chief who wants a different culture has to be willing to look honestly at what the current culture is actually teaching — and decide whether that's the lesson he intends to be giving.

That's the conversation the legal pad was really asking for. Not another program. An honest reckoning with what had been allowed to continue — and what it was going to take to close the gap between the standard on paper and the standard in practice.

That conversation is harder than ordering training. It's also the only one that actually works.

If this is something your command staff is navigating, I'm happy to think it through with you. The Command Culture Index™ is a tool that helps departments surface exactly where the perception gap between command staff and battalion chiefs has opened up — and what it means for how any development program should be designed. There's no obligation attached to that link. A 20-minute conversation is enough to figure out whether this is the right moment for it.