Description

This curriculum spans the breadth of operational challenges found in multi-year ITSM transformation programs, addressing the same governance, integration, and process-design complexities encountered when aligning service management practices across hybrid environments, competing business units, and regulated operations.

Module 1: Defining and Aligning ITSM Governance Frameworks

Selecting between centralized, federated, and decentralized governance models based on organizational size, regulatory requirements, and legacy system constraints.
Mapping ITIL practices to existing enterprise architecture standards without disrupting ongoing service delivery operations.
Establishing decision rights for service ownership across business units with competing priorities and budget control.
Integrating risk and compliance mandates (e.g., SOX, GDPR) into service management policies without creating excessive approval bottlenecks.
Designing escalation paths for incident and problem resolution that reflect actual organizational reporting lines, not just idealized RACI charts.
Documenting exception processes for bypassing standard workflows during mergers, acquisitions, or regulatory audits.

Module 2: Service Portfolio and Catalog Management in Complex Environments

Deciding which services to formalize in the catalog based on usage frequency, support cost, and contractual obligations.
Resolving conflicts between business units over service naming, classification, and ownership during catalog consolidation.
Implementing version control for service definitions when multiple teams contribute to the same service offering.
Managing shadow IT services that are actively used but not officially recognized in the portfolio.
Aligning service lifecycle stages (retire, maintain, develop) with budget cycles and vendor contract renewals.
Enforcing catalog accuracy through automated discovery tools while reconciling discrepancies with manual audits.

Module 3: Incident and Problem Management at Scale

Configuring event correlation rules to reduce alert noise without masking legitimate system degradation.
Setting thresholds for incident classification that balance response urgency with resource availability.
Implementing major incident management procedures that include non-IT stakeholders such as legal or customer support.
Deciding when to initiate a problem record based on recurrence patterns versus one-off incidents.
Integrating post-mortem findings into knowledge articles without exposing sensitive root cause details to all users.
Managing escalation timeouts when primary responders are unavailable due to shift changes or leave.

Module 4: Change Enablement and Risk-Based Approval Workflows

Classifying changes as standard, normal, or emergency based on impact, not just requester seniority.
Designing CAB membership that includes rotating representatives from development, security, and operations.
Implementing automated risk scoring for changes using historical success rates and affected component criticality.
Allowing pre-approved change templates while preventing scope creep during execution.
Handling emergency changes that bypass CAB review while ensuring audit trail completeness.
Reconciling change windows with third-party vendor maintenance schedules across multiple time zones.

Module 5: Configuration Management Database (CMDB) Strategy and Execution

Selecting authoritative data sources for CIs when multiple systems (e.g., SCCM, AWS Config, ServiceNow) report conflicting states.
Defining CI ownership accountability when infrastructure spans hybrid cloud and on-prem environments.
Implementing data reconciliation jobs that resolve duplicates without deleting active relationships.
Deciding which attributes to sync from discovery tools versus manual entry based on volatility and accuracy.
Managing access controls so that teams can update their own CIs without altering unrelated components.
Using dependency mapping to support impact analysis while avoiding overpopulation with trivial relationships.

Module 6: Service Level Management and Performance Accountability

Negotiating SLA terms with internal business units that have differing tolerance for downtime and performance degradation.
Defining measurable OLAs between support teams to ensure end-to-end accountability without creating blame cultures.
Adjusting SLA breach thresholds during planned maintenance without invalidating historical performance reporting.
Reporting uptime metrics that exclude externally caused outages while maintaining stakeholder trust.
Handling SLA exceptions for critical business events (e.g., product launches) without setting precedent.
Integrating customer satisfaction scores with technical SLAs to balance perception and performance.

Module 7: Knowledge and Self-Service Integration

Enforcing article ownership and review cycles to prevent outdated troubleshooting steps from being published.
Mapping knowledge base categories to incident ticket fields to enable automated suggestions during intake.
Deciding which content to expose in self-service portals based on sensitivity, language, and user role.
Measuring knowledge article effectiveness by tracking reuse rates versus resolution success.
Integrating AI-powered search with structured knowledge bases without over-relying on unverified responses.
Handling multilingual knowledge content when translation resources are limited or inconsistent.

Module 8: Continuous Improvement and Metrics-Driven Optimization

Selecting KPIs that reflect operational reality, not just what is easiest to extract from ITSM tools.
Conducting improvement workshops that include frontline staff, not just management, to identify process bottlenecks.
Using baseline metrics to evaluate the impact of tool upgrades or process changes over time.
Addressing data quality issues in reports caused by inconsistent field usage across teams.
Prioritizing improvement initiatives based on effort, risk, and potential service impact.
Documenting rejected improvement proposals to prevent redundant discussions in future cycles.