Lead Operational Resilience Manager study plan
Lead Operational Resilience Manager · Give each week a clear focus.
8 weeks · About 6 hours per week
Fundamental concepts of operational resilience
Define operational resilience and distinguish it from related disciplines such as business continuity, disaster recovery, enterprise risk management, and crisis management, writing a one-line differentiator for each
Explain the concept of important business services and how impact tolerances differ from risk appetite statements
Map the regulatory and standards landscape (Basel Committee principles, FCA/PRA-style expectations, DORA, NIST, ISO 22301 and ISO 27001 families) at a level sufficient to compare their core obligations
Identify the roles of the governing body, senior accountable owner, and business service owner in an operational resilience programme
Your checkpoint
A one-page glossary and comparison table covering at least 12 core terms and 5 frameworks, self-quizzed to 90% recall
Fundamental concepts of operational resilience & Planning operational resilience management framework
Describe the end-to-end lifecycle of an operational resilience management framework, from scoping through continuous improvement
Draft a scope statement that identifies critical operations, legal entities, and geographic perimeters
Distinguish maturity models from compliance checklists and select an appropriate maturity scale for a mid-size firm
Explain how resilience objectives cascade from strategy into service-level tolerances
Your checkpoint
A two-page framework scope and objective statement with an explicit in-scope/out-of-scope list and three strategic resilience objectives
Planning operational resilience management framework
Build a governance structure with clear decision rights across first, second, and third lines
Design an impact tolerance-setting methodology including severity scales and maximum tolerable disruption windows
Sequence a 12-month implementation roadmap with dependencies, owners, and quick wins
Identify the artefacts a framework needs, such as a service inventory, dependency map, and tolerance register
Your checkpoint
A governance RACI plus a 12-month roadmap on one page, reviewed against at least five dependency checkpoints
Establishing business resilience and digital and cyber resilience management practices
Construct a business impact analysis that links processes to important business services and their tolerances
Map critical dependencies for a sample service across people, premises, technology, data, and suppliers
Explain how cyber resilience practices (detection, response, recovery, and backup integrity) plug into the operational resilience framework
Distinguish recovery time objectives, recovery point objectives, and maximum tolerable disruption, and reconcile them for one service
Your checkpoint
A complete service-level resilience assessment for one fictitious important business service, including dependency map and reconciled recovery targets
Establishing business resilience and digital and cyber resilience management practices & Establishing third-party resilience management practices and resilience organizational culture
Design a scenario-testing approach that exercises severe-but-plausible disruptions rather than routine outages
Evaluate third-party concentration risk and define criticality tiers for vendors
Draft contractual and due-diligence requirements for critical suppliers, including exit and substitution options
Explain how to assess a supplier's own resilience posture through evidence rather than questionnaires alone
Your checkpoint
A critical-vendor register with tiering criteria and a due-diligence checklist of at least 15 evidence-based items
Establishing third-party resilience management practices and resilience organizational culture
Design a resilience culture programme that moves beyond awareness training into measurable behaviours
Define culture indicators such as near-miss reporting rates, escalation speed, and challenge behaviour in governance forums
Plan communication and training for executives, service owners, and front-line staff with differentiated content
Identify levers for embedding resilience into performance management and incentives
Your checkpoint
A culture and training plan with three measurable behavioural indicators, baseline measurement method, and a 90-day rollout schedule
Testing and continually improving operational resilience
Design a testing programme that combines desktop exercises, simulation, live failover, and red-team-style scenarios
Write test objectives, success criteria, and severity thresholds for a single exercise
Define remediation tracking, root-cause analysis, and lessons-learned processes after an exercise or incident
Select metrics and key indicators that evidence resilience posture to a board or regulator
Your checkpoint
A full exercise design pack for one scenario, including objectives, success criteria, injects, and a remediation log template
Testing and continually improving operational resilience & Fundamental concepts of operational resilience
Synthesize all domains into a single integrated resilience narrative suitable for a board paper
Critique a weak framework design and propose specific improvements with justification
Complete timed practice questions weighted by domain percentage and review every error against source concepts
Build a personal exam-day strategy covering question triage and time allocation
Your checkpoint
A mock board paper of no more than three pages plus a scored practice set with a written error log covering every missed question
Milestones
Week 2: Can explain, without notes, the difference between impact tolerance and risk appetite and name the five framework families in scope
Week 4: Service-level resilience assessment is complete and every recovery target is reconciled against the stated impact tolerance with no unexplained gaps
Week 6: Vendor tiering and culture indicators are both defined with measurable baselines; can articulate how supplier failure propagates to an important business service
Week 8: Practice score at or above 80% overall with no domain below 70%, and the board paper reads as a coherent single argument rather than five separate summaries