30 Questions — ITIL 5 – Master : Certified ITIL Master - Domain 1 - Value Streams, Service Design, and Transition

Expand any question to reveal the correct answer and explanation.

1. 1 An organization is currently transitioning from a legacy monolithic system to a microservices architecture. During the 'Design' activity of the Product and Service Lifecycle, the team is struggling to define success criteria for a specific API product. According to ITIL 5, which element is most critical to include in this definition to ensure value co-creation?

   Consider the relationship between the 'Discover' phase outcomes and the 'Design' phase success criteria.

   The specific stakeholder problems and desired outcomes the API aims to solve.

   In the 'Design' activity, defining architecture and success criteria must be anchored in the stakeholders' needs and desired outcomes identified during 'Discover'.

   • ✗ The technical specifications and throughput limits of the microservices.

     While technical specifications are necessary, focusing solely on outputs like throughput overlooks the broader outcomes and experience that define value in ITIL 5.

   • ✗ The cost-saving metrics achieved by retiring the monolithic legacy code.

     Efficiency gains are important, but success criteria should prioritize the value co-created with the consumer rather than just internal cost reductions.

   • ✗ The number of automated tests integrated into the CI/CD pipeline.

     Test volume is a process metric for the 'Build' and 'Transition' phases, not a foundational success criterion for the design of the product itself.

2. 2 A digital product team is utilizing Value Stream Mapping (VSM) to identify delays in their 'Build' to 'Transition' handoff. They notice that work often sits in a 'Pending Security Review' queue for five days. Which ITIL 5 concept should the team apply to optimize this specific flow without compromising governance?

   Think about how modern operating models move specialized knowledge closer to the point of work.

   Shift-left by integrating security practices earlier into the 'Build' activity.

   Shift-left culture and practices enable faster flow and quality by embedding specialized checks (like security) directly into earlier lifecycle activities.

   • ✗ Increasing the batch size of security reviews to improve reviewer efficiency.

     Increasing batch sizes typically leads to longer lead times and higher variability, which contradicts value stream optimization principles.

   • ✗ Moving the security review to the 'Support' activity to ensure faster delivery.

     Postponing critical governance to the 'Support' stage increases the risk of technical debt and service failure in live environments.

   • ✗ Implementing a rigid silo for security experts to ensure oversight integrity.

     Siloed functions are explicitly identified in the source material as barriers to holistic value stream management and end-to-end flow.

3. 3 In a complex environment where requirements are rapidly changing, a team is entering the 'Transition' activity for a new AI-enabled feature. Which transformation approach is most appropriate according to the ITIL Transformation Model?

   Focus on the ITIL 5 principle of managing change in 'complex and chaotic' landscapes.

   Using an iterative, learning-focused approach that adjusts based on feedback and real-world performance.

   ITIL 5 emphasizes adapting approaches based on the environment (e.g., complex vs. ordered) and leveraging learning as a core transformation layer.

   • ✗ Applying a linear, sequential approach with fixed milestones and strict change freezes.

     Linear approaches struggle in complex or uncertain environments where adaptation and learning are required to manage emergent risks.

   • ✗ Bypassing the 'Transition' activity entirely to reach the 'Operate' stage faster.

     Transition is essential for moving products into live environments safely; bypassing it risks operational stability and reliability.

   • ✗ Centralizing all decision-making within a single executive board to reduce complexity.

     Centralizing decisions in complex environments can lead to bottlenecks and a lack of responsiveness to local technical realities.

4. 4 When designing a digital service, a provider decides to implement Site Reliability Engineering (SRE) principles to manage reliability. How does this decision impact the 'Design' and 'Build' activities within the ITIL 5 lifecycle?

   SRE is not just about operations; it starts with how the system is planned and measured.

   It requires defining error budgets and SLOs as core service model components during Design.

   SRE integration requires that reliability targets (SLOs) and error budgets are architected into the design to guide build and transition decisions.

   • ✗ It eliminates the need for the 'Transition' activity by ensuring the code is always perfect.

     SRE accepts that failure is inevitable (error budgets); it does not eliminate the need for safe transition but rather manages the risk of it.

   • ✗ It shifts all operational responsibility from developers to a separate 'Reliability' silo.

     SRE promotes shared responsibility and cross-functional collaboration rather than creating new isolated siloos.

   • ✗ It focuses exclusively on the 'Support' phase, ignoring the 'Build' phase.

     SRE applies software engineering principles to the entire lifecycle, particularly design and build, to ensure scalable and reliable services.

5. 5 During the 'Acquire' activity of a value stream, an organization is evaluating whether to develop a chatbot internally or use a third-party SaaS provider. Which factor is most important to consider for long-term sustainability and value co-creation?

   Look for the option that emphasizes the 'Experience-led' shift in ITIL 5.

   The potential to integrate the solution into a seamless end-to-end customer journey.

   Value co-creation depends on how well a product or service integrates into the overall experience and journey, not just its standalone cost.

   • ✗ The lowest upfront procurement cost of the third-party provider.

     Upfront costs do not account for total cost of ownership or the long-term ability to adapt the solution to changing user needs.

   • ✗ Ensuring the internal team uses the most complex AI algorithms available.

     Technical complexity for its own sake can lead to increased risk and technical debt without necessarily improving the user experience.

   • ✗ Choosing the solution that requires the least amount of stakeholder engagement.

     Stakeholder engagement is a fundamental driver of value co-creation; avoiding it leads to products that do not meet real-world needs.

6. 6 An organization realizes that its digital products are managed by teams that never talk to the service desk analysts supporting those products. This is identified as a failure in 'integrated lifecycle thinking.' What is the primary risk of this siloed approach in Domain 1?

   Integrated lifecycles aim to close the gap between 'what is built' and 'how it is delivered/supported'.

   A disconnect between the 'Design' of the service and the 'Support' requirements for the user.

   Unified lifecycle management ensures that those designing and building products consider the supportability and delivery phases from the start.

   • ✗ The organization will be unable to purchase new hardware.

     Hardware procurement is a small tactical part of 'Acquire' and is not the primary risk of a lack of integrated lifecycle thinking.

   • ✗ The 'Discover' phase will take too much time.

     While silos can slow things down, the core risk is a lack of alignment between the stages of value creation rather than just the duration of one stage.

   • ✗ The Service Value System (SVS) will be replaced by a linear value chain.

     The SVS is the overarching model; silos impede its effectiveness but do not physically replace the model with something else.

7. 7 A value stream for 'Fixing a critical software bug' includes the following activities: Discover (User reports bug), Build (Developer creates fix), and Transition (Release to production). Which activity is missing if the goal is to ensure the fix actually meets the user's need before it is finalized?

   Success criteria and architecture are defined in this activity to prevent rework.

   Design

   The 'Design' activity defines requirements, architecture, and success criteria, ensuring the 'Build' phase has a clear target to meet.

   • ✗ Acquire

     Acquire involves sourcing components or services; if the developer is already fixing it, Acquire is not the missing feedback step.

   • ✗ Support

     Support happens after delivery; while it provides feedback, it is not the activity that shapes the fix during its creation.

   • ✗ Operate

     Operate is about day-to-day running; the missing step is the creative/architectural definition of the solution.

8. 8 In ITIL 5, how does 'Value Stream Mapping' (VSM) specifically support the 'Continual Improvement' of service transition?

   Flow and visibility are the key outcomes of this technique.

   By visualizing handoffs, delays, and bottlenecks to improve the flow of work from Build to Operate.

   VSM identifies waste and flow impediments, enabling teams to optimize the transition of products into live environments.

   • ✗ By providing a rigid checklist that must be followed for every single change.

     VSM is a visualization and analysis technique, not a static compliance checklist.

   • ✗ By automating the entire release process without any human oversight.

     While VSM may identify opportunities for automation, the mapping itself is a diagnostic and improvement planning tool.

   • ✗ By replacing the four dimensions of service management with a single dimension of speed.

     ITIL 5 retains all four dimensions; VSM is a technique used within the 'Value Streams and Processes' dimension.

9. 9 A financial firm is launching a new AI-driven investment advisor. During the 'Design' phase, they must adhere to the ITIL 5 guidance on 'AI Governance.' Which of the following is a core requirement for 'Responsible AI' in this context?

   Governance is about building trust and managing risk, not just performance.

   Establishing oversight, accountability, and risk management policies for the AI's decisions.

   Responsible AI governance focuses on ensuring that automated systems are trustworthy, ethical, and subject to appropriate human oversight.

   • ✗ Maximizing the complexity of the AI model to outperform competitors.

     Complexity is not a goal of governance; transparency, accountability, and ethical use are the primary focus areas.

   • ✗ Replacing all human financial advisors with automated bots immediately.

     Abruptly replacing people without managing the 'Organizations and People' dimension contradicts holistic management principles.

   • ✗ Hiding the AI's decision-making process to protect intellectual property.

     Transparency and ethics in AI often require the opposite of secrecy, especially in regulated industries like finance.

10. 10 According to the 'Unified Product and Service Lifecycle,' what is the primary difference between the 'Deliver' and 'Support' activities?

    One is about providing the value of the service, the other is about helping the user when they have trouble.

    Deliver provides value through high-quality interactions, while Support ensures users can consume services effectively.

    Deliver focuses on the consumption of the service's value, whereas Support addresses issues, feedback, and assistance to enable that consumption.

    • ✗ Deliver is about the 'Build' phase, while Support is about the 'Transition' phase.

      Both Deliver and Support occur late in the lifecycle, usually after a product has transitioned into live operation.

    • ✗ Deliver is managed by developers, while Support is managed exclusively by vendors.

      These activities involve various internal and external stakeholders; they are not strictly tied to one specific job family.

    • ✗ Support is a legacy ITIL 4 concept that is no longer used in ITIL 5.

      Both Deliver and Support are explicitly listed as the final two stages of the new ITIL 5 Product and Service Lifecycle.

11. 11 A team is designing a value stream for a 'Standard Change' (e.g., a pre-approved laptop request). In this stream, the 'Transition' activity is highly automated. Why is 'Service Validation and Testing' still relevant in this automated scenario?

    In high-velocity environments, you must 'test the test' and validate the 'automation' logic.

    To ensure that the automated scripts and delivery mechanisms themselves remain reliable and meet requirements.

    Validation and testing in automated environments shift toward ensuring the reliability of the automation and the outcomes it produces.

    • ✗ Because ITIL requires a manual signature for every release.

      ITIL does not mandate manual signatures; it encourages optimization and automation for repeatable tasks.

    • ✗ Because automation is inherently less trustworthy than human effort.

      ITIL 5 acknowledges AI and automation as core parts of modern environments; it focuses on governing it rather than distrusting it.

    • ✗ To provide work for the quality assurance team that was replaced by automation.

      ITIL practices should be outcome-focused rather than focused on maintaining specific traditional job roles.

12. 12 During a 'Design' workshop for a new healthcare app, the team uses 'Design Thinking' to better understand patient needs. Which specific ITIL 5 activity from the lifecycle are they primarily augmenting with this approach?

    Think about the stage where the 'problem' is clarified and 'empathy' is established.

    Discover

    The 'Discover' activity is where stakeholder needs, problems, and desired outcomes are understood, making it the natural fit for Design Thinking.

    • ✗ Acquire

      Acquire is about sourcing, while Design Thinking is about understanding and ideating solutions based on empathy.

    • ✗ Build

      Build is the execution of a design; the empathy and understanding phase should happen before construction starts.

    • ✗ Operate

      Operate is about running existing services; Design Thinking is most impactful during the early stages of creation.

13. 13 The 'Acquire' activity in the ITIL 5 lifecycle addresses a critical gap in many digital product teams by formally including which of the following?

    This activity is about getting what you need to build the solution.

    Sourcing capabilities through both internal development and external providers.

    Acquire is the lifecycle activity that focuses on obtaining the resources and capabilities needed, whether built or bought.

    • ✗ The development of internal source code.

      This is primarily handled in the 'Build' activity, although components might be 'Acquired' for it.

    • ✗ The resolution of user incidents.

      Incident resolution is part of 'Support' and 'Operate', not sourcing capabilities.

    • ✗ Setting the mission and vision for the entire enterprise.

      Strategy setting is part of 'Strategic Leader' streams and organizational governance, not a tactical sourcing activity.

14. 14 When mapping a value stream for a high-velocity digital product, a team identifies 'Toil' as a major bottleneck in the 'Transition' and 'Operate' phases. What is the most effective ITIL 5-aligned response?

    The goal is to free up human talent for creative and high-value work.

    Using automation and improved workflows to eliminate repetitive, low-value manual work.

    Toil reduction is a core concept (often from SRE) adopted by ITIL 5 to improve efficiency and human experience.

    • ✗ Hiring more junior staff to perform the repetitive manual tasks.

      Adding more people to manual toil does not address the root cause and is not a scalable improvement.

    • ✗ Accepting that toil is a natural part of IT and cannot be changed.

      Continual improvement encourages the identification and elimination of waste, including toil.

    • ✗ Moving all toilsome tasks to the 'Discover' phase.

      Toil usually consists of operational manual work; moving it to the discovery phase would impede strategic thinking and innovation.

15. 15 An IT manager is told that 'Service Design' in ITIL 5 now includes a stronger focus on 'Architecture.' Which of the following best describes 'Architecture' in the 'Design' activity context?

    It defines how different parts of the system fit together to work as a whole.

    The structural design of the service, its components, and how they interact to deliver value.

    Architecture ensures that all elements of a digital product or service are cohesive and support the intended outcomes.

    • ✗ The physical layout of the company's office building.

      Architecture in ITSM refers to the structure of digital systems, not civil engineering.

    • ✗ A list of every single server used by the organization.

      This is more representative of an asset list or configuration record rather than the architectural design.

    • ✗ The marketing logo used for the product.

      While visual design is part of experience, it is not what 'Architecture' refers to in a technical service context.

16. 16 A team realizes that while their code is perfectly built, it fails during 'Transition' because the production environment has different security configurations than the test environment. Which practice should have been more integrated into the 'Design' activity to prevent this?

    This practice is about knowing and managing the state of your infrastructure and environments.

    Service Configuration Management

    Configuration management ensures that environment requirements are understood and aligned throughout the lifecycle.

    • ✗ Service Desk

      The service desk handles user interactions and issues; it doesn't manage environment parity for developers.

    • ✗ Problem Management

      Problem management investigates root causes of incidents; while it might analyze this failure afterward, it is reactive.

    • ✗ Relationship Management

      Relationship management focuses on stakeholders and business value, not the technical parity of server environments.

17. 17 The ITIL 5 Product and Service Lifecycle includes a 'Transition' phase. Which of the following is a primary goal of this phase when using a 'Continuous Delivery' model?

    Think about the move from 'ready' to 'live' and who needs to be aware of it.

    Moving products into live environments safely while preparing stakeholders and operations.

    Transition is about readiness; even if deployment is automated, stakeholders and support teams must be prepared for the change.

    • ✗ Holding a weekly CAB meeting to manually approve every single line of code.

      High-velocity models typically replace manual CAB meetings with automated governance to maintain speed.

    • ✗ Writing the initial code for the software.

      Coding happens in the 'Build' phase; 'Transition' is about what happens after the code is built.

    • ✗ Replacing all operational staff with AI bots during the transition.

      ITIL 5 emphasizes team alignment and workforce culture, not the wholesale removal of staff.

18. 18 During the 'Design' of a new platform, a team identifies that the user experience (UX) is poor. Which ITIL 5 shift emphasizes that experience is as important as technical functionality?

    This shift moves the focus from 'fixing things' to 'how the service feels'.

    Experience at the Core

    ITIL 5 elevates experience as a key driver of value, focusing on how services feel to users, not just how they function technically.

    • ✗ Sustainability

      Sustainability is about long-term ethical and operational impact, not the immediate user interface or feeling.

    • ✗ AI-Native Design

      AI-native refers to leveraging automation and intelligence, which may improve experience but is not the same as the 'experience-led' principle.

    • ✗ Bi-modal IT

      Bi-modal IT is a reality described in the sources, but it's a state of organizational tension, not a principle centered on users.

19. 19 How does 'Technical Debt' typically accumulate during the 'Build' and 'Transition' activities in a high-velocity environment?

    It often happens when 'short-term speed' is the only metric being tracked.

    By prioritizing speed of delivery over long-term code quality and maintainability.

    Technical debt is the result of choosing faster, short-term fixes that will require rework or cause operational pain later.

    • ✗ By following every single best practice and documentation rule perfectly.

      Following all best practices generally reduces technical debt; debt comes from taking shortcuts.

    • ✗ By using AI to write code instead of human developers.

      AI can be used responsibly; the tool itself is not the cause of debt, but rather the governance of how it's used.

    • ✗ By engaging too many stakeholders during the 'Discover' phase.

      Engagement improves alignment; it does not inherently create technical code-level debt.

20. 20 An organization uses 'Value Stream Mapping' to improve their 'Transition' phase. They find that the handoff between 'Developers' and 'Operations' is full of errors. Which ITIL 5 recommendation would best address this 'Organizations and People' dimension issue?

    The solution involves breaking down functional silos and moving toward end-to-end ownership.

    Fostering integrated value stream teams that own the product from strategy through support.

    Integrated teams reduce handoff gaps by sharing goals and knowledge across the entire lifecycle.

    • ✗ Implementing a stricter hierarchy with more middle managers to supervise handoffs.

      More layers of management often increase delays and silos rather than improving cross-functional flow.

    • ✗ Replacing the human teams with fully autonomous AI systems.

      The source material emphasizes collaboration and human factors, even in AI-enabled environments.

    • ✗ Ignoring the issue as long as the software is technically functional.

      Unresolved handoff errors lead to operational instability and poor user experience, contradicting ITIL's value focus.

21. 21 A team is building a new digital service and decides to 'Acquire' a third-party security scanning tool. During the 'Transition' activity, they realize the tool's license doesn't cover the required number of servers. Which dimension of product management was most likely neglected during 'Design' and 'Acquire'?

    Contracts and third-party agreements fall under this dimension.

    Partners and Suppliers

    Licensing and vendor capabilities are core to the 'Partners and Suppliers' dimension, ensuring agreements support the actual service needs.

    • ✗ Organizations and People

      This dimension focuses on skills, culture, and roles, rather than the management of external contractual limits.

    • ✗ Value Streams and Processes

      While the 'process' of checking might have failed, the 'subject' of the failure is the supplier agreement and relationship.

    • ✗ Information and Technology

      The tool is technology, but the failure is a commercial/contractual one (Partners) rather than a technical one.

22. 22 In the ITIL 5 'Discover' phase, 'Empathy' is mentioned as a key trait for understanding stakeholders. Why is this important for 'Service Design' in Domain 1?

    Think about how empathy leads to a more accurate definition of 'Value'.

    It enables the team to identify the true problems and desired outcomes that the design must address.

    Understanding the user's perspective ensures the design creates real value rather than just technical output.

    • ✗ It helps the team feel sorry for users when a service fails.

      Empathy is about understanding needs to build better solutions, not just feeling emotion after a failure.

    • ✗ It reduces the need for technical skills in the 'Build' phase.

      Empathy augments technical skills; it does not replace the need for them in the construction phase.

    • ✗ It is a requirement for passing the closed-book Foundation exam.

      While empathy is a concept in the material, its importance lies in its practical application to service design, not just exam requirements.

23. 23 A 'Core Value Stream' is distinguished from an 'Enabling Value Stream' by which of the following characteristics?

    One is the 'main show' for the customer, the other is the 'backstage support'.

    Core value streams directly deliver value to external customers, whereas enabling value streams support core activities.

    Enabling streams (like HR or internal IT support) provide the foundation that allows core streams to reach their consumers.

    • ✗ Core value streams only use AI, while enabling value streams use manual labor.

      The type of technology used does not define whether a stream is core or enabling.

    • ✗ Core value streams are found only in ITIL v3, while enabling streams are new to ITIL 5.

      The concept of value streams was introduced in ITIL 4 and is expanded upon in ITIL 5.

    • ✗ There is no difference; the terms are used interchangeably.

      ITIL 5 differentiates between these streams to help organizations prioritize their resources and improvement efforts.

24. 24 During 'Service Validation and Testing' in the 'Transition' activity, a team discovers that the new AI algorithm provides biased results. According to the AI Governance guidance, what is the 'most appropriate' immediate action?

    This is an issue of 'Digital Ethics' and 'Responsible AI'.

    Halting the transition and returning to 'Design' or 'Build' to address the algorithmic bias.

    Governing AI means being accountable for its outcomes; biased results must be addressed before they reach the live environment.

    • ✗ Releasing the product anyway and fixing the bias in the 'Support' phase.

      Releasing biased AI violates ethical governance and risk management principles.

    • ✗ Deleting the entire product and firing the developers.

      This is an extreme and non-constructive reaction; the goal is improvement and responsible governance, not fear-based management.

    • ✗ Hiding the bias from stakeholders and hoping nobody notices.

      Governance requires transparency and accountability, especially regarding ethical AI concerns.

25. 25 A team is designing a 'High-Velocity' digital service. They want to ensure they can 'Fail Fast' safely. Which ITIL 5 concept most directly supports this goal during Transition?

    This concept from SRE balances the need for speed with the need for reliability.

    Error Budgets and SLOs

    Error budgets define the acceptable level of failure, allowing teams to innovate and move fast as long as they stay within the budget.

    • ✗ Annual Strategic Planning

      Annual planning is too slow for high-velocity environments that need to adapt and fail quickly.

    • ✗ A 12-month moratorium on all production changes.

      Stopping changes entirely prevents innovation and speed, which is the opposite of 'High-Velocity IT'.

    • ✗ Centralized, manual configuration management.

      Manual processes in high-velocity environments often become bottlenecks that slow down the 'Fail Fast' cycle.

26. 26 In Domain 1, why is it important to differentiate between 'Digital Products' and 'Digital Services'?

    One is the 'thing' you create, the other is the 'way' value is realized by the user.

    To clarify the distinction between what is built (product) and how value is consumed (service).

    This distinction helps organizations manage the entire lifecycle holistically rather than treating delivery as an afterthought.

    • ✗ Because they use completely different ITIL management practices.

      The 34 practices apply across both products and services within the same value streams.

    • ✗ Because digital products are only for external use, while services are only for internal use.

      Both products and services can be internal, external, or a mix of both.

    • ✗ It is not important; ITIL 5 uses the terms interchangeably.

      The source material explicitly states that ITIL 5 draws a 'clearer distinction' between the two.

27. 27 A service provider is struggling with 'Value Leakage' between their strategy and delivery teams. Which ITIL 5 concept is designed to bridge this gap in Domain 1?

    It ensures that what is planned actually delivers what is needed by stakeholders.

    Value Co-creation Model

    This model connects the service provider's strategy and delivery activities directly to the consumer's needs and outcomes.

    • ✗ The 3-year certification renewal cycle.

      Renewal cycles ensure individual competency but do not bridge the organizational gap between strategy and delivery.

    • ✗ Manual incident ticketing.

      Tactical ticketing is an operational task and does not address strategic alignment issues.

    • ✗ Standardized hardware procurement.

      Hardware is a component (Information and Technology), not the overarching model for strategic alignment.

28. 28 When an organization moves from 'Siloed Functions' to 'Integrated Value Streams,' which shift in management responsibility typically occurs during Transition?

    Think about who 'owns' the journey of the work from beginning to end.

    Ownership shifts away from specialized departments toward end-to-end product/service teams.

    Value streams emphasize holistic ownership from 'Discover' through 'Support', rather than passing work between isolated departments.

    • ✗ Ownership shifts entirely to the external vendor (SaaS provider).

      The organization still retains responsibility for the value co-creation and outcome management, even with external partners.

    • ✗ The service desk becomes the only team allowed to make changes to the product.

      Integrated teams include various roles; the service desk is part of the stream but does not suddenly become the sole change owner.

    • ✗ The 'Design' team is dissolved to save costs.

      Design remains a critical lifecycle activity; the goal is integration, not the removal of necessary expertise.

29. 29 A team is in the 'Build' phase of a new software module. They use 'AIOps' to monitor their development environment and predict potential build failures. Which of the 'Four Dimensions' are they primarily leveraging here?

    Automated tools and data-driven systems are categorized here.

    Information and Technology

    AIOps and predictive monitoring tools fall under the 'Information and Technology' dimension.

    • ✗ Organizations and People

      While people use the tool, AIOps is a technological capability.

    • ✗ Partners and Suppliers

      Unless the AIOps is provided by a specific vendor being managed, the focus here is on the technical tool itself.

    • ✗ Value Streams and Processes

      AIOps is a tool used *within* a value stream, but the tool itself is part of the technology dimension.

30. 30 A company is redesigning its customer onboarding value stream. They find that users are confused during the 'Support' stage. During the 'Design' phase of the improvement, which specific ITIL 5 concept should they use to visualize the customer's perspective?

    It tracks 'touchpoints' and 'interactions' across the service lifecycle.

    Customer Journey Mapping

    Journey mapping helps teams see the touchpoints and interactions from the customer's point of view to improve experience.

    • ✗ Service Catalogue Management

      The catalogue is a list of services, not a visualization of the customer's emotional or practical journey.

    • ✗ Technical Debt Log

      The debt log tracks technical issues in the code, not the customer's onboarding experience.

    • ✗ Financial Portfolio Planning

      Portfolio planning is a high-level strategic activity, not a tool for designing specific user interactions.