From the sticking point to a change that held
Three moments make the shift easy to follow.
- The situation
A multi-site SME had allowed each location to adapt its access practices, workarounds and incident response.
- What unlocked it
First, a shared minimum was defined: sensitive access, incident levels, the information to pass on and the first recovery actions.
- What changed
Sites kept their autonomy while sharing the same reflexes on critical points.
The situation
Starting point
A multi-site SME had allowed each location to adapt its access practices, workarounds and incident response. That autonomy helped day to day, but when a problem crossed sites, leaders first had to reconstruct the situation before they could decide.
Each site effectively had its own keyring and its own fire drill. The weakness appeared when several doors had to open together.
What was getting in the way
Set a few common rules for access and incidents without taking away each site’s ability to act locally.
The three moves
First, a shared minimum was defined: sensitive access, incident levels, the information to pass on and the first recovery actions. Everything else could remain local.
Next, a few shared indicators, alert thresholds and a map of responsibilities were brought into a single view. Leaders could understand an incident without collecting several versions of the story.
Finally, recovery exercises tested the rules in simple conditions. Each test corrected an access path, an instruction or a backup before a real incident exposed it.
What changed
In the way the work ran
- A shared minimum replaced implicit rules for access and incidents.
- Important signals moved into one view with a clear map of responsibilities.
- Recovery exercises turned written instructions into tested actions.
What the team noticed
- Less time was spent reconstructing the situation during an incident.
- Fewer avoidable interruptions.
- Coordination between sites and senior leaders became lighter.
What held
- The arrangement remains usable because it is limited to genuinely critical points.
- Regular exercises reveal when a rule no longer works before it becomes an incident.
What to take away
- Local autonomy works better when it rests on a small shared foundation.
- During an incident, one shared view is more useful than several detailed but incompatible reports.
What about your context?
If every incident starts by collecting different versions of events, a short conversation can identify the first shared rule worth putting in place.