A tailored course, built for your situation
Reference of Choice on Cross-Functional Risk Calls with ISO 31000
Become the practitioner peers proactively seek out when risks emerge
The situation this course is for
Technical contributors with deep system knowledge often aren't invited into risk discussions, even though their insights are essential. Without a shared framework, their input comes too late or gets filtered through layers.
Who this is for
Senior individual contributors in engineering and infrastructure roles who influence system resilience but lack formal risk language
Who this is not for
People looking for entry-level compliance training or those not involved in cross-team technical decision-making
What you walk away with
- Recognized as the go-to person for risk interpretation across engineering and risk teams
- Confidently apply ISO 31000 principles to real-world system design trade-offs
- Anticipate and shape risk discussions before escalation
- Articulate technical risk implications using a globally recognized framework
- Strengthen peer trust through consistent, structured reasoning during incidents
The 12 modules (with all 144 chapters)
- Defining risk context
- Linking systems to business objectives
- Establishing risk criteria
- Identifying stakeholders
- Determining risk ownership
- Documenting assumptions
- Scoping technical dependencies
- Using context diagrams
- Setting thresholds
- Aligning with compliance goals
- Maintaining flexibility
- Reviewing context updates
- Timing intervention
- Asking risk-focused questions
- Mapping controls to design
- Documenting design choices
- Flagging high-impact areas
- Engaging architecture teams
- Using precedent examples
- Highlighting uncertainty
- Capturing assumptions
- Creating risk-aware specs
- Reviewing past outages
- Improving review cycles
- Simplifying terminology
- Using relatable analogies
- Focusing on impact
- Avoiding jargon
- Structuring risk statements
- Prioritizing scenarios
- Explaining likelihood
- Conveying urgency
- Linking to business goals
- Building credibility
- Responding to pushback
- Maintaining neutrality
- Setting workshop goals
- Preparing materials
- Engaging diverse roles
- Managing group dynamics
- Capturing inputs
- Prioritizing risks
- Assigning actions
- Following up
- Using visual aids
- Maintaining objectivity
- Grounding in evidence
- Driving consensus
- Linking incidents to risk register
- Classifying root causes
- Assessing control gaps
- Prioritizing improvements
- Documenting lessons
- Updating risk profiles
- Tracking remediation
- Sharing insights
- Integrating into runbooks
- Reviewing effectiveness
- Updating assumptions
- Closing loops
- Capturing notable cases
- Organizing by pattern
- Adding context notes
- Linking to frameworks
- Indexing for retrieval
- Updating regularly
- Protecting confidentiality
- Sharing selectively
- Using in onboarding
- Teaching others
- Refining over time
- Connecting to trends
- Defining vendor boundaries
- Mapping dependencies
- Assessing control maturity
- Evaluating contractual terms
- Reviewing audit outputs
- Identifying escalation paths
- Setting monitoring frequency
- Defining exit criteria
- Documenting due diligence
- Aligning with procurement
- Using questionnaires
- Mitigating supply chain risk
- Scanning for novel risks
- Assessing maturity
- Mapping to known patterns
- Consulting early adopters
- Drafting risk charters
- Defining pilots
- Setting success metrics
- Monitoring performance
- Escalating concerns
- Updating risk register
- Revisiting assumptions
- Adjusting strategy
- Flagging high-risk systems
- Adding context to alerts
- Improving runbook clarity
- Defining escalation thresholds
- Training responders
- Reviewing past escalations
- Reducing noise
- Improving mean time to resolve
- Documenting risk posture
- Aligning with SRE
- Updating playbooks
- Measuring impact
- Identifying key concerns
- Focusing on impact
- Using data effectively
- Avoiding alarmism
- Providing options
- Stating confidence levels
- Linking to strategy
- Preparing visual aids
- Anticipating questions
- Delivering concisely
- Following up
- Tracking decisions
- Scheduling reviews
- Tracking changes
- Updating risk ratings
- Engaging owners
- Automating inputs
- Flagging drift
- Reassessing likelihood
- Revising treatments
- Reporting progress
- Aligning with releases
- Integrating feedback
- Closing outdated items
- Demonstrating reliability
- Sharing knowledge
- Mentoring others
- Publishing insights
- Contributing to standards
- Seeking feedback
- Building alliances
- Earning trust
- Documenting contributions
- Tracking influence
- Refining approach
- Sustaining momentum
How this maps to your situation
- When onboarding new systems
- Before launching major features
- During incident retrospectives
- When evaluating third-party tools
Before vs. after
What's included with your purchase
- 12 modules with 12 chapters each (144 chapters total)
- 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 week for 4 weeks, with flexible access for review and implementation.
How this compares to the alternatives
Unlike generic risk courses, this program is tailored to senior technical contributors who need to influence beyond their immediate domain without taking a management role.
Frequently asked
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.