Protocol

Give one person the incident command

Ten experts without coordination can create eleven incident plans.

About 1 min read

Before you use it

Use when
  • Many capable responders are acting at once and nobody has the whole operational picture.

Keep this limit in mind

  • Small incidents can combine roles; avoid bureaucracy that costs more than the coordination problem it solves.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Name one Incident Commander who holds the high-level state, delegates work, resolves coordination conflicts and makes sure missing roles are owned. The commander does not need to be the person typing the fix; keeping the response coherent is the job.

Steps

  1. Name the current Incident Commander explicitly.
  2. Give technical work, communication and planning owners where the incident size warrants it.
  3. Route major priority changes and conflicting actions through the commander.
  4. Make any command handoff explicit to the whole response group.

An example

A senior developer may remain Operations Lead while another responder coordinates priorities, dependencies and escalation.

Check your result

Every responder can name who currently owns cross-incident coordination.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingGive one person the incident command

Evidence and sources
Supports

Google SRE defines an Incident Commander role that maintains high-level state and coordinates the response by assigning responsibilities.

Small incidents may combine roles; the useful property is clear ownership, not a ceremonial title.

Managing Incidents · Incident Command

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details