One of the most operationally critical rules in ICS is Span of Control: the number of people any single manager can effectively supervise during an incident. ICS specifies a range of 3 to 7 direct reports, with 5 as the ideal. Below 3, you are under-utilizing a manager. Above 7, the manager becomes a bottleneck — they cannot process information fast enough to make good decisions.
The "pizza rule" is a useful mnemonic: if you cannot feed your direct reports with two pizzas, your span of control is too large. (This is also where Amazon's "two-pizza team" rule originates — the same cognitive load principle applied to team sizing.)
Why Span of Control Breaks Down Under Stress
Under normal conditions, a manager with 10 direct reports might function adequately — meetings are scheduled, Slack messages can wait, decisions are not time-critical. During an incident, every one of those 10 people needs a decision now. The manager's message queue fills faster than they can process it. Critical updates get buried. The manager starts making decisions with stale information. The incident worsens.
Modular Expansion in Practice
ICS is designed to expand modularly as an incident grows. The trigger for expansion is simple: when any manager's span of control exceeds 7, split their section and appoint a new chief.
Stage 1 — Small incident (3 people):
IC
├── Engineer A (Database)
├── Engineer B (Frontend)
└── Engineer C (Scribe)
Span of control: 3. IC manages everything directly.
Stage 2 — Growing incident (9 people):
IC
├── Operations Chief
│ ├── Database Team Lead
│ │ ├── Engineer A
│ │ └── Engineer B
│ └── Frontend Team Lead
│ ├── Engineer C
│ └── Engineer D
├── Planning Chief (Scribe)
│ └── Engineer E
└── Comms Lead (PIO)
Span of control at each level: 2-3. IC now manages 3 people and can think strategically.
Stage 3 — Major incident (30+ people):
Each section expands further. The Operations Section might have five branches — Database, Frontend, Infrastructure, Security, and Vendor Coordination — each with their own lead. The IC still manages only the Section Chiefs.
This modular expansion is what allows ICS to scale from a three-person kitchen fire to a 30,000-person hurricane response without redesigning the communication structure. The shape of the tree stays the same; only the depth changes.
Interviewers sometimes ask: "Your incident has grown to 20 engineers all in one Slack channel. The IC is overwhelmed. What do you do?" The wrong answer is "add more channels." The right answer is to apply ICS span of control: appoint Section Chiefs, create dedicated channels per section (ops-bridge, comms-bridge, planning-bridge), and restrict cross-section communication to the IC level. Structure the communication to match the organizational hierarchy.