Ramsay Resilience Group approaches operational resilience as an operating problem, not a documentation exercise. The work starts with what the organization needs to protect or improve, then uses available evidence to understand how work is actually performed, where dependencies sit, and what decisions are required.
1. Define the operating question
Every engagement should begin with a specific problem: a critical function, a facility exposure, a supplier dependency, an exercise objective, a recovery concern, or a leadership decision that needs better evidence.
2. Establish the evidence baseline
Relevant plans, records, observations, incident history, interviews, system information, supplier data, and existing assessments are reviewed within the agreed scope.
3. Compare documentation with real work
Where the engagement involves operations, the written process is compared with actual work and known operating conditions. Differences are treated as evidence rather than automatically as worker failure.
4. Prioritize by consequence and control strength
Findings are organized so leaders can see what requires immediate action, what needs deeper verification, and what can be sequenced into longer-term improvement.
5. Assign ownership and verification
Recommendations are most useful when the organization knows who owns the next step, what resources or authority are needed, and how the effectiveness of the change will be checked.
1. Frame the operating question
Start with the decision the client needs to make: what must continue, where the exposure is, why incidents keep recurring, whether a contingency is credible, or what should be tested before a change goes live. Clear questions keep scope practical.
2. Gather evidence from the work
Use the evidence appropriate to the problem: observation, interviews, plans, procedures, incident history, maintenance, supplier information, system dependencies, previous findings, exercises, and management decisions. Written policy is one input, not the whole picture.
3. Separate immediate control from structural improvement
Some conditions need prompt correction. Others require redesign, capital work, supplier changes, training, continuity planning, or leadership decisions. Distinguishing those categories helps organizations act without losing sight of the longer-term fix.
4. Assign ownership and verification
Recommendations are more useful when the responsible owner, expected result, due date, dependencies, and verification method are clear. Completion should not be confused with effectiveness.
5. Test important assumptions
Where the consequence matters, plans and controls should be exercised, observed, or otherwise validated. The objective is to learn before a disruption forces the same test under real pressure.
Frequently asked questions
Does every engagement follow exactly the same process?
No. The principles are consistent, but the work is tailored to the operating problem, available evidence, location, and agreed scope.
Does Ramsay use standard templates?
Structured tools may be used where helpful, but the engagement is intended to reflect the client’s actual operation rather than forcing every organization into the same template.
Does every engagement use the same framework?
No. The principles are consistent—evidence, usable guidance, ownership, and verification—but scope, methods, and deliverables are shaped around the operating question and the evidence needed to answer it.