A tailored course, built for your situation
Reference of choice on cross-functional ISO 22301 calls
Become the internal authority others consult when business continuity decisions arise
$199 one-time
24-hour access provisioning
30-day money-back guarantee
Hand-built implementation playbook
12 modules. 12 chapters per module. 144 chapters total.
12 modules, each with 12 chapters (144 chapters total), text-based, plus downloadable templates and a hand-built implementation playbook delivered alongside course access.
Being seen as just another contributor instead of the go-to expert on continuity frameworks
The situation this course is for
Skilled engineers often fly under the radar when it comes to cross-functional influence. Without clear ownership of critical frameworks like ISO 22301, their input arrives late, or not at all, on decisions that define system resilience.
Who this is for
Senior individual contributor in a large tech firm who influences system design and reliability but isn't formally recognized as the continuity subject-matter expert
Who this is not for
Junior engineers still mastering core systems, or executives who delegate framework ownership rather than executing it
What you walk away with
- First-call status on ISO 22301-related escalations across product, infrastructure, and compliance teams
- Repeatable templates for business impact analysis and continuity planning that reflect Meta-scale complexity
- Clarity on how to map technical dependencies to ISO 22301 control requirements
- Internal reputation as the source of record for continuity decisions
- Ability to articulate continuity requirements in cross-functional reviews with confidence and precision
The 12 modules (with all 144 chapters)
Module 1. Understanding ISO 22301 in high-velocity tech environments
Ground your knowledge in how ISO 22301 applies specifically to large-scale, rapidly changing systems like those at leading platforms.
12 chapters in this module
- Scope of ISO 22301 in distributed systems
- Continuity vs disaster recovery distinctions
- Mapping ISO 22301 to engineering workflows
- Why resilience ownership matters now
- Common misconceptions in tech orgs
- How ISO 22301 complements SRE practices
- Role of ICs in framework adoption
- Linking uptime goals to continuity planning
- Incident response overlap
- Dependency mapping at scale
- Recovery time objectives defined
- Organizational roles and responsibilities
Module 2. Initiating a business impact analysis
Learn how to start the most critical step in continuity planning with practical tools tailored to engineering inputs.
12 chapters in this module
- Identifying critical functions
- Stakeholder interview framework
- Defining maximum tolerable outage
- Technical service classification
- Data flow mapping techniques
- Assigning impact levels
- Validating assumptions with ops teams
- Documenting interdependencies
- Using logs to assess criticality
- Prioritizing systems for recovery
- Creating impact heatmaps
- Approval workflows for BIA
Module 3. Designing the continuity strategy
Translate BIA findings into a durable, technical continuity strategy aligned with ISO 22301 requirements.
12 chapters in this module
- Recovery point objectives by tier
- Backup frequency planning
- Failover architecture patterns
- Cloud redundancy options
- Data replication scope
- Fallback procedures overview
- Workforce availability planning
- Vendor dependencies assessment
- Cross-region coordination
- Automated recovery triggers
- Human intervention points
- Strategy review cadence
Module 4. Documenting the continuity plan
Create comprehensive, actionable documentation that audit teams and engineers can trust.
12 chapters in this module
- Plan structure and versioning
- Writing for technical reviewers
- Including runbooks in the plan
- Contact trees and on-call sync
- Escalation paths defined
- Communication protocols
- Embedded decision matrices
- Checklist integration
- Linking to incident response
- Change control process
- Storage and access permissions
- Audit preparation notes
Module 5. Testing the continuity plan
Run effective tests that validate recovery capabilities without disrupting production.
12 chapters in this module
- Test frequency by system tier
- Tabletop vs full interruption
- Designing realistic scenarios
- Involving engineering teams
- Measuring test success
- Post-test review process
- Documenting test outcomes
- Updating plan based on results
- Using chaos engineering safely
- Tracking unresolved gaps
- Leadership reporting
- Improvement loop integration
Module 6. Maintaining and updating the plan
Keep the continuity plan alive and relevant in fast-moving environments.
12 chapters in this module
- Change detection triggers
- Post-deployment review sync
- Architecture drift monitoring
- Ownership handoff protocol
- Quarterly refresh cycle
- Update approval workflow
- Version history tracking
- Archiving old versions
- Stakeholder notification
- Documentation tooling
- Integration with CI/CD
- Feedback from incident reviews
Module 7. Engaging cross-functional teams
Build credibility and collaboration across product, security, and operations.
12 chapters in this module
- Initiating partnership conversations
- Communicating engineer-to-engineer
- Translating continuity needs
- Facilitating joint planning
- Running alignment workshops
- Conflict resolution tactics
- Managing competing priorities
- Building trust with SREs
- Working with compliance teams
- Presenting to tech leads
- Influencing without authority
- Feedback collection methods
Module 8. Preparing for internal audits
Ensure your documentation and practices pass scrutiny from compliance and risk teams.
12 chapters in this module
- Common audit checklist items
- Evidence collection framework
- Control mapping to ISO 22301
- Technical proof points
- Audit interview preparation
- Gap remediation planning
- Pre-audit walkthroughs
- Response documentation
- Open finding tracking
- Corrective action plans
- Audit follow-up cadence
- Lessons from prior audits
Module 9. Responding to real incidents
Apply continuity planning during actual outages and disruptions.
12 chapters in this module
- Activating the continuity plan
- Declaring incident severity
- Initial response coordination
- Communication tree activation
- Engineering team mobilization
- Data preservation steps
- Rollback vs recovery decision
- Vendor involvement process
- Tracking recovery progress
- Post-incident review inputs
- Updating plans based on events
- Celebrating successful recovery
Module 10. Driving continuous improvement
Turn insights into action to strengthen resilience over time.
12 chapters in this module
- Identifying improvement opportunities
- Prioritizing changes by risk
- Integrating with sprint planning
- Ownership of backlog items
- Tracking enhancements
- Sharing lessons learned
- Benchmarking against peers
- Adopting new technologies
- Updating success metrics
- Engaging leadership support
- Scaling improvements
- Recognizing team contributions
Module 11. Communicating continuity value
Articulate the importance of continuity planning to non-technical stakeholders.
12 chapters in this module
- Explaining RTO and RPO simply
- Business cost of downtime
- Risk to customer trust
- Regulatory expectations
- Investor confidence factors
- Reputation protection
- Insurance implications
- Vendor contract risks
- Public disclosure concerns
- Media response planning
- Internal messaging strategy
- Success story sharing
Module 12. Owning the continuity roadmap
Take long-term ownership of resilience strategy evolution.
12 chapters in this module
- Setting 12-month goals
- Tracking maturity growth
- Identifying new threat vectors
- Evaluating tooling upgrades
- Training new team members
- Mentoring junior engineers
- Scaling frameworks across teams
- Integrating new acquisitions
- Benchmarking across orgs
- Influencing platform-wide change
- Representing internally externally
- Defining next-gen resilience
How this maps to your situation
- When starting a new BIA
- After an audit finding
- Before major system changes
- During incident post-mortems
Before vs. after
Before
Input is solicited only when required, not proactively sought
After
Teams reach out before decisions are made, knowing your insight prevents downstream rework
What's included with your purchase
- 12 modules with 12 chapters each (144 chapters)
- Downloadable templates and worked examples for every module
- Hand-built implementation playbook delivered alongside course access
- 30-day money-back guarantee
Delivery and format
- Course and learning environment access provisioned within 24 hours of purchase
- Hand-built implementation playbook delivered alongside course access
Format: Text-based modules and chapters in the Art of Service learning environment, plus downloadable templates and worked examples for every chapter, plus the hand-built implementation playbook delivered alongside course access.
Time investment: Approximately 90 minutes per module, designed to fit around engineering schedules.
If nothing changes
Continuing to deliver strong technical work without expanded recognition means others define the continuity narrative, and you're brought in late, if at all.
How this compares to the alternatives
Generic ISO 22301 certifications provide theory; this course delivers context-specific templates, real-world examples from peer tech firms, and a clear path to becoming the recognized continuity authority in your organization.
Frequently asked
How is the course structured?
12 modules, each containing 12 chapters (144 chapters total).
Is this relevant to someone at a large platform like Meta?
Yes, it's tailored for engineers in high-scale environments where continuity planning intersects with distributed systems, rapid deployment cycles, and complex dependencies.
Will I actually become the go-to person after this?
You'll have the tools, templates, and structured knowledge to step into that role confidently, whether your org currently has a named owner or not.
$199 one-time. Approximately 90 minutes per module, designed to fit around engineering schedules..
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.
30-day money-back guarantee·
144 chapters·
Hand-built playbook included·
Account access within 24 hours