SkarpChapter 7 of 13
Customer Experience, Stakeholders, and Service Level Management
SLAs, XLAs, and stakeholder expectations can make or break your service reputation. See how ITIL 5 connects service level management, experience design, and stakeholder engagement into a coherent, testable set of concepts.
1. From Governance to Customer Experience (ITIL 5 Context)
Where This Fits
In ITIL 5, customer experience and stakeholder satisfaction sit at the heart of the Service Management System (SMS), not as extras but as core design goals.
Links to Previous Modules
You already saw how governance, risk, and control define what services must achieve, and how value streams describe how work flows from demand to value.
Focus of This Module
Here we zoom in on service level management and experience design: capturing expectations, shaping SLAs and OLAs, and balancing experience with efficiency.
ITIL 5 Perspective
Since ITIL 4, and continued in ITIL 5, the focus moved from rigid processes to flexible practices and co-created value. Service level management is one such key practice.
2. Stakeholders, Customers, and Experience vs. Satisfaction
Who Are the Stakeholders?
Stakeholders include customers, users, sponsors, and suppliers. Customers define requirements and pay; users actually use the service; sponsors authorize and fund; suppliers provide components.
Customer Experience (CX)
Customer experience is the overall perception stakeholders have when interacting with the service across all touchpoints: apps, portals, support, and communications.
Stakeholder Satisfaction
Satisfaction is how well the service meets or exceeds expectations, shaped by outcomes, interactions, and emotions during the service journey.
Co-Creating Value
In ITIL 5, value is co-created: it appears when stakeholders get outcomes they care about with a positive experience, at acceptable cost and risk.
3. SLAs, OLAs, Underpinning Contracts – The Basics
Service Level Management Focus
Service level management is about negotiating, agreeing, and managing service targets with stakeholders so promises and delivery align.
SLA: External Promise
A Service Level Agreement is between provider and customer. It defines service targets and responsibilities in business-friendly language.
OLA: Internal Support
An Operational Level Agreement is internal. It describes how teams inside the provider organization work together to meet the SLA.
Underpinning Contracts
Underpinning contracts are agreements with external suppliers whose performance supports the SLA, such as cloud or telecom providers.
The Alignment Triangle
Picture a triangle: SLA at the top, OLA at bottom left, underpinning contract at bottom right. All must align, or you risk over-promising or under-delivering.
4. Real-World Example: University Wi‑Fi Service
Scenario Overview
You manage IT at a university. Campus Wi‑Fi is a critical service. Stakeholders include administration, faculty, students, staff, visitors, and external providers.
The Wi‑Fi SLA
SLA promises: 99.5% availability in teaching hours, capacity for 200 users per hall, 15-minute response and 2-hour resolution for critical incidents, plus a 4.2/5 satisfaction score.
Internal OLAs
OLAs: the network team restores lecture hall outages within 90 minutes; the service desk answers Wi‑Fi calls within 30 seconds and logs incidents accurately.
Underpinning Contracts
Contracts: ISP provides 99.9% link availability and 4-hour fix time; hardware vendor offers next-business-day replacement of failed access points.
Spotting Misalignment
If suppliers only guarantee 95% availability but your SLA promises 99.5%, there is misalignment. Service level management must negotiate realistic, aligned targets.
5. From SLAs to XLAs: Measuring Experience
Limits of Classic SLAs
Traditional SLAs focus on technical metrics like uptime and response time. Useful, but they do not fully capture how users actually feel about the service.
What Are XLAs?
Experience Level Agreements focus on experience outcomes, such as ease of use or satisfaction scores, complementing technical SLAs.
SLA vs. XLA Example
SLA: 99.9% availability and 30-minute response. XLA: 90% of users rate Wi‑Fi as easy to use and average satisfaction is at least 4 out of 5.
ITIL 5 View on Metrics
ITIL 5 encourages combining hard metrics (uptime) with soft metrics (satisfaction, effort, Net Promoter Score) to monitor value and outcomes.
Design from Experience Backwards
Start with desired experiences, define experience indicators, then shape SLAs, OLAs, and contracts that support those experiences.
6. Metrics, KPIs, and Value Realization
Why Metrics Matter
ITIL 5 stresses that you get what you measure. If you pick the wrong metrics, you can unintentionally encourage the wrong behaviors in teams.
Key Metric Terms
A metric is any measurable value. A KPI is a critical metric. A target is the desired KPI level. Value realization is proof that stakeholders get real benefits.
Types of Metrics
Track utility (does it work?), warranty (is it reliable and secure?), experience (how does it feel?), and business metrics (does it help the organization?).
Trade-Offs in Practice
Exam scenarios often involve trade-offs: cutting support hours may save cost but hurt experience; maximizing performance may require higher spend.
Balancing for Value
You are expected to balance cost vs. quality, efficiency vs. experience, and short-term savings vs. long-term satisfaction and trust.
7. Thought Exercise: Redesign a Frustrating Service
Activity: Take 3–4 minutes to redesign a service from the user experience and service level point of view.
- Pick a frustrating digital service you know (for example, a slow university portal, a confusing ticket system, or a streaming app that buffers a lot).
- Identify stakeholders:
- Who is the customer?
- Who are the users?
- Who might be suppliers?
- List 3 pain points users experience. For each, decide whether it is mainly about:
- Utility (it does not do what they need),
- Warranty (it is unreliable or insecure), or
- Experience (it is confusing, slow to use, or unfriendly).
- Draft 2–3 SLA-style targets that would reduce those pain points. Use clear, testable wording, such as:
- "90% of login attempts succeed within 5 seconds during peak hours."
- "Critical portal outages are resolved within 60 minutes, 95% of the time."
- Add 1 XLA-style target that captures experience, for example:
- "Average ease-of-use rating for the portal is at least 4/5 in student surveys."
- Reflect: What internal OLAs or supplier contracts would you need to adjust so that these targets are realistic?
Write your answers in short bullet points. If you are revising for an exam, practice turning each pain point into a clear metric with a realistic target.
8. Quiz: SLAs, XLAs, and Trade-Offs
Answer this practice question to check your understanding of service level management and experience.
Your IT team meets its SLA of resolving 95% of incidents within 8 hours, but user satisfaction scores are falling. Which is the BEST explanation in line with ITIL 5 guidance?
- The SLA is sufficient; falling satisfaction must be due to unrealistic user expectations.
- The SLA focuses on a technical metric that does not fully reflect user experience, so you should review and possibly add experience-focused measures.
- The team should ignore satisfaction scores as long as SLA targets are met, because SLAs are contractually binding.
- The solution is to tighten the SLA to 100% resolution within 8 hours, without changing what is measured.
Show Answer
Answer: B) The SLA focuses on a technical metric that does not fully reflect user experience, so you should review and possibly add experience-focused measures.
ITIL 5 emphasizes that metrics should reflect value and experience, not just technical activity. Meeting an 8-hour resolution SLA does not guarantee a good experience. The best response is to review the SLA and add or adjust experience-focused measures, such as satisfaction or effort scores.
9. Flashcards: Key Terms Review
Use these flashcards to reinforce core concepts from this module.
- Service Level Agreement (SLA)
- An agreement between a service provider and a customer that describes the service, documents service level targets, and specifies responsibilities of both parties.
- Operational Level Agreement (OLA)
- An internal agreement between parts of the same organization that supports the delivery of services to customers and helps fulfill SLAs.
- Underpinning Contract
- A contract between a service provider and an external supplier whose performance supports the delivery of a service and achievement of SLA targets.
- Customer Experience (CX)
- The overall perception and feelings of a stakeholder resulting from interactions with a service across all touchpoints.
- Experience Level Agreement (XLA)
- A set of agreed experience-focused targets (such as satisfaction or ease-of-use scores) that complement traditional SLAs. Common in practice and aligned with ITIL 5 principles, even if not a formal ITIL term.
- Metric vs. KPI
- A metric is any measurable value. A KPI (Key Performance Indicator) is a metric that is critical to achieving objectives and is actively used to manage performance.
- Value Realization
- Evidence that a service is delivering the expected benefits, outcomes, and experiences that matter to stakeholders, relative to cost and risk.
- Stakeholder Satisfaction
- The degree to which a stakeholder's expectations about a service are met or exceeded, influenced by outcomes, interactions, and emotions.
- Service Level Management (ITIL 5)
- The practice of setting clear, realistic, and value-focused service targets with stakeholders and managing performance against them to support co-created value.
10. Quiz: Stakeholders and Alignment
One more quick question to solidify your understanding of alignment between SLAs, OLAs, and contracts.
A company promises its customers 99.9% availability for an online service. Internally, the database team has an OLA of fixing database issues within 8 hours, and the cloud provider’s contract guarantees 95% availability. What is the MOST important action for the service level management practice?
- Do nothing; as long as incidents are fixed eventually, the SLA is valid.
- Lower the customer SLA to 95% availability without consulting stakeholders.
- Review and renegotiate OLAs and supplier contracts, or adjust the SLA, so that all three are realistically aligned.
- Increase monitoring frequency to detect database issues faster, without changing any agreements.
Show Answer
Answer: C) Review and renegotiate OLAs and supplier contracts, or adjust the SLA, so that all three are realistically aligned.
Service level management must ensure that SLAs, OLAs, and underpinning contracts are aligned and realistic. Here, the supplier's 95% availability cannot support a 99.9% customer SLA, so agreements need to be reviewed and adjusted.
Key Terms
- Metric
- A measurable value used to track and assess the status of a specific process, activity, or outcome.
- Stakeholder
- Any individual or organization that has an interest in, or is affected by, a service, including customers, users, sponsors, and suppliers.
- Value Realization
- Demonstrable evidence that a service is delivering the expected benefits, outcomes, and experiences to stakeholders, considering cost and risk.
- Underpinning Contract
- A contract between a service provider and an external supplier that supports the delivery of a service and achievement of SLA targets.
- Customer Experience (CX)
- The overall perception and emotional response of a stakeholder resulting from interactions with a service across all touchpoints.
- Service Level Management
- The ITIL 5 practice focused on setting, agreeing, and managing service level targets with stakeholders and monitoring performance to support co-created value.
- Service Level Agreement (SLA)
- A documented agreement between a service provider and a customer that defines the service, service level targets, and responsibilities.
- Key Performance Indicator (KPI)
- A critical metric that indicates how well an objective is being achieved and is used to manage performance.
- Experience Level Agreement (XLA)
- An agreement that defines measurable experience outcomes, such as satisfaction or ease-of-use, complementing traditional SLAs.
- Operational Level Agreement (OLA)
- An internal agreement between parts of the same organization that supports the provider in delivering services to customers and meeting SLAs.