The Promotion Your Department Never Recovers From
The chief called me six months after the list posted. Not because anything had exploded. Because nothing had — and that was what was worrying him.
"The grievances stopped," he said. "The union stopped pushing. My command staff stopped bringing me promotion concerns. Everything got quiet."
He paused.
"And I've been in this job long enough to know that quiet isn't always good."
He was right. What he was describing wasn't resolution. It was withdrawal. The department hadn't accepted the promotion — it had decided the promotion told them everything they needed to know, and they'd stopped investing in the conversation. High performers had gotten the message and adjusted their calculations accordingly. Informal leaders had updated the story they were already telling about how this organization works. And the people who most needed to believe the system was fair had quietly concluded that it wasn't — and started making decisions based on that conclusion.
The promotion wasn't a scandal. It was defensible. The process was clean, the documentation was solid, and the selected officer was within the allowable range. By every measurable standard, it was a legitimate selection.
By every cultural standard, it was a wound that was going to take years to close — if it closed at all.
What a promotion actually communicates
Every promotion in a fire department sends a message to everyone who didn't get promoted. That message isn't in the announcement email, the press release, or the chief's remarks at the ceremony. It's in the gap between what the department said it valued and what the department just demonstrated it values.
People in fire stations are extraordinary readers of organizational behavior. They've spent years watching how decisions get made. They know who gets protected and who doesn't. They know which standards are real and which ones are negotiable. They know the difference between a chief who talks about meritocracy and a chief who actually runs one. And when a promotion happens, they process it through everything they already know — not through the official narrative.
What they're asking, whether they say it out loud or not, is: What does this decision tell me about what it actually takes to get ahead here?
When the answer to that question doesn't match what they see on the floor every day — when the officer with the stronger performance record gets passed and the officer with the better political connections gets the rank — the message lands hard and stays. Not as anger, usually. Anger burns off. What stays is something quieter and more durable: a recalibration. A decision about whether investing in this organization is worth the return.
"The single biggest way to impact an organization is to focus on leadership development. There is almost no limit to the potential of an organization that recruits good people, raises them up as leaders, and continually develops them." — John Maxwell
Maxwell's point assumes a system people believe in. When a promotion cycle breaks that belief — not catastrophically, but quietly, at the level of a single decision — it doesn't just affect the person who didn't get promoted. It affects everyone who watched the decision get made and drew a conclusion about what this organization rewards.
The second-order effects nobody tracks
Most chiefs track the visible fallout from a contested promotion. The grievances. The union meetings. The conversations with HR. The performance review language. Those things are manageable. They have processes attached to them.
What doesn't have a process attached to it is the slower, quieter damage that happens in the months that follow. And that damage is almost always worse than the visible fallout.
The firefighters who were closest to the officer who didn't get promoted watch what happens to him. They watch whether he stays engaged or pulls back. They watch whether the chief makes any effort to acknowledge what the decision cost him. They watch whether anything changes in the next cycle, or whether the same inputs produce the same outputs. And they update their own calculations based on what they see.
The officers who were on the promotional track — who had been working toward the next cycle, putting in the extra hours, taking the hard assignments — start asking a question they don't always ask out loud: Is this worth it? Not because one promotion went sideways. But because one promotion going sideways confirmed something they'd been watching for. The people who perform at the highest level are also, in most departments, the most options-aware. They know what other departments look like. They know what their skills are worth. And when they start to believe the internal promotion system isn't a meritocracy, they start making decisions that departments can't always see until they're already paying the price.
The informal leaders — the senior firefighters, the respected lieutenants, the officers who don't have rank but carry enormous cultural weight — update the story they tell about the organization. Not to cause problems. Because storytelling is how they make sense of what they're seeing. And once a story takes hold in a fire station, it's extraordinarily difficult to dislodge.
"In organizations, real power and energy is generated through relationships. The patterns of relationships and the capacities to form them are more important than tasks, functions, roles, and positions." — Margaret Wheatley
In a fire department, those relationships are built around trust — trust that the organization is going to apply its stated values consistently. When a promotion cycle fractures that trust, the fracture doesn't stay contained to the people directly affected. It travels through the network of relationships that holds the culture together. And it does something particularly corrosive: it makes people more guarded. Less willing to share information up the chain. Less willing to bring problems forward. Less willing to invest discretionary effort in an organization they're no longer sure is investing in them.
That's the dynamic the chief was describing when he called me. Not chaos. Guardedness. And guardedness in a fire department is expensive in ways that never make it into any budget line.
What the organization is actually learning
There's a concept in organizational behavior that gets applied to fire departments less often than it should: the difference between espoused values and values in use. Espoused values are what the organization says it believes — the language in the strategic plan, the chief's remarks at the promotional ceremony, the department's stated criteria for advancement. Values in use are what the organization actually demonstrates through its decisions — the pattern of behavior that people can observe, track, and draw conclusions from over time.
In most departments, chiefs genuinely believe their espoused values and their values in use are aligned. They've built a process. They've documented the criteria. They've tried to be consistent.
What they underestimate is how sharply their people can see the gap — even when the gap is narrow, even when it only shows up in one or two decisions per cycle. Because the people inside a fire department are not evaluating each decision in isolation. They're running a longitudinal study. They're tracking patterns across years. And when a pattern emerges that contradicts the espoused values, the espoused values lose.
The chief who made the promotion I described at the top of this article wasn't a corrupt leader. He wasn't running a patronage system. He made one decision shaped by political relationships he'd been managing carefully, used the policy flexibility available to him, and satisfied the external pressure he was feeling. By any standard he could articulate, the decision was defensible.
What he couldn't see clearly enough, until it was too late to undo it, was what the department was learning. Not from the decision itself. From the gap between the decision and what the department knew about the two officers involved.
"The most important thing about a leader is not what happens when he is there, but what happens when he is not there." — John C. Maxwell
That's the real test of a culture. Not what people do when they're being observed. Not what they do when the chief is in the room. What they do when nobody's watching — and whether that behavior matches the standard the organization claims to hold. A promotion cycle that undermines belief in the meritocracy doesn't just affect the moment. It affects what happens in every moment that follows, in every decision made by every person who drew a conclusion from what they saw.
What closes the gap
The chief who called me had not made an unfixable error. He had made a recoverable one. But recovery from a promotion cycle that has damaged organizational trust doesn't happen through policy revision or a well-crafted announcement. It happens through what the organization does next — visibly, consistently, and over enough time for people to believe the pattern has actually changed.
The first thing that has to happen is an honest accounting. Not a public one. A private one — between the chief and himself. What actually drove that decision? Was it the criteria? Or was it something else — a relationship, a pressure, a calculation about what would create the least short-term friction? If it was something else, the next cycle has to be built differently. Not just documented differently. Actually decided differently.
The second thing that has to happen is a conversation with the high performer who didn't get promoted — not a managed conversation, not an HR-approved conversation, but a real one. One that acknowledges what the decision cost him without offering excuses for it. That conversation is harder than any discipline case. It requires a chief to sit with something uncomfortable and not manage his way around it. But it's the conversation that makes the next cycle possible.
The third thing is structural: the rationale for promotional decisions has to be built before the pressure arrives. The written framework for why one officer was selected over another — based on documented performance, not post-hoc justification — has to exist before the list is made, not after it's contested. Departments that build this framework in advance don't eliminate political pressure. They give themselves something to point to that's more durable than a chief's word.
None of this is fast. Culture operates on a long clock. A department that watched one promotion cycle confirm a story it had already been telling isn't going to update that story after one clean cycle. It's going to watch the next three and make a decision based on the pattern.
That's the work. It's slower than any training program, harder than any policy revision, and it doesn't produce visible results on any timeline that satisfies city hall or a command staff that wants to move on. But it's the only thing that actually closes the gap between what the organization says it values and what the organization demonstrates.
The chief who called me already knew most of this. He'd known it when he signed the memo. What he was calling about wasn't the answer — it was whether it was too late to apply it.
It wasn't. But the window for clean recovery was narrowing, and he'd been quiet for six months in a situation that required the opposite.
If this is a conversation your department needs to have — about where the gap between espoused and actual values has opened up in your culture — I'm at TheThinkingChief.com. The Command Culture Index™ is a tool that helps surface exactly where that gap exists and what it's costing you. A 20-minute conversation is enough to figure out whether this is the right moment for it.
— Chief Chris ArmstrongThe Thinking Chief Leadership Group, LLC