ITIL 5 MP : ITIL Product (Domain 1)
ITIL 5 – Managing Professional : Certified ITIL Managing Professional - Domain 1 - ITIL Product (Version 5)
Introduction to Digital Product and Service Management (DPSM)
The evolution of ITIL into Version 5 represents a fundamental shift in how modern organizations perceive and deliver value. Moving beyond the traditional boundaries of IT service management, ITIL 5 introduces the concept of Digital Product and Service Management (DPSM). This paradigm shift acknowledges that in a digital-first economy, value is no longer just about the delivery of isolated services but is co-created through integrated digital products, advanced automation, and seamless connectivity.
Digital Product and Service Management establishes a common language for modern organizational practices. It recognizes that digital products are the foundational engines that power services. A digital product is characterized by its lifecycle and its ability to create value through specific service offerings. As organizations navigate an era defined by AI, data-driven decision-making, and complex ecosystems, the DPSM approach provides a structured framework to align engineering efforts with customer outcomes. This domain focuses on the design, development, and lifecycle management of these digital products, ensuring that every stage—from initial discovery to ongoing support—is geared toward maximizing value realization.
The Digital Product and Service Lifecycle Model
A core enhancement in ITIL 5 is the introduction of the ITIL Product and Service Lifecycle Model. This model provides a comprehensive structure for managing digital products from inception to retirement. Unlike linear models of the past, this lifecycle is dynamic and adaptable, reflecting the complexities of modern environments like cloud platforms and multi-provider ecosystems.
The lifecycle consists of eight primary activities that interact to create and improve products and services:
- Discover: Focusing on vision, positioning, and portfolio to identify market needs and opportunities.
- Design: Translating requirements into detailed product specifications and prototypes.
- Acquire: Obtaining the necessary technology, people, and third-party services required to realize the product.
- Build: The actual creation and integration of the product, heavily informed by design outputs.
- Transition: Moving the product from development into live environments using various deployment approaches.
- Operate: Ensuring resilient, reliable, and scalable product operations in the production environment.
- Deliver: Executing the service delivery activities that enable active value co-creation with the consumer.
- Support: Providing the necessary maintenance and assistance to resolve issues and maintain product health.
Understanding the purpose and challenges of each activity is essential for a Managing Professional. Each stage must be managed with an end-to-end perspective to avoid silos and ensure that the product roadmaps remain aligned with business strategy.
Value Co-Creation and Modern Service Relationships
The relationship between the provider and the consumer is the primary engine of value in ITIL 5. Value is not “delivered” in a one-way transaction; it is co-created through the interactions between various stakeholders. ITIL 5 expands the service relationship model to include the “Digital Product Vendor” alongside traditional roles.
Key Stakeholder Roles
- Organization: A person or group of people that has its own functions with responsibilities, authorities, and relationships to achieve its objectives.
- Service Provider: The role that provides services to consumers.
- Service Consumer: The role that receives or uses services. This is further broken down into:
- Customer: The person who defines the requirements for a service and takes responsibility for the outcomes of service consumption.
- User: The person who uses the services.
- Sponsor: The person who authorizes the budget for service consumption.
- Digital Product Vendor: A new role specializing in the provision of the digital products that underpin service offerings.
Types of Service Relationships
The nature of these relationships can vary based on the level of integration and shared objectives:
- Basic: Standardized interactions with minimal collaboration.
- Cooperative: Shared efforts to achieve specific goals.
- Collaborative (Partnership): High levels of integration where both parties work together to co-create value and share risks and rewards.
These relationships are influenced by how digital products and services are perceived. Positive experiences build trust and loyalty, while negative ones create distance and disengagement, highlighting why “experience” is a core driver of value in the modern framework.
The ITIL Value System (ITIL VS)
The ITIL Value System (ITIL VS) is the overarching framework that describes how all the components and activities of an organization work together to facilitate value creation. In Version 5, the Value System is refined to support AI-enabled, value-driven organizations.
The components of the ITIL Value System include:
- Guiding Principles: Recommendations that guide an organization in all circumstances, regardless of changes in its goals, strategies, type of work, or management structure.
- Governance: The means by which an organization is directed and controlled. In Version 5, governance is an enabling activity that ensures alignment between digital products and organizational goals.
- Service Value Chain: A set of interconnected activities that an organization performs to deliver a valuable product or service to its consumers.
- Management Practices: Sets of organizational resources designed for performing work or accomplishing an objective.
- Continual Improvement: An ongoing activity performed at all levels to ensure that an organization’s performance continually meets stakeholders’ expectations.
The ITIL VS acts as a governance lens, supporting experience improvement initiatives and ensuring that the organization remains adaptable to different contexts and maturity levels.
Managing Digital Products as Integrated Value Streams
One of the most critical skills for an ITIL Managing Professional is the ability to identify, map, and manage value streams. A value stream is the series of steps an organization undertakes to create and deliver products and services to consumers. In the context of Domain 1, managing digital products as integrated value streams means breaking down functional silos and looking at the end-to-end journey of a product.
Value Stream Mapping and Management
Value stream mapping involves documenting every activity required to take a product from “Discover” to “Support.” The purpose is to identify waste, bottlenecks, and opportunities for automation. By managing these streams holistically, organizations can ensure that the transition between lifecycle stages—such as from Build to Transition—is seamless.
Value streams integrate different lifecycle stages and management practices. For instance, an incident management practice might be a critical component of the “Support” activity within a specific value stream. Effective value stream management ensures that the resources (people, technology, partners) are optimized to deliver the specific outcome the customer desires.
Product Specification and Prototyping
In the “Design” activity of the ITIL Product and Service Lifecycle, the focus is on translating the vision identified in the “Discover” phase into a tangible plan. This involves meticulous product specification and prototyping.
The Role of Specification
Specification is the process of defining the functional and relational requirements of the digital product. This includes:
- Utility: The functionality offered by a product or service to meet a particular need (what the product does).
- Warranty: Assurance that a product or service will meet agreed requirements (how the product performs, including availability, capacity, and security).
- User Experience (UX): How a person feels and responds to interactions with the digital product.
Prototyping and Feedback loops
Prototyping allows for the creation of preliminary versions of the product to test concepts and gather early feedback. This is a vital component of the “Design” activity, as it enables “reflection loops.” These loops allow designers and stakeholders to evaluate if the product is meeting trust requirements and intended outcomes before significant resources are committed to the “Build” phase. Practical recommendations for successful design emphasize that design is not a one-time event but an iterative process that continues to inform the “Build” activity.
Design-Build Collaboration and Acquisition
The transition from planning to creation is marked by the “Build” and “Acquire” activities. In modern ITIL practices, these are rarely isolated events; they require intense collaboration between engineering teams and stakeholders.
Integration of Design and Build
The “Build” activity is where the product is actually constructed. Version 5 emphasizes that design is integrated into build activities. This means that as developers and engineers construct the digital product, they are constantly referring back to the design specifications and UX requirements. This collaboration ensures that the final product “feels as good as it functions.”
The “Acquire” Activity
Rarely does an organization build everything from scratch. The “Acquire” activity involves obtaining:
- Technology: Cloud platforms, software components, and hardware.
- People: Specialized talent or contractors.
- Third-party Services: Managed services or APIs that the product relies upon.
Managing the differences between acquiring technology and acquiring people is a key competency. The “Acquire” activity must have clear critical success factors (CSFs) and metrics to ensure that third-party components do not introduce risks to the product’s overall warranty or utility.
Continuous Integration and Delivery Pipelines
The “Transition” activity in Version 5 represents the bridge between development and live operations. In modern, high-velocity environments, this is often managed through continuous integration and continuous delivery (CI/CD) pipelines.
The “Transition” stage involves moving the built and tested product into the production environment where it can be used by consumers. There are various approaches to product transition, ranging from traditional big-bang releases to phased rollouts and automated pipelines.
Leveraging DevOps
ITIL and DevOps are complementary in the management of the product lifecycle. While DevOps provides the “ways of working”—such as automation, small batch sizes, and fast feedback—ITIL provides the structured framework to manage the service relationships and governance around those pipelines. Managing Professional Transition involves understanding how ITIL practices collaborate with DevOps to ensure that deployment is not just fast, but also reliable and compliant with organizational standards.
Operational Excellence and Resilient Support
Once a digital product is live, the focus shifts to the “Operate,” “Deliver,” and “Support” activities. These stages are where the consumer interacts most directly with the product, and where value is actively co-created.
Operating for Resilience
The “Operate” activity is concerned with the daily health of the digital product. It requires managing the infrastructure, applications, and data to ensure they perform consistently. The goal is to deliver resilient, reliable, and scalable service operations. Key concepts here include monitoring, event management, and ensuring that the product continues to meet its warranty requirements.
Delivery and Support
- Deliver: This activity focuses on the actual execution of the service. It is the moment of value realization. For a digital product, this might be the seamless functioning of an app or the successful processing of a transaction.
- Support: Support is the safety net. It involves helping users when they encounter issues and maintaining the product through updates and bug fixes. Effective support requires a deep understanding of user experience and the ability to resolve frictions—such as broken expectations or unclear agreements—that may occur in the provider-consumer relationship.
The Four Dimensions of Product Management
To ensure a holistic approach to DPSM, Managing Professionals must apply the “Four Dimensions of Product and Service Management.” These dimensions represent the perspectives required to deliver value effectively.
- Organizations and People: Focusing on roles, responsibilities, culture, and staffing levels. This dimension shapes the perceived experience of the product through the people who support it.
- Information and Technology: The data, applications, and infrastructure required. This includes the role of AI and automation in the service model.
- Partners and Suppliers: The external relationships with vendors and digital product vendors that support the product lifecycle.
- Value Streams and Processes: The workflows and activities coordinated to create value.
Version 5 introduces AI as a factor that influences all four dimensions. Managing Professionals must use these dimensions as a governance lens to support improvement initiatives, ensuring that a change in technology (Dimension 2) does not negatively impact the people (Dimension 1) or the value streams (Dimension 4).
ITIL and AI Governance in Domain 1
The inclusion of Artificial Intelligence is a defining characteristic of ITIL Version 5. AI is not just a tool; it is a fundamental component of the modern service model that affects how digital products are managed across their entire lifecycle.
AI in the Lifecycle
AI supports experience management by enabling more sophisticated experience capture and measurement. In the “Discover” and “Design” phases, AI can analyze vast amounts of data to identify consumer trends. In “Operate” and “Support,” AI-driven automation (such as AIOps) can predict failures before they happen and provide intelligent self-service options to users.
AI Governance and Ethics
With the power of AI comes the need for robust AI governance. This involves:
- Digital Ethics: Ensuring that AI adoption does not compromise human dignity or privacy.
- AI Capability Model: Understanding the organization’s maturity in managing AI-enabled services.
- Accountability: Ensuring that AI-driven decisions are transparent and that there is clear accountability for the outcomes they produce.
Governance in Version 5 is “enabling,” meaning it provides the guardrails that allow teams to innovate with AI while remaining compliant and ethical.
Continual Improvement of the Product Value System
The final piece of the ITIL 5 framework is the Continual Improvement Model. In Domain 1, this model is applied to both the “system” (the overall ITIL Value System) and the “product” itself.
The Continual Improvement Steps
- What is the vision?
- Where are we now?
- Where do we want to be?
- How do we get there?
- Take action.
- Did we get there?
- How do we keep the momentum going?
Notice – Interpret – Hypothesize – Experiment
For experience-led product management, Version 5 introduces a specific mode of improvement:
- Notice: Capture signals and evidence of experience (or lack thereof).
- Interpret: Understand what those signals mean in the context of the provider-consumer relationship.
- Hypothesize: Propose a change to improve the experience.
- Experiment: Test the change in a controlled way to see if it delivers the expected value.
This iterative approach fosters resilience and ensures that digital products continue to evolve in alignment with changing customer needs and technological advancements.
Practice Section
Short-Answer Questions
- What is the definition of a Digital Product in ITIL Version 5?
- Name the eight activities of the ITIL Product and Service Lifecycle.
- How does “Utility” differ from “Warranty”?
- What are the four dimensions of product and service management?
- What is the purpose of the “Discover” activity in the lifecycle?
- Define “Value Co-creation.”
- What is a “Value Stream”?
- List three roles on the consumer side of a service relationship.
- What is the role of a “Digital Product Vendor”?
- What is the purpose of the “Acquire” activity?
Answer Key
- Answer: A digital product is an entity characterized by its lifecycle and its ability to create value through specific service offerings.
- Answer: Discover, Design, Acquire, Build, Transition, Operate, Deliver, and Support.
- Answer: Utility refers to the functionality or “what the product does,” while Warranty refers to the assurance of performance or “how the product performs” (e.g., availability and security).
- Answer: Organizations and People; Information and Technology; Partners and Suppliers; Value Streams and Processes.
- Answer: To focus on vision, positioning, and the portfolio to identify opportunities for new or improved products.
- Answer: The process where value is created through the active collaboration and interaction between providers and consumers.
- Answer: A series of steps an organization takes to create and deliver a product or service to a consumer.
- Answer: Customer, User, and Sponsor.
- Answer: To provide the digital products that power and underpin an organization’s service offerings.
- Answer: To obtain the technology, people, and third-party services needed to develop or operate a product.
Open-Ended / Design Questions
- Value Stream Mapping: You are tasked with improving a digital product that has high user dissatisfaction. Design a plan to map the value stream for this product. Which lifecycle activities would you focus on first to identify “experience frictions”?
- AI Integration: Your organization wants to integrate a generative AI component into an existing digital product. Using the ITIL Four Dimensions, analyze the potential impact of this change. What governance considerations must be addressed?
- Design-Build Collaboration: Describe a scenario where a lack of collaboration between the “Design” and “Build” teams leads to a failure in the “Transition” phase. How would you apply the ITIL Guiding Principles to resolve this systemic issue?
- Service Relationships: Compare a “Basic” service relationship with a “Collaborative Partnership.” In which scenario is “Value Co-creation” more prominent, and what are the specific trust requirements for the provider in a partnership?
- Continual Improvement: Apply the “Notice – Interpret – Hypothesize – Experiment” model to a digital service that is experiencing frequent downtime (Operate activity). How would you use “Experience Signals” to drive this improvement?
Glossary of Key Terms
- AIOps: The application of artificial intelligence to IT operations to enhance monitoring, predictive analysis, and automation.
- Continual Improvement: An ongoing organizational activity at all levels to ensure performance meets stakeholder expectations.
- Customer: A person who defines service requirements and takes responsibility for the outcomes of consumption.
- Digital Product and Service Management (DPSM): A framework for managing the full lifecycle of digital products and the services they enable.
- Digital Product Vendor: An external or internal role that provides the digital products used to power service offerings.
- Experience Signals: Data points or evidence (emotional, cognitive, or bodily) used to evaluate how a person perceives an interaction with a product.
- Governance: The system by which an organization is directed and controlled, ensuring alignment with strategic goals.
- ITIL Product and Service Lifecycle: A model consisting of eight activities (Discover to Support) used to manage a product from inception to retirement.
- Management Practices: Sets of organizational resources designed to perform specific types of work or achieve objectives.
- Organization: A person or group with its own functions, responsibilities, and authorities to achieve objectives.
- Service Offering: A formal description of one or more services designed to address the needs of a target consumer group.
- Service Provider: An organization or role that provides services to internal or external consumers.
- Sponsor: A person who authorizes the budget for service consumption.
- Sustainability: The ability of a product, service, or organization to remain viable and provide value over the long term without compromising future resources.
- User: A person who interactively uses a service or digital product.
- User Experience (UX): The total sum of responses (feelings, thoughts, and physical reactions) a person has when interacting with a digital product.
- Utility: The functionality offered by a product or service to meet a specific need; “fit for purpose.”
- Value Co-creation: A collaborative process where providers and consumers work together to realize mutual value.
- Value Stream: A coordinated series of activities that create and deliver value to a customer.
- Warranty: Assurance that a product or service will meet agreed performance requirements; “fit for use.”
Leaderboard
No scores saved yet. Be the first!
30 Questions — ITIL 5 – Managing Professional : Certified ITIL Managing Professional - Domain 1 - ITIL Product (Version 5)
Expand any question to reveal the correct answer and explanation.
-
1 An organization is transitioning its operating model to align with ITIL 5. Which specific structural change represents the shift from the ITIL 4 Service Value Chain to the ITIL (Version 5) Product and Service Lifecycle Model (PSLM)?
Consider the number of stages involved in the new unified end-to-end lifecycle model.
The replacement of six linear value chain activities with eight integrated, non-linear lifecycle stages.
ITIL 5 evolves the six-activity Service Value Chain into an eight-stage Product and Service Lifecycle Model to reflect the inseparable nature of digital products and services.
-
✗ The expansion of the four dimensions into a five-pillar framework including Artificial Intelligence.
While AI is integrated throughout the framework, the Four Dimensions remain the core holistic structure rather than expanding to a fifth pillar.
-
✗ The consolidation of 34 management practices into three specific product-centric categories.
ITIL 5 reorganizes practices into two groups (Product and Service management and General management) rather than three categories.
-
✗ The transition from a Service Value System (SVS) to a Digital Product Delivery System (DPDS).
The SVS is updated and refined into the ITIL Value System (IVS), not a Digital Product Delivery System.
-
-
2 During the 'Discover' activity of the Product and Service Lifecycle Model, what is the primary focus for a product team utilizing 'Strategic Discovery'?
This stage occurs at the very beginning of the lifecycle and involves identifying what should be created.
Prioritizing the product backlog and shaping roadmaps based on customer opportunities.
The Discover stage focuses on identifying opportunities, understanding customer needs, and prioritizing the backlog to shape the product's direction.
-
✗ Conducting empathy mapping and iterative prototyping to refine the user interface.
Empathy mapping and prototyping are primary concerns of the 'Design' activity rather than 'Discover'.
-
✗ Establishing telemetry frameworks to monitor system state during the initial launch.
Telemetry and monitoring are critical components of the 'Transition' and 'Operate' activities.
-
✗ Coordinating zero-downtime deployments with site reliability engineering constructs.
Deployment coordination is a technical task associated with 'Build' and 'Transition' stages.
-
-
3 In the context of ITIL 5 Product management, how is a 'Digital Product' distinctively defined compared to a traditional 'Service'?
Think about how ITIL 5 views the 'packaging' of technology capabilities.
Products are viewed as integrated value streams that act as technological containers for capabilities.
ITIL 5 defines digital products as integrated value streams and containers of capabilities, whereas services are the operational vehicles for value realization.
-
✗ Products are intangible outcomes while services represent physical goods transferred to consumers.
Services are generally intangible; digital products often encompass both software and the infrastructure supporting them.
-
✗ Products only create value upon transfer of ownership, while services create value through shared access.
Digital products in ITIL 5 create value through co-creation across their full lifecycle, not just at transfer.
-
✗ Services follow a rigid eight-stage lifecycle while products utilize a flexible four-dimension model.
Both products and services are managed via the eight-stage PSLM and governed through the Four Dimensions.
-
-
4 A product team is evaluating whether to develop a machine-learning module internally or utilize a third-party API. In which stage of the Product and Service Lifecycle Model does this 'Resource and Supplier Orchestration' primarily reside?
This activity involves making the 'buy vs. build' decision and managing the procurement of components.
Acquire
The Acquire activity specifically deals with sourcing, evaluating vendors, and obtaining components or services needed for the product.
-
✗ Design
Design focuses on creating the solution architecture rather than the act of sourcing or building the components.
-
✗ Build
Build focuses on the internal development and configuration of the product once resources are acquired.
-
✗ Transition
Transition involves moving the built product into the live operational environment.
-
-
5 Which concept in ITIL 5 focuses on mitigating user anxiety during machine-driven service interactions to ensure psychological safety?
Look for a term that combines technological advancement with user cognitive and emotional responses.
AI and Human Perception
The ITIL Experience module emphasizes managing how users perceive and respond to AI to maintain trust and psychological safety.
-
✗ AI Governance and Ethics
Governance focuses on oversight and accountability; human perception management is more specific to the experience domain.
-
✗ Cognitive Load Management
This is a general design principle but not a specific ITIL 5 term for managing emotional responses to AI.
-
✗ Human-Centred Design
While related, this is the broader methodology used to apply empathy, not the specific focus on AI-driven anxiety.
-
-
6 When mapping experience signals across a service journey, which of the following represents a 'Relational' experience driver as opposed to a 'Functional' one?
Focus on the interpersonal and emotional aspects of the service connection.
The level of trust and psychological safety felt during a provider interaction.
Relational drivers focus on the quality of the interaction and the bonds formed between the consumer and provider.
-
✗ The speed and reliability of a digital interface's response time.
Performance metrics like speed are functional drivers focused on utility.
-
✗ The availability of a specific feature within a software application.
Feature availability is a functional aspect of the product's design.
-
✗ The accessibility of technical support documentation.
Accessibility of resources is generally a functional or operational driver.
-
-
7 In ITIL 5, the integration of software development and operations is largely enabled by aligning the framework with which external methodology?
Think about modern approaches to building and running high-availability software.
DevOps and Site Reliability Engineering (SRE)
ITIL 5 explicitly aligns its product and service lifecycle activities with DevOps principles and SRE constructs for operational reliability.
-
✗ PRINCE2
PRINCE2 is used for project management alignment, not specifically for integrating dev and ops.
-
✗ Six Sigma
Six Sigma focuses on process improvement and waste reduction rather than technical dev-ops integration.
-
✗ COBIT
COBIT is a governance framework that ITIL 5 can align with, but it is not the primary driver for dev-ops integration.
-
-
8 An ITIL 5 Managing Professional is tasked with 'Technical Debt Governance'. In which activity of the Product and Service Lifecycle Model is this most likely to be embedded?
This relates to the ongoing health and architecture of the product during its creation and configuration.
Build
Quality engineering and technical debt governance are core components of the Build activity to ensure long-term system health.
-
✗ Support
Support focuses on resolving incidents and maintaining quality, though technical debt might be identified here, its governance belongs in build.
-
✗ Retire
Retire involves decommissioning products rather than governing their development quality.
-
✗ Discover
Discover is about opportunity identification, not the technical management of code quality.
-
-
9 According to the ITIL 5 structure, what replaces the 'Service Value Chain' from ITIL 4 within the updated ITIL Value System (IVS)?
Identify the eight-stage model that now defines how value is created.
The Eight Lifecycle Activities of the PSLM
The eight stages of the Product and Service Lifecycle Model are the operational activities within the IVS, replacing the six SVC activities.
-
✗ The Digital Value Stream Map
Value Stream Mapping is a practice used within the model, not the replacement for the chain itself.
-
✗ The Service Journey Model
The Service Journey Model is an additional tool used to understand experience, not a direct replacement for value chain activities.
-
✗ The 6C AI Governance Model
The 6C model is a specific governance lens for AI, not a holistic replacement for the value chain.
-
-
10 A team is using the 'Notice – Interpret – Hypothesize – Experiment' cycle. Which core ITIL 5 concept are they applying to drive improvement?
This cycle is used to translate qualitative signals into actionable experiments.
Continual Experience Improvement Modes
ITIL 5 introduces these four modes specifically for driving the continual improvement of stakeholder experiences.
-
✗ The Seven Guiding Principles
While aligned with 'Progress Iteratively,' this specific four-step cycle is distinct to experience improvement.
-
✗ Value Stream Management
Value stream management focuses on flow and bottleneck removal rather than this specific feedback cycle.
-
✗ AI Maturity Mapping
AI maturity mapping assesses technical capabilities rather than a qualitative improvement loop.
-
-
11 Which of the following is identified as a 'Technical Management Practice' in the ITIL (Version 5) Foundation syllabus?
Look for the practices focused on the hands-on engineering aspects of product delivery.
Deployment management
Technical Management Practices specifically include deployment management and software development/management.
-
✗ Incident management
Incident management is categorized as a Service Management Practice.
-
✗ Strategy management
Strategy management is categorized as a General Management Practice.
-
✗ Service level management
Service level management is a Service Management Practice.
-
-
12 The ITIL 5 framework is described as 'Complexity-native'. What does this imply for organizations operating in a 'VUCA' world?
Think about how a framework should behave when the future is unpredictable and volatile.
ITIL supports experimentation to find direction rather than just executing fixed plans.
Being complexity-native means ITIL acknowledges the volatile nature of modern business and encourages experimentation to navigate it.
-
✗ The framework provides rigid, predefined plans that must be executed without variation.
Complexity-native design explicitly moves away from rigid plans in favor of experimentation.
-
✗ Organizations should focus primarily on automating simple tasks to reduce human error.
While automation is key, complexity-native design focuses on navigating unclear environments.
-
✗ The four dimensions are replaced by a single complexity dimension for all products.
The Four Dimensions are maintained and enhanced to handle complexity, not replaced.
-
-
13 What is the primary distinction between 'Value Stream Mapping' and 'Value Stream Management' in ITIL 5?
Consider the difference between drawing a diagram and running an operation.
Mapping is the visualization of the current state, while Management is the ongoing optimization of flow and outcomes.
Mapping is a technique for visibility, while management is the discipline of governing and improving those streams over time.
-
✗ Mapping is for technical teams, while Management is reserved for executive leadership.
Both involve cross-functional teams; the difference lies in the activity, not the organizational level.
-
✗ Mapping focuses on AI-enabled streams, while Management focuses on legacy services.
Both concepts apply equally to all types of digital products and services.
-
✗ Mapping is a one-time activity, while Management occurs only during the Retire stage.
Management is a continual lifecycle activity, not restricted to the Retire stage.
-
-
14 An organization is using 'XLAs' to supplement their existing 'SLAs'. What is the primary purpose of this change?
Think about the limitations of 'watermelon' metrics that look green on the outside but feel red to the user.
To measure and manage qualitative signals that standard performance metrics often miss.
Experience Level Agreements (XLAs) capture human-centered signals like trust and sentiment to supplement functional SLAs.
-
✗ To increase the technical performance requirements of cloud infrastructure.
XLAs focus on qualitative experience rather than increasing raw technical performance.
-
✗ To automate the renewal process of multi-supplier service contracts.
XLAs are not about contract automation; they are about experience measurement.
-
✗ To provide a legal framework for the transfer of physical goods.
XLAs focus on the 'feel' and 'value' of the interaction, not the legalities of goods transfer.
-
-
15 In the ITIL (Version 5) Product and Service Lifecycle Model, which activity is specifically responsible for the decommissioning and safe removal of digital products?
This is the final stage of the unified lifecycle.
Retire
Retire is the final stage of the PSLM, dedicated to decommissioning and safely removing products and services.
-
✗ Support
Support maintains and fixes products while they are live.
-
✗ Optimize
Optimize focuses on continuous improvement of performance for existing products.
-
✗ Transition
Transition involves moving products into live use, not out of it.
-
-
16 Which of the following is NOT one of the 'Four Dimensions' of product and service management retained in ITIL 5?
Three of these have been core to ITIL for years; one is a new focus area integrated into an existing dimension.
Artificial Intelligence and Automation
While critical in ITIL 5, AI and automation are handled within 'Information and Technology' rather than being a standalone fifth dimension.
-
✗ Value Streams and Processes
This is one of the four dimensions focusing on the flow of activities.
-
✗ Information and Technology
This dimension focuses on data management and digital infrastructure.
-
✗ Partners and Suppliers
This dimension manages the ecosystem of external providers.
-
-
17 When ITIL 5 states that it is 'AI-native by design', what is the intended meaning for its practices and value streams?
Consider how a framework might be built if AI was already a common reality rather than an afterthought.
Practices and workflows are structured so AI can be naturally integrated to enhance decision-making.
AI-native means the framework was built with the assumption that AI would be part of the infrastructure to predict and automate outcomes.
-
✗ Every practice must be fully automated without human intervention.
ITIL 5 emphasizes human-centered design alongside AI, not the total removal of humans.
-
✗ AI is a standalone practice that operates independently of the value chain.
AI is integrated into every stage of the lifecycle and across practices.
-
✗ Only organizations with a high AI maturity score are allowed to use ITIL 5.
ITIL 5 is applicable to organizations of all sizes and maturity levels.
-
-
18 A product owner is analyzing the 'Total Cost of Ownership' and 'Technical Debt' of a new digital product. According to the ITIL 5 Managing Professional guidance, these activities help achieve which mindset?
This mindset involves looking at a product from its initial concept all the way through its retirement.
The lifecycle mindset
The lifecycle mindset enables smarter decisions across the full product lifespan, including managing debt and continuity.
-
✗ The collaborative mindset
The collaborative mindset focuses on transparency and cross-team alignment.
-
✗ The growth mindset
Growth mindset is associated with the continuous improvement mindset.
-
✗ The AI-native mindset
AI-native refers to the technological readiness of the framework itself.
-
-
19 Within the ITIL Value System, which component is specifically responsible for ensuring that the organization's activities are aligned with strategic objectives and ethical standards?
This component provides the 'guardrails' and direction for the entire organization.
Governance
Governance ensures that the organization is directed and controlled, enabling compliance and strategic alignment.
-
✗ Management Practices
Management practices are the sets of organizational resources for performing work.
-
✗ Continual Improvement
Continual improvement focuses on the recurring activity of enhancing performance.
-
✗ Value Chain
The value chain is the set of activities used to create products.
-
-
20 An organization experiences a conflict between the 'Product Manager' and the 'Service Delivery Manager' regarding resource allocation. How does ITIL 5 recommend resolving this structural tension?
The solution involves a 'unified' approach that bridges the gap between different teams.
By following the Product and Service Lifecycle Model to establish a shared language and unified value streams.
The PSLM is designed to integrate product and service communities to prevent the silos that create such tensions.
-
✗ By prioritizing the Product Manager's roadmap as they are the 'Principal' in the relationship.
ITIL 5 focuses on co-creation and balance rather than defaulting to one role's dominance.
-
✗ By outsourcing the service delivery to a third-party vendor to simplify internal roles.
Outsourcing doesn't necessarily solve structural tension and may introduce more complexity.
-
✗ By eliminating the Service Delivery role in favor of an 'AI Governance Manager'.
Service management roles are still vital; they are simply more integrated into the product lifecycle.
-
-
21 Which of the following is a new stage introduced in the ITIL 5 PSLM that was not explicitly a separate activity in the ITIL 4 Service Value Chain?
Think about the very first step added to ensure customer needs are truly understood before development.
Discover
Discover is a new explicit activity in the PSLM focused on initial opportunity and need identification.
-
✗ Deliver
Deliver was part of 'Deliver and Support' in ITIL 4.
-
✗ Design
Design was part of 'Design and Transition' in ITIL 4.
-
✗ Improve
Improve was a core SVC activity in ITIL 4.
-
-
22 When defining the 'Service Journey' in the ITIL Experience module, what is the primary focus of 'Anticipation'?
This happens before the person even begins the actual service interaction.
How a person feels and thinks before they interact with a digital service.
Anticipation covers the mindset and expectations of the user before the actual interaction takes place.
-
✗ The user's retrospective evaluation of whether value was achieved.
Retrospective evaluation is part of the 'Evaluation' phase.
-
✗ The real-time sensory perception of the interface during use.
Sensory response occurs during the 'Perception' phase.
-
✗ The technical latency of the system before the user logs in.
Technical latency is a functional metric, not a psychological stage of the experience journey.
-
-
23 In the ITIL 5 'Acquire' stage, what is a primary challenge when acting as a 'Digital Product Vendor'?
Think about the complexities of dealing with external sources for your product's parts.
Orchestrating multi-supplier agreements and evaluating cloud component interoperability.
Sourcing and acquiring third-party components involves significant challenges in orchestration and technical compatibility.
-
✗ Managing the emotional response of the internal development team.
While important, this is more related to internal 'Build' or 'Organizations and People' dynamics.
-
✗ Conducting empathy mapping for the end-user base.
Empathy mapping is a design challenge, not an acquisition challenge.
-
✗ Decommissioning legacy software after the new product launch.
This belongs to the 'Retire' activity.
-
-
24 How does ITIL 5 view the relationship between 'Sustainability' and 'Value Co-creation'?
Consider how high-performing organizations treat environmental and social responsibility today.
Sustainability is a core component that contributes to how value is co-created and perceived.
ITIL 5 incorporates sustainability into the fundamental definition of service quality and value co-creation.
-
✗ Sustainability is a secondary objective that should only be pursued if costs are low.
Sustainability is built into the core framework and contributes directly to long-term value.
-
✗ Sustainability only refers to the energy efficiency of data centers.
Sustainability in ITIL 5 covers environmental, social, and economic factors in the digital lifecycle.
-
✗ Value co-creation is purely financial, while sustainability is purely ethical.
ITIL 5 breaks down these silos, viewing sustainability as a factor in the overall 'value' of the service.
-
-
25 A team is implementing 'Site Reliability Engineering (SRE)' to manage their digital product. Which lifecycle activity are they primarily enhancing?
SRE focus on ensuring that a live system stays running and recovers from failure automatically.
Operate
SRE constructs like error budgets and automated healing are primarily utilized during the 'Operate' activity to ensure reliability.
-
✗ Design
Design sets the plan, but SRE is about live reliability and operations.
-
✗ Discover
Discover is about market needs, not system reliability management.
-
✗ Acquire
Acquire is about sourcing, not live system operations.
-
-
26 In the ITIL 5 Experience Model, the 'Evaluation' of an interaction is influenced by which of the following?
Consider the human factors that determine how someone judges an experience after it happens.
The user's emotional, cognitive, and bodily state, both past and present.
Evaluation is a psychological process shaped by the user's personal state and context, not just the system's performance.
-
✗ Only the raw technical uptime of the system during the session.
Evaluation is subjective and goes beyond raw uptime to include perception and expectations.
-
✗ The total number of service interactions logged in the CRM system.
Quantity of interactions is an operational metric, not a psychological driver of evaluation.
-
✗ The initial cost of the product at the time of purchase.
Cost is a factor, but evaluation refers to the psychological response to the interaction itself.
-
-
27 What is the primary goal of the 'Transition' activity in the Product and Service Lifecycle Model?
This stage bridges the gap between the internal 'Build' environment and the live user environment.
To coordinate zero-downtime deployments and establish system observability.
Transition focuses on moving the product into the live environment with minimal disruption while ensuring telemetry is active.
-
✗ To identify new market opportunities for a future product iteration.
Market opportunities are identified during the 'Discover' stage.
-
✗ To resolve hardware incidents during peak usage hours.
Ongoing incident resolution is part of 'Support' and 'Operate'.
-
✗ To finalize the service relationship agreements with cloud providers.
Finalizing agreements is typically handled in 'Acquire' or 'Design'.
-
-
28 An organization adopts ITIL 5 to 'break down silos between IT, product, and business teams'. This is primarily achieved through which mindset?
Think about the term that emphasizes working together as a single unit.
The collaborative mindset
The collaborative mindset is explicitly designed to improve collaboration across roles and promote transparency through unified value streams.
-
✗ The continuous improvement mindset
Continuous improvement focuses on performance gains rather than structural alignment.
-
✗ The growth mindset
Growth mindset refers to individual or team learning rather than structural integration.
-
✗ The complexity mindset
Complexity-native thinking handles uncertainty but doesn't specifically define the cross-team collaboration model.
-
-
29 In ITIL 5, the 34 management practices are organized into two groups. What are they?
Look for the groups that distinguish between specific delivery disciplines and general organizational capabilities.
Product and Service Management practices and General Management practices
ITIL 5 organizes all 34 practices into these two specific groups to ensure alignment with digital product/service delivery.
-
✗ IT Management Practices and Business Management Practices
This distinction is too broad; the framework uses more specific digital-centric terminology.
-
✗ Technical Management practices and Operational Management practices
These were sub-categories in ITIL 4, but the top-level organization has changed in Version 5.
-
✗ Value Chain practices and Lifecycle practices
These are concepts within the system, not the name of the two practice groups.
-
-
30 A product team is analyzing 'Waste Reduction' and 'Flow Optimization'. Which ITIL 5 methodology are they most likely applying?
This methodology is borrowed from Lean and focuses on the end-to-end efficiency of the work process.
Value Stream Mapping and Management
Value Stream Mapping is used to identify bottlenecks and waste, while management optimizes the flow of activities to create value.
-
✗ AI Governance Framework
AI governance focuses on ethics and risk, not specifically on operational flow waste.
-
✗ The PSLM Discover stage
Discover is about needs and opportunities; optimization occurs later during the management of the live streams.
-
✗ The Experience Service Journey
The service journey focuses on user perception, not operational waste in the production process.
-