Skip to main content
Service Management in ITSM

Service Management in ITSM

$249.00
Your guarantee:
30-day money-back guarantee — no questions asked
How you learn:
Self-paced • Lifetime updates
Toolkit Included:
Includes a practical, ready-to-use toolkit containing implementation templates, worksheets, checklists, and decision-support materials used to accelerate real-world application and reduce setup time.
When you get access:
Course access is prepared after purchase and delivered via email
Who trusts this:
Trusted by professionals in 160+ countries
Adding to cart… The item has been added

This curriculum spans the design and governance of an enterprise ITSM function, comparable in scope to a multi-phase internal capability build, addressing strategic alignment, service operations, and integration with modern development practices across global and hybrid environments.

Module 1: Defining and Aligning ITSM Strategy with Business Objectives

  • Selecting which business units to prioritize for ITSM rollout based on operational criticality and change readiness.
  • Mapping core business services to underlying IT components to establish service ownership and accountability.
  • Deciding whether to adopt a centralized, decentralized, or hybrid ITSM governance model across global offices.
  • Establishing KPIs that reflect business outcomes rather than IT activity metrics (e.g., incident volume vs. business process uptime).
  • Conducting stakeholder workshops to reconcile conflicting priorities between IT, finance, and business leaders.
  • Determining the scope of initial ITSM implementation—starting with incident and request management versus full lifecycle coverage.

Module 2: Designing and Implementing Service Catalogs and Portals

  • Classifying services into customer-facing, technical, and supporting categories to ensure accurate catalog structuring.
  • Defining service ownership and approval workflows for catalog entry creation, updates, and retirement.
  • Integrating the service portal with identity providers (e.g., Azure AD, Okta) to enable single sign-on and role-based access.
  • Designing request fulfillment workflows with automated approvals based on cost thresholds or risk profiles.
  • Validating service descriptions with legal and compliance teams to avoid ambiguous SLAs or regulatory exposure.
  • Optimizing portal usability through iterative user testing with non-technical requesters to reduce support burden.

Module 3: Incident and Problem Management at Scale

  • Implementing event correlation rules to suppress noise and prevent alert storms from monitoring tools.
  • Establishing severity classification criteria that align with business impact, not just technical downtime.
  • Creating dedicated war rooms and communication protocols for major incident response across time zones.
  • Deciding when to escalate from incident resolution to formal problem management with root cause analysis.
  • Integrating incident data with CMDB to improve diagnosis accuracy and reduce mean time to repair (MTTR).
  • Enforcing post-incident review discipline, including action item tracking and follow-up validation.

Module 4: Change Enablement and Risk-Based Approval Workflows

  • Categorizing changes into standard, normal, and emergency types with differentiated approval requirements.
  • Implementing CAB structures—permanent vs. rotating members—based on organizational complexity and change volume.
  • Configuring automated risk scoring for changes using inputs like change type, affected CIs, and maintenance window.
  • Defining rollback procedures and success criteria prior to change authorization, especially for production systems.
  • Managing shadow IT by detecting unauthorized changes through integration with configuration monitoring tools.
  • Conducting change advisory board meetings with time-boxed agendas and documented decision rationales.

Module 5: Configuration Management and CMDB Governance

  • Selecting authoritative data sources for CIs (e.g., SCCM for workstations, ServiceNow Discovery for servers).
  • Defining CI ownership and stewardship roles to ensure data accuracy and timely updates.
  • Establishing reconciliation processes to resolve discrepancies between discovery tools and manual records.
  • Determining the depth of relationship mapping—direct dependencies only versus full impact chains.
  • Implementing lifecycle states for CIs (planned, live, retired) to support asset and change management.
  • Controlling CMDB access to prevent unauthorized modifications while enabling service impact analysis.

Module 6: Service Level Management and Performance Reporting

  • Negotiating SLA terms with business units, including realistic uptime targets and penalty-free maintenance windows.
  • Designing OLAs and UCs to align internal teams and third-party vendors with end-to-end service delivery.
  • Automating SLA breach alerts with escalation paths to prevent reactive firefighting.
  • Calculating and reporting on service availability using actual transaction data, not synthetic monitoring.
  • Handling SLA exceptions for planned outages without undermining accountability.
  • Presenting performance dashboards to executives using business-relevant metrics, not IT jargon.

Module 7: Continual Service Improvement and Metrics Utilization

  • Selecting improvement initiatives based on cost-benefit analysis of pain points identified in incident and change data.
  • Applying Lean or Six Sigma techniques to reduce waste in request fulfillment and incident resolution.
  • Validating improvement outcomes with before-and-after metrics, not anecdotal feedback.
  • Embedding CSI reviews into existing governance meetings to maintain momentum without creating overhead.
  • Using customer satisfaction surveys strategically—timing, frequency, and question design—to avoid survey fatigue.
  • Integrating feedback loops from support teams into CSI planning to address frontline operational bottlenecks.

Module 8: Integrating ITSM with DevOps and Agile Practices

  • Aligning change management processes with CI/CD pipelines using automated change records for low-risk deployments.
  • Defining service ownership models for microservices where development teams manage production behavior.
  • Integrating incident response with on-call engineering rotations and alerting systems like PagerDuty.
  • Adapting problem management to support blameless postmortems in DevOps cultures.
  • Mapping ITSM roles (e.g., service owner) to Agile roles (e.g., product owner) for shared accountability.
  • Using service modeling in ITSM tools to reflect dynamic cloud infrastructure and containerized workloads.
!