A tailored course, built for your situation
Mastering ISO 20000 for Service Delivery Practitioners
A step-by-step path to structured, scalable service management in complex engineering environments
$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.
The service transition package that keeps getting sent back for fixes
The situation this course is for
Despite strong technical delivery, service documentation often requires multiple review cycles due to inconsistent control mapping, unclear ownership handoffs, and misaligned audit expectations, especially under client or internal regulator scrutiny. This delays sign-off and dims visibility on engineering excellence.
Who this is for
Senior service delivery or engineering professional in a global systems integrator, responsible for designing, documenting, or transitioning managed services with compliance and audit readiness built in.
Who this is not for
Entry-level technicians, pure software developers without service ownership, or executives seeking board-level summaries. This is for practitioners who own the artefacts, not delegate them.
What you walk away with
- Produce service delivery packages that pass internal review without rework
- Apply ISO 20000 principles to real-world engineering workflows without overhead
- Align cross-functional teams using a shared, audit-ready service framework
- Reduce validation effort by documenting only what matters to auditors and clients
- Build trusted authority through consistent, referenceable deliverables
The 12 modules (with all 144 chapters)
Module 1. Understanding ISO 20000 in the Context of Engineering Services
Establish the foundational alignment between service management standards and real-world engineering delivery, focusing on scope relevance and integration points with existing the firm Engineering practices.
12 chapters in this module
- Defining service management in a systems engineering context
- Mapping ISO 20000 clauses to engineering service lifecycles
- Differentiating ISO 20000 from ISO 27001 and SOC 2 controls
- Recognizing where service ownership begins and ends
- Integrating service requests with technical delivery timelines
- Documenting service scope without overspecifying
- Auditor expectations for service transition evidence
- Common missteps in interpreting clause 4.2
- Aligning with client SLAs without scope creep
- Tracking service changes across distributed teams
- Ensuring continuous compliance during agile iterations
- Using ISO 20000 to strengthen vendor coordination
Module 2. Designing Service Level Agreements That Hold Up
Learn to draft SLAs that are technically enforceable, audit-ready, and aligned with delivery realities across engineering engagements.
12 chapters in this module
- Identifying core service components for SLA inclusion
- Setting measurable performance thresholds without guesswork
- Documenting availability commitments for hybrid systems
- Writing response time clauses that match incident workflows
- Avoiding ambiguous terms like 'best effort' or 'reasonable'
- Linking SLA metrics to monitoring tool outputs
- Handling third-party dependencies in SLA design
- Defining escalation paths that don’t stall
- Validating SLA feasibility with operations teams
- Capturing client-specific requirements in annexes
- Updating SLAs without triggering renegotiation
- Embedding audit evidence collection into SLA tracking
Module 3. Building the Service Portfolio with Purpose
Create a service portfolio that reflects actual capabilities, supports sales enablement, and withstands regulatory scrutiny.
12 chapters in this module
- Cataloging services without duplicating engineering docs
- Differentiating between service types and delivery modes
- Documenting service scope with clear boundary statements
- Including compliance-relevant metadata in service entries
- Versioning the service portfolio for audit trails
- Aligning service descriptions with client contracts
- Avoiding overpromising in service definitions
- Linking portfolio items to control objectives
- Updating service entries post-transition
- Using the portfolio to streamline onboarding
- Auditor focus areas in service portfolio reviews
- Maintaining portfolio accuracy across global teams
Module 4. Managing Service Requests Efficiently
Implement processes that handle service requests with speed and compliance, reducing manual intervention and rework.
12 chapters in this module
- Defining what constitutes a service request
- Routing requests to correct teams without delay
- Automating request classification using templates
- Validating request ownership before processing
- Integrating request workflows with change management
- Setting realistic fulfillment timelines
- Avoiding scope creep in standard service offerings
- Documenting request handling for audit purposes
- Measuring request resolution effectiveness
- Reducing back-and-forth through clear intake forms
- Handling non-standard requests without blocking flow
- Linking request data to continuous improvement
Module 5. Change Management Aligned to Engineering Cycles
Adapt ISO 20000 change control to fast-moving engineering environments without sacrificing compliance.
12 chapters in this module
- Classifying changes by risk and impact level
- Integrating change requests with sprint planning
- Documenting emergency changes without delays
- Ensuring CAB reviews are timely and decisive
- Using automated tools to track change approvals
- Linking changes to service impact assessments
- Avoiding change board bottlenecks in agile teams
- Capturing post-implementation reviews systematically
- Maintaining audit-ready change logs
- Handling rollback plans for failed changes
- Aligning change scope with client expectations
- Reducing change-related outages through planning
Module 6. Incident Management That Supports Continuous Delivery
Design incident workflows that resolve issues fast while preserving compliance and learning.
12 chapters in this module
- Defining incident severity levels with engineering input
- Routing incidents to correct support tiers automatically
- Documenting root cause without blame
- Linking incidents to known errors and workarounds
- Ensuring timely escalation paths
- Maintaining incident records for audit
- Avoiding duplicate tickets across teams
- Using incident data to improve service design
- Integrating monitoring tools with ticketing systems
- Reducing mean time to resolution with templates
- Closing incidents with client confirmation
- Reporting incident trends to leadership
Module 7. Problem Management That Prevents Recurrence
Turn incidents into long-term fixes by embedding problem management into engineering culture.
12 chapters in this module
- Identifying recurring incidents worth deeper analysis
- Initiating problem records without overburdening teams
- Conducting root cause analysis using 5 Whys or fishbone
- Documenting permanent fixes and workarounds
- Linking problems to change management workflows
- Assigning ownership for resolution
- Tracking problem resolution timelines
- Using problem records to update training materials
- Sharing lessons across delivery teams
- Measuring problem resolution effectiveness
- Auditing problem management outputs
- Integrating problem data into service reviews
Module 8. Configuration Management for Complex Systems
Build and maintain accurate configuration records that support audit, security, and service continuity.
12 chapters in this module
- Defining configuration items in hybrid environments
- Using automation to discover and update CMDB entries
- Linking CIs to service dependencies
- Ensuring CMDB accuracy without manual updates
- Handling cloud and on-prem CI differences
- Integrating CMDB with change and incident workflows
- Defining CI ownership across teams
- Auditing CMDB completeness and accuracy
- Reducing configuration drift through validation
- Using CI data for impact analysis
- Protecting CMDB from unauthorized changes
- Reporting on CMDB health to leadership
Module 9. Service Continuity Planning That Works in Practice
Develop recovery plans that are testable, understood, and effective when disruption hits.
12 chapters in this module
- Identifying critical services for continuity planning
- Setting realistic RTOs and RPOs with stakeholders
- Documenting recovery procedures clearly
- Testing recovery plans without disrupting delivery
- Involving engineering teams in test design
- Capturing test results for audit
- Updating plans based on test findings
- Aligning with client disaster recovery expectations
- Maintaining plan relevance during system changes
- Automating recovery validation where possible
- Reducing recovery time through preparation
- Reporting on continuity readiness to leadership
Module 10. Supplier Management Aligned to Service Delivery
Manage third-party suppliers to ensure they meet service, compliance, and audit expectations.
12 chapters in this module
- Defining supplier roles in service delivery
- Documenting supplier responsibilities clearly
- Integrating supplier performance into SLAs
- Conducting regular supplier reviews
- Handling underperforming suppliers
- Ensuring supplier compliance with ISO 20000
- Auditing supplier deliverables effectively
- Managing contract renewals proactively
- Reducing supplier-related outages
- Using supplier data for continuous improvement
- Maintaining supplier records for audit
- Building strong supplier relationships
Module 11. Service Reporting That Informs Decisions
Generate reports that reflect service performance accurately and drive meaningful improvements.
12 chapters in this module
- Identifying key service metrics for reporting
- Setting baselines and targets
- Automating report generation from tools
- Avoiding data overload in reports
- Linking reports to business outcomes
- Presenting data clearly to stakeholders
- Using reports for service improvement
- Validating report accuracy regularly
- Aligning with auditor expectations
- Reducing manual reporting effort
- Sharing reports securely
- Updating report content based on feedback
Module 12. Continuous Service Improvement in Engineering Contexts
Embed improvement into delivery cycles so that quality rises without adding burden.
12 chapters in this module
- Identifying improvement opportunities from service data
- Prioritizing improvements with impact-effort matrix
- Integrating CSI into sprint retrospectives
- Documenting improvement initiatives clearly
- Assigning ownership for improvement actions
- Measuring improvement effectiveness
- Sharing success stories across teams
- Using CSI to strengthen client trust
- Aligning improvements with business goals
- Reducing rework through proactive fixes
- Maintaining momentum in improvement cycles
- Reporting on CSI outcomes to leadership
How this maps to your situation
- Service transition under audit pressure
- SLA design for hybrid delivery models
- Incident response in distributed engineering teams
- Continuous improvement without process bloat
Before vs. after
Before
Service delivery packages require multiple review cycles, especially when auditors question control alignment or completeness.
After
Service packages are structured once, validated fast, and accepted on first submission, freeing time for higher-impact work.
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 week over 5 weeks, designed to fit around core delivery responsibilities.
If nothing changes
Without a structured approach, service delivery efforts remain reactive, rework persists, and influence stays limited to execution, not decision-shaping.
How this compares to the alternatives
Unlike generic ISO 20000 overviews, this course is tailored to engineering service delivery contexts, focusing only on what’s needed to pass review and reduce rework, not theoretical compliance.
Frequently asked
Do I need prior ISO 20000 experience?
No. The course starts from foundational concepts and builds to advanced application in real engineering contexts.
How is the course structured?
12 modules, each containing 12 chapters (144 chapters total).
Is this relevant if I work in cloud infrastructure?
Yes. The course includes hybrid and cloud-specific examples for service documentation, change, and continuity.
$199 one-time. Approximately 90 minutes per week over 5 weeks, designed to fit around core delivery responsibilities..
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