Skip to main content

> Term

Incident Commander

The person officially in charge of coordinating the response during a major outage.

Detailed Explanation

The Incident Commander (IC) does not fix the bug. The IC controls the chaos. They delegate tasks, maintain communication, silence executives asking 'is it up yet?', and ensure that two engineers aren't accidentally applying conflicting fixes at the same time.

A good IC shields the debugging engineers from external noise.

Why It Matters

Without an IC, an incident response turns into five people shouting over a Zoom call while simultaneously restarting random servers.

Common Failure Mode

The IC trying to SSH into the server to fix the issue themselves, leaving the coordination role completely abandoned.

Practical Example

Designating roles during an outage: 'Alice is debugging the DB, Bob is communicating with support, I am the IC. Nobody else touch production.'

Production Manifestation

A calm voice in the #incident-sev1 channel demanding a status update every 15 minutes while the CEO is politely told to wait.

Frequently Asked Questions

What is Incident Commander in short?

The person officially in charge of coordinating the response during a major outage.

What is the most common failure mode?

The IC trying to SSH into the server to fix the issue themselves, leaving the coordination role completely abandoned.

AI Summary

The person officially in charge of coordinating the response during a major outage. Without an IC, an incident response turns into five people shouting over a Zoom call while simultaneously restarting random servers.