ITIL 5 MP : ITIL Experience (Domain 3)
ITIL 5 – Managing Professional : Certified ITIL Managing Professional - Domain 3 - ITIL Experience (Version 5)
This comprehensive study guide is designed for professionals seeking the ITIL Managing Professional designation under the Version 5 framework. It focuses on Domain 3, ITIL Experience, which represents a paradigm shift from traditional service performance metrics toward human-centered, experience-led design and delivery. In a digital-first economy, the value of a service is no longer measured solely by technical uptime or functional utility; instead, value is co-created through the thoughts, feelings, and bodily responses of stakeholders throughout the service relationship.
1. Defining Digital Experience in the ITIL Framework
In ITIL (Version 5), digital experience is defined as the holistic response of an individual to their interactions with digital products and services. This is not a superficial measure of user satisfaction, but a deep exploration of how a person feels, thinks, and physically responds to a digital environment.
The Components of Experience
The framework categorizes these responses into three primary domains:
- Affective (Feelings): The emotional state triggered by an interaction, such as frustration during a service outage or confidence during a seamless transaction.
- Cognitive (Thoughts): The mental processing and evaluation of the interaction, including the logic applied to determine if a service met its intended purpose.
- Physiological (Bodily Responses): The physical reaction to digital stimuli, which can include stress responses (elevated heart rate) or ease of use (reduced eye strain).
These responses are not isolated to the moment of interaction. They are influenced by the individual’s anticipation (what they expect to happen), their perception (what they believe is happening), and their evaluation (the judgment they pass after the event). Past experiences and the current emotional or cognitive state of the person also play significant roles in shaping the final experience.
2. The ITIL Experience Model: Anticipation, Perception, and Evaluation
The ITIL Experience Model provides a structured way to understand the lifecycle of a single interaction or a long-term relationship. It moves beyond the “moment of truth” to look at the context surrounding every touchpoint.
Anticipation
Every user or customer enters a service relationship with a set of expectations. Anticipation is shaped by the service offering, brand reputation, and previous interactions. If a provider promises a “frictionless” experience, the stakeholder anticipates a specific level of ease.
Perception
Perception occurs during the interaction. It is the stakeholder’s subjective reality of the service delivery. This is often where “frictions” are identified. For example, even if a system is technically “up” and performing within parameters, a user may perceive it as slow or difficult if the interface is counter-intuitive.
Evaluation
After the interaction, the stakeholder reflects on the outcome. They compare their perception against their initial anticipation. The result of this evaluation determines the level of trust and the likelihood of future engagement. Positive evaluations build loyalty and advocacy, while negative evaluations create distance and disengagement.
3. Experience Stakeholders and Role-Based Tensions
Experience is a multi-sided phenomenon involving various roles within both the consumer and provider organizations. Each role has distinct needs, which often leads to inherent tensions that must be managed to ensure a positive outcome.
Consumer Stakeholders
| Role | Responsibility | Experience Focus |
|---|---|---|
| User | Interacts directly with the product/service. | Usability, reliability, and emotional ease. |
| Customer | Defines requirements and agrees to service levels. | Value realization and alignment with business goals. |
| Sponsor | Authorizes the budget for the service. | Return on investment (ROI) and cost-efficiency. |
Provider Stakeholders
| Role | Responsibility | Experience Focus |
|---|---|---|
| Agent | Delivers or supports the service (e.g., Service Desk). | Clear instructions, effective tools, and psychological safety. |
| Principal | Responsible for the overall delivery and quality. | Operational stability and adherence to agreements. |
| Provider Sponsor | Funds the internal development of products. | Strategic alignment and market competitiveness. |
| Enabler | Supports the provider internally (e.g., HR, IT). | Internal process efficiency. |
Managing Tensions
Tensions typically arise when the goals of these stakeholders conflict. For example, a Sponsor may want to reduce costs, leading to a “Design” that is less intuitive for the User, thereby creating a negative experience. ITIL Experience provides guidance on identifying these tensions and proposing mitigation approaches that preserve human dignity and service value.
4. Experience and the ITIL Four Dimensions
To improve experience, an organization must analyze it through the lens of the Four Dimensions of Product and Service Management. Experience is not a separate “fifth dimension”; rather, it is the result of how these four areas interact.
Organizations and People
This dimension focuses on the culture, skills, and communication styles that shape perception. For example, the empathy shown by a service desk agent significantly influences the “relational” driver of experience, regardless of the technical resolution.
Information and Technology
Technology is the primary medium for digital experience. The interface design, speed of automation, and the use of AI all determine how a user “physically” and “cognitively” responds to the service.
Partners and Suppliers
Modern services are often end-to-end ecosystems involving multiple third parties. Experience is often broken when there is a lack of alignment between the primary provider and their suppliers, leading to “broken expectations” for the consumer.
Value Streams and Processes
This dimension examines the steps taken to create value. If a process is overly complex or includes unnecessary “loops,” it creates friction. Experience-led design aims to streamline value streams to remove these obstacles.
5. Service Journey Mapping: The ITIL Service Journey Model
The ITIL Service Journey Model is a central tool for mapping the end-to-end experience of a stakeholder. It identifies the specific “steps” or touchpoints where experience signals are generated.
Steps in the Journey
The journey is not a straight line but a series of interconnected phases:
- Discover: The initial awareness of a need and the exploration of service offerings.
- Design: The collaborative phase where the service is shaped to meet stakeholder needs.
- Acquire: The formalization of the relationship through agreements.
- Build/Transition: The implementation of the service.
- Operate/Deliver/Support: The ongoing interactions where the service functions and is maintained.
Mapping Experience Signals
By applying the journey model, providers can identify “experience moments”—specific times when the stakeholder’s evaluation is most critical. Providers map “signals” (data points indicating how the stakeholder feels) across these steps to identify areas for improvement.
6. Experience Drivers: Functional vs. Relational
ITIL Experience distinguishes between two types of drivers that influence the stakeholder’s evaluation.
Functional Drivers
These are the “hard” requirements of a service.
- Performance: Is the service fast enough?
- Reliability: Does the service work when needed?
- Cost: Is the service within the budget? Functional success is the baseline. If a service fails functionally, it is almost impossible to have a positive experience.
Relational Drivers
These are the “soft” or human elements of the service.
- Trust: Does the consumer believe the provider has their best interests at heart?
- Communication: Are the updates clear and timely?
- Empathy: Does the provider understand the impact of a service issue on the user’s work? Positive relational drivers can often mitigate the impact of a minor functional failure, whereas a lack of trust can ruin even a technically perfect service.
7. Capturing Experience: Evidence, Signals, and Telemetry
To manage experience, a provider must be able to capture and analyze it. This involves collecting different types of evidence and signals across multiple “tiers” of data.
Types and Sources of Evidence
- Quantitative Telemetry: Objective data such as response times, error rates, and system uptime.
- Qualitative Evidence: Subjective data gathered through surveys, interviews, and sentiment analysis.
- Signals: Specific indicators that represent a change in stakeholder experience (e.g., a sudden drop in portal logins may signal frustration).
Data Quality: Trustworthiness and Coherence
When evaluating experience evidence, two criteria must be met:
- Trustworthiness: Is the data accurate and unbiased? (e.g., avoiding “anti-patterns” like leading questions in surveys).
- Coherence: Does the data make sense when compared across different sources? (e.g., if technical metrics are “green” but user sentiment is “red,” there is a lack of coherence).
8. Experience Domains and Experience Level Agreements (XLAs)
Traditional Service Level Agreements (SLAs) often focus on technical performance (output). ITIL Experience introduces the concept of managing the relationship through experience domains and outcome-focused agreements, often referred to as XLAs (Experience Level Agreements).
The Four Experience Domains
Experience management is categorized into domains to ensure comprehensive coverage:
- Product Experience: Focuses on the features and usability of the digital tool.
- Service Experience: Focuses on the support and delivery mechanisms.
- Relationship Experience: Focuses on the long-term trust and partnership between organizations.
- Outcome Experience: Focuses on whether the stakeholder actually achieved their goals.
Beyond the “Watermelon Effect”
Traditional SLAs can lead to the “watermelon effect”—where metrics appear “green” on the outside (technical uptime), but the stakeholder experience is “red” on the inside (unmet needs). XLAs use experience telemetry to align performance with actual stakeholder perception.
9. Continual Experience Improvement
Experience is not static; it requires constant monitoring and refinement. ITIL Experience proposes a specific cycle for improvement: Notice – Interpret – Hypothesize – Experiment.
The Improvement Cycle
- Notice: Identify a signal or a friction point in the service journey.
- Interpret: Understand the root cause of the friction. Is it functional or relational?
- Hypothesize: Propose a change that might improve the experience.
- Experiment: Test the change in a controlled environment and measure the results.
Improvements “By” vs. “To” the System
- Improvements BY the System: Operational fixes performed within existing processes (e.g., training a service desk agent to be more empathetic).
- Improvements TO the System: Changing the fundamental structure of the service value chain or governance model (e.g., redesigning the service portal to remove three steps from a request process).
10. Human-AI Service Interaction and Governance
The introduction of AI into digital products and services creates new experience challenges and opportunities. ITIL (Version 5) emphasizes that AI must be “human-aware” and governed ethically.
AI and the Service Journey
AI can support experience management in several ways:
- Experience Capture: Using sentiment analysis to interpret written feedback.
- Measurement: Predicting potential experience frictions before they happen.
- Interaction: Using intelligent agents (chatbots) to provide immediate support.
AI Governance and Ethics
AI interactions must be transparent and accountable. Governance ensures that AI does not compromise human dignity or introduce bias into the service relationship. The ITIL AI Capability Model provides a framework for integrating AI into the service lifecycle without losing the “human touch” that drives relational experience.
11. Practice Section
Short-Answer Questions
- How does ITIL (Version 5) define “digital experience”?
- What are the three components of the ITIL Experience Model?
- Identify the three primary consumer stakeholders and their main experience focus.
- What is the “watermelon effect” in service management?
- Distinguish between functional and relational experience drivers.
- What are the four steps in the continual experience improvement cycle?
- How does the “Information and Technology” dimension influence perceived experience?
- What is the purpose of the “Discover” activity in the ITIL Service Journey?
- What are the two criteria used to evaluate experience evidence?
- Define an “experience moment” in the context of the service lifecycle.
Answer Key
- Digital experience is how a person feels, thinks, and bodily responds to interactions with digital products and services and their co-creating organizations.
- The three components are Anticipation (expectations), Perception (subjective reality during interaction), and Evaluation (post-interaction judgment).
- The consumer stakeholders are the User (focus on usability), the Customer (focus on value realization), and the Sponsor (focus on ROI/budget).
- The “watermelon effect” refers to a situation where technical metrics (SLAs) appear “green” or successful, but the stakeholder experience is “red” or negative.
- Functional drivers relate to technical performance and utility (does it work?), while relational drivers relate to human elements like trust, empathy, and communication.
- The four steps are Notice, Interpret, Hypothesize, and Experiment.
- This dimension determines the physical and cognitive response through interface design, automation speed, and the effectiveness of technology tools.
- The purpose of the “Discover” activity is the initial identification of a stakeholder’s need and the awareness of potential service offerings.
- The two criteria are Trustworthiness (accuracy/lack of bias) and Coherence (consistency across different data sources).
- An experience moment is a specific point in the product or service lifecycle where a stakeholder interaction creates a distinct and lasting impression.
Open-Ended / Design Questions
- Scenario: You are a Service Designer for a new AI-driven HR portal. Map a stakeholder journey for a new employee and identify three potential “frictions” they might encounter during the “Transition” phase.
- Design Task: Create a set of three XLAs (Experience Level Agreements) for a cloud storage service. Ensure they cover the “Product Experience” and “Outcome Experience” domains.
- Analysis: A provider’s technical logs show 99.9% uptime for an application, but the “Customer Journey” mapping shows high levels of user frustration. Apply the “Four Dimensions” to identify potential root causes beyond technical performance.
- Proposal: Develop a “Hypothesis” for an experiment aimed at improving the “Relational Driver” of trust between a managed service provider and its customer sponsor.
- Ethics Review: Propose a set of three governance criteria for using an AI chatbot to handle “Support” activities, ensuring the interaction maintains human dignity and transparency.
12. Glossary of Key Terms
- Anticipation: The state of expectation a stakeholder has before a service interaction occurs.
- Bodily Response: The physical reaction (e.g., stress, heart rate, eye strain) an individual has to a digital product or service.
- Coherence: A quality of experience evidence where data from different sources provides a consistent and logical story.
- Digital Experience: The combined feelings, thoughts, and physical responses to digital interactions and their outcomes.
- Evaluation: The cognitive judgment a stakeholder makes after comparing their service perception to their initial anticipation.
- Experience Domain: One of four specific areas of focus in experience management: Product, Service, Relationship, or Outcome.
- Experience Evidence: The data (both quantitative and qualitative) collected to understand stakeholder experience.
- Experience Friction: A point of tension or difficulty in the service journey that negatively impacts the stakeholder’s experience.
- Experience Moment: A critical point in the service lifecycle where an interaction significantly influences a stakeholder’s perception of value.
- Experience Signal: An indicator or data point that suggests a change in the state of stakeholder experience.
- Functional Driver: A technical or logical aspect of a service (like speed or reliability) that affects the experience.
- ITIL Service Journey Model: A framework used to map the steps a stakeholder takes from discovering a service to realizing its value.
- Perception: The subjective reality of a stakeholder during an interaction with a product or service.
- Relational Driver: A human-centered aspect of a service relationship, such as trust, communication, or empathy.
- Service Relationship: The co-creative interaction between a service provider and a service consumer.
- Stakeholder Tension: A conflict between the needs, goals, or expectations of different roles within the service relationship.
- Trustworthiness: The degree to which experience data is accurate, reliable, and free from bias or leading questions.
- Value Co-creation: The collaborative process where both providers and consumers contribute to the realization of service value.
- Watermelon Effect: A metaphor for service reports that show positive technical results (green) while hiding negative stakeholder experiences (red).
- XLA (Experience Level Agreement): An agreement focused on the human experience and outcomes of a service rather than just technical outputs.
Leaderboard
No scores saved yet. Be the first!
30 Questions — ITIL 5 – Managing Professional : Certified ITIL Managing Professional - Domain 3 - ITIL Experience (Version 5)
Expand any question to reveal the correct answer and explanation.
-
1 A consumer uses a digital portal to submit a complex request and finds the interface visually pleasing but technically unresponsive. According to the ITIL Experience Model, which element is primarily associated with the user's cognitive processing of this interaction?
Consider the phase of the experience model that involves weighing the outcomes of an interaction.
Evaluation
Evaluation is the cognitive phase where the person assesses and weighs the interaction and its outcomes against their needs and context.
-
✗ Anticipation
This stage relates to the user's expectations and state before the interaction occurs, not the processing of the active interaction.
-
✗ Perception
Perception involves the immediate sensory and bodily response to the interaction, whereas the question asks about the cognitive processing of the outcome.
-
✗ Bodily response
Bodily response is a physical reaction included in the definition of digital experience, rather than the cognitive assessment phase.
-
-
2 During a service journey, a service desk agent feels restricted by rigid automated workflows that prevent them from empathizing with a frustrated customer. This scenario represents a tension between which two provider-side stakeholders?
Identify the stakeholder representing the organizational authority and the one representing the frontline employee.
Principal and Agent
The tension between the principal (organization/leadership) and the agent (employee) often arises when organizational rules conflict with the agent's ability to deliver a human-centered experience.
-
✗ Enabler and Provider Sponsor
This pair typically involves the technical support for the service and the executive funding it, rather than the conflict between rules and frontline delivery.
-
✗ Principal and Enabler
Principal and enabler tensions usually relate to the organizational goals versus the technical capabilities provided to achieve them.
-
✗ Agent and User
While the agent and user interact, the source of the friction described is the internal organizational constraint, not a consumer-side role conflict.
-
-
3 When assessing the validity of experience evidence, a service manager notices that while individual surveys are positive, the narrative logs show deep frustration with the service lifecycle. Which criterion is used to evaluate the consistency across these different data sources?
Think of the term that describes how well different pieces of a story fit together.
Coherence
Coherence is the criterion used to evaluate whether different types of evidence align and form a logical, non-contradictory picture of the experience.
-
✗ Trustworthiness
Trustworthiness focuses on the reliability and integrity of the source itself rather than the logical connection between different evidence pieces.
-
✗ Partiality
Partiality is an inherent characteristic of metrics in experience management, not a criterion for evaluating evidence quality.
-
✗ Synthetic capturing
This refers to a technique for collecting data, not a qualitative criterion for evaluating the result of that collection.
-
-
4 In the ITIL Product and Service Lifecycle Model, which activity is specifically responsible for creating 'experience moments' by ensuring that the digital product is technically integrated and ready for active use?
Look for the activity that bridges the gap between creation and live operation.
Transition
Transition involves moving products into the live environment, where critical experience moments occur as users first encounter the operational reality.
-
✗ Build
The build activity focuses on construction and assembly, but the readiness for active use and integration into the environment occurs later.
-
✗ Acquire
Acquire is about obtaining components or resources, which is too early in the lifecycle for the integration moments described.
-
✗ Design
Design sets the plan for the experience but does not involve the live technical integration that creates the operational experience moment.
-
-
5 An organization monitors 'time to resolution' for incidents but realizes this metric does not reflect how users felt during the downtime. Why does ITIL Experience suggest that all metrics should be treated as 'hypotheses'?
Consider the relationship between a data point and the complex reality of human emotion.
Metrics only reflect a partial segment of the human experience.
Experience is subjective and multidimensional; metrics are proxy indicators that require testing to see if they truly correlate with the human reality.
-
✗ Metrics are only narrative and lack numerical precision.
ITIL recognizes both numerical and narrative signals; the issue is not the format but the scope of what is captured.
-
✗ Capture techniques always introduce survivorship bias.
While survivorship bias is an anti-pattern, it is not the fundamental reason why metrics are considered hypotheses.
-
✗ Operational data is always synthetic and lacks direct evidence.
Data can be direct, indirect, or synthetic; the hypothetical nature arises from the gap between data and human sentiment.
-
-
6 A company decides to change the interface of its internal HR system based on a new corporate identity. According to the 'Continual Experience Improvement' modes, this change is classified as:
Distinguish between working within a design and changing the design itself.
Improvement to the system
Improvements to the system involve changing the fundamental design, rules, or structure of the system itself.
-
✗ Improvement by the system
Improvements by the system occur within the existing rules and operational parameters of the current system.
-
✗ Synthetic improvement
This is not a recognized classification within the ITIL Experience framework for improvement types.
-
✗ Relational improvement
While it may affect relations, the formal classification depends on whether the system's structure is being altered.
-
-
7 In the context of experience management, which stakeholder role is defined as the individual or group that provides the necessary resources or infrastructure to allow a service to function, without directly delivering the service themselves?
This role acts behind the scenes to provide the 'means' for service delivery.
Enabler
The enabler provides the technology, tools, or support that 'enables' the agent to perform their role in the service relationship.
-
✗ Agent
The agent is the one who actively delivers the service or interacts with the consumer.
-
✗ Principal
The principal is the entity on whose behalf the service is provided, usually the organization's leadership.
-
✗ Customer Sponsor
The customer sponsor is a consumer-side role that provides funding or authority for the service.
-
-
8 Which experience domain focuses specifically on the physical, social, or technical environment in which a service interaction occurs?
Think about the external surroundings of an interaction.
Contextual
The contextual domain encompasses the external circumstances and environment surrounding the interaction.
-
✗ Personal
The personal domain relates to the individual's inner state, such as their mood or past history.
-
✗ Functional
The functional domain relates to the task performance and technical success of the interaction.
-
✗ Relational
The relational domain focuses on the trust and communication between the provider and consumer.
-
-
9 When applying the ITIL Continual Improvement Model to experience, the loop of 'Notice – Interpret – Hypothesize – Experiment' is used. Which step involves forming a proposed explanation for a detected experience signal?
This step is the bridge between understanding a problem and testing a solution.
Hypothesize
Hypothesizing is the phase where a theory is developed regarding why an experience is occurring and what might improve it.
-
✗ Notice
Noticing is the initial detection of a signal or data point.
-
✗ Interpret
Interpretation is about understanding the meaning of what was noticed, but not yet proposing a specific change.
-
✗ Experiment
Experimenting is the active testing of the hypothesis in a real or simulated environment.
-
-
10 If an organization uses 'synthetic capturing' for experience evidence, what are they primarily doing?
Focus on the 'artificial' nature of the data collection method.
Using automated scripts to simulate user interactions and measure performance.
Synthetic capturing involves bots or scripts that mimic user behavior to identify frictions before actual humans encounter them.
-
✗ Conducting one-on-one interviews with users.
This is a direct capture technique, whereas synthetic capturing is automated.
-
✗ Analyzing historical logs of past service interactions.
This is generally considered indirect capture, as it uses data created as a byproduct of actual human interactions.
-
✗ Gathering feedback via third-party review sites.
This is a form of indirect capture that relies on external narrative signals.
-
-
11 A service provider and a consumer move from a 'basic' service relationship to a 'collaborative' one. How does this shift primarily affect trust requirements in the service journey?
Consider the impact of shared responsibility on the need for reliability.
Trust requirements increase as both parties share more risk and information.
Collaborative relationships (partnerships) involve high levels of shared goals and transparency, necessitating deeper mutual trust.
-
✗ Trust requirements decrease because the relationship is more transactional.
Collaborative relationships are less transactional and require significantly more trust.
-
✗ Trust requirements stay the same, but the duration of the journey shortens.
The intensity and nature of trust change fundamentally when moving toward collaboration.
-
✗ Trust is replaced by rigid Service Level Agreements (SLAs).
Collaborative relationships often rely more on XLAs and relational trust than on rigid, punitive SLAs.
-
-
12 Which 'dimension' of product and service management is most directly responsible for shaping the organizational culture that influences how employees (agents) perceive their own work experience?
Look for the dimension that explicitly includes 'culture' and 'competencies'.
Organizations and People
This dimension covers team structures, culture, and competencies, all of which are foundational to employee experience.
-
✗ Information and Technology
While technology supports work, the culture and perception of experience are rooted in the people and organizational structure.
-
✗ Value Streams and Processes
This dimension focuses on the flow of activities rather than the cultural and human elements of the workforce.
-
✗ Partners and Suppliers
This dimension relates to external ecosystems rather than the internal employee culture.
-
-
13 When designing for experience, what is the primary difference between 'functional' and 'relational' interactions?
Distinguish between 'getting the job done' and 'how it feels to work together'.
Functional focus is on task completion; relational focus is on the quality of the connection.
Functional drivers relate to the utility of the service, while relational drivers relate to trust, communication, and empathy.
-
✗ Functional interactions are human-to-human, while relational are machine-to-machine.
Functional interactions are often machine-based, and relational interactions often involve human sentiment or trust.
-
✗ Functional interactions occur only in the 'Design' phase of the lifecycle.
Both types of interactions occur across the entire lifecycle, from Discovery to Support.
-
✗ Relational interactions are always automated to ensure consistency.
Automation often struggles with the empathy required for high-quality relational interactions.
-
-
14 An organization is implementing AI to handle first-level support. Which element of the '6C AI governance model' is most critical for ensuring that users can understand how the AI reached a specific decision?
Think about the term for having knowledge or awareness of internal processes.
Cognizance
Cognizance (or transparency/explainability) relates to the clarity and openness of how the AI functions and makes decisions.
-
✗ Control
Control focuses on the ability to direct or intervene in AI operations.
-
✗ Compliance
Compliance refers to meeting regulatory and legal requirements.
-
✗ Capability
Capability refers to the technical power and skills required to run the AI.
-
-
15 Why is 'psychological safety' mentioned as a core enabler of continual experience improvement?
Consider what is needed for people to be honest about mistakes or poor results.
It allows employees to report experience frictions and failures without fear of reprisal.
Without psychological safety, the 'Notice' phase of improvement fails because people hide problems or data.
-
✗ It ensures that the technology never fails during a service journey.
Psychological safety is a human cultural factor, not a technical reliability metric.
-
✗ It is a legal requirement under AI governance frameworks.
While related to ethics, it is primarily a cultural enabler for improvement, not a specific legal mandate.
-
✗ It automatically converts narrative signals into numerical data.
Psychological safety involves human trust, not automated data conversion.
-
-
16 In the Service Journey Model, 'anti-patterns' are common mistakes that harm experience. Which of the following is a provider-side anti-pattern during the 'Operate' stage?
Look for a provider behavior that ignores the human perspective of service stability.
Prioritizing internal technical metrics over the actual user impact of a failure.
Focusing on 'green' system metrics while the user experience is 'red' is a classic provider-side operational friction.
-
✗ Scope creep in user requirements.
This is typically a consumer-side or design-phase issue rather than a provider-side operational anti-pattern.
-
✗ Users bypassing the official service desk.
This is a consumer behavior anti-pattern, though it may be triggered by provider failures.
-
✗ Over-funding a project during the Acquire phase.
This relates to the Acquire activity, not the Operate stage of the journey.
-
-
17 Which tier of experience data typically includes narrative signals like customer comments, social media posts, and open-ended survey responses?
Identify the data level that captures feelings and opinions.
Tier 2: User Sentiment Data
Tier 2 data focuses on how users feel, often captured through qualitative narrative signals.
-
✗ Tier 1: System and Operational Data
Tier 1 data consists of objective, numerical technical metrics like uptime or latency.
-
✗ Tier 3: Business Outcome Data
Tier 3 data measures the high-level impact on the organization, such as revenue or market share.
-
✗ Tier 4: Environmental Data
There is no 'Tier 4' in the standard ITIL three-tier data model for experience.
-
-
18 When mapping a service journey, why is it important to distinguish between the 'User' and the 'Customer Sponsor'?
Consider who uses the tool versus who holds the budget.
They may have conflicting trust requirements and experience priorities.
A user might prioritize ease of use, while a sponsor might prioritize cost-efficiency or regulatory compliance.
-
✗ The User pays for the service, while the Customer Sponsor only uses it.
It is usually the opposite; the sponsor provides funding, while the user interacts with the service.
-
✗ The Customer Sponsor is always a third-party vendor.
The sponsor is a consumer-side role within the customer organization.
-
✗ ITIL (Version 5) considers them the same role for experience mapping.
ITIL explicitly differentiates these roles to highlight consumer-side tensions.
-
-
19 The ITIL Experience Model highlights 'Anticipation' as a key element. How can a service provider best manage a user's anticipation during the 'Deliver' activity?
Think about how you feel while waiting for a package or a software update.
By providing clear, transparent updates on service status and delivery times.
Anticipation is the pre-interaction state; managing it requires aligning the user's expectations with the upcoming reality.
-
✗ By maximizing the technical speed of the product.
Speed is functional, but anticipation is managed through communication and expectation-setting.
-
✗ By ignoring user feedback until the service is fully retired.
Ignoring feedback creates negative evaluation and destroys future anticipation.
-
✗ By automating all relational interactions to remove human error.
Relational interactions are key to managing feelings like anticipation, and automation can sometimes make them feel cold.
-
-
20 In experience management, a 'broken reflection loop' is a common friction point. This occurs when:
Think of a conversation where one person speaks and the other never listens or acts.
User feedback is collected but never used to drive service improvements.
A reflection loop is only complete when insights are fed back into the lifecycle to create change; if not, it is 'broken'.
-
✗ The database fails to replicate data to the backup server.
This is a technical failure, not an experience-led process failure.
-
✗ A user forgets their password and cannot log in.
This is a functional access issue, not a failure of the feedback and learning cycle.
-
✗ The provider sponsor refuses to fund a new project.
This is a resource constraint, though it may be a consequence of a poor reflection loop.
-
-
21 Experience Level Agreements (XLAs) differ from traditional Service Level Agreements (SLAs) because XLAs focus on:
Focus on the 'human' side of the agreement.
The value and sentiment outcomes experienced by the user.
XLAs are designed to measure and manage the human experience and the perceived value of the service.
-
✗ Technical uptime and system availability percentages.
These are the traditional focus of SLAs.
-
✗ Penalties for vendor non-compliance.
While SLAs may include penalties, XLAs focus on value and outcomes rather than punishment.
-
✗ The number of lines of code written per sprint.
This is a productivity metric, not an experience-led agreement.
-
-
22 Which activity in the Product and Service Lifecycle involves a service manager actively engaging with potential consumers to understand their unmet needs and desired outcomes?
This is the very first stage of the lifecycle.
Discover
Discover is the initial stage where the provider explores the market, user needs, and opportunities for value creation.
-
✗ Build
Building is the creation phase, occurring after the needs are understood.
-
✗ Operate
Operating is about maintaining existing services, not the initial discovery of new needs.
-
✗ Acquire
Acquiring is about obtaining specific resources once the requirements are already known.
-
-
23 A 'narrative signal' in experience management is best exemplified by which of the following?
Look for the signal that uses words to describe a situation.
A detailed email from a user explaining why a recent update was confusing.
Narrative signals are qualitative and story-based, providing depth and context that numbers cannot.
-
✗ A 99.9% uptime report.
This is a numerical signal representing operational data.
-
✗ An average CSAT score of 4.5/5.
While it measures sentiment, a score is a numerical signal, not a narrative one.
-
✗ The number of tickets closed in a single day.
This is a numerical signal representing transactional volume.
-
-
24 In the ITIL Experience Model, the concept of 'Perception' is heavily influenced by which factor?
Consider the internal human factors that change how a person sees a situation.
The user's emotional and cognitive state at the time of interaction.
Perception is subjective and is shaped by the individual's current state, past experiences, and immediate sensory input.
-
✗ The actual cost of the service infrastructure.
Cost is an organizational factor, but perception is a psychological human response.
-
✗ The programming language used to build the digital product.
This is a technical detail that is usually invisible to the user's perception of the service.
-
✗ The brand of the hardware being used.
While hardware affects performance, 'perception' in the ITIL model is about the user's holistic response to the service interaction.
-
-
25 When an organization uses the Four Dimensions as a 'governance lens' for experience, what are they essentially doing?
Think about the word 'holistic' in the context of organizational management.
Ensuring that experience improvements are balanced and supported across all four dimensions.
The lens ensures that an improvement in technology (for example) doesn't negatively impact the people or process dimensions.
-
✗ Limiting the budget for all four dimensions equally.
A governance lens is about oversight and alignment, not necessarily budget cutting.
-
✗ Using only the 'Information and Technology' dimension to measure success.
This would be a narrow technical view, the opposite of the holistic 'Four Dimensions' approach.
-
✗ Replacing the Service Value System with a dimension-based model.
The dimensions work *within* the value system; they do not replace it.
-
-
26 Which role in the provider-consumer relationship is responsible for defining the requirements and expected outcomes of a digital product from a business perspective?
Distinguish between the person using the tool and the person defining the tool's purpose.
Customer
In ITIL, the customer is the role that defines the requirements for a service and takes responsibility for the outcomes of service consumption.
-
✗ User
The user interacts with the product to achieve tasks but may not define the high-level business outcomes.
-
✗ Principal
The principal is on the provider side, representing the organization providing the service.
-
✗ Agent
The agent is the individual provider-side employee who delivers the service.
-
-
27 How does ITIL (Version 5) define 'Digital Experience'?
Focus on the internal human response described in the syllabus.
How a person feels, thinks, and bodily responds to interactions with digital products and services.
The definition focuses on the holistic human response (emotional, cognitive, and physical) to digital interactions.
-
✗ The total uptime of all digital services over a fiscal year.
This is a technical availability metric, not an experience definition.
-
✗ The number of clicks required to complete a transaction.
This is a usability metric, which is only one small part of the overall experience.
-
✗ The market share of a company's digital service portfolio.
This is a business outcome, not a definition of an individual's experience.
-
-
28 In the PSLM activity of 'Support', which type of driver is most likely to resolve a user's frustration after a functional failure has already been fixed?
Think about what is needed to make someone 'feel' better after a mistake has been corrected.
Relational driver
Relational drivers, such as empathy and communication, are needed to repair trust and address emotional responses after a failure.
-
✗ Functional driver
Functional drivers fix the technical problem, but frustration is a human sentiment that remains.
-
✗ Acquisition driver
Acquisition relates to getting resources and is not relevant to post-incident human support.
-
✗ Contextual driver
While context matters, the active resolution of user frustration is a relational task.
-
-
29 An 'Experience Level Agreement' (XLA) often utilizes 'Experience Evidence' that is 'indirect'. What is an example of indirect experience evidence?
Look for evidence that is a 'footprint' left behind by normal user activity.
Logs showing that users are repeatedly clicking a broken button before abandoning a page.
Indirect evidence is data generated as a byproduct of natural interactions, which can be interpreted to reveal experience frictions.
-
✗ A direct interview with a customer about their satisfaction.
Interviews are direct capture because the data is provided intentionally by the human for that purpose.
-
✗ A simulated bot running a script to test page load times.
This is synthetic capture, not indirect capture of actual human behavior.
-
✗ A focus group session designed to test a new prototype.
Focus groups are a form of direct capture.
-
-
30 Why does ITIL Experience emphasize the 'bodily response' in its definition of digital experience?
Think about how your body reacts when you are very angry at a slow computer.
Because physical reactions (like stress-induced heart rate increase) are real signals of experience quality.
Experience is not just intellectual; it has physical manifestations that reflect the user's stress, ease, or frustration.
-
✗ To track the physical location of users via GPS.
Location tracking is a privacy/technology issue, not related to the bodily experience of the service.
-
✗ To sell more ergonomic computer hardware.
Hardware sales are a business goal, not a core reason for the framework's human definition.
-
✗ It is a legacy term from ITIL v3 that has no current practical use.
This is a new, deliberate focus in Version 5 to reflect modern human-centered design.
-