The event
Under pressure, capable people rarely freeze. The structure around them narrows. Every decision starts routing to one person, and that person quietly runs out of room.
On 7 January 2025 the Palisades Fire ran through Los Angeles. Roughly 23,000 acres. More than 6,000 structures gone. Over 60,000 people told to leave.
Police and fire worked out of the same command post. According to the after-action report published later that year, they never collectively established a unified command structure, and never agreed on shared objectives, missions, or strategies. Two commands, one room, and no single picture of who owned what.
It reads at first like a communication failure, and parts of it were. Underneath sits something more structural. The response grew faster than the structure meant to hold it. Decisions that should have fanned out across a widening chart kept routing back to the same few people.
That is not a story about a bad decision. It is a story about where decisions go.
Busy and saturated are different states. From the outside, both look like a person working hard.
Span of control. The Incident Command System puts the workable range at one supervisor to five people, three to seven at the edges. Past that, a single person can no longer track what is happening beneath them well enough to direct it.
Most organizations can recite the number. Very few watch it move. Because span of control is not fixed. It collapses under pressure.
As the tempo rises, decisions that were delegated in the calm quietly climb back up the chart. A capable leader, wanting to keep a grip on a worsening picture, pulls choices inward. The span narrows at the exact moment it needed to widen.
Here is the distinction that matters, and it is not the one people reach for. The failing node is rarely the one that looks overwhelmed. It is the one that looks impressively busy.
From the outside, both look like a person working hard. Only one of them is still in control of the span. This is the failure cinten was built to surface. Not whether the org chart is correct, but whether the structure can still absorb the next decision once the pressure is on.
The chart shows the span you intended. It says nothing about the span you will actually have at minute forty, when three branches are all escalating to the same name at once. This is why the structure has to be run, not drawn.
This is diagnostic, not predictive. cinten does not forecast which node will fail on the day. It shows the point at which your structure stops absorbing, and whether anyone around the saturated node knows it is now their place to act. On the record, not as a feeling in the room.
Span of control is a number you set before the incident and defend during it. Widening it does not mean asking one person to hold more. It means adding a layer before you need it, and naming who inherits a decision the moment the top saturates.
For the role everything routes to, decide the most direct reports it can carry under load, before the exercise starts.
cinten drives decisions at that role mid-run, until the queue forms, without pausing the scenario.
The moment a decision arrives and waits becomes visible, and so does whether anyone beside the saturated node steps in.
Rehearse the handoff so the next decision has an owner the instant the top node is full, until it is reflex rather than permission.
The chart said one to five. The exercise shows you the one to twelve you were actually running.
Book a demo and see how cinten loads the role everything routes to, surfaces the moment it saturates, and reads the team’s next move from the run itself.
One short essay a month on decision-making under pressure. No promotional emails, no recycled posts.