Stakeholder Management During Long Incidents

Long incidents attract stakeholders. The protocol that informs without distracting the response.

Communicator role

Stakeholder management is its own role during long incidents. A dedicated communicator handles execs and adjacent teams; the IC stays on technical response. Conflating the two roles burns the IC's attention on context-switching that the response cannot afford.

• Dedicated communicator. Named comms lead per incident. Distinct person from the incident commander.
• Frees the IC. Technical-focus protection. IC drives response; communicator handles stakeholders.
• Explicit role declaration. "Comms lead" announcement in the incident channel. Catches "everyone and no one" comms.
• Trained communicator pool. Named comms-trained engineers per rotation. Supports continuity through long incidents.

Cadence

Cadence is severity-driven and predictable so stakeholders stop asking ad-hoc questions. Sev 1 gets exec updates every 30 minutes; customer-facing comms run on their own (slower) cadence; structured template per update keeps skim-readers oriented; ramp-down post-resolution catches abrupt comms cutoffs.

• Sev 1 exec updates every 30 minutes. Standing exec cadence per incident. Predictable rhythm reduces ad-hoc questions.
• Customer comms separate cadence. Independent customer-facing rhythm. Different audience, different timing.
• Structured update template. Summary, progress, ETA shape. Supports skim-readers without sacrificing detail.
• Post-resolution ramp-down. Communication cadence continues after resolution at lower frequency. Catches abrupt comms cutoffs that look like silence.

When to escalate

Escalation to execs is informational, not approval-seeking. Notify at sev 1 start, update steadily through, do not ask permission for technical decisions inside the IC's authority. Documented exception list per org catches exec overreach and IC under-authority before they show up mid-incident.

• Sev 1 start: notify execs. Explicit kickoff notification per incident. Exec awareness lands without delay.
• Updates throughout. Steady exec cadence. Maintains awareness without becoming micromanagement.
• Inform, do not ask permission. IC has authority on reversible technical decisions; execs are informed, not consulted.
• Documented exception list. Per-org "decisions requiring exec approval" list. Catches exec overreach and IC under-authority before they show up mid-incident.