Skip to content

ITIL 5 Foundation : Value Stream Identification (Domain 5)

ITIL 5 – Foundation : Certified ITIL Foundation - Domain 5 - Value Stream Identification, Mapping, and Management

30 questionsmedium

This comprehensive study guide is designed to prepare candidates for the ITIL 5 Foundation examination, specifically focusing on Domain 5: Value Stream Identification, Mapping, and Management. In the ITIL 5 framework, value stream management has evolved into a critical competency for Digital Product and Service Management (DPSM). This domain emphasizes flow-based thinking, the elimination of operational waste, and the optimization of work sequences to ensure that organizational resources are converted into value as efficiently as possible.


1. Introduction to Value Stream Management in ITIL 5

The transition from ITIL 4 to ITIL 5 represents a shift from traditional IT Service Management (ITSM) to a paradigm focused on the entire lifecycle of digital products. A central pillar of this new architecture is the ability to identify, map, and manage value streams. Domain 5 accounts for 5% of the Foundation exam, focusing on the systemic coordination of resources to optimize throughput and minimize delays.

Value stream management is the practice of eliminating waste, optimizing the flow of work, and mapping the sequences required to deliver a product or service. This requires a holistic view of the organization, integrating the “Four Dimensions” (Organizations and People, Information and Technology, Partners and Suppliers, and Value Streams and Processes) to ensure that activities are structured for maximum efficiency.

Syllabus FocusLearning Outcome
Flow-Based ThinkingUnderstanding work as a continuous movement toward value.
Stream ClassificationDistinguishing between core and enabling value streams.
Metric CalculationMeasuring performance through Lead Time and Flow Efficiency.
Mapping TechniquesVisualizing the flow of code, data, and metadata.

2. The Philosophy of Flow-Based Thinking

Flow-based thinking is a fundamental concept in ITIL 5 that encourages professionals to view work as a continuous sequence of activities rather than isolated tasks. This approach is rooted in Lean methodology, which focuses on optimizing processes by eliminating waste and enhancing value delivery.

Key Tenets of Flow:

  • Continuity: Work should move through the Product and Service Lifecycle Model (PSLM) without unnecessary pauses or handoffs.
  • Visibility: All stakeholders must be able to see the state of the value stream to identify where bottlenecks occur.
  • Throughput Optimization: The goal is to maximize the speed at which a request or idea moves from the “Discover” activity to the “Support” activity.

In the high-velocity environments of Industry 5.0, flow-based thinking helps eliminate organizational friction. By treating development and operations as a single, continuous stream, organizations can reduce the “historic division” that previously caused delays in product creation and operational support.

3. Core vs. Enabling Value Streams

ITIL 5 categorizes value streams into two distinct types to help organizations better allocate resources and define accountability.

Core Value Streams

Core value streams are the primary sequences of activities that deliver value directly to an external customer or user. These streams are the “revenue-generating” or “mission-critical” paths of the organization. Examples include the end-to-end process of developing a new software feature, processing a customer order, or restoring service after a major incident.

Enabling Value Streams

Enabling value streams provide the internal support and resources necessary for core value streams to function. While they do not deliver value directly to the final customer, they are essential for organizational stability and efficiency.

  • Examples: Employee onboarding, IT infrastructure provisioning, and internal knowledge management.
  • Strategic Importance: Without efficient enabling streams, core value streams eventually stall due to a lack of resources, data, or technical support.

4. Mapping Digital Artifact Flow: Code, Data, and Metadata

In a digital-first environment, value streams are often composed of the movement of digital artifacts. Mapping these flows is essential for identifying technical debt and operational silos.

The Three Flows of Mapping:

  1. Code Flow: This represents the journey of software from the “Build” activity through “Transition” and into “Operate.” Mapping code flow involves understanding CI/CD (Continuous Integration/Continuous Delivery) pipelines and ensuring that deployment management practices do not introduce bottlenecks.
  2. Data Flow: This involves the movement of raw information through the value stream. Data must be ingested, processed, and analyzed to drive decisions. ITIL 5 emphasizes data governance within these streams to prevent “garbage-in, garbage-out” scenarios.
  3. Metadata Flow: Often overlooked, metadata (data about data) is critical for observability. It includes audit logs, configuration item (CI) relationships in the CMDB, and version control details. Mapping metadata flow ensures that the system remains governable and transparent.

5. The Product and Service Lifecycle Model (PSLM) as a Stream Template

The PSLM replaces the linear Service Value Chain of previous versions with an eight-activity model that serves as the backbone for value stream mapping. These activities are non-linear “stepping stones” that allow teams to move fluidly based on feedback loops.

PSLM ActivityRole in the Value Stream
DiscoverIdentifying demand and verifying feasibility.
DesignModeling the user experience and service parameters.
AcquireSecuring resources, licenses, or cloud infrastructure.
BuildCompiling code and configuring systems.
TransitionDeploying releases and managing operational risk.
OperateMonitoring system health and site reliability.
DeliverCoordinating active value co-creation during use.
SupportAddressing incidents and gathering improvement feedback.

Value stream mapping involves tracing a specific request (e.g., “A user needs a new analytics dashboard”) through these eight activities to identify every step required to fulfill that request.

6. Identifying Operational Delays and Waste

A primary goal of Domain 5 is the identification of “non-value-added” steps. In Lean and ITIL 5 terminology, this is known as identifying waste.

Common Sources of Delay:

  • Excessive Handoffs: Moving work between departments (e.g., from Development to QA to Operations) often results in “wait time” where the work sits idle.
  • Over-Processing: Performing steps that the customer does not value or that do not improve the quality of the digital product.
  • Siloed Data: When information is trapped in business units, teams must wait for manual transfers, stalling the value stream.
  • Shadow IT/AI: The adoption of tools without formal review creates “hidden” value streams that are unmonitored and introduce risk.

Mapping out these processes allows companies to eliminate non-value-added steps, reduce cycle times, and improve overall efficiency.

7. Measuring Performance: Lead Time and Flow Efficiency

To manage a value stream effectively, it must be measured. ITIL 5 focuses on two primary metrics for flow-based performance.

Lead Time

Lead Time is the total elapsed time from the moment a request is identified (the “Discover” activity) until the value is delivered to the customer (the “Deliver” or “Support” activity).

  • Calculation: End Time - Start Time.
  • Objective: Organizations aim to reduce Lead Time to increase agility and responsiveness.

Flow Efficiency

Flow Efficiency is a ratio that compares the time spent actively working on a task (“Active Time”) to the total Lead Time.

  • Calculation: (Active Work Time / Total Lead Time) x 100.
  • Example: If a software update takes 10 days to deliver (Lead Time), but engineers only spent 2 days actually coding and testing (Active Time), the Flow Efficiency is 20%.
  • Insight: A low Flow Efficiency score indicates that work is spending most of its time waiting in queues or handoffs, highlighting a need for process optimization.

8. The Live ‘Value Stream Walk’

The “Value Stream Walk” (often referred to in Lean as a Gemba Walk) is an observational technique used in ITIL 5 to validate that the mapped process matches reality.

Purpose and Execution:

The Value Stream Walk involves leaders and practitioners literally or virtually “walking” through the steps of a process as they occur in real-time. Instead of relying on dashboards or reports, observers engage with the people performing the work.

  • Identify Friction: See where tools are failing or where staff are resorting to manual workarounds.
  • Verify Compliance: Ensure that governance and safety controls are actually being used.
  • Build Trust: Demonstrate that management is interested in the operational realities of the team.

This practice is essential for “Starting where you are,” one of the ITIL Guiding Principles, as it prevents the design of value streams based on idealized but inaccurate assumptions.

9. Decision-Making Contexts: Ordered, Complex, Chaotic, and Confused

Value streams do not exist in a vacuum. ITIL 5 integrates complexity theory to help practitioners understand how to manage streams based on the environment.

The Four Contexts:

  1. Ordered (Clear/Complicated): The relationship between cause and effect is known. Value streams in this context can be standardized and automated (e.g., standard service requests like password resets).
  2. Complex: Cause and effect can only be understood in retrospect. These streams require experimentation and iterative progress (e.g., developing a brand-new AI capability).
  3. Chaotic: There is no relationship between cause and effect. The priority is to “Act-Sense-Respond” to establish order (e.g., during a major, unprecedented system outage).
  4. Confused (Disorder): The context is unknown, and stakeholders are using different decision-making models. The goal is to break the situation down into parts to move them into the other three domains.

Understanding these contexts prevents the mistake of applying “best practices” (appropriate for Ordered) to “Complex” problems where “emergent practices” are required.

10. Integrating AI and Modern Frameworks into the Value Stream

As organizations adopt Industry 5.0 principles, the value stream must integrate AI as an active partner. The 6C AI Capability Model provides a structured way to classify how AI assists value stream flow:

  • Creation: Generating artifacts (code, documentation) to speed up the “Build” activity.
  • Curation: Filtering alerts to reduce noise in “Operate.”
  • Clarification: Translating technical logs into business updates for “Support.”
  • Cognition: Predicting incident severity to optimize “Incident Management” flow.
  • Communication: Interacting with users via virtual assistants in the “Service Desk.”
  • Coordination: Automating routing and workflow orchestration.

Furthermore, value stream management in ITIL 5 is designed to be interoperable with DevOps (for continuous delivery pipelines), Agile (for iterative cycles), and Lean (for waste elimination).


11. Practice and Assessment

Short-Answer Questions

Answers are provided in the key following this section.

  1. What is the primary difference between a core value stream and an enabling value stream?
  2. How is Flow Efficiency calculated in an ITIL 5 context?
  3. Define “Lead Time” as it relates to a digital product request.
  4. Which PSLM activity focuses on verifying the feasibility of a customer demand?
  5. What is the purpose of the 6C AI Capability Model in a value stream?
  6. How does a “Value Stream Walk” improve organizational governance?
  7. In complexity theory, how does a “Complex” context differ from an “Ordered” one?
  8. What are the three types of digital artifact flows that should be mapped in a value stream?
  9. What ITIL Guiding Principle is most closely related to the practice of a Value Stream Walk?
  10. Why is “wait time” considered waste in value stream management?

Answer Key

  1. Answer: A core value stream delivers value directly to external customers, while an enabling value stream supports the internal capabilities required to maintain core operations.
  2. Answer: Flow Efficiency is calculated by dividing the time spent on active work by the total lead time, then multiplying by 100.
  3. Answer: Lead Time is the total elapsed time from the initial identification of a request until the final value is delivered to the consumer.
  4. Answer: The “Discover” activity focuses on identifying customer demands and verifying feasibility before capital is invested.
  5. Answer: The 6C model classifies AI capabilities (Creation, Curation, etc.) to help organizations understand how AI can optimize specific activities within a value stream.
  6. Answer: It provides live, observational evidence of how work is actually performed, allowing leaders to identify friction points and verify that controls are effective.
  7. Answer: In an Ordered context, cause and effect are known and predictable; in a Complex context, cause and effect can only be understood in retrospect through experimentation.
  8. Answer: The three types of flows are code flow (software movement), data flow (information processing), and metadata flow (observability and governance data).
  9. Answer: “Start where you are” is most relevant, as it emphasizes observing the current reality before making changes.
  10. Answer: Wait time is considered waste because it represents a period where no value is being added to the product despite the Lead Time clock continuing to run.

Open-Ended Design Questions

These questions are intended for deep reflection or group discussion. No answers are provided.

  1. Design a Value Stream: Map the value stream for a “High-Priority Software Bug Fix.” Identify which PSLM activities are involved and where the most likely “wait times” would occur in a traditional siloed organization.
  2. AI Integration Scenario: Select three of the “6C” AI capabilities and explain how they could be used to specifically improve the Flow Efficiency of a “New Employee Onboarding” enabling value stream.
  3. Complexity Analysis: Describe a recent major IT incident your organization faced. Categorize it using the complexity contexts (Ordered, Complex, Chaotic, Confused) and explain how the value stream for “Incident Management” changed during the crisis.
  4. Metric Application: You discover a core value stream has a Lead Time of 30 days but a Flow Efficiency of only 5%. Propose three specific changes to the “Four Dimensions” to address this efficiency gap.
  5. Governance Mapping: Explain how “Metadata Flow” supports the “Regulatory Compliance” perspective of AI Governance. What happens to the value stream if metadata is not accurately captured during the “Build” and “Transition” activities?

12. Glossary of Key Terms

  • 6C Model: A framework for classifying AI capabilities: Creation, Curation, Clarification, Cognition, Communication, and Coordination.
  • Active Time: The duration during which a resource is actively working on completing a specific task within a value stream.
  • AI Governance Model: A four-perspective framework (Decision Authority, Ethics, Data Governance, Regulatory Compliance) used to ensure AI is adopted responsibly.
  • Artifact Flow: The movement of digital assets, such as code, data, and metadata, through the lifecycle of a product.
  • Complexity Theory: A method for categorizing environments into Ordered, Complex, Chaotic, or Confused contexts to determine the appropriate management approach.
  • Core Value Stream: A sequence of activities that results in the direct delivery of value to an external customer.
  • Digital Product and Service Management (DPSM): The ITIL 5 paradigm that integrates product development and operational support into a unified management approach.
  • Enabling Value Stream: An internal sequence of activities that supports the organization’s ability to perform core value-creating work.
  • Flow Efficiency: A metric representing the percentage of total lead time spent on active, value-adding work.
  • Guiding Principles: Seven recommendations that guide an organization’s decisions and actions in all circumstances, regardless of changes in goals or management.
  • Lead Time: The total time elapsed from the start of a request until the final delivery of value.
  • Product and Service Lifecycle Model (PSLM): The ITIL 5 framework consisting of eight activities (Discover to Support) used to manage digital offerings.
  • Shadow AI: AI tools or systems adopted by employees or business units without formal authorization or oversight from the IT or governance departments.
  • Value Co-creation: The collaborative process where service providers and consumers work together to realize value from a service.
  • Value Stream: A series of steps an organization undertakes to create and deliver products and services to consumers.
  • Value Stream Mapping: A visual method for documenting the flow of activities and information required to bring a product or service to a consumer.
  • Value Stream Walk: An observational technique involving the real-time review of a work process to identify waste and friction.
  • Waste: Any activity or resource usage within a value stream that does not contribute directly to the value realized by the consumer.

Leaderboard

No scores saved yet. Be the first!

30 Questions — ITIL 5 – Foundation : Certified ITIL Foundation - Domain 5 - Value Stream Identification, Mapping, and Management

Expand any question to reveal the correct answer and explanation.

  1. 1 An organization is analyzing an internal workflow used for onboarding third-party SaaS vendors. According to ITIL (Version 5), how should this specific sequence of activities be categorized?

    Distinguish between flows that face the customer versus those that support the internal infrastructure.

    Enabling value stream

    Enabling value streams represent internal flows that support core streams, such as supplier onboarding or resource allocation.

    • Core value stream

      Core value streams are defined by their direct delivery of value to external consumers, rather than internal support functions.

    • Operational process

      While it is a process, ITIL (Version 5) prefers the term 'enabling value stream' when discussing end-to-end flows that support value delivery.

    • Value chain activity

      The value chain refers to the overarching model of activities, whereas the specific internal flow is categorized as a type of value stream.

  2. 2 A DevOps team notices that while their deployment velocity is high, the total time from a user's initial request to the feature's availability remains unchanged. Which metric should they prioritize to expose this specific delay?

    Look for a metric that tracks the entire duration of the journey from the customer's perspective.

    Lead Time

    Lead time measures the total elapsed time from the point of initiation or request to the final delivery of value.

    • Flow Efficiency

      Flow efficiency measures the ratio of active time to wait time, but it does not represent the total duration from initiation.

    • Deployment Frequency

      This measures how often code is deployed, which the team already identified as high, failing to account for front-end delays.

    • Value Realization

      Value realization is an experience-driven outcome metric rather than a time-based flow metric.

  3. 3 During a value stream mapping session, the facilitator insists on tracking 'digital artifacts' rather than physical materials. Which of the following is considered a digital artifact in the ITIL (Version 5) context?

    Think about the specific technical work products that move through a continuous delivery pipeline.

    Infrastructure as Code (IaC) templates

    Digital artifacts include items like code, metadata, and data that represent the 'material' of a digital value stream.

    • User experience feedback

      Feedback is an input or sentiment, whereas artifacts refer to the specific technical objects flowing through the pipeline.

    • Service Level Agreements (SLAs)

      SLAs are governance documents or commitments rather than the digital components that flow and transform during delivery.

    • Organizational roles

      Roles are part of the 'Organizations and People' dimension, not artifacts flowing through a stream.

  4. 4 An IT team is mapping a value stream and finds that the 'work as performed' differs significantly from the 'work as designed.' Which ITIL (Version 5) concept describes the 'work as performed'?

    Consider the distinction between a theoretical manual and actual daily reality.

    Value Stream

    In ITIL (Version 5), value streams are defined as the 'workflows as performed'—the real-world, context-specific steps taken to enable value.

    • Management Practice

      Practices provide the capabilities and methods used, but the specific performance of work is tied to the stream definition.

    • Documented Process

      A documented process represents the 'work as designed,' which may not reflect real-world execution.

    • Operating Model

      An operating model is a high-level conceptual representation of value co-creation, not the specific sequence of performed steps.

  5. 5 A service provider is dealing with a highly unpredictable environment where outcomes can only be understood in retrospect. Which execution pattern is recommended for this 'Complex' context?

    In complex situations, you must experiment and learn from the results before standardizing.

    Bound $\rightarrow$ Design $\rightarrow$ Run $\rightarrow$ Examine $\rightarrow$ Distil

    This is the 'Discover' pattern designed for 'Complex' contexts, emphasizing experimentation and hypothesis testing.

    • Appraise $\rightarrow$ Plan $\rightarrow$ Do $\rightarrow$ Study $\rightarrow$ Act

      This is the 'Implement' pattern used for 'Ordered' contexts where cause-and-effect is predictable.

    • Act $\rightarrow$ Sense $\rightarrow$ Respond

      This sequence is the management strategy for 'Chaotic' contexts, where immediate stabilization is the priority.

    • Discover $\rightarrow$ Design $\rightarrow$ Build $\rightarrow$ Support

      These are individual activities within the Product and Service Lifecycle, not a specialized execution pattern for complexity.

  6. 6 A value stream has a total Lead Time of 20 days. Analysis shows that the active, value-adding time across all activities is exactly 4 days. What is the Flow Efficiency of this stream?

    Calculate the percentage of the total time that was actually spent doing productive work.

    $20\%$

    Flow efficiency is calculated as $(\text{Active Time} / \text{Total Lead Time}) \times 100$. Here, $(4 / 20) \times 100 = 20\%$.

    • $5\%$

      This would be the result of 1 divided by 20, whereas active time is 4 days.

    • $80\%$

      This represents the percentage of 'wait time' or waste in the stream, rather than efficiency.

    • $25\%$

      This would be the result of 5 divided by 20, which does not match the data provided.

  7. 7 In the context of 'Complexity Thinking,' how should a manager approach a 'Chaotic' value stream where the relationship between actions and outcomes is turbulent?

    Identify the strategy that prioritizes immediate crisis management over analysis.

    Act first to establish order, then sense stability

    In chaos, the priority is to stabilize the situation immediately ('Act') before attempting to understand or respond.

    • Establish rigid procedures to force order

      Rigid procedures are explicitly warned against in chaotic or complex situations as they cannot adapt to the turbulence.

    • Perform a detailed Value Stream Map to identify bottlenecks

      There is no time for detailed analysis in a chaotic state; stabilization must come before mapping.

    • Empower the team with autonomy and guiding principles

      While autonomy is useful in complexity, the immediate requirement for chaos is a move toward stabilization through direct action.

  8. 8 A team is conducting a 'Value Stream Walk.' What is the primary objective of this activity in ITIL (Version 5)?

    Think about the Japanese concept of going to the actual place where value is created.

    To directly experience the actual steps and information flow in practice

    Similar to a 'Gemba walk,' the goal is to observe reality to gain situational awareness and identify actual bottlenecks.

    • To verify that employees are following documented processes

      The walk focuses on observing actual performance ('as performed') rather than enforcing compliance with 'as designed' documents.

    • To provide on-the-spot training for technical staff

      While training may occur, the core purpose of the walk is observation and analysis of the stream.

    • To audit the configuration management database (CMDB)

      A value stream walk analyzes flow and activities, not the static data within a repository.

  9. 9 When mapping the 'To-Be' state of a digital value stream, ITIL (Version 5) recommends differentiating between the 'Future' state and the 'Ideal' state. What characterizes the 'Future' state?

    One state is about pragmatic next steps, while the other is about long-term aspiration.

    Feasible improvements targeted for the next $3\text{--}6$ months

    The 'Future' state focuses on realistic, actionable changes that can be achieved in the short-to-medium term.

    • A perfect version used to inspire long-term innovation

      This describes the 'Ideal' state, which serves as a long-term North Star for the organization.

    • The current workflow exactly as it is performed today

      This describes the 'As-Is' state, not the 'Future' state.

    • A state that relies on technology not yet available in the organization

      The 'Future' state must be feasible; relying on non-existent tech would align more with an 'Ideal' vision.

  10. 10 Which of the following is a key differentiator between traditional industrial value stream mapping and mapping for 'digital-first' environments in ITIL (Version 5)?

    Think about the 'substance' that moves from one department to another in a software company.

    Industrial mapping tracks physical materials while digital tracks information and artifact flow

    Digital environments focus on the movement of code, data, and metadata rather than physical parts.

    • Digital mapping ignores wait times between steps

      Identifying wait times (waste) is a central component of both industrial and digital mapping to improve efficiency.

    • Digital mapping is a one-time project to establish a baseline

      ITIL (Version 5) views mapping as a continual activity for situational orientation, not a one-off project.

    • Industrial mapping focuses on Lead Time while digital ignores it

      Lead Time is a critical metric for digital flow, often more difficult to define but essential for measuring value delivery speed.

  11. 11 In an organization where the nature of a value stream is not yet understood and the context is 'Confused,' what is the mandatory next step?

    Before you can fix the problem, you have to categorize what kind of problem you are facing.

    Identify whether the stream is ordered, complex, or chaotic

    The priority in a 'Confused' state is to determine the underlying stability of the system so the correct management strategy can be applied.

    • Implement the 7-step Continual Improvement Model

      This model requires a baseline ('Where are we now?'), which cannot be established if the context is still confused.

    • Automate the existing activities to reveal the true flow

      Automating an unknown or confused process can lead to 'automating waste' and worsening the confusion.

    • Grant the team autonomy to resolve the confusion independently

      While autonomy is good, situational awareness must be established first to ensure efforts are aligned with system reality.

  12. 12 When dealing with 'Complex' value streams, ITIL (Version 5) suggests using 'Reverse Mapping.' What does this technique entail?

    In some systems, you can only see the pattern once the work is finished.

    Understanding outcomes in retrospect to identify the paths that led there

    In complex environments where cause-and-effect isn't clear upfront, reverse mapping helps reconstruct the flow based on realized results.

    • Starting from the supplier and mapping forward to the customer

      This is standard forward mapping; reverse mapping starts from the outcome.

    • Mapping the enabling value streams before the core value streams

      This refers to prioritization of stream types, not the reverse mapping technique itself.

    • Switching the roles of service provider and service consumer

      This describes value co-creation dynamics, not a mapping technique for complexity.

  13. 13 Why does ITIL (Version 5) warn against applying 'rigid procedures' to chaotic or complex value streams?

    Consider what happens when a rulebook encounters a situation the author never imagined.

    Rigid procedures cannot account for emergent behavior and unexpected outcomes

    In these contexts, the environment changes too rapidly for fixed rules to remain relevant or effective.

    • Procedures are too expensive to document for complex systems

      Cost is not the primary factor; the warning is based on the inability of rigid rules to handle unpredictability.

    • Procedures inherently reduce Flow Efficiency to zero

      Procedures do not eliminate active time, though they may increase wait times if they are overly bureaucratic.

    • Rigid procedures are only compatible with physical manufacturing

      Rigid procedures can work in 'Ordered' digital contexts, but fail in 'Complex' or 'Chaotic' ones.

  14. 14 A manager wants to improve the Lead Time of a core value stream. According to the framework, what is the relationship between 'Management Practices' and 'Value Streams' in this effort?

    Think of the practices as a toolkit and the value stream as the project you are working on.

    Value streams are improved by optimizing the management practices that support them

    Management practices provide the 'how' for activities within the stream; improving a practice (like Incident Management) improves the overall stream performance.

    • Value streams are used to optimize the 34 management practices

      The relationship is inverse; practices are the tools used to improve the streams.

    • Management practices and value streams are independent and do not interact

      Management practices are the foundational building blocks that enable every activity in a value stream.

    • Value streams replace management practices in ITIL (Version 5)

      All 34 practices remain essential; value streams simply provide the end-to-end perspective for applying them.

  15. 15 An organization adopts 'Total Experience' (TX) as a formal measure of success for its digital value streams. What does TX encompass in the ITIL (Version 5) context?

    Value is perceived differently by the person paying, the person using, and the person supporting the service.

    The integration of Customer Experience (CX), User Experience (UX), and Employee Experience (EX)

    Total Experience moves beyond just the external customer to include everyone involved in or affected by the stream.

    • The combination of availability and capacity metrics

      These are technical metrics, whereas TX is explicitly human-centered and experience-driven.

    • The total financial value realized over the product lifecycle

      Financial value is part of 'value realization' but does not define the experience of the people involved.

    • The sum of all digital artifacts produced by the stream

      Artifacts are outputs of the flow, while TX measures the subjective outcome for stakeholders.

  16. 16 Value Stream mapping reveals that a high percentage of Lead Time is spent waiting for approvals between 'Build' and 'Transition.' Which ITIL Guiding Principle should be applied to address this waste?

    Which principle suggests that if a step isn't adding value, you should rethink or remove it?

    Keep it simple and practical

    This principle encourages eliminating steps that don't add value, such as redundant or overly bureaucratic approval cycles.

    • Start where you are

      This principle focuses on not starting from scratch, but doesn't directly address process complexity or delays.

    • Think and work holistically

      While applicable, this principle focuses on the whole system rather than specifically simplifying a bottlenecked process step.

    • Focus on value

      This principle helps identify what the customer wants, but 'Keep it simple' is more targeted at the act of removing process waste.

  17. 17 A team is using the 'Product and Service Lifecycle Model' (PSLM) to manage a new software release. They find they need to move back to the 'Design' activity after testing in the 'Build' activity. How does ITIL (Version 5) describe this movement?

    Consider the non-linear, agile nature of modern digital work.

    Stepping stones allowing teams to move back and forth based on feedback

    The activities in the PSLM are not linear; they are flexible 'stepping stones' that support agile delivery and complexity.

    • A failure of the initial Planning stage

      ITIL (Version 5) expects and encourages iterative movement rather than viewing it as a failure.

    • A violation of the Unified Lifecycle sequence

      The lifecycle is unified but iterative; moving backward for refinement is part of its design.

    • An exception that requires board-level governance approval

      The model is designed for this flexibility at the operational level without requiring external intervention for every iteration.

  18. 18 Which specific 'Management Practice' is now grouped under 'General Management' and focuses on nurturing links between providers, consumers, and other stakeholders?

    This practice is categorized differently than technical delivery practices and emphasizes stakeholders.

    Relationship Management

    Relationship Management is a General Management practice that focuses on stakeholders and organizational links.

    • Service Level Management

      This is a Product and Service Management practice focused on performance targets, not relationship nurturing.

    • Supplier Management

      Supplier Management is now categorized as a Product and Service Management practice.

    • Change Enablement

      Change Enablement is a Product and Service Management practice focused on risk and safety of modifications.

  19. 19 An organization is defining 'Value Stream Management' in the context of Industry 5.0. What shift in focus does this represent compared to Industry 4.0?

    Consider how the latest industrial revolution re-introduces the human element into automated systems.

    From pure automation and efficiency to human-centricity and sustainability

    Industry 5.0 prioritizes how people and the environment co-exist with technology within the value system.

    • From human-centered resilience to pure technical efficiency

      This is the inverse; Industry 5.0 moves *away* from pure efficiency toward resilience and human-centricity.

    • From digital product management back to traditional ITSM

      The framework is evolving forward to digital product management, not backward.

    • From value co-creation to delivering services TO the customer

      Value co-creation (creating value *with* the customer) is a core modern principle that ITIL (Version 5) strengthens.

  20. 20 What is the primary purpose of 'Value Stream Identification' before mapping begins?

    You have to know what you are looking at before you can draw a picture of it.

    To define the boundaries and starting/ending points of the flow to be optimized

    You cannot map or manage a stream if you haven't identified where it begins (demand/opportunity) and ends (value realization).

    • To document every individual task performed by every employee

      Identification focuses on end-to-end flows that deliver value, not an exhaustive list of all human tasks.

    • To assign costs to each step in the Product and Service Lifecycle

      Cost analysis is a downstream activity; identification is about scope and boundary setting.

    • To determine which AI models can replace human workers in the stream

      This is a capability assessment, not the primary purpose of identifying value streams.

  21. 21 A team calculates Flow Efficiency and discovers it is only $12\%$. What does this result typically imply about their value stream?

    If the efficiency is $12\%$, what is happening during the other $88\%$ of the time?

    The vast majority of the Lead Time is spent in non-value-adding 'wait' states

    In low-efficiency streams, work often sits idle between departments, handoffs, or approval gates for $88\%$ of the time.

    • The team is working too fast and creating defects

      Low efficiency refers to the ratio of work to waiting, not the speed or quality of the active work itself.

    • The core value stream is incorrectly categorized as an enabling stream

      Efficiency metrics are independent of stream categorization.

    • The organization has achieved 'near-perfect' quality through Six Sigma

      Low flow efficiency is a sign of operational waste, whereas near-perfect quality would suggest high efficiency and low defects.

  22. 22 An organization is applying 'Human-Centered Design' (HCD) to its value streams. What is the core requirement of this approach?

    Think about empathy-driven problem solving.

    To prioritize the needs of the people for whom a solution is designed throughout the journey

    HCD is rooted in empathy and ensures that solutions (and the value streams that deliver them) are focused on human outcomes.

    • To ensure AI agents have final decision authority over human requests

      HCD prioritizes human needs; AI 'authority' is a governance question that HCD might limit to protect the human experience.

    • To eliminate the need for Employee Experience (EX) metrics

      EX is a critical part of the 'Total Experience' focus in modern value stream management.

    • To automate the 'Support' activity of the lifecycle entirely

      HCD may identify that certain support scenarios require human empathy rather than full automation.

  23. 23 In the ITIL (Version 5) taxonomy, which grouping of management practices from ITIL 4 was removed and its practices repositioned into other categories?

    Identify the category that used to include software development and deployment.

    Technical Management Practices

    The Technical Management category was removed, and its practices (like Deployment Management) were moved to the Product and Service category.

    • General Management Practices

      General Management Practices remain a core part of the simplified two-category model.

    • Service Management Practices

      This category was renamed/refocused into 'Product and Service Management' but not eliminated.

    • Lifecycle Management Practices

      This was never a formal ITIL 4 category; the lifecycle is a model that uses practices.

  24. 24 Which of the following describes a 'Value Stream Network' (VSN) in a revolutionary organizational model?

    Consider how multiple flows might cross and interact between different departments and external partners.

    A collection of interconnected value streams extending beyond organizational boundaries

    A VSN treats the entire business and its ecosystem (suppliers, partners) as a web of flowing value rather than isolated silos.

    • A single linear flow from one supplier to one customer

      This is a simple value chain, not a complex network of interconnected streams.

    • A technology platform used to automate value stream maps

      VSN is an organizational and conceptual model, not a specific software tool.

    • A network of AI agents managing the 'Operate' stage of the lifecycle

      While AI might participate, a VSN encompasses all human and technical value flows across the business.

  25. 25 An IT team is using AI to correlate raw monitoring alerts and deduplicate incidents. According to the 6C AI Capability Model, which capability are they using?

    This capability is about tidying up and making sense of a large, messy collection of technical data.

    Curation

    Curation involves correlating data, deduplicating records, and reducing operational noise.

    • Creation

      Creation involves generating new assets or summaries, not organizing existing data.

    • Cognition

      Cognition involves predicting severity or suggesting root causes through advanced reasoning.

    • Coordination

      Coordination involves automating routing or triggering scripts, not organizing alert data.

  26. 26 What is the primary risk of neglecting 'Digital Experience' (DX) in a high-velocity value stream?

    A system can be 'up' $99.9\%$ of the time and still be hated by its users.

    Disconnected stakeholders who feel the service is fragmented despite high technical uptime

    Value in ITIL (Version 5) is defined by experience; technical efficiency means nothing if the user's journey is frustrating.

    • Increased technical debt

      Technical debt is a result of poor development practices, which is separate from the experience of the user.

    • A failure to comply with the EU AI Act

      The EU AI Act focuses on governance and risk, whereas DX focuses on the user's subjective perception.

    • A reduction in the number of digital artifacts produced

      An organization can produce many artifacts while still delivering a poor experience.

  27. 27 When defining 'Decision Rights' in an AI-enabled value stream, which ITIL (Version 5) perspective is being addressed?

    This is part of the new 4-perspective governance model for AI.

    Decision Authority and Risk Management

    This governance perspective defines who has authority over AI-driven decisions and operational boundaries.

    • Information and Technology

      While it involves tech, the authority to decide is a governance and accountability concern.

    • Ethical Principles and Responsible AI

      This perspective focuses on bias and fairness rather than the formal assignment of decision authority.

    • Value Stream and Processes

      Decision rights govern the flow, but 'Decision Authority' is the specific perspective within the AI governance model.

  28. 28 An organization wants to achieve 'Value Continuity.' What is the primary mindset shift required according to the framework?

    Think about moving away from the 'throw it over the wall' mindset.

    From isolated task completion to a continuous, end-to-end perspective on value creation

    Value continuity requires looking past individual 'projects' to the entire lifespan and support of a service.

    • From long-term strategy to short-term task execution

      This is the opposite of the framework's intent; it promotes long-term value over isolated tasks.

    • From human-centric design to AI-native automation

      ITIL (Version 5) integrates both rather than shifting from one to the other.

    • From complex systems thinking to rigid process standardization

      The framework moves toward complexity thinking, acknowledging that rigid standardization often fails in digital environments.

  29. 29 Which of the following describes 'Shadow AI' and its impact on value stream governance?

    It's the digital version of employees using unauthorized software to get their work done.

    AI tools adopted by employees independently without formal review or oversight

    Shadow AI creates invisible governance gaps where sensitive data might be shared with external systems without control.

    • AI models used to monitor server temperature in data centers

      This is a standard operational use of AI, not 'shadow' use.

    • A specific security feature in ITIL (Version 5) used to protect user privacy

      Shadow AI is a risk to be managed, not a built-in security feature.

    • The use of AI to automatically generate value stream maps from log files

      This is an advanced mapping technique, not related to the risks of 'shadow' adoption.

  30. 30 In ITIL (Version 5), 'Lead Time' is defined as the time from 'initiation to delivery.' How does this differ from 'Flow Efficiency'?

    One tells you how long the customer waited; the other tells you how much of that time your team was actually working.

    Lead time measures the total duration, while flow efficiency measures the percentage of active work time

    Lead Time is the 'calendar time' of the journey, whereas Flow Efficiency identifies how much of that time was productive versus waiting.

    • Lead time measures cost, while flow efficiency measures speed

      Both are speed-related metrics; neither is primarily a cost metric.

    • Lead time is for Core value streams, while flow efficiency is only for Enabling streams

      Both metrics are essential for analyzing and optimizing all types of value streams.

    • Flow efficiency includes the 'Retire' activity, while Lead Time stops at 'Deliver'

      Both metrics can be applied to any segment of the lifecycle depending on the scope of the value stream mapping.