Skip to main content
Image coming soon

OPS9142 Mastering ISO 20000 for Lead Infrastructure Engineers

$199.00
Adding to cart… The item has been added

A tailored course, built for your situation

Mastering ISO 20000 for Lead Infrastructure Engineers

Build repeatable service management systems that scale across global infrastructure teams

$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.
Frustrated that strong service designs stay trapped in one team?

The situation this course is for

High-performing infrastructure engineers often build excellent service models, but they’re not reused. Other units rebuild the same capabilities in silos, leading to compliance drift, inconsistent uptime, and duplicated audit effort. The cost isn't just inefficiency, it's missed influence.

Who this is for

Senior infrastructure engineers leading service design in highly regulated environments who want their architecture to become the default, not just one option

Who this is not for

Junior admins, helpdesk leads, or practitioners not involved in cross-team service definition or compliance frameworks

What you walk away with

  • Design service definitions that other teams adopt without central mandate
  • Structure SLAs and incident workflows that survive team boundaries
  • Produce reusable service artifacts aligned with ISO 20000 that pass audit scrutiny
  • Embed consistency across network, cloud, and platform teams using common service language
  • Position yourself as the integrator when new cross-functional services launch

The 12 modules (with all 144 chapters)

Module 1. Understanding ISO 20000's Expanded Role in Infrastructure
Explore how ISO 20000 now applies beyond ITSM to core infrastructure domains like cloud provisioning, network services, and platform reliability. Learn where it intersects with your current design work and how to position it as a cross-cutting enabler.
12 chapters in this module
  1. How ISO 20000 evolved beyond helpdesk ticketing
  2. Mapping infrastructure-as-a-service to service level requirements
  3. Aligning network uptime SLAs with ISO 20000 clause 8.1
  4. Integrating change management for cloud infrastructure teams
  5. Defining scope boundaries for distributed infrastructure units
  6. Using process maturity levels to benchmark service teams
  7. How ISO 20000 supports compliance with SOX and NIST CSF
  8. Differentiating ISO 20000 from ISO 27001 in practice
  9. Service reporting expectations for infrastructure leads
  10. Documenting incident response within service agreements
  11. Integrating automation workflows into service definitions
  12. Preparing for auditor questions on infrastructure service scope
Module 2. Structuring Reusable Service Definitions
Learn how to write service definitions so they’re adopted across teams. Focus on clarity, interoperability, and ease of audit-readiness.
12 chapters in this module
  1. Writing service scope statements for cross-team use
  2. Defining service owners and responsible parties clearly
  3. Creating service blueprints that non-specialists can adopt
  4. Using common language across cloud, network, and security teams
  5. Documenting dependencies without overcomplicating design
  6. Building service onboarding templates for new units
  7. Standardizing service KPIs across infrastructure domains
  8. Avoiding over-engineering in multi-region deployments
  9. Making service documentation version-controlled and accessible
  10. Integrating feedback loops into service design updates
  11. Using ISO 20000 templates to accelerate team adoption
  12. Reducing ambiguity in handoff procedures between teams
Module 3. Designing SLAs That Hold Across Teams
SLAs fail when they’re too rigid or too vague. This module teaches how to write SLAs that are both enforceable and flexible enough for distributed teams.
12 chapters in this module
  1. Setting realistic uptime targets for hybrid infrastructure
  2. Differentiating SLA, OLAs, and underpinning contracts
  3. Negotiating SLAs with internal cloud platform teams
  4. Using percentage-based vs time-based uptime metrics
  5. Handling SLA breaches without blame escalation
  6. Aligning SLAs with business criticality tiers
  7. Automating SLA tracking across distributed systems
  8. Documenting SLA review cycles and adjustments
  9. Integrating SLA reporting into operational dashboards
  10. Avoiding SLA bloat with too many metrics
  11. Creating SLA summaries for non-technical stakeholders
  12. Using SLAs to improve service continuity planning
Module 4. Change Management for Complex Infrastructure
Master change workflows that reduce risk while allowing velocity. Focus on integration with existing CI/CD and incident systems.
12 chapters in this module
  1. Aligning change workflows with ISO 20000 clause 8.5
  2. Categorizing changes by risk and automation readiness
  3. Implementing emergency change procedures without bypassing controls
  4. Integrating change advisory boards with sprint cycles
  5. Automating low-risk change approvals
  6. Documenting change backouts and rollback plans
  7. Linking change records to incident and problem data
  8. Using change success rates to improve governance
  9. Reducing CAB meeting fatigue with pre-approved changes
  10. Ensuring change compliance in multi-cloud environments
  11. Training teams to log changes correctly and consistently
  12. Auditing change workflows for ISO 20000 readiness
Module 5. Incident Management Across Domains
Incidents span networks, clouds, and applications. Learn how to design response workflows that coordinate across silos and close faster.
12 chapters in this module
  1. Defining incident ownership in shared infrastructure
  2. Integrating monitoring alerts into incident workflows
  3. Using automated triage to reduce mean time to assign
  4. Establishing cross-team war room procedures
  5. Documenting incident timelines for audit purposes
  6. Reducing duplicate tickets across monitoring tools
  7. Escalating incidents without blame culture
  8. Linking incidents to problem records and root cause analysis
  9. Measuring incident resolution against SLAs
  10. Using incident data to improve service design
  11. Creating post-mortems that drive change, not finger-pointing
  12. Aligning incident workflows with ISO 20000 clause 8.3
Module 6. Problem Management That Prevents Recurrence
Move from firefighting to prevention. Learn how to structure problem records that lead to systemic fixes.
12 chapters in this module
  1. Differentiating incidents from underlying problems
  2. Identifying chronic issues through incident pattern analysis
  3. Creating problem records with clear ownership
  4. Using root cause analysis frameworks like 5 Whys
  5. Prioritizing problem resolution by business impact
  6. Linking problem resolution to change management
  7. Documenting known errors and workarounds
  8. Reducing problem backlog with automation triggers
  9. Integrating problem data into service reviews
  10. Using problem trends to influence architecture changes
  11. Ensuring problem records meet ISO 20000 audit standards
  12. Training teams to contribute to problem management
Module 7. Configuration Management for Distributed Systems
Ensure configuration accuracy across thousands of nodes. Learn how to design CMDB practices that stay current and trusted.
12 chapters in this module
  1. Defining configuration items for hybrid infrastructure
  2. Integrating CMDB with cloud auto-discovery tools
  3. Maintaining CI ownership and accuracy over time
  4. Using CI relationships to improve incident root cause
  5. Automating CI updates from deployment pipelines
  6. Handling configuration drift in containerized environments
  7. Aligning CMDB scope with ISO 20000 requirements
  8. Auditing CMDB accuracy without manual checks
  9. Using configuration data to support change impact analysis
  10. Integrating CMDB with asset management systems
  11. Reducing CMDB bloat with lifecycle rules
  12. Training teams to update configuration records
Module 8. Service Continuity Planning for Infrastructure
Design continuity plans that are testable and adaptive. Focus on practical recovery over theoretical scenarios.
12 chapters in this module
  1. Assessing service criticality across business units
  2. Identifying single points of failure in network design
  3. Creating realistic RTO and RPO targets
  4. Designing failover procedures for cloud and on-prem systems
  5. Integrating DR testing into regular operations
  6. Documenting recovery workflows clearly and concisely
  7. Using tabletop exercises to improve readiness
  8. Aligning continuity plans with ISO 20000 clause 8.6
  9. Reducing recovery time with pre-staged environments
  10. Testing multi-region failover without downtime
  11. Maintaining continuity plans in agile environments
  12. Auditing recovery readiness without disruptive tests
Module 9. Supplier Management in Multi-Vendor Environments
You don't control all the infrastructure, but you're accountable for service. Learn how to manage external dependencies effectively.
12 chapters in this module
  1. Defining service level expectations with cloud providers
  2. Mapping vendor SLAs to internal service agreements
  3. Tracking third-party performance objectively
  4. Managing contract renewals with audit evidence
  5. Using SIG questionnaires to assess vendor compliance
  6. Integrating vendor data into incident and problem workflows
  7. Handling vendor disputes with documented evidence
  8. Ensuring subcontractor compliance with ISO 20000
  9. Auditing vendor deliverables against contract terms
  10. Reducing vendor lock-in through modular design
  11. Negotiating better terms with performance data
  12. Creating vendor scorecards for leadership reviews
Module 10. Service Reporting and Performance Visibility
Turn operational data into compelling service narratives for leadership and auditors.
12 chapters in this module
  1. Selecting KPIs that reflect real service health
  2. Creating dashboards that tell a story, not just show data
  3. Reporting uptime without hiding context
  4. Using trend data to justify infrastructure investments
  5. Aligning reports with ISO 20000 audit requirements
  6. Reducing report fatigue with automated summaries
  7. Presenting service performance to non-technical leaders
  8. Integrating customer feedback into service reviews
  9. Benchmarking service quality against industry standards
  10. Using reports to drive continuous improvement
  11. Auditing report accuracy and completeness
  12. Archiving service reports for compliance
Module 11. Continuous Improvement Through Service Reviews
Institutionalize learning from operations. Move from ad hoc fixes to systemic upgrades.
12 chapters in this module
  1. Scheduling regular service review meetings
  2. Using data to prioritize improvement opportunities
  3. Creating action plans from service review findings
  4. Tracking improvement initiatives to closure
  5. Integrating retrospectives into sprint cycles
  6. Using customer feedback to shape service evolution
  7. Measuring the impact of service changes
  8. Communicating improvements across teams
  9. Aligning improvements with ISO 20000 clause 10
  10. Avoiding improvement fatigue with focused sprints
  11. Documenting improvement history for auditors
  12. Scaling improvements across multiple service lines
Module 12. Implementing ISO 20000 Across Infrastructure Teams
Roll out ISO 20000 not as a compliance exercise, but as a lever for consistency, reliability, and influence.
12 chapters in this module
  1. Assessing current service management maturity
  2. Identifying quick wins for ISO 20000 alignment
  3. Building a rollout plan for multiple teams
  4. Training leads to sustain service practices
  5. Using internal audits to improve, not punish
  6. Preparing for external ISO 20000 certification
  7. Creating a living service management system
  8. Integrating ISO 20000 with other frameworks like NIST
  9. Reducing audit findings with proactive evidence
  10. Using certification as a credibility signal
  11. Maintaining ISO 20000 compliance over time
  12. Scaling practices to new divisions organically

How this maps to your situation

  • Service design reuse across infrastructure units
  • SLA consistency in multi-team environments
  • Change control in agile infrastructure operations
  • Incident coordination across network and cloud domains

Before vs. after

Before
Service models stay siloed, SLAs vary by team, and improvements require top-down mandates.
After
Your service definitions are reused across units, SLAs are consistent, and teams adopt them voluntarily.

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 2.5 hours per module, or 30 hours total to complete. Designed for practitioners to complete one module per week while working.

If nothing changes
Without structured service management, infrastructure teams will keep rebuilding the same capabilities independently, leading to higher compliance risk, longer incident resolution times, and missed opportunities for you to lead at scale.

How this compares to the alternatives

Unlike generic ITIL courses, this program focuses specifically on infrastructure engineers implementing ISO 20000 in regulated, multi-domain environments. It skips theory and delivers battle-tested templates and real-world decision frameworks used by senior leads.

Frequently asked

Is this course only for IT service desk managers?
No. This is tailored for infrastructure engineers who design and manage services across cloud, network, and platform teams. It’s built for those who need systems that scale beyond a single unit.
How is the course structured?
12 modules, each containing 12 chapters (144 chapters total).
Will this help me if my organization isn’t ISO 20000 certified?
Yes. The course teaches how to use ISO 20000 principles to create consistency, reduce risk, and extend your influence, even without formal certification.
$199 one-time. Approximately 2.5 hours per module, or 30 hours total to complete. Designed for practitioners to complete one module per week while working..

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
!