Principle
Give production changes one operational lane
Parallel thinking helps. Parallel uncoordinated production changes often do not.
Before you use it
- Use when
- Several responders could independently modify the same live system during an incident.
Keep this limit in mind
- Emergency authority and separation of duties must still follow local security, safety and compliance requirements.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Keep live modifications under one Operations Lead or clearly coordinated operations group. Other responders can investigate, propose and validate, but production changes should enter through the same lane so the incident state remains interpretable and rollback ownership stays clear.
An example
Two teams can investigate in parallel while only the designated operations group applies configuration changes.
Check your result
For every live change, the incident record shows one coordinated owner and an observable result.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingGive production changes one operational lane
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaSeparate fixing from explaining during an incident
Evidence and sources
Google SRE recommends that the operations team be the only group modifying the system during an incident.
Exact authorization must follow the organization's safety, security and regulatory controls.
Managing Incidents · Operational Work
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.