Choreographing alarm floods without muting evidence
Mute buttons are not villains; unclear policy is. A field bulletin on how one NOC rewrote its storm script.
Alarm floods punish everyone when mute policies live only in chat threads. The NOC studied here posted a literal conductor checklist next to each operator console: acknowledge, tag, correlate, then decide whether silence is safe. Supervisors rotate through the role hourly so no single voice dominates.
Instructors observed that the hardest habit was writing the mute reason in the activity log before touching the keyboard. Technicians who skipped that step—even once—reopened incidents that should have stayed quiet. The rewrite took a Saturday workshop and two weeks of gentle reminders, not a new software license.
The Alarm storm choreography lab borrows audio snippets from this NOC (scrubbed) so participants feel the cognitive load. Graduates report calmer weekend bridges, though some still wish for more time on vendor-specific macros—that trade-off is intentional to keep the class vendor-neutral.
Editorial note: we never recommend muting life-safety circuits; scenarios stay on mechanical and power alarms only.