The Myth of the Single Incident Commander
The lone decisive leader makes a clean diagram and a poor reality. Modern incidents reward distributed command — and the discipline to design for it.
The org charts pinned inside every crisis room tell the same story: a triangle, with a single Incident Commander at the apex. Information flows up, decisions flow down, the heroic individual holds the picture. It is a tidy mental model borrowed largely from emergency services, and it does not survive contact with a modern, cross-jurisdictional, technology-mediated incident.
Real incidents now play out across regions, vendors, regulators, and public channels simultaneously. The cognitive load of holding all of that in one head is not difficult — it is impossible. What actually happens is that the named Incident Commander becomes a bottleneck, decisions queue behind them, and the people closest to the problem make the real calls anyway, quietly and without authority.
The teams that handle these incidents well design for distributed command on a normal Tuesday, not at 3am. They name decision rights by domain rather than by seniority. They make it explicit which calls the IC will make, which calls the function leads will make without asking, and which calls require a five-minute huddle. They rehearse the handoffs between shifts as carefully as the response itself.
The lone commander is a comforting story to tell a board. The honest one is harder: that resilience under pressure is a property of a network of people who trust each other to act, not of an individual who happens to be wearing the tabard that day.