Fireground leadership is characterized by decisiveness under pressure, but the deeper requirement is sensemaking under uncertainty. Incidents involving large commercial fires, extended-duration hazmat operations, simultaneous rescue and fire attack problems, or wildland-urban interface fires compress time while expanding consequences. In these environments, the incident commander’s challenge is not merely choosing a tactic, but also continuously answering three questions:
- What is happening right now?
- What does it mean for our objectives and risk?
- What is likely to happen next?
The Incident Command System (ICS) exists to bring structure to that uncertainty by organizing information, resources, objectives and communications into a common framework. Yet even a well-designed system depends on human attention, judgment and discipline, and that is where the presence of senior leadership can either strengthen the system or unintentionally destabilize it.
| READ NEXT: The impact of policy and procedure on fire command
Avoiding CHAOS
You may have seen the acronym CHAOS — Chief Has Arrived on Scene — used in this context, but it’s certainly not all bad. When a battalion chief, division chief or fire chief arrives at a complex incident, their presence can expand the organization’s capacity to think, see and anticipate. Properly applied, senior leaders widen the information aperture, stabilize operational tempo, strengthen risk controls, and help the IC maintain strategic focus.
Improperly applied, the same experience and rank can trigger a predictable failure mode: The senior leader becomes the incident within the incident, rather than supporting the incident manager. In this failure mode, authority becomes blurry, communications become noisy and crews begin to triangulate direction. The incident does not become safer or more efficient; it becomes less coherent. This is the difference between a command coach and a command thief.
Command coach vs. command thief
The most effective senior leaders are not simply “extra commanders”; they are command coaches who use their experience to increase the IC’s cognitive bandwidth, decrease allostatic load, improve the quality and flow of information, and reinforce unity of command. A command thief, often unintentionally, robs the IC of decision space, ownership, learning and credibility by inserting competing direction, publicly second-guessing or creating role confusion.
The distinction between command coach and command thief is not about rank or personality. It is about function, timing and the effect a senior leader has on the incident management system.
A command coach is an “IC enabler.” They arrive with the explicit intent to help the IC see more, interpret more accurately and anticipate sooner. They provide decision support while preserving the IC’s authority and accountability. Their influence is felt in the quality of the command process rather than in the volume of their voice. They protect the IC’s attention, reduce friction in communications, and expand the system’s ability to manage information and risk.
A command thief is an “IC replacer,” whether formally or informally. Sometimes this occurs through an abrupt takeover without a clear transfer-of-command process. More often it happens through subtler behaviors that communicate doubt: correcting the IC on the radio, challenging strategic choices in front of subordinates, issuing directions directly to companies outside the command structure, or rapidly building a large command organization without regard to what the incident actually requires.
Research on ICS as a high-reliability organizing mechanism highlights a related trap: Leaders can reflexively populate organizational “boxes” and drain operational resources, only to discover that the expanding structure has consumed the very capacity needed to do the work (Bigley & Roberts, 2001). A similar phenomenon occurs cognitively.
When senior leaders flood the command space with questions, corrections and parallel direction, they consume the IC’s limited attention and degrade performance even if their intent is supportive.
It should be noted that command theft is rarely malicious. The behavior commonly emerges from urgency, anxiety or an understandable desire to prevent a bad outcome. But the impact is consistent: reduced clarity, fractured unity, delayed decisions and a weakened IC, both in the moment and in the organization’s long-term development.
Capture, comprehend, predict
Senior leadership matters most when incidents become complex, extended or unstable. Complexity increases when the incident involves multiple hazards, competing priorities, challenging access or water supply, deteriorating structural conditions, limited staffing or high-risk victim profiles. Extended incidents increase fatigue, resource turnover and the probability of communication drift. In these situations, the IC is forced to manage both operations and the cognitive load of maintaining a working picture of the incident. The senior leader’s unique value extends beyond experience to increase the quality of situational awareness and decision support. This value can be captured with a simple operational posture: capture, comprehend and predict.
Situation awareness research describes effective performance in dynamic systems as a cycle of perceiving critical elements, comprehending their meaning in context, and projecting future states (Endsley, 1995). On the fireground, this translates into attention to cues that matter, accurate interpretation of those cues, and proactive forecasting of what is likely to happen next:
- Capture means collecting relevant information without turning the command post into a debate club. It includes confirming accountability, tracking critical benchmarks, monitoring radio traffic for inconsistency, and identifying emerging hazards and resource stress.
- Comprehend means integrating those cues into a coherent understanding of the incident. A veteran leader’s experience is especially useful here because they can recognize patterns, detect contradictions, and spot early indicators of a deteriorating situation.
- Predict means projecting likely outcomes and creating time for the IC to make decisions before the incident makes them. That forecasting might include anticipating extension paths, collapse potential, air management limitations, the need for relief resources, or the conditions that should trigger a tactical shift.
The senior leader who shows up to do these three things becomes a force multiplier for the IC. The IC remains the IC, but they are stronger because the system is feeding better information and earlier forecasts. On the other hand, the senior leader who shows up to direct tactics and “run the fire” becomes a competitor inside the same command system, even if they do not intend to.
How to support the IC
One of the fastest ways to weaken command is to make the IC doubt themselves in public. Confidence on the fireground is not bravado; it is a functional requirement. An IC who is constantly defending decisions, re-explaining intent or reacting to public critique loses momentum and cognitive bandwidth. The command coach understands that their job is to strengthen the IC’s thinking, not to perform their own thinking in front of everyone else.
Support begins with protecting the IC’s decision space. The command coach avoids public correction and avoids questions that imply incompetence when heard by crews. If the senior leader perceives a significant risk or a major gap in the plan, they address it privately, ideally face-to-face at the command post or through a direct command channel that preserves unity. They seek to understand intent first, then offer information and options that improve the plan. When senior leaders ask clarifying questions privately and affirm the IC publicly, they preserve legitimacy while still improving outcomes.
Support also includes improving information quality and flow. On complex incidents, the IC is often flooded with partial reports, competing narratives, and radio traffic that varies in clarity. The command coach can quietly enhance the system by prompting consistent progress reports, ensuring accountability processes remain disciplined, verifying that tactical assignments align with strategic objectives, and identifying missing pieces of information that create hidden risk. In practice, this looks like reducing friction: ensuring the IC receives timely, relevant and actionable inputs rather than a pile of raw data.
A critical component of command coaching is forecasting. The command coach anticipates what the IC will need next and presents it in a way that preserves ownership. Instead of issuing directives, the coach offers projections and triggers: If conditions continue, certain outcomes become likely; if certain benchmarks are not met, a shift should be considered; if resources remain committed at this pace, relief and rehab must be planned earlier than usual. The coach’s experience becomes a predictive tool that expands the IC’s time horizon. The point is not to “be right.” The point is to give the IC more time and better options.
Finally, support includes risk management that enables action rather than paralyzing it. A command coach helps the IC continuously align risk to benefit by returning the conversation to conditions, survivability, resources and objectives. They help the IC avoid drift, especially on extended incidents where fatigue and normalization can distort judgment. This does not mean becoming the “no” person. It means becoming the “clarity” person, anchoring decisions to what is known, what is unknown and what must be true for a given tactic to remain justified.
Command theft in action
Command theft tends to appear as well-intentioned behaviors that quietly erode command unity. One common form is radio overrides or parallel command. When a senior leader gives tactical direction directly to companies without routing through the IC or the established operations structure, they create a second command system. Even if the direction is technically sound, the cost is fragmentation. Crews begin to receive multiple sources of “truth,” the IC loses the ability to coordinate coherent action, and accountability becomes muddled because decisions are no longer owned within one system.
Another form of command theft is public second-guessing. Questions can be supportive in private, but on the radio they can function as reputational damage. A senior leader who challenges the IC in front of others communicates doubt to the organization, which invites hesitation and triangulation. Fireground command depends on clear authority. When authority appears conditional, the operation slows, and safety margins can shrink because teams are no longer synchronized.
Command theft also occurs when senior leaders overbuild the incident organization. ICS is scalable, but scalability is not an excuse for reflexive staffing. Building a large structure can consume resources, create more communication pathways than the incident can support, and delay operational action. The irony is that leaders often build structure to control complexity, but an oversized structure can create complexity of its own. Bigley and Roberts (2001) describe how leaders can misuse ICS by focusing on filling organizational positions instead of matching structure to actual incident demands. When this happens, the system becomes heavier and slower at the moment it needs to remain agile.
Perhaps the most consequential form of command theft is developmental. When senior leaders seize decisions, they deprive emerging ICs of the chance to experience consequence, refine judgment and build credibility. Credibility is not granted by rank; it is earned by competent performance under pressure. If senior leaders routinely remove decision opportunities from developing ICs, they may win the moment but lose the future. The department becomes dependent on a small number of experienced leaders and fails to build a deep bench, which is a strategic vulnerability.
Command transfers
Command coaching is not a prohibition against decisive leadership. There are moments when the senior leader must assume command. This may be necessary when there is clear evidence of unsafe operations, loss of command coherence, rapidly escalating complexity that exceeds the current IC’s capacity, or the need to transition to a broader incident management approach. The question is not whether transfer can happen; the question is how it happens and what it communicates to the organization.
A proper transfer should be explicit, structured and announced through the appropriate channels. It should include a clear statement of who is in command, confirmation of current strategy and objectives, resource status and critical safety concerns. Just as important, it should preserve the dignity of the IC. The senior leader can acknowledge the work already done, articulate the reason for transfer in professional terms, and assign the previous IC to a meaningful role that supports the incident and supports their continued learning. This approach protects unity, avoids rumor-driven narratives, and ensures the transfer strengthens rather than fractures the command system.
If transfers happen frequently without clarity, the organization begins to expect instability at the command level. If transfers happen with respect, structure and a developmental mindset, the organization learns that command is a disciplined system, not a personality contest.
Set expectations — and train on them
Command coaching is not merely an individual virtue; it is a departmental choice. High-reliability organizing research suggests that performance in volatile environments depends on structures and practices that enable flexible, accurate action under pressure (Bigley & Roberts, 2001). Departments that want reliable outcomes must intentionally develop leaders who can support cognition, not just assert control.
This begins with expectations. Departments can define the on-scene role of senior leaders in a way that emphasizes decision support, information management, forecasting and risk alignment. When leaders know the standard, they are less likely to improvise their way into command theft. It also requires training that focuses on “supporting command,” not just “being command.” Many courses emphasize the IC role, but fewer train chiefs and senior officers to function as a second brain without becoming a second commander. Departments can practice these skills in simulations and after-action reviews by evaluating not only the IC’s decisions but also the senior leader’s impact on clarity, tempo and authority.
Language matters as well. Command coaches use communication that preserves IC ownership while still injecting experience. They speak in observations, interpretations and projections rather than directives that bypass the chain of command. They offer options and triggers rather than issuing public corrections. Over time, this becomes a culture: The organization expects senior leaders to reinforce the IC publicly and refine them privately. That norm protects the IC’s legitimacy and strengthens performance on the fireground.
Finally, the department must debrief deliberately. Post-incident learning should be designed to extract lessons without shaming. If the on-scene environment is where credibility is earned, the debrief environment is where capability is built. When senior leaders model respectful, data-informed critique after the incident, they are more likely to model respectful, system-focused support during the incident. The goal is not to protect feelings; it is to protect learning, which is the only sustainable path to growing incident command capacity.
Elevate the IC
Senior leadership is essential on complex and extended incidents, not because of their rank but rather their cognition. The command coach arrives to capture, comprehend and predict, expanding situation awareness and increasing the IC’s capacity to manage risk, strategy and tempo (Endsley, 1995).
The command thief arrives and unintentionally narrows the system by adding noise, creating parallel direction or undermining legitimacy, leaving the organization with a weaker commander and a weaker bench.
A department that takes incident command seriously must take command coaching seriously. The operational standard should be unmistakable: Support the IC, fill the gaps, and never steal the opportunity to learn, grow and gain credibility in the role. When senior leaders consistently elevate the IC rather than eclipse them, the organization becomes safer, faster, more coherent and more resilient because it produces good outcomes today and stronger commanders tomorrow.
REFERENCES
- Bigley, G. A., & Roberts, K. H. (2001). The incident command system: High-reliability organizing for complex and volatile task environments. Academy of Management Journal, 44(6), 1281–1299.
- Endsley, M. R. (1995). Toward a theory of situation awareness in dynamic systems. Human Factors, 37(1), 32–64.
