Principle

Separate fixing from explaining during an incident

Every status request steals the same attention you are asking to restore service.

About 1 min read

Before you use it

Use when
  • The same responders are trying to change the system, answer executives, update users and maintain the incident record.

Keep this limit in mind

  • Do not create separate roles for a tiny incident when one person can safely do both jobs.

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

Assign operational work and communications to separate owners when incident load justifies it. Operations focuses on mitigation and diagnosis. Communications gathers verified state and publishes updates. The split protects technical attention while keeping stakeholders informed instead of forcing them to interrupt the fixers.

An example

The Communications Lead turns the incident document into a concise update while Operations tests the rollback.

Check your result

Stakeholders receive current information without repeatedly pulling the Operations Lead out of active work.

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 readingSeparate fixing from explaining during an incident

Evidence and sources
Supports

Google SRE separates operational work from the communications role, which issues periodic updates to responders and stakeholders.

Role separation should reduce cognitive load, not block direct technical clarification between people who need it.

Managing Incidents · Operational Work; Communication

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