Who is the Influence Across More Business Units course for?
Senior software engineer or technical IC in a large-scale tech environment leading or contributing to business continuity, resilience planning, or cross-functional compliance initiatives.
What do you take away from the Influence Across More Business Units course?
Lead ISO 22301 readiness assessments that align engineering teams with global business continuity goals Produce audit-ready documentation that scales across regions and regulatory environments Translate technical system resilience into formal business continuity reporting artefacts Serve as a cross-functional liaison between engineering, compliance, and operations on continuity planning Design repeatable continuity testing protocols adopted by multiple business units.
How does this map to your situation?
Leading continuity planning in a global tech organisation Contributing to enterprise risk resilience beyond core engineering Bridging technical and compliance teams on audit readiness Expanding influence across product, security, and operations.
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.
What does the Influence Across More Business Units cover on delivery and format?
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 3 hours per module, designed for working professionals. Most complete the course in 6-8 weeks at 1-2 modules per week.
How does this compare to the alternatives?
Unlike generic compliance courses, this program is tailored for senior technical contributors in large-scale environments. It avoids theoretical overviews and focuses on concrete deliverables, documentation patterns, and cross-functional influence strategies used in organisations like Meta.
What does the Influence Across More Business Units cover on frequently asked?
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.
How is the Influence Across More Business Units delivered?
The Influence Across More Business Units is fully self-paced with immediate online access after enrolment. Access does not expire and future updates are included at no cost. A certificate of completion is issued by The Art of Service when you finish.
Closely related courses: Influence across more business units, Influence Across More Operational Units.
More answers: what you get with every course, refund policy, all help answers.
A tailored course, built for your situation
Influence Across More Business Units with ISO 22301 Implementation
Build cross-functional impact as a technical leader through business continuity planning that connects engineering rigor with enterprise resilience
Who this is for
Senior software engineer or technical IC in a large-scale tech environment leading or contributing to business continuity, resilience planning, or cross-functional compliance initiatives
Who this is not for
Entry-level developers, non-technical staff, or practitioners focused solely on internal tooling without enterprise impact
What you walk away with
- Lead ISO 22301 readiness assessments that align engineering teams with global business continuity goals
- Produce audit-ready documentation that scales across regions and regulatory environments
- Translate technical system resilience into formal business continuity reporting artefacts
- Serve as a cross-functional liaison between engineering, compliance, and operations on continuity planning
- Design repeatable continuity testing protocols adopted by multiple business units
The 12 modules (with all 144 chapters)
- What ISO 22301 means for engineering teams
- Business continuity vs disaster recovery
- Role of ICs in resilience planning
- Meta-scale systems and continuity demands
- Regulatory expectations behind the standard
- Linking uptime to business impact
- Common misconceptions in tech
- How ISO 22301 complements SOC 2
- Global variation in implementation
- Engineering culture and compliance
- Documenting continuity for auditors
- First steps as a non-compliance owner
- Scoping the BIA effectively
- Identifying critical functions
- Engaging product teams early
- Mapping system dependencies
- Estimating maximum tolerable downtime
- Recovery time objectives by service tier
- Documenting cascading failures
- Prioritising services objectively
- Cross-region service mapping
- Validating with incident data
- Avoiding over-engineering
- Producing the first draft
- Defining response phases clearly
- Failover vs fallback decisions
- Data replication requirements
- Redundancy patterns for microservices
- Stateful system recovery design
- Cloud region failover planning
- Capacity planning for surge
- Traffic rerouting strategies
- Secrets and config management
- DNS continuity options
- Monitoring during transition
- Post-failover validation
- Standard sections of the BCP
- Service-specific annexes
- Ownership and maintenance model
- Version control strategy
- Linking to runbooks
- Automated plan validation
- Integration with incident response
- Approval workflow design
- Accessibility during outages
- Multilingual considerations
- Stakeholder distribution list
- Review and update cadence
- Incident classification mapping
- Escalation paths and roles
- Cross-functional war rooms
- Legal and comms coordination
- Internal notification trees
- External stakeholder updates
- Regulatory disclosure triggers
- Data preservation requirements
- Post-mortem integration
- Legal hold procedures
- Executive briefing templates
- Drill integration points
- Types of continuity tests
- Tabletop exercise design
- Technical failover drills
- Participant selection strategy
- Success criteria definition
- Measuring effectiveness
- Documentation of findings
- Tracking gaps and remediation
- Executive participation models
- Automated test triggers
- Remote team inclusion
- Test frequency by risk tier
- Vendor risk classification
- Contractual continuity clauses
- SLA vs continuity requirements
- Audit rights for partners
- Multi-cloud failover planning
- API dependency mapping
- Fallback service design
- Vendor communication plan
- Joint exercise coordination
- Escrow arrangements
- Exit strategy considerations
- Resilience scorecards
- Continuity checks in PRs
- Automated BCP validation
- Service registration requirements
- Tagging critical systems
- DR testing in staging
- Failover simulation triggers
- Chaos engineering integration
- Documentation automation
- Ownership assignment rules
- Alerting for plan drift
- Audit trail integration
- Post-deploy continuity checks
- Executive summary structure
- Technical depth on demand
- Risk heat maps
- Test result reporting
- Gap tracking dashboard
- Compliance status indicators
- Benchmarking against peers
- Lessons learned reporting
- Board-level summary version
- Investment justification narratives
- Cross-region alignment score
- Progress over time visuals
- Trigger-based update mechanisms
- Integration with change management
- Automated drift detection
- Ownership verification cycles
- Decommissioning plan updates
- Architecture review integration
- Knowledge transfer protocols
- Succession planning for roles
- Document retention rules
- Version history management
- Archive strategy
- Audit readiness checks
- Auditor expectations timeline
- Evidence pack structure
- Interview preparation
- Common findings to avoid
- Gap remediation workflow
- Corrective action tracking
- Management review minutes
- Internal audit process
- Certification timeline
- Surveillance audit prep
- Scope change process
- Nonconformance response
- Global plan architecture
- Regional variations handling
- Localization of communications
- Legal requirement mapping
- Cultural considerations
- Time zone coordination
- Language support planning
- Data sovereignty implications
- Regional ownership model
- Central oversight structure
- Consistency vs customisation
- Global exercise coordination
How this maps to your situation
- Leading continuity planning in a global tech organisation
- Contributing to enterprise risk resilience beyond core engineering
- Bridging technical and compliance teams on audit readiness
- Expanding influence across product, security, and operations
Before vs. after
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 3 hours per module, designed for working professionals. Most complete the course in 6-8 weeks at 1-2 modules per week.
How this compares to the alternatives
Unlike generic compliance courses, this program is tailored for senior technical contributors in large-scale environments. It avoids theoretical overviews and focuses on concrete deliverables, documentation patterns, and cross-functional influence strategies used in organisations like Meta.
Frequently asked
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.