30 Questions — ITIL 5 – Master : Certified ITIL Master - Domain 3 - Stakeholder Engagement and Customer Journey

Expand any question to reveal the correct answer and explanation.

1. 1 A global financial service provider achieves $99.99\%$ availability across all digital platforms, yet the annual stakeholder satisfaction survey reveals a significant decline in 'perceived value.' Which action should the Business Relationship Manager (BRM) prioritize to address this discrepancy?

   Consider the shift in ITIL 5 from purely technical outputs to experience-led outcomes.

   Implement Experience Level Agreements (XLAs) to measure sentiment and journey friction.

   XLAs focus on the human experience and perceived value, which technical SLAs often fail to capture despite high uptime.

   • ✗ Negotiate more stringent Service Level Agreements (SLAs) with backend suppliers.

     This addresses technical performance which is already high, rather than the disconnect in customer perception.

   • ✗ Increase the frequency of automated system status reports to stakeholders.

     More reporting on technical success does not bridge the gap if the user experience itself is the source of dissatisfaction.

   • ✗ Redesign the Service Value Chain to prioritize the 'Support' activity over 'Design'.

     Prioritizing support focuses on reactive issue resolution rather than proactive experience design and relationship management.

2. 2 During the 'Design' phase of a new customer journey, a project team is using service design-thinking to identify 'moments of truth.' What is the primary objective of this specific activity?

   Focus on the subjective perception of the stakeholder at key interaction points.

   To identify critical touchpoints where a customer forms a lasting impression of the service.

   Moments of truth are pivotal interactions in the customer journey that significantly impact stakeholder perception and trust.

   • ✗ To map the technical dependencies between microservices and external APIs.

     This relates to system architecture and technical design rather than the stakeholder's subjective experience journey.

   • ✗ To calculate the total cost of ownership (TCO) for the product's underlying infrastructure.

     TCO is a financial metric that, while important, does not define the qualitative experience of the customer journey.

   • ✗ To define the minimum viable product (MVP) requirements for the next Agile sprint.

     While related to design, moments of truth focus on human interaction quality rather than functional scope prioritization.

3. 3 An organization is migrating to a multi-sourced digital estate using a SIAM (Service Integration and Management) model. How should the BRM role adapt its stakeholder engagement strategy at the senior level?

   Think about the BRM's role in a complex environment involving many different service providers.

   Shift focus from managing individual vendor performance to orchestrating value co-creation across the ecosystem.

   In multi-sourced environments, the BRM ensures that various partners collaborate effectively to deliver end-to-end stakeholder value.

   • ✗ Assume direct operational control over the service desks of all third-party suppliers.

     Direct operational control of suppliers is usually the responsibility of supplier management or service integration, not senior-level BRM.

   • ✗ Eliminate the use of OLAs (Operating Level Agreements) to simplify the relationship structure.

     OLAs remain necessary to define internal support expectations in complex, multi-sourced service models.

   • ✗ Act as the sole point of contact for all technical incident escalations from users.

     A senior BRM focuses on strategic alignment and relationship health, while incident management handles technical escalations.

4. 4 When mapping a customer journey for an AI-augmented service, which element is essential for ensuring 'Digital Ethics' and 'Responsible Innovation' are addressed?

   Consider the ITIL 5 focus on AI governance, accountability, and user trust.

   Transparency in how AI-driven decisions are made and presented to the user.

   Responsible AI in the customer journey requires clarity and accountability regarding automated decisions to maintain user trust.

   • ✗ Maximizing the use of 'black-box' algorithms to improve predictive accuracy.

     Black-box algorithms often lack transparency, which contradicts the principles of digital ethics and accountability.

   • ✗ Prioritizing speed of delivery over the validation of data privacy controls.

     Speed at the expense of privacy violates the core tenets of responsible innovation and risk-aware governance.

   • ✗ Ensuring that the AI agent has a human-sounding name to improve empathy scores.

     While affecting perception, anthropomorphizing AI is secondary to the ethical governance and transparency of its outputs.

5. 5 In the ITIL 5 Product and Service Lifecycle, the 'Discover' activity is often the starting point of the service journey. What is a common mistake organizations make during this stage?

   Recall the purpose of 'Discover' versus later stages like 'Build' or 'Design'.

   Focusing on technical solutions before fully understanding the desired business outcomes.

   The 'Discover' stage is meant for understanding stakeholder needs and problems, not jumping to solution architecture.

   • ✗ Collaborating too closely with consumers during the initial brainstorming sessions.

     Value co-creation encourages early collaboration; it is rarely considered a mistake in modern service management.

   • ✗ Using 'Empathy Mapping' to understand the user's perspective.

     Empathy mapping is a best-practice tool in service design-thinking used to gain deep stakeholder insights.

   • ✗ Identifying external environmental factors that may impact the service's success.

     Understanding the external context is a vital part of the discovery and strategic alignment process.

6. 6 A software company is seeing high user drop-off immediately after the 'Onboarding' phase. Which area of the service journey should be analyzed using 'Design Thinking' to improve retention?

   Look for the gap where the user expected to start seeing benefits but didn't.

   The transition from 'Onboarding' to 'Continual Value Realization'.

   Retention issues often stem from a failure to demonstrate ongoing value once the initial setup is complete.

   • ✗ The efficiency of the 'Acquire' stage in sourcing third-party code libraries.

     The 'Acquire' stage is an internal lifecycle activity and is usually invisible to the user's retention experience.

   • ✗ The 'Build' stage's adherence to CI/CD pipeline automation protocols.

     Automated pipelines improve delivery speed but do not inherently solve issues related to user experience and value perception.

   • ✗ The 'Operate' stage's server-side latency metrics.

     Technical latency is an operational metric that may contribute to friction but doesn't address the broader value journey.

7. 7 Which type of service relationship involves a high degree of shared risk and reward, where the provider and consumer work as an integrated team?

   This relationship type reflects the highest level of service partnership mentioned in ITIL 5 Foundation.

   Collaborative relationship

   Collaborative relationships are characterized by joint efforts, shared goals, and high levels of value co-creation.

   • ✗ Basic relationship

     Basic relationships are typically transactional and involve minimal interaction beyond the delivery of goods or services.

   • ✗ Cooperative relationship

     Cooperative relationships involve some mutual adjustment but lack the deep integration found in collaborative models.

   • ✗ Adversarial relationship

     ITIL 5 emphasizes partnership and co-creation, making adversarial models contrary to the framework's intent.

8. 8 A BRM is managing a portfolio of digital services for an enterprise. They notice that 'Demand Management at Scale' is failing because business units are bypassing the standard request process. What is the most likely root cause from a DSV perspective?

   Focus on the user experience of the request process itself.

   The service journey for new requests is too complex or lacks visible progress updates.

   Friction in the stakeholder experience often leads users to find 'shadow IT' workarounds to achieve their outcomes faster.

   • ✗ The organization's SRE error budgets are too generous.

     Error budgets relate to reliability and deployment velocity, not the intake process for new business demand.

   • ✗ The service desk has not been scaled using AI-augmented ChatOps.

     While AI can help, the underlying issue is likely the design of the journey rather than the specific technology used at the desk.

   • ✗ There is a lack of 'Chaos Engineering' in the 'Operate' phase.

     Chaos engineering is used for testing resilience, which is unrelated to the governance of business demand intake.

9. 9 An IT team is using Value Stream Mapping (VSM) to optimize the delivery of a digital product. How does 'Customer Journey Mapping' complement VSM in this scenario?

   Consider the perspectives of the service provider versus the service consumer.

   Customer Journey Mapping provides the 'outside-in' view of the experience, while VSM provides the 'inside-out' view of the process.

   Combining both views ensures that internal optimizations lead to actual improvements in the stakeholder's experience.

   • ✗ VSM replaces the need for Journey Mapping by identifying all stakeholder touchpoints automatically.

     VSM focuses on work flow and waste, whereas Journey Mapping captures the qualitative experience and emotions of stakeholders.

   • ✗ Journey Mapping is used to manage server capacity, while VSM manages customer expectations.

     These roles are inverted; VSM deals with internal capacity/flow, and Journey Mapping deals with expectations and experience.

   • ✗ They are identical techniques used by different teams (IT vs. Marketing).

     Although related, they have distinct focuses: one on internal efficiency and flow, the other on external interaction and perception.

10. 10 Stakeholder engagement at the 'Strategic Leader' level involves authoring digital strategy. Which tool is most appropriate for aligning technology initiatives with a complex business model?

    Look for a high-level tool used to design or analyze how an organization functions.

    Business Model Canvas

    The Business Model Canvas allows leaders to visualize how technology creates, delivers, and captures value within the business context.

    • ✗ Service Level Agreement (SLA) template

      SLAs are operational documents that define performance targets, not tools for high-level strategic alignment.

    • ✗ Incident Command (IC) framework

      IC is used for managing major incidents in real-time, not for long-term digital strategy authoring.

    • ✗ Kanban board for the service desk

      Kanban boards are tactical tools for managing work-in-progress at the operational level.

11. 11 During the 'Offboarding' phase of a service relationship, what is the BRM's primary responsibility to ensure long-term value?

    Consider the goals of risk management and brand reputation during an exit.

    Ensuring the secure transfer of assets and data while maintaining relationship health for future opportunities.

    Offboarding must manage risks and compliance while preserving the organization's reputation and potential for future collaboration.

    • ✗ Deleting all customer records immediately to reduce storage costs.

      Immediate deletion may violate data retention policies or prevent the customer from retrieving necessary information.

    • ✗ Upselling the customer on a new, unrelated product line to prevent churn.

      Offboarding should focus on a successful exit; aggressive upselling during this phase can damage relationship trust.

    • ✗ Assigning the customer's technical support tickets to a lower-priority queue.

      Reducing support quality during offboarding creates a negative final impression and can lead to significant reputational damage.

12. 12 Which of the following describes the ITIL 5 concept of 'Value Co-creation'?

    Think about the relationship between 'facitiliating outcomes' and 'active participation'.

    The active collaboration between providers and consumers to realize outcomes and manage risks.

    Value is not just delivered; it is co-created through the ongoing interaction and contribution of both parties.

    • ✗ The provider's ability to minimize all costs for the consumer regardless of quality.

      Co-creation focuses on outcomes and value, whereas cost minimization in isolation often degrades value.

    • ✗ A one-way transfer of software from a vendor to a client.

      This describes a traditional transactional model, not the integrated co-creation model championed by ITIL 5.

    • ✗ The customer's sole responsibility to extract value from the services provided.

      Co-creation implies that the provider also plays an active role in enabling and ensuring value realization.

13. 13 In the context of 'Experience-led Service Design,' why is it important to define clear roles and accountability?

    Consider how a lack of ownership impacts a user's journey through different departments.

    To ensure that stakeholders know who is responsible for their experience at every stage of the journey.

    Accountability prevents gaps in the customer journey where a stakeholder might feel unsupported or ignored.

    • ✗ To allow the service provider to blame specific employees when a journey fails.

      Accountability should drive improvement and ownership, not facilitate a culture of blame.

    • ✗ To reduce the number of staff members needed to operate the service.

      Defining roles is about clarity and quality of service, not necessarily about headcount reduction.

    • ✗ To automate the Business Relationship Management function entirely.

      BRM requires human empathy and strategic judgment, which are difficult to automate fully even with AI.

14. 14 What is the primary difference between 'Customer Experience (CX)' and 'User Experience (UX)' in the ITIL 5 framework?

    Think about the scope: the whole relationship versus the specific tool.

    CX covers all interactions with the organization, while UX focuses on interactions with a specific product or service interface.

    CX is broader and includes brand perception, support, and sales, whereas UX is specific to the functionality and design of the tool itself.

    • ✗ UX is for external customers, and CX is for internal employees.

      Both CX and UX apply to any stakeholder, whether internal (employees) or external (customers/users).

    • ✗ CX is measured by technical uptime, and UX is measured by user surveys.

      Technical uptime is a system metric; CX and UX are both human-centric experience metrics measured through various feedback loops.

    • ✗ They are synonymous and can be used interchangeably in all documentation.

      While related, they represent different granularities of interaction that require different management approaches.

15. 15 A service provider is using 'Wardley Mapping' as part of their stakeholder engagement. What insight does this provide to the senior leadership team?

    Think about 'position' and 'movement' in the context of service components and user needs.

    The evolution of components in the value chain and their strategic importance relative to the user need.

    Wardley Mapping helps leaders understand the landscape, maturity, and competitive positioning of their services.

    • ✗ The exact number of CPU cycles consumed by the AI model during peak hours.

      This is a technical resource utilization metric, not a strategic mapping of service evolution.

    • ✗ The individual performance reviews of the service desk analysts.

      Individual performance management is a general management practice, not a strategic mapping output.

    • ✗ The physical location of all data centers in the provider's network.

      Geographic mapping is part of facility or asset management, whereas Wardley Mapping focuses on strategic evolution.

16. 16 How does the 'Start Where You Are' guiding principle apply to a BRM team that is redesigning a customer journey?

    Think about the value of existing data and current interactions.

    By assessing existing touchpoints and data before deciding what to discard or improve.

    It is essential to understand the current state to avoid wasting resources or destroying elements that are already working well.

    • ✗ By ignoring all previous customer feedback to ensure a fresh, unbiased design.

      Ignoring feedback contradicts the principle, as it discards valuable information about the current reality.

    • ✗ By immediately replacing all legacy systems with AI-augmented platforms.

      This assumes a 'rip and replace' strategy, which is the opposite of leveraging what is already available.

    • ✗ By waiting for the customer to provide a complete list of new requirements before taking any action.

      This is a reactive approach that does not involve assessing current capabilities or iterating based on current data.

17. 17 Which phase of the 'Service Journey' focuses on translating a customer's business requirements into a concrete service offering?

    Consider the activities that happen before a contract is signed or a service is launched.

    Engagement

    Engagement is where relationships are built and requirements are discovered and shaped into a potential offering.

    • ✗ Onboarding

      Onboarding involves getting the customer started with a service that has already been defined and agreed upon.

    • ✗ Acquisition

      Acquisition is an internal lifecycle stage (Acquire) where the provider builds or buys the components needed to deliver the service.

    • ✗ Operationalizing

      Operationalizing is about moving into steady-state delivery, not the initial translation of business needs to offerings.

18. 18 A BRM uses 'Hoshin Kanri' to cascade strategic objectives. How does this benefit the 'Customer Journey'?

    Focus on the 'alignment' and 'cascading' aspect of this strategic tool.

    By ensuring that individual touchpoints are aligned with the organization's high-level vision for customer value.

    Hoshin Kanri (policy deployment) connects top-level strategy to daily operations, ensuring consistency in value delivery.

    • ✗ By automating the generation of user passwords through the service desk.

      Hoshin Kanri is a strategic planning methodology, not a technical automation tool for identity management.

    • ✗ By replacing XLAs with a more rigid set of binary technical metrics.

      Cascading strategic objectives should reinforce experience-led values, not revert to narrow technical silos.

    • ✗ By allowing each team to define their own independent goals without central oversight.

      This describes a fragmented approach, whereas Hoshin Kanri is designed specifically to ensure alignment across the whole organization.

19. 19 When designing a service for 'Sustained Value,' why should a BRM include 'Offboarding' in the initial service journey map?

    Consider the long-term lifecycle and the principle of 'Think and Work Holistically'.

    To address data privacy, asset return, and transition risks at the beginning of the relationship.

    Proactively designing the exit ensures that both parties are protected and that the relationship ends on positive terms.

    • ✗ To encourage the customer to leave as soon as possible to make room for others.

      The goal is sustained value and retention; planning for an exit is about risk management, not encouraging churn.

    • ✗ To calculate the early termination fees that will be charged to the client.

      While financial, the primary goal of journey mapping is experience and risk management, not just fee calculation.

    • ✗ To hide potential risks from the customer until they are already locked into a contract.

      Transparency and ethics are core to ITIL 5; hiding risks violates the 'Collaborate and Promote Visibility' principle.

20. 20 An IT team is using 'AIOps' to observe the service journey. What is the primary benefit to the stakeholder from this technology?

    Focus on the concepts of 'Observability' and 'Proactivity' in operations.

    Proactive identification of issues before the user experiences a service degradation.

    AIOps uses telemetry and machine learning to find patterns that allow for automated remediation or proactive intervention.

    • ✗ Replacing all human service desk agents with rule-based chatbots.

      AIOps supports observability and operations; replacing humans is a separate (and often risky) strategic decision.

    • ✗ Allowing the provider to stop measuring XLAs.

      AIOps provides the data that often feeds into XLAs; it does not replace the need to measure human experience.

    • ✗ Reducing the need for the 'Discover' phase in the product lifecycle.

      Discovering stakeholder needs remains a human-centric design activity that technology supports but does not eliminate.

21. 21 In ITIL 5, how does 'Demand Management' at the strategic level differ from its operational equivalent?

    Consider the 'Portfolio Planning' vs. 'Service Request' perspectives.

    Strategic demand management looks at portfolio-level trends and investment prioritization, while operational demand manages short-term fluctuations.

    Strategic demand aligns with the organization's vision and long-term capacity, while operational demand deals with day-to-day service desk or infrastructure load.

    • ✗ Strategic demand is only for external customers, while operational demand is for internal users.

      Both levels of demand management apply to internal and external stakeholders.

    • ✗ Operational demand management is handled by the C-suite, while strategic demand is handled by developers.

      The C-suite handles strategy; developers and operations teams handle the tactical execution and load management.

    • ✗ They are the same practice, but 'Strategic' is the term used for AI-enabled services.

      The terms refer to the scope and time horizon of the management activity, not the specific technology used.

22. 22 What is the role of 'Empathy' in service design-thinking?

    Think about the 'Empathy Map' and why it is used at the start of a design process.

    To gain a deep understanding of the stakeholder's needs, frustrations, and environment to create more effective solutions.

    Empathy is the foundational step in design thinking that ensures services are human-centric rather than purely technology-centric.

    • ✗ To ensure that the provider always agrees with the customer's technical requests.

      Empathy means understanding the 'why' behind a request; the provider may still need to advise against a technically unsound request.

    • ✗ To reduce the cost of the service by sympathizing with the customer's budget constraints.

      Sympathy and budget reduction are financial matters, whereas empathy in design is about insight and problem-solving.

    • ✗ To replace the need for data-driven metrics with gut feelings.

      Empathy provides qualitative insights that complement, but do not replace, quantitative performance data.

23. 23 A stakeholder engagement plan identifies a 'Silent Influencer' in the customer organization. How should the BRM handle this individual?

    Consider the subtle and varied nature of stakeholder mapping and management.

    Engage them through indirect channels or peer networks to ensure their perspective is considered without forcing direct formal interaction.

    Influencers who are not formal decision-makers still affect project success; the BRM must find ways to align with their needs.

    • ✗ Ignore them until they make a formal complaint through the service desk.

      Ignoring influencers can lead to 'shadow resistance' that undermines strategic initiatives.

    • ✗ Remove them from all mailing lists to prevent them from gathering information.

      Restricting information usually increases resistance and destroys trust in the relationship.

    • ✗ Escalate the situation to their manager and demand that they become a formal project sponsor.

      Demanding a formal role can backfire and does not respect the individual's preferred way of engaging.

24. 24 A BRM is monitoring an XLA that measures 'Onboarding Speed.' The metric is green (fast), but user feedback indicates they feel 'lost and confused.' What should the BRM do next?

    Think about the 'Watermelon Effect' where metrics look green but the reality is red.

    Use design-thinking to investigate the quality and clarity of the onboarding content rather than just the speed.

    The conflict between a 'green' metric and 'red' feedback indicates that the metric is measuring the wrong thing (output speed vs. outcome clarity).

    • ✗ Disregard the feedback as subjective and continue to focus on the high-speed metric.

      Subjective feedback is the heart of experience management; ignoring it leads to poor value co-creation.

    • ✗ Slow down the onboarding process intentionally to match the users' confusion level.

      Slowing down a process without fixing the quality only makes a slow, confusing process, which is worse.

    • ✗ Automate the onboarding even further using AI to eliminate human interaction.

      If the process is already confusing, automating it will likely scale the confusion rather than resolve it.

25. 25 In a 'Collaborative' service relationship, who is responsible for identifying improvement opportunities?

    Recall the definition of a collaborative relationship versus a basic one.

    Both the service provider and the service consumer jointly.

    Co-creation implies that both parties actively contribute to the continual improvement of the service ecosystem.

    • ✗ Only the service provider's 'Continual Improvement' team.

      In a partnership, limiting improvement to the provider misses valuable insights from the consumer's perspective.

    • ✗ The third-party auditor during the annual compliance review.

      Auditors find compliance gaps; the day-to-day partners are best positioned to find value improvement opportunities.

    • ✗ Only the consumer, since they are the ones paying for the service.

      A provider who does not proactively suggest improvements is failing to add value as a strategic partner.

26. 26 Why does ITIL 5 emphasize 'Lifecycle Thinking' in stakeholder engagement?

    Consider the goal of breaking down silos between 'Build' and 'Run' teams.

    To ensure that decisions made during 'Strategy' or 'Design' consider the long-term impacts on 'Operations' and 'Support'.

    Thinking holistically across the lifecycle reduces technical debt and ensures sustained value for the stakeholder.

    • ✗ To force stakeholders to commit to a 5-year contract before the 'Design' phase begins.

      Lifecycle thinking is about management quality and foresight, not about forcing long-term legal commitments.

    • ✗ To ensure that the service desk is only involved at the very end of the project.

      Lifecycle thinking requires early involvement of operational teams to ensure the service is supportable.

    • ✗ To allow the 'Acquire' team to work in a silo without interacting with 'Deliver'.

      Siloed working is the opposite of the integrated, holistic approach promoted by lifecycle thinking.

27. 27 A senior leader is using 'OKRs' (Objectives and Key Results) to manage a digital transformation. How should these be communicated to the workforce as part of stakeholder engagement?

    Think about the role of 'Strategic Communication' mentioned in the SL domains.

    With clarity and transparency, connecting individual tasks to the strategic 'why' of the organization.

    Strategic communication ensures that the workforce understands their contribution to the transformation's success.

    • ✗ As a confidential list of targets that only the C-suite can access.

      Secrecy in OKRs defeats their purpose, which is to align and inspire the organization toward common goals.

    • ✗ By replacing all existing job descriptions with a single OKR metric for every employee.

      OKRs are for strategic focus and alignment; they do not replace the need for clear role definitions and responsibilities.

    • ✗ As a rigid set of rules that cannot be changed even if the market shifts.

      OKRs should be adaptable and provide the flexibility needed in fast-moving, digital environments.

28. 28 A BRM is mapping the 'Service Relationship Model.' Which interaction describes the 'Facilitated Outcome'?

    Look for the achievement of a business goal that the service made possible.

    A business manager successfully completing a payroll run using the HR system without managing the underlying servers.

    The service facilitates the outcome (payroll) by removing the burden of managing technical costs and risks from the customer.

    • ✗ The provider's IT team upgrading the database version on a Saturday night.

      This is a technical activity/output, not the business outcome experienced by the customer.

    • ✗ The procurement department signing a contract for a new cloud provider.

      Contracting is part of the 'Acquire' stage, not the final facilitated outcome of the service itself.

    • ✗ The customer paying their monthly invoice on time.

      Payment is a customer responsibility and part of the relationship model, but it is not the service's facilitated outcome.

29. 29 When assessing the 'Four Dimensions' during a customer journey redesign, which factor falls under 'Partners and Suppliers'?

    Recall the definitions of the four dimensions used for holistic management.

    The contract terms and communication protocols with a third-party AI platform provider.

    Managing the relationships and agreements with external entities is the core focus of this dimension.

    • ✗ The skill level of the internal developers working on the product.

      Internal skills and staff fall under the 'Organizations and People' dimension.

    • ✗ The specific software architecture used to process customer data.

      Architecture and software fall under the 'Information and Technology' dimension.

    • ✗ The step-by-step workflow for resolving a high-priority incident.

      Workflows and procedures fall under the 'Value Streams and Processes' dimension.

30. 30 A stakeholder engagement strategy for a 'Transformation' initiative emphasizes 'Maturity Assessments.' What is the primary risk of over-focusing on these assessments?

    Think about the 'Progress Iteratively with Feedback' principle versus 'chasing a score'.

    Treating the maturity level as an end goal rather than a means to improve value delivery.

    Maturity should support value co-creation; chasing a high score can distract from actual service performance and stakeholder needs.

    • ✗ Allowing the BRM to spend too much time talking to customers.

      Time spent with customers is generally a positive investment for a BRM team.

    • ✗ Ensuring that the ITIL 5 framework is followed too closely.

      The risk is misapplication or 'tick-box' compliance, not following the framework's adaptable principles.

    • ✗ Revealing that the organization is already performing at a high level.

      Identifying high performance is a benefit, not a risk, as it allows the team to 'Start Where They Are' and focus elsewhere.