Your Battalion Chiefs Aren't Avoiding Accountability. They're Avoiding the Environment You Built Around It.
I've asked command staff and battalion chiefs to describe their organization's culture in the same sitting — separately, before they've heard each other's answers. I've done this enough times now that the pattern is no longer surprising, but it still stops me every time I see it laid out.
The executives tend to describe a department that is functional, improving, and hampered by middle leaders who won't fully own their span of control. The battalion chiefs tend to describe a department that is compliance-driven, where accountability is applied selectively, and where making a decision that gets scrutinized from above is a professional risk they've learned to manage carefully.
Both groups are describing the same organization. Both are telling the truth. And in most cases, neither side has ever sat in the same room and heard the other say it.
That gap — between what leadership sees from the top and what the middle experiences every shift — is where culture actually lives. And it is almost never closed by training alone.
How the perception gap forms
It doesn't happen because anyone is being dishonest. It forms the way most organizational problems form — gradually, through the accumulation of small signals that go unaddressed.
A battalion chief makes a call. It goes sideways — not badly, not catastrophically, just sideways. Instead of the kind of institutional backing that says "we support good-faith decisions even when they don't land perfectly," the response from above is quiet distance. The process runs. The BC carries it mostly alone. He's cleared, eventually, but what he learns from that experience isn't about the decision. It's about what the organization does when things get complicated.
So he adjusts. He starts consulting up before deciding down. He documents more before acting. He waits for clearer direction before moving. The decisiveness that got him promoted becomes something he manages carefully, because the cost of getting it wrong has turned out to be higher than the cost of moving slowly.
Command, watching this from above, sees a BC who won't own his span of control. What they're actually watching is a rational adaptation to the environment they helped create — one decision at a time, through what got backed and what didn't.
"You are not responsible for the environment you were born into, but you are responsible for the one you create." — General James Mattis
Mattis's standard is unambiguous — and it applies directly to this. The environment a BC is operating in didn't appear from nowhere. It was built, gradually and often unintentionally, by the accumulated decisions of the command staff above him: what got backed, what got abandoned, what was enforced consistently and what wasn't, whose grievance got fought and whose got settled quietly to make it go away. Those decisions communicate something more durable than any leadership program can teach.
The grievance calculation nobody talks about
There is a dynamic in the fire service that sits just beneath most leadership development conversations, rarely named directly even though it shapes behavior at the battalion level more than almost anything else. It's the calculation a BC makes every time a standard is worth enforcing — weighing what holding the line will actually cost against what letting it go will cost.
In departments where grievance culture has calcified, that calculation almost always goes the same direction. The BC knows that enforcing a standard on the wrong person, in the wrong way, can trigger a process that takes months, consumes significant administrative energy, and may ultimately go nowhere — leaving him exposed and the person he addressed no more accountable than before. He also knows that in some departments, the way a grievance gets resolved sends a clearer message to the workforce than the original enforcement did.
So he makes the calculation. He picks his moments. He enforces where the path is clean and steps back where it isn't. And what looks, from above, like a confidence problem or a willingness problem is actually a risk management problem — the direct result of an environment that has repeatedly taught the middle that holding the line is a solo act.
The training can tell a BC all the right things about accountability and ownership and leading with courage. But if the environment he walks back into on Monday morning hasn't changed, the training gets absorbed by the environment — not the other way around.
"The single biggest problem in communication is the illusion that it has taken place." — George Bernard Shaw
Shaw's line lands differently in this context than it usually does. Most chiefs believe they've communicated their expectations clearly. The values are stated. The standards are written. The training has been delivered. The communication, by every visible measure, has taken place. What hasn't happened — in most departments — is the conversation where both sides actually say what they're experiencing. Where the BC tells the chief what it feels like to make a call and carry it alone. Where the chief tells the BC what it looks like from above when decisions don't get made. Where both sides sit with the discomfort of recognizing that they've been designing solutions for opposite halves of the same problem.
What closing the gap actually requires
The departments that move — the ones where the culture actually shifts rather than the language shifting — tend to share something in common. At some point, the command staff stopped diagnosing the battalion chiefs and started listening to them. Not in a survey. Not in an anonymous feedback process. In a room, with both sides present, looking at the same data about what each group is experiencing.
That conversation is uncomfortable. It requires a chief to hear things about his own organization that he may not have heard before — or may have heard and not fully believed until he saw it reflected back by his entire battalion chief group at once. It requires the BCs to say, directly, what they need from command in order to lead the way command is asking them to lead. And it requires both sides to resist the instinct to defend their own position long enough to genuinely understand the other one.
What tends to come out of that conversation, when it's structured well, is not blame — it's recognition. A chief who sees clearly, often for the first time, that his battalion chiefs are not avoiding accountability because they lack courage. They're avoiding it because the environment has consistently taught them that accountability is a risk the organization is not reliably willing to share. And a BC group that sees, often for the first time, that the command staff's frustration isn't about control — it's about genuinely not understanding why the middle won't move.
I watched a chief sit with that recognition once and say something I've thought about since: "I've been asking them to own decisions I haven't actually given them room to own." Not as an excuse. As a reckoning. The kind that opens something rather than closing it.
"A good leader takes a little more than his share of the blame, a little less than his share of the credit." — Arnold H. Glasow
What this means for how development should be designed
If your department is preparing a leadership program, or evaluating why a previous one didn't hold, the most honest question to ask before the curriculum is designed is this: do both sides of your command structure understand what the other side is actually experiencing?
Not what they think the other side is experiencing. Not what they've been told in a memo or a debrief. What the battalion chiefs say, in their own words, when asked directly — about what it feels like to lead in this organization, what they need from command in order to hold their people accountable, and where the environment consistently works against the standard they're being asked to enforce.
Until that question has a clear answer — one that both groups have heard together — training design is largely guesswork. You're building a curriculum for a problem you've only seen from one direction.
The gap between what command observes and what the middle experiences is not a communication failure. It's a structural feature of organizations that have never created a formal mechanism for surfacing it. Closing it doesn't require a perfect chief or a flawless BC group. It requires a structured conversation, held in the right setting, where the data from both sides gets named together before anyone starts talking about solutions.
That conversation is where most real change in a fire service organization actually begins.
The Command Culture Index™ was built specifically to create that conversation — surveying your executive group and your battalion chiefs separately, then presenting both groups' data simultaneously in a facilitated debrief where both sides hear each other's experience for the first time. If that sounds like something your department needs, a 20-minute call is the right place to start. No pitch. Just a conversation about what you're seeing.