Principle
Separate fixing from explaining during an incident
Every status request steals the same attention you are asking to restore service.
When it fits
- The same responders are trying to change the system, answer executives, update users and maintain the incident record.
When to avoid it
- Do not create separate roles for a tiny incident when one person can safely do both jobs.
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.
Keep this limit in mind
- Do not create separate roles for a tiny incident when one person can safely do both jobs.
Connected ideas
Useful withGive production changes one operational laneUseful with
Update stakeholders on a deliberate cadence
Evidence and sources
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