ITIL Transformation (Version 5) ITIL V5 Transformation Dumps in PDF

Free ITIL ITIL V5 Transformation Real Questions (page: 3)

Introduction to ITIL Car Rental:
Ten years ago, ITIL Car Rental (ICR) was launched in Seattle with the aim to provide convenient and affordable rental cars to customers around the world. After a relatively short time, ICR became a globally recognized company, with a wide network of franchising partners across Europe, the US, and Asia-Pacific, with approximately 400 direct employees. In the first few years of operation, repeat business accounted for nearly a third of all reservations. Shareholders saw steady growth, and the company earned a reputation for putting customers first. ICR quickly became a model of modern mobility: fast, reliable, and profitable. Following its early success, the company expanded through mergers and acquisitions to new markets and new services, including car sharing. ICR relies heavily on digital technology for internal operations and service delivery, using a mix of internal and external digital products. Customer-facing mobile applications are developed and run by the internal IT team. AI is increasingly used in internal and external products and services for predictive maintenance, customer support, scheduling, smart check-in and return processes, and so on. As new competitors, such as car-sharing services, rideshare apps, and driverless cars, enter the market, customers now expect a seamless digital experience: quick bookings, app-based help, and flexible options that fit easily into their daily lives. At the same time, customers are paying more attention to companies that value social responsibility, sustainability, and environmental consciousness. These expectations are driving ICR to set clear and ambitious sustainability goals, as well as pursue further growth. The board members strongly believe that the company’s success in the years to come will be defined by innovation and the use of digital technology. For this reason, they appointed a new GIO, Max. Max was chosen for his experience in digitalization and his track record in successful, large-scale IT transformations. Max’s strong background in ITIL and ITSM indicates that he values ITIL certification, and his hiring policy reflects this. Having worked with Design Thinking, DevOps, and agile methods, he believes sustainable business requires a blended approach to digital product and service management. Max is keen to see how his team can redefine the car rental experience and ensure that ICR is the first choice for new and existing customers.

Meet the employees of ITIL Car Rental:
Max, Chief Information Officer (CIO):
Max is the new CIO. He is an experienced executive with a track record of leading digital transformations. He believes in an integrated approach to DPSM.

Anna, Product Manager:
Anna has been with ITIL Car Rental for five years. She focuses on commercial success and continual B2C development. She is detail-oriented, eco-conscious, and dedicated to improving overall customer experience.

Maria, Business Analyst:
Maria is a proactive communicator who ensures smooth collaboration between IT and business teams. She works mostly on discovery and planning activities, supporting continual improvement of the company’s digital products. She asks a lot of questions and is great at spotting patterns and trends.

Omar, IT Delivery Manager:
Omar manages ongoing service delivery. He applies ITIL practices to improve efficiency and customer satisfaction. However, Omar has had little experience with a blended or collaborative approach to product and service management.

Sam, Head of Product Development:
Sam has more than 10 years of experience in leading cross-functional product teams in the domains of mobility and automotive innovation. He oversees the entire product lifecycle at ITIL Car Rental from strategic vision to delivery and ensures that customer needs, market trends, and sustainability are all in sync.

Alex, Enterprise Architect:
Alex is responsible for ensuring that product design and technological strategy are aligned, sustainable, and future-proof. She provides architectural guidance across teams, works to identify systemic risks, and holds coherence in a fast-changing digital ecosystem. She is highly analytical with a strong intuition for patterns and risks.

The CIO’s vision for ITIL Car Rental Max:
We live in an era of rapid change, where all companies are going through some kind of digital transformation. Service expectations have changed drastically since ITIL Car Rental was created 10 years ago. Customers want seamless and immediate access to rental services from their smartphones, as well as innovation as part of their daily lives. Autonomous vehicles are the future; they will make car rental companies stand out and continue successfully. My vision is for ITIL Car Rental to pioneer this transformation and become the go-to name for car rentals worldwide. We will continue offering outstanding customer service while maintaining competitive car rental rates. After all, ITIL Car Rental is more than just a service. We are here to enhance the entire travel experience.

Governance:
ITIL Car Rental has branches in other countries, some of which are franchises. Each country may have its own regulations when it comes to the services offered by ICR. Although all services are focused on enhancing the entire travel experience, different services may be subjects to different regulation. For example, car-sharing is regulated differently, and self-driving cars cannot be introduced at all in some countries. ICR has adopted a governance approach that blends clear global direction with local autonomy, enabling the company to stay competitive in a fast-moving mobility landscape. As ICR continues to grow across regions and expand its portfolio, moving from traditional rentals to car-sharing and self-driving services, its governance structure ensures consistency, compliance, and customer-focused innovation. ICR’s approach to change is practical and adaptive. The company encourages experimentation and continual improvement as long as new ideas follow shared principles and meet regulatory expectations in each market. This balanced approach helps ICR introduce new digital features quickly while maintaining trust and reliability. The Board evaluates progress through a focused set of indicators, including commercial results, market share, innovation outcomes, cost efficiency, and customer satisfaction. Coordinated autonomy is a key feature of ICR’s governance.
While the Board defines the overall vision and strategic direction, local branches and service owners have freedom in how they achieve their goals. Market leaders and service-line managers work closely to tailor solutions to regional needs, ensuring that global standards remain compatible with local realities. Risk management reflects the diverse environments in which the company operates. Within heavily regulated domains, such as safety, traffic rules, and data protection, the company maintains a very low risk appetite and prioritizes prevention. In innovative settings, ICR accepts limited risks as long as they are identified early and controlled quickly. ICR’s operational context is constantly changing. Regulations evolve, cities introduce new environmental rules, and economic factors such as tariffs or sanctions may affect the business. To stay ahead, ICR continuously monitors these developments and adjusts its operations accordingly. To achieve this, the company relies on fast decision-making. Local teams and product groups can act independently within agreed principles and legal boundaries, allowing ICR to respond to customer needs and regulatory changes without delays. Compliance is an essential pillar of the governance model. Because requirements vary widely by region and service type, compliance responsibilities are distributed across the organization. Internal audit provides central oversight to ensure consistency and coherence using digital systems to standardize reporting and track evidence. ICR also serves a wide variety of stakeholders, ranging from city authorities to business clients and service partners. Their expectations differ by region, engagement approaches are adapted to local circumstances while staying aligned with ICR’s values and commitments. The company’s global reach demands broad governance oversight. Digital systems and processes are shared internationally but are tailored to each country’s regulations, customer behaviour, and available services. This combination helps ICR operate as a unified global brand while remaining locally relevant. Overall, ICR’s governance capabilities are well-established. Accountability is clear at board level, with defined responsibilities for central and local leaders. Regular audits and strong analytical tools support informed decision-making. As the company expands into new markets and introduces new mobility solutions, this governance foundation enables the company to grow responsibly, innovate confidently, and maintain a high standard of service for customers worldwide.

AI Governance:
Artificial Intelligence (AI) is increasingly embedded in ITIL Car Rental’s digital products and services. AI is used to support predictive maintenance, customer support, analytics, scheduling, and smart check-in and return processes. As ICR expands its service portfolio and geographic footprint, AI is expected to play a larger role in operational decision-making, customer experience, and service optimization. AI adoption creates new opportunities for ICR. AI-driven analytics can improve fleet utilization, sustainability performance, and cost efficiency. AI-enabled customer interaction can enhance responsiveness and personalization across markets. Automation and coordination capabilities can accelerate operational decisions and improve service reliability. These opportunities align with ICR’s strategic focus on digital experience, innovation, and sustainable growth. However, AI also introduces governance challenges. AI systems can act autonomously, operate at high speed, and learn over time, which challenges traditional approval-based decision structures. Risks related to explainability, bias, data protection, regulatory compliance, and accountability increase as AI influences customer-facing and safety-critical services. Differences in national regulation further complicate AI deployment across regions. ICR’s governance model combines clear global direction with local autonomy. The Board defines strategic objectives, risk appetite, and global principles, while local branches and service owners have flexibility in how they achieve outcomes within regulatory and legal boundaries. This governance pattern enables experimentation and innovation while maintaining compliance, consistency, and accountability. ICR’s existing governance both enables and constrains AI adoption. Strong compliance, audit, and risk management practices support trust and regulatory alignment but may slow adoption if applied too rigidly. Local autonomy supports innovation but requires stronger coordination to avoid fragmentation of AI practices and inconsistent customer experience. To address this, ICR is evolving its governance approach to AI. AI use cases are being classified by risk and impact, with governance intensity matched accordingly. Lower-risk AI solutions are enabled through local experimentation, while higher-risk applications require stronger oversight, clear accountability, explainability, and human-in-the-loop controls. Internal audit and reporting mechanisms are being extended to include AI-specific evidence and monitoring. Through this approach, ICR aims to enable responsible AI adoption that supports innovation, maintains trust, and aligns AI-enabled decisions with business objectives, regulatory requirements, and customer expectations.

Strategy:
ICR’s strategy centres on pioneering digital, sustainable mobility while growing globally and maintaining strong local responsiveness.

Vision statement:
“To be the world’s most trusted and innovative mobility partner, using digital technology and sustainable practices to enhance every journey for customers, wherever they travel.” This vision is realized through ICR’s strategy, which combines innovation, sustainability, a focus on customer experience, and sustainable growth. The company’s strategic direction has been transformed by the executive team into five strategic objectives, approved by the Board of Directors. Each objective has been further detailed into strategic initiatives. To implement these initiatives, many ICR teams will have to work together, involving external suppliers where additional resources and competencies are needed.

Objective 1: Lead in digital customer experience ICR aims to offer a seamless, app-first experience that makes renting, sharing, and returning vehicles effortless across all markets. Roll out a unified global mobile platform with localized features, languages, and payment options.
Embed AI-driven capabilities such as predictive maintenance, smart check-in/return, and proactive support into all core services. Establish continuous discovery and UX improvement cycles led by product and business analysis teams.

Objective 2: Innovate in autonomous and new mobility services ICR wants to be an early and trusted provider of self-driving and car-sharing services where regulations allow, integrating them into its mainstream portfolio. Launch regulated pilots for self-driving and car-sharing services in priority markets, starting with the US and expanding to EU and other markets. Build a standardized service design and safety framework for autonomous services, aligned with local laws and ICR’s low risk appetite in safety and data protection. Create joint innovation programmes between product, architecture, and operations to scale successful pilots globally.

Objective 3: Grow sustainably and profitably across markets ICR seeks to expand through franchising, mergers, and acquisitions while maintaining strong financial performance and customer loyalty. Maintain an up-to-date integration playbook covering governance, branding, systems, and supplier relationships for new acquisitions. Implement market- and service-level performance dashboards tracking revenue, market share, innovation progress, and customer satisfaction. Optimize fleet and cost structures using analytics to balance utilization, pricing, and sustainability targets.

Objective 4: Embed sustainability and social responsibility ICR intends to align its growth with environmental responsibility and evolving city and national regulations. Define clear sustainability targets (such as fleet emissions profile, use of EVs, or eco-options in the app) and report progress regularly. Cooperate with cities and regulators to adapt services to local environmental rules, parking policies, and low-emission zones. Design service offerings that reward sustainable choices, such as greener vehicle options or smarter routing.

Objective 5: Strengthen governance, risk, and capabilities ICR will maintain robust governance while allowing local autonomy, ensuring decisions are fast, compliant, and data-informed. Clarify and document global and local decision rights, principles, and escalation paths for all service lines. Enhance internal audit, compliance monitoring, and digital evidence-tracking across all countries and franchises. Invest in skills and certifications (ITIL, DevOps, data governance) for key roles such as CIO and office, product, delivery, and architecture. managers to support continual transformation.

Transformation:
ICR always looks for opportunities to expand the business to new markets. As part of this strategy, the company agreed an acquisition of a local rental company in a small, fast-developing country in Europe. The company being acquired has an established customer base and reputation in its home country. It is known in neighbouring countries, though it does not have branches in them. The government of the country where the company is based just passed a regulation approving use of self-diving vehicles, and ICR is keen to be the first provider of such a service in the region. The acquired company needs to be integrated into the ICR governance and management structure and information systems, including internal and customer-facing systems. The objective is to retain the existing customer base, provide reassurance that the acquisition will improve (rather than worsen) the quality of familiar rental services, and introduce new service lines (car-sharing, self-driving cars). The Board of Directors expects the integration to be completed within three months (including branding, information systems, governance, people, and relationships with local suppliers). ICR identified five transformational initiatives that need to be completed to fulfil the transformation:

1. Governance and structure integration ICR needs to integrate the acquired company into its existing governance model by aligning the local board reporting lines, decision rights, and accountability with ICR’s global principles, while preserving a high degree of local autonomy for market- and service-specific decisions. This includes defining how the local management team participates in ICR’s governance forums and how global policies, such as risk management and sustainability, are applied in the new country. ICR has gone through this many times and has an established playbook for governance and management integration, which proved to be effective during previous acquisitions.

2. Regulatory, risk, and compliance setup ICR must establish a comprehensive regulatory and compliance framework for the new market, with particular emphasis on the newly approved self-driving vehicle regulation and existing rules for rental and car-sharing services. This initiative should set up local controls and escalation paths consistent with ICR’s low risk appetite in safety, data protection, and traffic law. These controls and paths should be supported by internal audit oversight and appropriate reporting mechanisms. The company also has extensive experience in this area; however, every new country introduces new challenges which sometimes need to be addressed quickly.

3. Technology and platform integration ICR needs to migrate or integrate the acquired company’s systems into its global digital ecosystem, including customer-facing apps, booking platforms, fleet and maintenance systems, and analytics. During the transition period, ICR must ensure continuity of service for existing customers. AI-enabled capabilities such as predictive maintenance, smart check-in/return, and customer support should be progressively rolled out to the new operation, aligning with local regulations and infrastructure. Although the existing technology solutions of the acquired company were briefly assessed before the acquisition, there is a lot to explore, and the technology team should be ready for surprises.

4. Brand, customer, and stakeholder transition A coordinated rebranding and customer communication programme is required to transition the local brand to ICR within three months. This communication should clearly explain that familiar services will be maintained or improved and that new options like car-sharing and self-driving services will be introduced. In parallel, ICR should engage proactively with local authorities, business customers, partners, and suppliers to reinforce trust, clarity expectations, and position ICR as an innovative yet reliable mobility provider in the region. ICR has a playbook for such campaigns, but for it to be effective, detailed information about the customers, their expectations, and the ongoing relationships is needed.

5. Operating model, people, and service portfolio ICR should redesign the local operating model to match its global standards, including roles, responsibilities, and performance metrics, while retaining local knowledge and relationships that underpin the acquired company’s reputation. As part of this, the service portfolio in the new country should be structured to cover traditional rental, car-sharing, and self-driving services under a unified framework, with clear service ownership, targets for commercial performance and customer satisfaction, and mechanisms for rapid local decision-making. Although ICR has a large and positive experience of adapting the operating models of acquired companies, introduction of the self-driving cars to a new market is a new and challenging task. Together, these transformation efforts should allow ICR to enter the new region as a trusted, forward-looking mobility partner. Supported by strong governance, modern technology, and an effective integration approach, ICR is well positioned to deliver a reliable, future-ready travel experience to customers in its newest market.

Experience:
Understanding user experience as a strategic imperative
ICR recognizes that achieving a sustainable competitive advantage in modern mobility depends fundamentally on delivering exceptional user experience. Max articulated in his vision for the company that “customers want seamless and immediate access to rental services from their smartphones, as well as innovation as part of their daily lives.” This expectation applies not only to traditional car rental services but extends across the expanding portfolio of car-sharing and driverless tax offerings. The digital applications and web interfaces that customers interact with have become the primary touchpoints for the ICR brand, making digital experience inseparable from overall business success.
The customer journey across digital touchpoints
The user journey with ICR spans multiple critical steps, each mediated through digital applications and interfaces: Discovery and search begin when prospective customers evaluate their mobility options. Here, ICR’s digital presence must clearly communicate availability, pricing transparency, and service advantages over competitors, whether customers are considering traditional car rental, flexible car-sharing, or autonomous ride options. Registration and onboarding follow as users create profiles and establish trust with the platform. At this point they share their personal data, driving licence, and financial details with ICR. This makes this step particularly important for building trust and capturing customer preferences that will enhance future interactions. Selection and booking require intuitive navigation and clear presentation of options. The digital interface must accommodate the different decision-making patterns across the three service modes: the planning-focused car rental customer, the spontaneous car-sharing user, and the on-demand autonomous ride passenger. Payment processing must inspire confidence while remaining frictionless. Secure, flexible payment options that adapt to different service models strengthen customer trust and reduce transaction abandonment. This is a sensitive aspect of service interactions, as car rental users are often worried about unexpected security deposits, additional charges and costly insurance. Although this part of user journey often seems to be less important than the core service utility, it may have a significant and sometimes damaging impact on the overall experience. Check-in and vehicle access have evolved significantly with smart technologies. Digital applications now provide seamless vehicle access, reduced friction at pick-up, and immediate problem resolution when complications arise. In-journey support enables customers to address questions or concerns in real time.
Whether requesting roadside assistance, reporting issues, or seeking clarification, rapid response through integrated digital channels demonstrates the ICR’s commitment to the travel experience it has promised. Check-out and feedback close the transaction but open an opportunity for continual improvement. Digital interfaces capture usage data, soliciting feedback that informs service enhancements.
Differentiation across service models
While these touchpoints are universal, their expression differs significantly across ICR’s service offerings. Traditional car rental customers typically plan ahead, expecting detailed vehicle information and insurance clarity through structured booking flows. Car-sharing users demand spontaneity and simplicity, prioritizing booking speed and lock/unlock mechanisms. Driverless taxi passengers expect transparency about autonomous capabilities, safety systems, and real-time trip information without the complexity of vehicle selection.
Capturing, analysing, and improving user experience
Recognizing that understanding is a prerequisite to improvement, ICR has embedded experience measurement into the digital ecosystem. ICR applications capture behavioural data (interaction patterns, abandonment points, feature usage, and satisfaction signals), providing teams with rich insight into the customer journey and occurring points of friction.
This data flows into structured analysis processes. Maria, the Business Analyst, uses AI to identify patterns and trends that highlight experience bottlenecks and opportunities. Cross-functional collaboration between Anna’s product management, Sam’s product development oversight, and Omar’s service delivery team ensures that insights translate into rapid and noticeable improvements. The teams employ both quantitative metrics (completion rates, task duration, error frequency) and qualitative feedback mechanisms. Customer surveys, user testing sessions, and support interaction analysis combine with operational data to paint a complete picture of experience quality. Improvement cycles operate continuously, enabled by the ICR’s commitment to the end-to-end product and service lifecycle management and iterative development. The service enhancements are tested incrementally, which allows the teams to measure their impact and iterate rapidly. This approach ensures that ICR remains responsive to evolving customer expectations while maintaining the reliability and service quality that have defined the company’s reputation. By treating user experience as both a strategic priority and an operational discipline, ICR ensures that the company’s digital services serve their essential purpose: enabling customers to access mobility solutions effortlessly, building loyalty through consistent excellence, and positioning ICR as the thoughtful choice in an increasingly competitive and technologically sophisticated market.

Product:
ICR’s Unified Mobile App: A Product Lifecycle Journey
The challenge:
ITIL Car Rental’s vision for digital transformation demanded a bold move: consolidating traditional car rental, car-sharing, and emerging autonomous vehicle services into a single, seamless mobile application. This unified platform would serve millions of customers globally while adapting to diverse regulatory environments and local market conditions. The product team (led by Sam and guided by Anna’s product management expertise, Maria’s business analysis insight, and Alex’s architectural know-how) embarked on a comprehensive product lifecycle journey.

Discover: charting the course:
The team began by analysing the business context using the PESTLE method. Regulatory changes permitting autonomous vehicles in several markets, shifting customer expectations towards mobile-first experiences, and competitive pressures from ride-sharing services created both urgency and opportunity. Sam convened discovery sessions with stakeholders across the organization. Market analysis revealed fragmented customer expectations: traditional renters wanted clarity and planning capability; car-sharing users demanded spontaneity and speed; autonomous rice passengers expected transparency and trust. Maria identified critical patterns in user behaviour across regions, while Alex assessed the architectural implications of managing three distinct service models within a single platform. The team agreed strategic direction: create one app that intelligently presents rental, sharing, and autonomous options based on user context and local regulations. This vision was communicated across all product teams, establishing alignment and guiding subsequent activities. Investment in the initiative was secured, with clear timelines and resource commitments.

Design: shaping the experience:
Service design workshops brought together user research, human-centred design principles, and regulatory requirements. Anna led a detailed analysis of the customer journey across all three service models, identifying touchpoints, decision moments, and friction points. The design iterations incorporated feedback from early user testing. The team prototyped distinct user flows: a structured booking experience for renters planning days ahead; a rapid-access interface for car sharing users; and a transparent, safety-focused experience for autonomous ride passengers. Meanwhile, Alex developed target architecture blueprints ensuring that different service models could scale independently while sharing core infrastructure for authentication, payment, and support. Design specifications documented user interface, service interactions and operational requirements. The team designed for continuous improvement: metrics, feedback mechanisms, and analytics touchpoints were embedded into the design from the outset.

Acquire: securing resources:
With design specifications complete, the ‘acquire’ activity identified the required resources. Cloud infrastructure capable of handling peak demand across multiple regions; AI/machine learning services for predictive maintenance and smart routing; payment processing services compliant with regulations in each market; map and navigation services adapted to local conditions. The team assessed sourcing options, negotiating contracts with multiple cloud providers and service partners. Procurement was coordinated carefully to ensure integration readiness. Resource availability was confirmed before the ‘build’ phase began, preventing downstream delays.

Build: constructing the solution
The product development team, under Sam’s oversight, executed a phased build approach. The core app framework was developed first, establishing shared foundations for authentication, payment processing, and support channels. Feature teams then implemented the rental, sharing, and autonomous service modules in parallel, maintaining integration points and shared design patterns. Rigorous testing occurred throughout. Service validation teams ensured the app functioned flawlessly across devices, network conditions, and geographic regions. Integration testing verified that switching between service models felt seamless. Security testing confirmed compliance with data protection requirements in each market.
Supporting documentation, including user guides, service manuals, and operational runbooks, was developed alongside the software.

Transition: going live:
Before full launch, the team executed a carefully staged transition strategy. Soft launches in select markets allowed real users to interact with the new experience under controlled conditions. Omar, the IT Delivery Manager, coordinated the operational handover, ensuring monitoring systems captured live performance data and incident response procedures were operational. Supplier onboarding was critical: map service providers, payment processors, and cloud infrastructure teams needed to understand their roles in the live environment. Customer communication emphasized that familiar services would be enhanced, not disrupted. The team monitored the transition closely, ready to address any issues.

Operate: maintaining excellence:
With the app in live environments, the ‘operate’ activity ensured continuous, reliable performance. Infrastructure monitoring tracked application health, system performance, and availability across regions. The team managed routine updates, security patches, and scaling adjustments responding to demand fluctuations. Automated systems monitored performance metrics: response times, transaction completion rates, error frequencies.
When deviations appeared, such as unusual latency in a particular region or unexpected payment processing delays, alerts triggered investigation and rapid response.

Deliver: serving customers:
The ‘deliver’ activity brought the product to life for customers. Service delivery teams ensured seamless onboarding to new users, providing multiple languages, localized payment options, and support channels adapted to each market. Service level agreements committed to fast booking, reliable vehicle access, and responsive support. Customer service teams used the app’s built-in support features (in-app chat, knowledge bases, and contextual help) to address questions. Anna monitored service quality metrics and customer satisfaction indicators religiously. Usage patterns revealed which features resonated, where users abandoned workflows, and which regions had distinct preferences.

Support: resolving and learning:
Despite meticulous planning, incidents occurred. A payment processing outage in one market triggered rapid incident response: the support team engaged customers, offered alternatives, and restored service within hours.
When an unexpected interaction between autonomous ride features and local traffic regulations created user confusion, the team diagnosed the issue, implemented a fix, and deployed it to users within days. More importantly, each incident triggered investigation.
Why did it happen? What signals did we miss? How do we prevent recurrence? Post-mortem reviews informed improvements to both the app and the operational processes. Issues discovered in ‘support’ fed back into the ‘discover’ and ‘design’ cycles, continuously refining the product.

Continual improvement:
The journey from ‘discover’ to ‘support’ was not linear but cyclical. Feedback from ‘support’ informed new ‘discover’ iterations as market conditions evolved. Performance data from ‘operate’ fed into ‘deliver’ improvements. Customer insights from ‘deliver’ shaped strategic decisions about feature prioritization and regional adaptations. By embedding DPSM practices throughout this lifecycle, ICR’s unified mobile app became more than a technical achievement. It became a reflection of the company’s commitment to customers: reliable, innovative, responsive to local needs, and continuously improving. As Max envisioned, ITIL Car Rental had taken a bold step toward being the world’s most trusted mobility partner, delivering the vision through every customer interaction, every design decision, and every operational moment.

Service:
Implementing a global HR management service: an internal service lifecycle
The challenge:
ITIL Car Rental’s expansion across multiple regions and service lines created mounting complexity in workforce management. Different legal entities, varying employment regulations, localized payroll requirements, and regulatory compliance across jurisdictions had strained the company’s aging HR systems. The company’s executive team identified modernization of HR management services as essential to support ICR’s growth strategy whilst maintaining operational consistency and compliance across markets. Omar’s IT delivery team took ownership of implementing a new vendor-supplied HR management system, a solution that would run on ICR servers, integrate seamlessly with existing internal systems, and serve thousands of employees and contractors across dozens of countries.

Discover: understanding the landscape
The team began by organizing a comprehensive ‘discover’ iteration. Assessing the organizational context, the team analysed how ICR’s expansion strategy, new regulatory requirements in different markets, evolving workplace expectations, and the growing complexity of managing multiple legal entities across regions created both pressure and opportunity for modernization. Working closely with the HR business partner and Max’s office, Omar’s team gathered requirements from across the organization: HR representatives and business managers in each country, payroll departments, compliance officers, finance teams managing workforce costs, and executives overseeing the talent strategy. The discovery revealed critical patterns. European operations faced strict data protection and employment law requirements. Asia-Pacific branches needed sophisticated multi-currency payroll capabilities. The US and Canadian operations required integration with complex benefits administration systems. Every region needed consistency in talent management and performance tracking, yet each had distinct regulatory demands.
A business analyst from Omar’s team documented these needs systematically, whilst Alex, the Enterprise Architect, assessed the technical implications of supporting multiple legal entities, integrating with existing systems (payroll, finance, learning management, employee engagement platforms), and ensuring data security and regulatory compliance. The vendor’s product roadmap was evaluated against ICR’s requirements, revealing both strong alignment and specific gaps requiring customization. The team agreed on a clear direction: implement a core HR platform from a reputable software vendor as the system of record for employee master data, organizational structure, and talent management across all regions, while integrating specialized capabilities for payroll, benefits, compliance reporting, and data protection. Investment was secured with realistic timelines accounting for the complexity of multi-region deployment, and a formal steering committee was established to guide implementation.

Design: defining the solution:
With requirements agreed, Omar’s team began detailed design activities. Service design workshops brought together local HR representatives, payroll specialists, compliance officers, and technology architects. The team mapped existing HR processes in each region, identifying which would be standardized globally and which would require local customization. Design workshops revealed critical service interactions. HR teams needed intuitive interfaces for managing recruitment, onboarding, performance management, and learning across different employment models. Employees required easy access to personal information, benefits enrolment, and career development features. Payroll teams needed reliable data integration with local accounting systems and regulatory reporting tools. Compliance officers required audit trails, secure data management, and reporting to meet legal obligations in each jurisdiction. Alex developed detailed integration architecture, specifying how the HR system would communicate with existing payroll, finance, learning management, and employee engagement platforms. Data flows were mapped, ensuring that changes in one system were reliably distributed to dependent systems without manual intervention or data errors. Security and data protection requirements were designed into every integration point; this was particularly critical given GDPR, CCPA, and local data residency requirements. Data migration became one of the key design points. The team designed a phased deployment approach: implementation across ICR headquarters first, then staged rollout to major regional clusters, enabling learning and refinement before full global deployment. Supporting documentation, such as user guides for different roles, migration playbooks, and integration manuals, was planned in detail.

Acquire: securing resources:
With design specifications complete, Omar’s team identified required resources. The vendor’s licensing model (supporting anticipated growth); implementation consultant expertise (to guide customization and deployment); cloud infrastructure capacity for testing and staging environments; integration middleware (to connect the new HR system with existing enterprise systems); and data migration tools were all specified. The ‘acquire’ activity involved careful sourcing decisions. The vendor partnership was formalized, establishing support levels (the vendor providing third-line support, with first-line and specialist support to be provided by Omar’s team). External systems integrators with expertise in the vendor’s platform and multi-region HR implementations were evaluated and contracted. Cloud infrastructure capacity was procured, allowing for future growth. Service agreements included service level commitments and compliance obligations aligned with ICR’s governance standards. Resources were also identified internally: team members who would receive specialized training to support the system; members of Omar’s operations team who would provide day-to-day administration; security and compliance specialists to oversee implementation controls. Procurement was coordinated to ensure availability ahead of the ‘build’ phase.

Build: constructing the solution
Omar’s team established an implementation program, structured as a series of building activities. First, the core HR system was configured to match ICR’s organizational structure, employment classifications, and role hierarchies. Configuration activities addressed fundamental requirements: multi-legal entity support, multi-language and multi-currency capabilities, and foundational data structures. Parallel to core configuration, integration development began. The team, supported by the vendor and a vendor’s consulting partner, configured data flows from the HR system to payroll systems, ensuring employee changes (salary adjustments, location changes, benefits modifications) flowed reliably to payroll processing. Integration with the finance system ensured workforce costs were accurately captured. Learning management system connections ensured course assignments and certifications were synchronized. Security and compliance controls were embedded throughout, including audit logging, data encryption, access controls, and automated reporting for regulatory requirements. Extensive testing occurred throughout the ‘build’ phase. Functional testing verified that each configuration matched requirements. Integration testing validated that data flowed correctly between systems without errors or data loss. Security testing confirmed that sensitive personal data was protected and that access controls functioned as designed. Business process testing involved HR teams walking through common scenarios (such as hiring a new employee, transferring someone to a different country, or managing a separation), ensuring the system supported the complete workflow. User acceptance testing engaged representatives from different regions and roles. HR teams in Germany tested GDPR compliance features. Payroll teams in multiple countries verified that their specific regulatory requirements were met. Local compliance officers confirmed that reporting would support local legal obligations. Supporting documentation, such as operational runbooks for system administration, user guides tailored to different roles, and troubleshooting guides, was developed and reviewed. Apart from the HR teams, selected users from all affected teams were involved, testing the interfaces and workflows for requesting leave, conducting assessments, reserving training, of reporting HR incidents. These tests revealed the need for end-user training and onboarding during the new service roll-out. Transition plans were updated to allow time for this.

Transition: going live:
The team carefully prepared a transition strategy. Headquarters implementation was planned first, serving as a dress rehearsal. A parallel run, with both old and new systems operating simultaneously, was conducted for three weeks, allowing both systems to process payroll and generate reports for comparison. The payroll teams validated that the new system calculated amounts identically to the legacy system, detecting and resolving discrepancies before they affected employees. Omar coordinated the preparation activities. User training was delivered to HR teams, payroll specialists, managers, and employees. Help desks were staffed and trained. Communication plans explained the transition to all users, emphasizing continuity of services and highlighting new capabilities. Vendor support teams were onboarded, understanding their roles during the transition period. Data migration, which involved extracting employee master data from legacy systems, cleansing it, loading it into the new system, and validating completeness and accuracy, was carefully orchestrated and verified. Transition day at headquarters was carefully planned. The legacy system was frozen at a specific point, a final data extract was taken, loaded into the new system, and system access was switched over. The team remained staffed throughout the transition and into the following week, monitoring system performance closely, responding to questions, and resolving issues. Incident response procedures were in place, with escalation paths to the vendor’s support team available if needed. Following successful headquarters transition, the team planned regional deployments. Each regional cluster (Europe, Asia-Pacific, Americas) had a transition period, with lessons from earlier transitions incorporated and local considerations addressed. The staggered approach allowed the central team to support each region and enabled best practices to propagate from early transitions to later ones.

Operate: maintaining excellence:
With the system live across regions, Omar’s team shifted focus to reliable operations. Infrastructure monitoring tracked system health, performance, and availability across all deployment sites. Automated health checks, such as database integrity tests, integration validation, and backup verification, ran daily, alerting the team to any deviations from expected operation. The team established routine operational activities: security patches supplied by the vendor were tested in staging environments, then deployed to production overnight. Data backups were performed daily, with regular restoration tests confirming that recovery was possible. System performance was monitored, with growth projections ensuring sufficient capacity as employee counts increased. User access was reviewed every week, ensuring that accounts of employees that had left the company were promptly deactivated and that role changes were reflected in system permissions.
When issues appeared, monitoring detected these deviations and triggered investigation. The team maintained a problem backlog, working with the vendor to address underlying issues and implementing fixes or workarounds as appropriate.

Deliver: serving the organization
The ‘deliver’ activity brought the HR system into daily organizational use. Omar’s team established service level commitments: HR teams would have to access to the system 99.5% of the time; user support queries would be acknowledged within four hours; critical issues affecting payroll or compliance would be resolved within eight hours. The team was constrained by the respective commitments of the vendor and, although in many cases a higher service level was provided, it could not be formally committed to. A first-line support team knowledgeable about ICR’s specific configuration and trained on common issues responded to user questions. A knowledge base captured solutions to frequent issues, enabling self-service support. Employees received training on using the service: how to access their information, update personal details, enrol in benefits, and request time off through the HR portal. Delivery included routine service actions: onboarding new employees to the system (ensuring they were created with appropriate access and initial data); offboarding departing employees (deactivating access, generating final pay calculations, archiving records); managing organizational changes (updating reporting structures when teams were reorganized); conducting benefits enrolment campaigns (ensuring employees could select and modify coverage). The team monitored delivery metrics carefully: system availability, user satisfaction (gathered through surveys), processing timeliness (time from employee action to system reflection), and error rates (incorrect calculations, missing data). Service level reporting informed ongoing improvements and triggered escalations if service quality threatened to fall below the agreed level.

Support: resolving and learning:
Despite robust operational procedures, incidents occurred. A payroll integration process failed one month due to an unexpected data format in the finance system, causing a four-hour delay in the payroll. The support team immediately engaged payroll managers, communicating the issue and estimated resolution time. The technical team worked with the finance team and the vendor to understand the root cause, developed a fix to handle the unexpected data format, implemented the fix, reran the integration process, and verified accuracy. By the end of the day, normal payroll processing resumed. On another occasion, a regional compliance officer discovered that a localized tax calculation in one country was producing results that didn’t align with current regulations. The incident was escalated to the vendor’s specialist support team. Together, they analysed the regulation change, determined that a configuration parameter needed adjustment, updated the system, revalidated historical calculations, and rolled forward with correct calculations prospectively. Each incident triggered a post-mortem review, where the support team asked: why did the issue occur? Were there warning signs we missed? How do we prevent recurrence? Findings from post-mortems informed improvements to configuration, integration design, monitoring, documentation, and training. Particularly significant improvements, such as enhanced validation of finance system data before processing payroll, were incorporated into the ‘discover’ and ‘design’ phases to shape future improvements.

Continual improvement:
The journey from ‘discover’ to ‘support’ was cyclical. Feedback from ‘support’, including new issues and lessons learned, informed new ‘discover’ iterations as regulations evolved, ICR’s business expanded into new markets, or new compliance requirements emerged. Performance data from ‘operate’ informed design improvements when system bottlenecks were identified or user experience could be enhanced. User feedback from ‘deliver’, captured through surveys and support interactions, shaped priorities for new features and refinements.
When HR teams requested better reporting capabilities to support talent analytics, this feedback was captured, evaluated during ‘discover’ activities, and prioritized in design cycles. By embedding DPSM practices throughout this lifecycle, Omar’s team transformed HR management at ITIL Car Rental.
What had been a patchwork of legacy systems and manual processes became a unified, reliable platform supporting the company’s global growth. Compliance risks were reduced through automation and audit trails. HR teams gained visibility into workforce data and could respond quickly to business needs. Employees had instant access to their information and could manage their own preferences. The system provided a foundation for HR analytics, enabling data-driven decisions about talent, compensation, and organizational structure. As Max envisioned, ICR’s transformation extended beyond customer-facing products to the internal systems and processes that enabled the company to operate effectively. By treating internal HR services with the same rigor and discipline as external products, Omar’s team ensured that ITIL Car Rental’s greatest asset, its people, were supported by systems as reliable, responsive, and capable as the mobility services ICR offered to customers worldwide. Please refer to the ITIL Car Rental scenario for additional context when answering this question. ICR is launching a transformation to standardize processes across its regions and branches. The assessment shows high integration requirements, high stakeholder diversity, and the need for structured coordination across workstreams. Based on this, the organization applies the coordinated autonomy governance pattern. Is coordinated autonomy the right governance pattern?

  1. Yes, because high integration and diverse stakeholders require structured coordination while allowing local execution
  2. Yes, because it gives complete freedom to teams without any structured oversight
  3. No, the organization should use organic evolution since high structure is not required
  4. No, dedicated command should be used because any cross-department work always needs centralized authority

Answer(s): A



Introduction to ITIL Car Rental:
Ten years ago, ITIL Car Rental (ICR) was launched in Seattle with the aim to provide convenient and affordable rental cars to customers around the world. After a relatively short time, ICR became a globally recognized company, with a wide network of franchising partners across Europe, the US, and Asia-Pacific, with approximately 400 direct employees. In the first few years of operation, repeat business accounted for nearly a third of all reservations. Shareholders saw steady growth, and the company earned a reputation for putting customers first. ICR quickly became a model of modern mobility: fast, reliable, and profitable. Following its early success, the company expanded through mergers and acquisitions to new markets and new services, including car sharing. ICR relies heavily on digital technology for internal operations and service delivery, using a mix of internal and external digital products. Customer-facing mobile applications are developed and run by the internal IT team. AI is increasingly used in internal and external products and services for predictive maintenance, customer support, scheduling, smart check-in and return processes, and so on.
As new competitors, such as car-sharing services, rideshare apps, and driverless cars, enter the market, customers now expect a seamless digital experience: quick bookings, app-based help, and flexible options that fit easily into their daily lives. At the same time, customers are paying more attention to companies that value social responsibility, sustainability, and environmental consciousness. These expectations are driving ICR to set clear and ambitious sustainability goals, as well as pursue further growth. The board members strongly believe that the company’s success in the years to come will be defined by innovation and the use of digital technology. For this reason, they appointed a new GIO, Max. Max was chosen for his experience in digitalization and his track record in successful, large-scale IT transformations. Max’s strong background in ITIL and ITSM indicates that he values ITIL certification, and his hiring policy reflects this. Having worked with Design Thinking, DevOps, and agile methods, he believes sustainable business requires a blended approach to digital product and service management. Max is keen to see how his team can redefine the car rental experience and ensure that ICR is the first choice for new and existing customers.

Meet the employees of ITIL Car Rental:
Max, Chief Information Officer (CIO):
Max is the new CIO. He is an experienced executive with a track record of leading digital transformations. He believes in an integrated approach to DPSM.

Anna, Product Manager:
Anna has been with ITIL Car Rental for five years. She focuses on commercial success and continual B2C development. She is detail-oriented, eco-conscious, and dedicated to improving overall customer experience.

Maria, Business Analyst:
Maria is a proactive communicator who ensures smooth collaboration between IT and business teams. She works mostly on discovery and planning activities, supporting continual improvement of the company’s digital products. She asks a lot of questions and is great at spotting patterns and trends.

Omar, IT Delivery Manager:
Omar manages ongoing service delivery. He applies ITIL practices to improve efficiency and customer satisfaction. However, Omar has had little experience with a blended or collaborative approach to product and service management.

Sam, Head of Product Development:
Sam has more than 10 years of experience in leading cross-functional product teams in the domains of mobility and automotive innovation. He oversees the entire product lifecycle at ITIL Car Rental from strategic vision to delivery and ensures that customer needs, market trends, and sustainability are all in sync.

Alex, Enterprise Architect:
Alex is responsible for ensuring that product design and technological strategy are aligned, sustainable, and future-proof. She provides architectural guidance across teams, works to identify systemic risks, and holds coherence in a fast-changing digital ecosystem. She is highly analytical with a strong intuition for patterns and risks.

The CIO’s vision for ITIL Car Rental Max:
We live in an era of rapid change, where all companies are going through some kind of digital transformation. Service expectations have changed drastically since ITIL Car Rental was created 10 years ago. Customers want seamless and immediate access to rental services from their smartphones, as well as innovation as part of their daily lives. Autonomous vehicles are the future; they will make car rental companies stand out and continue successfully. My vision is for ITIL Car Rental to pioneer this transformation and become the go-to name for car rentals worldwide. We will continue offering outstanding customer service while maintaining competitive car rental rates. After all, ITIL Car Rental is more than just a service. We are here to enhance the entire travel experience.

Governance:
ITIL Car Rental has branches in other countries, some of which are franchises. Each country may have its own regulations when it comes to the services offered by ICR. Although all services are focused on enhancing the entire travel experience, different services may be subjects to different regulation. For example, car-sharing is regulated differently, and self-driving cars cannot be introduced at all in some countries. ICR has adopted a governance approach that blends clear global direction with local autonomy, enabling the company to stay competitive in a fast-moving mobility landscape. As ICR continues to grow across regions and expand its portfolio, moving from traditional rentals to car-sharing and self-driving services, its governance structure ensures consistency, compliance, and customer-focused innovation. ICR’s approach to change is practical and adaptive. The company encourages experimentation and continual improvement as long as new ideas follow shared principles and meet regulatory expectations in each market. This balanced approach helps ICR introduce new digital features quickly while maintaining trust and reliability. The Board evaluates progress through a focused set of indicators, including commercial results, market share, innovation outcomes, cost efficiency, and customer satisfaction. Coordinated autonomy is a key feature of ICR’s governance.
While the Board defines the overall vision and strategic direction, local branches and service owners have freedom in how they achieve their goals. Market leaders and service-line managers work closely to tailor solutions to regional needs, ensuring that global standards remain compatible with local realities. Risk management reflects the diverse environments in which the company operates. Within heavily regulated domains, such as safety, traffic rules, and data protection, the company maintains a very low risk appetite and prioritizes prevention. In innovative settings, ICR accepts limited risks as long as they are identified early and controlled quickly. ICR’s operational context is constantly changing. Regulations evolve, cities introduce new environmental rules, and economic factors such as tariffs or sanctions may affect the business. To stay ahead, ICR continuously monitors these developments and adjusts its operations accordingly. To achieve this, the company relies on fast decision-making. Local teams and product groups can act independently within agreed principles and legal boundaries, allowing ICR to respond to customer needs and regulatory changes without delays. Compliance is an essential pillar of the governance model. Because requirements vary widely by region and service type, compliance responsibilities are distributed across the organization. Internal audit provides central oversight to ensure consistency and coherence using digital systems to standardize reporting and track evidence. ICR also serves a wide variety of stakeholders, ranging from city authorities to business clients and service partners. Their expectations differ by region, engagement approaches are adapted to local circumstances while staying aligned with ICR’s values and commitments. The company’s global reach demands broad governance oversight. Digital systems and processes are shared internationally but are tailored to each country’s regulations, customer behaviour, and available services. This combination helps ICR operate as a unified global brand while remaining locally relevant. Overall, ICR’s governance capabilities are well-established. Accountability is clear at board level, with defined responsibilities for central and local leaders. Regular audits and strong analytical tools support informed decision-making. As the company expands into new markets and introduces new mobility solutions, this governance foundation enables the company to grow responsibly, innovate confidently, and maintain a high standard of service for customers worldwide.

AI Governance:
Artificial Intelligence (AI) is increasingly embedded in ITIL Car Rental’s digital products and services. AI is used to support predictive maintenance, customer support, analytics, scheduling, and smart check-in and return processes. As ICR expands its service portfolio and geographic footprint, AI is expected to play a larger role in operational decision-making, customer experience, and service optimization. AI adoption creates new opportunities for ICR. AI-driven analytics can improve fleet utilization, sustainability performance, and cost efficiency. AI-enabled customer interaction can enhance responsiveness and personalization across markets. Automation and coordination capabilities can accelerate operational decisions and improve service reliability. These opportunities align with ICR’s strategic focus on digital experience, innovation, and sustainable growth. However, AI also introduces governance challenges. AI systems can act autonomously, operate at high speed, and learn over time, which challenges traditional approval-based decision structures. Risks related to explainability, bias, data protection, regulatory compliance, and accountability increase as AI influences customer-facing and safety-critical services. Differences in national regulation further complicate AI deployment across regions. ICR’s governance model combines clear global direction with local autonomy. The Board defines strategic objectives, risk appetite, and global principles, while local branches and service owners have flexibility in how they achieve outcomes within regulatory and legal boundaries. This governance pattern enables experimentation and innovation while maintaining compliance, consistency, and accountability. ICR’s existing governance both enables and constrains AI adoption. Strong compliance, audit, and risk management practices support trust and regulatory alignment but may slow adoption if applied too rigidly. Local autonomy supports innovation but requires stronger coordination to avoid fragmentation of AI practices and inconsistent customer experience. To address this, ICR is evolving its governance approach to AI. AI use cases are being classified by risk and impact, with governance intensity matched accordingly. Lower-risk AI solutions are enabled through local experimentation, while higher-risk applications require stronger oversight, clear accountability, explainability, and human-in-the-loop controls. Internal audit and reporting mechanisms are being extended to include AI-specific evidence and monitoring. Through this approach, ICR aims to enable responsible AI adoption that supports innovation, maintains trust, and aligns AI-enabled decisions with business objectives, regulatory requirements, and customer expectations.

Strategy:
ICR’s strategy centres on pioneering digital, sustainable mobility while growing globally and maintaining strong local responsiveness.

Vision statement:
“To be the world’s most trusted and innovative mobility partner, using digital technology and sustainable practices to enhance every journey for customers, wherever they travel.” This vision is realized through ICR’s strategy, which combines innovation, sustainability, a focus on customer experience, and sustainable growth. The company’s strategic direction has been transformed by the executive team into five strategic objectives, approved by the Board of Directors. Each objective has been further detailed into strategic initiatives. To implement these initiatives, many ICR teams will have to work together, involving external suppliers where additional resources and competencies are needed.

Objective 1: Lead in digital customer experience ICR aims to offer a seamless, app-first experience that makes renting, sharing, and returning vehicles effortless across all markets. Roll out a unified global mobile platform with localized features, languages, and payment options. Embed AI-driven capabilities such as predictive maintenance, smart check-in/return, and proactive support into all core services.
Establish continuous discovery and UX improvement cycles led by product and business analysis teams.

Objective 2: Innovate in autonomous and new mobility services ICR wants to be an early and trusted provider of self-driving and car-sharing services where regulations allow, integrating them into its mainstream portfolio. Launch regulated pilots for self-driving and car-sharing services in priority markets, starting with the US and expanding to EU and other markets. Build a standardized service design and safety framework for autonomous services, aligned with local laws and ICR’s low risk appetite in safety and data protection. Create joint innovation programmes between product, architecture, and operations to scale successful pilots globally.

Objective 3: Grow sustainably and profitably across markets ICR seeks to expand through franchising, mergers, and acquisitions while maintaining strong financial performance and customer loyalty. Maintain an up-to-date integration playbook covering governance, branding, systems, and supplier relationships for new acquisitions. Implement market- and service-level performance dashboards tracking revenue, market share, innovation progress, and customer satisfaction. Optimize fleet and cost structures using analytics to balance utilization, pricing, and sustainability targets.

Objective 4: Embed sustainability and social responsibility ICR intends to align its growth with environmental responsibility and evolving city and national regulations. Define clear sustainability targets (such as fleet emissions profile, use of EVs, or eco-options in the app) and report progress regularly. Cooperate with cities and regulators to adapt services to local environmental rules, parking policies, and low-emission zones. Design service offerings that reward sustainable choices, such as greener vehicle options or smarter routing.

Objective 5: Strengthen governance, risk, and capabilities ICR will maintain robust governance while allowing local autonomy, ensuring decisions are fast, compliant, and data-informed. Clarify and document global and local decision rights, principles, and escalation paths for all service lines. Enhance internal audit, compliance monitoring, and digital evidence-tracking across all countries and franchises. Invest in skills and certifications (ITIL, DevOps, data governance) for key roles such as CIO and office, product, delivery, and architecture. managers to support continual transformation.

Transformation:
ICR always looks for opportunities to expand the business to new markets. As part of this strategy, the company agreed an acquisition of a local rental company in a small, fast-developing country in Europe. The company being acquired has an established customer base and reputation in its home country. It is known in neighbouring countries, though it does not have branches in them. The government of the country where the company is based just passed a regulation approving use of self-diving vehicles, and ICR is keen to be the first provider of such a service in the region. The acquired company needs to be integrated into the ICR governance and management structure and information systems, including internal and customer-facing systems. The objective is to retain the existing customer base, provide reassurance that the acquisition will improve (rather than worsen) the quality of familiar rental services, and introduce new service lines (car-sharing, self-driving cars). The Board of Directors expects the integration to be completed within three months (including branding, information systems, governance, people, and relationships with local suppliers). ICR identified five transformational initiatives that need to be completed to fulfil the transformation:

1. Governance and structure integration ICR needs to integrate the acquired company into its existing governance model by aligning the local board reporting lines, decision rights, and accountability with ICR’s global principles, while preserving a high degree of local autonomy for market- and service-specific decisions. This includes defining how the local management team participates in ICR’s governance forums and how global policies, such as risk management and sustainability, are applied in the new country. ICR has gone through this many times and has an established playbook for governance and management integration, which proved to be effective during previous acquisitions.

2. Regulatory, risk, and compliance setup ICR must establish a comprehensive regulatory and compliance framework for the new market, with particular emphasis on the newly approved self-driving vehicle regulation and existing rules for rental and car-sharing services. This initiative should set up local controls and escalation paths consistent with ICR’s low risk appetite in safety, data protection, and traffic law. These controls and paths should be supported by internal audit oversight and appropriate reporting mechanisms. The company also has extensive experience in this area; however, every new country introduces new challenges which sometimes need to be addressed quickly.

3. Technology and platform integration ICR needs to migrate or integrate the acquired company’s systems into its global digital ecosystem, including customer-facing apps, booking platforms, fleet and maintenance systems, and analytics. During the transition period, ICR must ensure continuity of service for existing customers. AI-enabled capabilities such as predictive maintenance, smart check-in/return, and customer support should be progressively rolled out to the new operation, aligning with local regulations and infrastructure. Although the existing technology solutions of the acquired company were briefly assessed before the acquisition, there is a lot to explore, and the technology team should be ready for surprises.

4. Brand, customer, and stakeholder transition A coordinated rebranding and customer communication programme is required to transition the local brand to ICR within three months. This communication should clearly explain that familiar services will be maintained or improved and that new options like car-sharing and self-driving services will be introduced. In parallel, ICR should engage proactively with local authorities, business customers, partners, and suppliers to reinforce trust, clarity expectations, and position ICR as an innovative yet reliable mobility provider in the region. ICR has a playbook for such campaigns, but for it to be effective, detailed information about the customers, their expectations, and the ongoing relationships is needed.

5. Operating model, people, and service portfolio ICR should redesign the local operating model to match its global standards, including roles, responsibilities, and performance metrics, while retaining local knowledge and relationships that underpin the acquired company’s reputation. As part of this, the service portfolio in the new country should be structured to cover traditional rental, car-sharing, and self-driving services under a unified framework, with clear service ownership, targets for commercial performance and customer satisfaction, and mechanisms for rapid local decision-making. Although ICR has a large and positive experience of adapting the operating models of acquired companies, introduction of the self-driving cars to a new market is a new and challenging task. Together, these transformation efforts should allow ICR to enter the new region as a trusted, forward-looking mobility partner. Supported by strong governance, modern technology, and an effective integration approach, ICR is well positioned to deliver a reliable, future-ready travel experience to customers in its newest market.

Experience:
Understanding user experience as a strategic imperative
ICR recognizes that achieving a sustainable competitive advantage in modern mobility depends fundamentally on delivering exceptional user experience. Max articulated in his vision for the company that “customers want seamless and immediate access to rental services from their smartphones, as well as innovation as part of their daily lives.” This expectation applies not only to traditional car rental services but extends across the expanding portfolio of car-sharing and driverless tax offerings. The digital applications and web interfaces that customers interact with have become the primary touchpoints for the ICR brand, making digital experience inseparable from overall business success.
The customer journey across digital touchpoints
The user journey with ICR spans multiple critical steps, each mediated through digital applications and interfaces: Discovery and search begin when prospective customers evaluate their mobility options. Here, ICR’s digital presence must clearly communicate availability, pricing transparency, and service advantages over competitors, whether customers are considering traditional car rental, flexible car-sharing, or autonomous ride options. Registration and onboarding follow as users create profiles and establish trust with the platform. At this point they share their personal data, driving licence, and financial details with ICR. This makes this step particularly important for building trust and capturing customer preferences that will enhance future interactions. Selection and booking require intuitive navigation and clear presentation of options. The digital interface must accommodate the different decision-making patterns across the three service modes: the planning-focused car rental customer, the spontaneous car-sharing user, and the on-demand autonomous ride passenger. Payment processing must inspire confidence while remaining frictionless. Secure, flexible payment options that adapt to different service models strengthen customer trust and reduce transaction abandonment. This is a sensitive aspect of service interactions, as car rental users are often worried about unexpected security deposits, additional charges and costly insurance. Although this part of user journey often seems to be less important than the core service utility, it may have a significant and sometimes damaging impact on the overall experience. Check-in and vehicle access have evolved significantly with smart technologies. Digital applications now provide seamless vehicle access, reduced friction at pick-up, and immediate problem resolution when complications arise. In-journey support enables customers to address questions or concerns in real time.
Whether requesting roadside assistance, reporting issues, or seeking clarification, rapid response through integrated digital channels demonstrates the ICR’s commitment to the travel experience it has promised. Check-out and feedback close the transaction but open an opportunity for continual improvement. Digital interfaces capture usage data, soliciting feedback that informs service enhancements.
Differentiation across service models
While these touchpoints are universal, their expression differs significantly across ICR’s service offerings. Traditional car rental customers typically plan ahead, expecting detailed vehicle information and insurance clarity through structured booking flows. Car-sharing users demand spontaneity and simplicity, prioritizing booking speed and lock/unlock mechanisms. Driverless taxi passengers expect transparency about autonomous capabilities, safety systems, and real-time trip information without the complexity of vehicle selection.
Capturing, analysing, and improving user experience
Recognizing that understanding is a prerequisite to improvement, ICR has embedded experience measurement into the digital ecosystem. ICR applications capture behavioural data (interaction patterns, abandonment points, feature usage, and satisfaction signals), providing teams with rich insight into the customer journey and occurring points of friction. This data flows into structured analysis processes. Maria, the Business Analyst, uses AI to identify patterns and trends that highlight experience bottlenecks and opportunities. Cross-functional collaboration between Anna’s product management, Sam’s product development oversight, and Omar’s service delivery team ensures that insights translate into rapid and noticeable improvements. The teams employ both quantitative metrics (completion rates, task duration, error frequency) and qualitative feedback mechanisms. Customer surveys, user testing sessions, and support interaction analysis combine with operational data to paint a complete picture of experience quality. Improvement cycles operate continuously, enabled by the ICR’s commitment to the end-to-end product and service lifecycle management and iterative development. The service enhancements are tested incrementally, which allows the teams to measure their impact and iterate rapidly. This approach ensures that ICR remains responsive to evolving customer expectations while maintaining the reliability and service quality that have defined the company’s reputation. By treating user experience as both a strategic priority and an operational discipline, ICR ensures that the company’s digital services serve their essential purpose: enabling customers to access mobility solutions effortlessly, building loyalty through consistent excellence, and positioning ICR as the thoughtful choice in an increasingly competitive and technologically sophisticated market.

Product:
ICR’s Unified Mobile App: A Product Lifecycle Journey
The challenge:
ITIL Car Rental’s vision for digital transformation demanded a bold move: consolidating traditional car rental, car-sharing, and emerging autonomous vehicle services into a single, seamless mobile application. This unified platform would serve millions of customers globally while adapting to diverse regulatory environments and local market conditions. The product team (led by Sam and guided by Anna’s product management expertise, Maria’s business analysis insight, and Alex’s architectural know-how) embarked on a comprehensive product lifecycle journey.

Discover: charting the course:
The team began by analysing the business context using the PESTLE method. Regulatory changes permitting autonomous vehicles in several markets, shifting customer expectations towards mobile-first experiences, and competitive pressures from ride-sharing services created both urgency and opportunity. Sam convened discovery sessions with stakeholders across the organization. Market analysis revealed fragmented customer expectations: traditional renters wanted clarity and planning capability; car-sharing users demanded spontaneity and speed; autonomous rice passengers expected transparency and trust. Maria identified critical patterns in user behaviour across regions, while Alex assessed the architectural implications of managing three distinct service models within a single platform. The team agreed strategic direction: create one app that intelligently presents rental, sharing, and autonomous options based on user context and local regulations. This vision was communicated across all product teams, establishing alignment and guiding subsequent activities. Investment in the initiative was secured, with clear timelines and resource commitments.

Design: shaping the experience:
Service design workshops brought together user research, human-centred design principles, and regulatory requirements. Anna led a detailed analysis of the customer journey across all three service models, identifying touchpoints, decision moments, and friction points. The design iterations incorporated feedback from early user testing. The team prototyped distinct user flows: a structured booking experience for renters planning days ahead; a rapid-access interface for car sharing users; and a transparent, safety-focused experience for autonomous ride passengers. Meanwhile, Alex developed target architecture blueprints ensuring that different service models could scale independently while sharing core infrastructure for authentication, payment, and support. Design specifications documented user interface, service interactions and operational requirements. The team designed for continuous improvement: metrics, feedback mechanisms, and analytics touchpoints were embedded into the design from the outset.

Acquire: securing resources:
With design specifications complete, the ‘acquire’ activity identified the required resources. Cloud infrastructure capable of handling peak demand across multiple regions; AI/machine learning services for predictive maintenance and smart routing; payment processing services compliant with regulations in each market; map and navigation services adapted to local conditions. The team assessed sourcing options, negotiating contracts with multiple cloud providers and service partners. Procurement was coordinated carefully to ensure integration readiness. Resource availability was confirmed before the ‘build’ phase began, preventing downstream delays.

Build: constructing the solution
The product development team, under Sam’s oversight, executed a phased build approach. The core app framework was developed first, establishing shared foundations for authentication, payment processing, and support channels. Feature teams then implemented the rental, sharing, and autonomous service modules in parallel, maintaining integration points and shared design patterns. Rigorous testing occurred throughout. Service validation teams ensured the app functioned flawlessly across devices, network conditions, and geographic regions. Integration testing verified that switching between service models felt seamless. Security testing confirmed compliance with data protection requirements in each market. Supporting documentation, including user guides, service manuals, and operational runbooks, was developed alongside the software.
Transition: going live:
Before full launch, the team executed a carefully staged transition strategy. Soft launches in select markets allowed real users to interact with the new experience under controlled conditions. Omar, the IT Delivery Manager, coordinated the operational handover, ensuring monitoring systems captured live performance data and incident response procedures were operational. Supplier onboarding was critical: map service providers, payment processors, and cloud infrastructure teams needed to understand their roles in the live environment. Customer communication emphasized that familiar services would be enhanced, not disrupted. The team monitored the transition closely, ready to address any issues.

Operate: maintaining excellence:
With the app in live environments, the ‘operate’ activity ensured continuous, reliable performance. Infrastructure monitoring tracked application health, system performance, and availability across regions. The team managed routine updates, security patches, and scaling adjustments responding to demand fluctuations. Automated systems monitored performance metrics: response times, transaction completion rates, error frequencies.
When deviations appeared, such as unusual latency in a particular region or unexpected payment processing delays, alerts triggered investigation and rapid response.

Deliver: serving customers:
The ‘deliver’ activity brought the product to life for customers. Service delivery teams ensured seamless onboarding to new users, providing multiple languages, localized payment options, and support channels adapted to each market. Service level agreements committed to fast booking, reliable vehicle access, and responsive support. Customer service teams used the app’s built-in support features (in-app chat, knowledge bases, and contextual help) to address questions. Anna monitored service quality metrics and customer satisfaction indicators religiously. Usage patterns revealed which features resonated, where users abandoned workflows, and which regions had distinct preferences.

Support: resolving and learning:
Despite meticulous planning, incidents occurred. A payment processing outage in one market triggered rapid incident response: the support team engaged customers, offered alternatives, and restored service within hours.
When an unexpected interaction between autonomous ride features and local traffic regulations created user confusion, the team diagnosed the issue, implemented a fix, and deployed it to users within days. More importantly, each incident triggered investigation.
Why did it happen? What signals did we miss? How do we prevent recurrence? Post-mortem reviews informed improvements to both the app and the operational processes. Issues discovered in ‘support’ fed back into the ‘discover’ and ‘design’ cycles, continuously refining the product.

Continual improvement:
The journey from ‘discover’ to ‘support’ was not linear but cyclical. Feedback from ‘support’ informed new ‘discover’ iterations as market conditions evolved. Performance data from ‘operate’ fed into ‘deliver’ improvements. Customer insights from ‘deliver’ shaped strategic decisions about feature prioritization and regional adaptations. By embedding DPSM practices throughout this lifecycle, ICR’s unified mobile app became more than a technical achievement. It became a reflection of the company’s commitment to customers: reliable, innovative, responsive to local needs, and continuously improving. As Max envisioned, ITIL Car Rental had taken a bold step toward being the world’s most trusted mobility partner, delivering the vision through every customer interaction, every design decision, and every operational moment.

Service:
Implementing a global HR management service: an internal service lifecycle
The challenge:
ITIL Car Rental’s expansion across multiple regions and service lines created mounting complexity in workforce management. Different legal entities, varying employment regulations, localized payroll requirements, and regulatory compliance across jurisdictions had strained the company’s aging HR systems. The company’s executive team identified modernization of HR management services as essential to support ICR’s growth strategy whilst maintaining operational consistency and compliance across markets. Omar’s IT delivery team took ownership of implementing a new vendor-supplied HR management system, a solution that would run on ICR servers, integrate seamlessly with existing internal systems, and serve thousands of employees and contractors across dozens of countries.

Discover: understanding the landscape
The team began by organizing a comprehensive ‘discover’ iteration. Assessing the organizational context, the team analysed how ICR’s expansion strategy, new regulatory requirements in different markets, evolving workplace expectations, and the growing complexity of managing multiple legal entities across regions created both pressure and opportunity for modernization. Working closely with the HR business partner and Max’s office, Omar’s team gathered requirements from across the organization: HR representatives and business managers in each country, payroll departments, compliance officers, finance teams managing workforce costs, and executives overseeing the talent strategy. The discovery revealed critical patterns. European operations faced strict data protection and employment law requirements. Asia-Pacific branches needed sophisticated multi-currency payroll capabilities. The US and Canadian operations required integration with complex benefits administration systems. Every region needed consistency in talent management and performance tracking, yet each had distinct regulatory demands. A business analyst from Omar’s team documented these needs systematically, whilst Alex, the Enterprise Architect, assessed the technical implications of supporting multiple legal entities, integrating with existing systems (payroll, finance, learning management, employee engagement platforms), and ensuring data security and regulatory compliance. The vendor’s product roadmap was evaluated against ICR’s requirements, revealing both strong alignment and specific gaps requiring customization. The team agreed on a clear direction: implement a core HR platform from a reputable software vendor as the system of record for employee master data, organizational structure, and talent management across all regions, while integrating specialized capabilities for payroll, benefits, compliance reporting, and data protection. Investment was secured with realistic timelines accounting for the complexity of multi-region deployment, and a formal steering committee was established to guide implementation.

Design: defining the solution:
With requirements agreed, Omar’s team began detailed design activities. Service design workshops brought together local HR representatives, payroll specialists, compliance officers, and technology architects. The team mapped existing HR processes in each region, identifying which would be standardized globally and which would require local customization. Design workshops revealed critical service interactions. HR teams needed intuitive interfaces for managing recruitment, onboarding, performance management, and learning across different employment models. Employees required easy access to personal information, benefits enrolment, and career development features. Payroll teams needed reliable data integration with local accounting systems and regulatory reporting tools. Compliance officers required audit trails, secure data management, and reporting to meet legal obligations in each jurisdiction. Alex developed detailed integration architecture, specifying how the HR system would communicate with existing payroll, finance, learning management, and employee engagement platforms. Data flows were mapped, ensuring that changes in one system were reliably distributed to dependent systems without manual intervention or data errors. Security and data protection requirements were designed into every integration point; this was particularly critical given GDPR, CCPA, and local data residency requirements. Data migration became one of the key design points. The team designed a phased deployment approach: implementation across ICR headquarters first, then staged rollout to major regional clusters, enabling learning and refinement before full global deployment. Supporting documentation, such as user guides for different roles, migration playbooks, and integration manuals, was planned in detail.

Acquire: securing resources:
With design specifications complete, Omar’s team identified required resources. The vendor’s licensing model (supporting anticipated growth); implementation consultant expertise (to guide customization and deployment); cloud infrastructure capacity for testing and staging environments; integration middleware (to connect the new HR system with existing enterprise systems); and data migration tools were all specified. The ‘acquire’ activity involved careful sourcing decisions. The vendor partnership was formalized, establishing support levels (the vendor providing third-line support, with first-line and specialist support to be provided by Omar’s team). External systems integrators with expertise in the vendor’s platform and multi-region HR implementations were evaluated and contracted. Cloud infrastructure capacity was procured, allowing for future growth. Service agreements included service level commitments and compliance obligations aligned with ICR’s governance standards. Resources were also identified internally: team members who would receive specialized training to support the system; members of Omar’s operations team who would provide day-to-day administration; security and compliance specialists to oversee implementation controls. Procurement was coordinated to ensure availability ahead of the ‘build’ phase.

Build: constructing the solution
Omar’s team established an implementation program, structured as a series of building activities. First, the core HR system was configured to match ICR’s organizational structure, employment classifications, and role hierarchies. Configuration activities addressed fundamental requirements: multi-legal entity support, multi-language and multi-currency capabilities, and foundational data structures. Parallel to core configuration, integration development began. The team, supported by the vendor and a vendor’s consulting partner, configured data flows from the HR system to payroll systems, ensuring employee changes (salary adjustments, location changes, benefits modifications) flowed reliably to payroll processing. Integration with the finance system ensured workforce costs were accurately captured. Learning management system connections ensured course assignments and certifications were synchronized. Security and compliance controls were embedded throughout, including audit logging, data encryption, access controls, and automated reporting for regulatory requirements. Extensive testing occurred throughout the ‘build’ phase. Functional testing verified that each configuration matched requirements. Integration testing validated that data flowed correctly between systems without errors or data loss. Security testing confirmed that sensitive personal data was protected and that access controls functioned as designed. Business process testing involved HR teams walking through common scenarios (such as hiring a new employee, transferring someone to a different country, or managing a separation), ensuring the system supported the complete workflow. User acceptance testing engaged representatives from different regions and roles. HR teams in Germany tested GDPR compliance features. Payroll teams in multiple countries verified that their specific regulatory requirements were met. Local compliance officers confirmed that reporting would support local legal obligations. Supporting documentation, such as operational runbooks for system administration, user guides tailored to different roles, and troubleshooting guides, was developed and reviewed. Apart from the HR teams, selected users from all affected teams were involved, testing the interfaces and workflows for requesting leave, conducting assessments, reserving training, of reporting HR incidents. These tests revealed the need for end-user training and onboarding during the new service roll-out. Transition plans were updated to allow time for this.

Transition: going live:
The team carefully prepared a transition strategy. Headquarters implementation was planned first, serving as a dress rehearsal. A parallel run, with both old and new systems operating simultaneously, was conducted for three weeks, allowing both systems to process payroll and generate reports for comparison. The payroll teams validated that the new system calculated amounts identically to the legacy system, detecting and resolving discrepancies before they affected employees. Omar coordinated the preparation activities. User training was delivered to HR teams, payroll specialists, managers, and employees. Help desks were staffed and trained. Communication plans explained the transition to all users, emphasizing continuity of services and highlighting new capabilities. Vendor support teams were onboarded, understanding their roles during the transition period. Data migration, which involved extracting employee master data from legacy systems, cleansing it, loading it into the new system, and validating completeness and accuracy, was carefully orchestrated and verified. Transition day at headquarters was carefully planned. The legacy system was frozen at a specific point, a final data extract was taken, loaded into the new system, and system access was switched over. The team remained staffed throughout the transition and into the following week, monitoring system performance closely, responding to questions, and resolving issues. Incident response procedures were in place, with escalation paths to the vendor’s support team available if needed. Following successful headquarters transition, the team planned regional deployments. Each regional cluster (Europe, Asia-Pacific, Americas) had a transition period, with lessons from earlier transitions incorporated and local considerations addressed. The staggered approach allowed the central team to support each region and enabled best practices to propagate from early transitions to later ones.

Operate: maintaining excellence:
With the system live across regions, Omar’s team shifted focus to reliable operations. Infrastructure monitoring tracked system health, performance, and availability across all deployment sites. Automated health checks, such as database integrity tests, integration validation, and backup verification, ran daily, alerting the team to any deviations from expected operation. The team established routine operational activities: security patches supplied by the vendor were tested in staging environments, then deployed to production overnight. Data backups were performed daily, with regular restoration tests confirming that recovery was possible. System performance was monitored, with growth projections ensuring sufficient capacity as employee counts increased. User access was reviewed every week, ensuring that accounts of employees that had left the company were promptly deactivated and that role changes were reflected in system permissions.
When issues appeared, monitoring detected these deviations and triggered investigation. The team maintained a problem backlog, working with the vendor to address underlying issues and implementing fixes or workarounds as appropriate.

Deliver: serving the organization
The ‘deliver’ activity brought the HR system into daily organizational use. Omar’s team established service level commitments: HR teams would have to access to the system 99.5% of the time; user support queries would be acknowledged within four hours; critical issues affecting payroll or compliance would be resolved within eight hours. The team was constrained by the respective commitments of the vendor and, although in many cases a higher service level was provided, it could not be formally committed to. A first-line support team knowledgeable about ICR’s specific configuration and trained on common issues responded to user questions. A knowledge base captured solutions to frequent issues, enabling self-service support. Employees received training on using the service: how to access their information, update personal details, enrol in benefits, and request time off through the HR portal. Delivery included routine service actions: onboarding new employees to the system (ensuring they were created with appropriate access and initial data); offboarding departing employees (deactivating access, generating final pay calculations, archiving records); managing organizational changes (updating reporting structures when teams were reorganized); conducting benefits enrolment campaigns (ensuring employees could select and modify coverage). The team monitored delivery metrics carefully: system availability, user satisfaction (gathered through surveys), processing timeliness (time from employee action to system reflection), and error rates (incorrect calculations, missing data). Service level reporting informed ongoing improvements and triggered escalations if service quality threatened to fall below the agreed level.

Support: resolving and learning:
Despite robust operational procedures, incidents occurred. A payroll integration process failed one month due to an unexpected data format in the finance system, causing a four-hour delay in the payroll. The support team immediately engaged payroll managers, communicating the issue and estimated resolution time. The technical team worked with the finance team and the vendor to understand the root cause, developed a fix to handle the unexpected data format, implemented the fix, reran the integration process, and verified accuracy. By the end of the day, normal payroll processing resumed.
On another occasion, a regional compliance officer discovered that a localized tax calculation in one country was producing results that didn’t align with current regulations. The incident was escalated to the vendor’s specialist support team. Together, they analysed the regulation change, determined that a configuration parameter needed adjustment, updated the system, revalidated historical calculations, and rolled forward with correct calculations prospectively. Each incident triggered a post-mortem review, where the support team asked: why did the issue occur? Were there warning signs we missed? How do we prevent recurrence? Findings from post-mortems informed improvements to configuration, integration design, monitoring, documentation, and training. Particularly significant improvements, such as enhanced validation of finance system data before processing payroll, were incorporated into the ‘discover’ and ‘design’ phases to shape future improvements.

Continual improvement:
The journey from ‘discover’ to ‘support’ was cyclical. Feedback from ‘support’, including new issues and lessons learned, informed new ‘discover’ iterations as regulations evolved, ICR’s business expanded into new markets, or new compliance requirements emerged. Performance data from ‘operate’ informed design improvements when system bottlenecks were identified or user experience could be enhanced. User feedback from ‘deliver’, captured through surveys and support interactions, shaped priorities for new features and refinements.
When HR teams requested better reporting capabilities to support talent analytics, this feedback was captured, evaluated during ‘discover’ activities, and prioritized in design cycles. By embedding DPSM practices throughout this lifecycle, Omar’s team transformed HR management at ITIL Car Rental.
What had been a patchwork of legacy systems and manual processes became a unified, reliable platform supporting the company’s global growth. Compliance risks were reduced through automation and audit trails. HR teams gained visibility into workforce data and could respond quickly to business needs. Employees had instant access to their information and could manage their own preferences. The system provided a foundation for HR analytics, enabling data-driven decisions about talent, compensation, and organizational structure. As Max envisioned, ICR’s transformation extended beyond customer-facing products to the internal systems and processes that enabled the company to operate effectively. By treating internal HR services with the same rigor and discipline as external products, Omar’s team ensured that ITIL Car Rental’s greatest asset, its people, were supported by systems as reliable, responsive, and capable as the mobility services ICR offered to customers worldwide. Please refer to the ITIL Car Rental scenario for additional context when answering this question. ICR started to integrate a newly acquired company’s maintenance system into its global AI predictive-maintenance platform. The first migration triggered widespread failures. Maintenance alerts stopped being generated, vehicles could not be assigned, and branches lost booking capabilities. The impact spread rapidly across regions. The team immediately halted integration and focused solely on restoring basic system stability before conducting any root cause analysis or planning next steps. Is the execution pattern applied in this situation appropriate?

  1. Yes, discover is appropriate to probe the uncertain system behaviour through small experiments before attempting full restoration
  2. Yes, contain is appropriate for crisis situations requiring immediate action to stop damage spread when no time exists for experiments or detailed analysis
  3. No, discover should be used as this complex integration represents an uncertain environment needing safe-to-fail experiments to understand cause-effect relationships
  4. No, implement should be used since migration activities follow known procedures with predictable cause-effect relationships

Answer(s): B



Introduction to ITIL Car Rental:
Ten years ago, ITIL Car Rental (ICR) was launched in Seattle with the aim to provide convenient and affordable rental cars to customers around the world. After a relatively short time, ICR became a globally recognized company, with a wide network of franchising partners across Europe, the US, and Asia-Pacific, with approximately 400 direct employees. In the first few years of operation, repeat business accounted for nearly a third of all reservations. Shareholders saw steady growth, and the company earned a reputation for putting customers first. ICR quickly became a model of modern mobility: fast, reliable, and profitable. Following its early success, the company expanded through mergers and acquisitions to new markets and new services, including car sharing. ICR relies heavily on digital technology for internal operations and service delivery, using a mix of internal and external digital products. Customer-facing mobile applications are developed and run by the internal IT team. AI is increasingly used in internal and external products and services for predictive maintenance, customer support, scheduling, smart check-in and return processes, and so on. As new competitors, such as car-sharing services, rideshare apps, and driverless cars, enter the market, customers now expect a seamless digital experience: quick bookings, app-based help, and flexible options that fit easily into their daily lives. At the same time, customers are paying more attention to companies that value social responsibility, sustainability, and environmental consciousness. These expectations are driving ICR to set clear and ambitious sustainability goals, as well as pursue further growth. The board members strongly believe that the company’s success in the years to come will be defined by innovation and the use of digital technology. For this reason, they appointed a new GIO, Max. Max was chosen for his experience in digitalization and his track record in successful, large-scale IT transformations. Max’s strong background in ITIL and ITSM indicates that he values ITIL certification, and his hiring policy reflects this. Having worked with Design Thinking, DevOps, and agile methods, he believes sustainable business requires a blended approach to digital product and service management. Max is keen to see how his team can redefine the car rental experience and ensure that ICR is the first choice for new and existing customers.

Meet the employees of ITIL Car Rental:
Max, Chief Information Officer (CIO):
Max is the new CIO. He is an experienced executive with a track record of leading digital transformations. He believes in an integrated approach to DPSM.

Anna, Product Manager:
Anna has been with ITIL Car Rental for five years. She focuses on commercial success and continual B2C development. She is detail-oriented, eco-conscious, and dedicated to improving overall customer experience.

Maria, Business Analyst:
Maria is a proactive communicator who ensures smooth collaboration between IT and business teams. She works mostly on discovery and planning activities, supporting continual improvement of the company’s digital products. She asks a lot of questions and is great at spotting patterns and trends.

Omar, IT Delivery Manager:
Omar manages ongoing service delivery. He applies ITIL practices to improve efficiency and customer satisfaction. However, Omar has had little experience with a blended or collaborative approach to product and service management.

Sam, Head of Product Development:
Sam has more than 10 years of experience in leading cross-functional product teams in the domains of mobility and automotive innovation. He oversees the entire product lifecycle at ITIL Car Rental from strategic vision to delivery and ensures that customer needs, market trends, and sustainability are all in sync.

Alex, Enterprise Architect:
Alex is responsible for ensuring that product design and technological strategy are aligned, sustainable, and future-proof. She provides architectural guidance across teams, works to identify systemic risks, and holds coherence in a fast-changing digital ecosystem. She is highly analytical with a strong intuition for patterns and risks.

The CIO’s vision for ITIL Car Rental Max:
We live in an era of rapid change, where all companies are going through some kind of digital transformation. Service expectations have changed drastically since ITIL Car Rental was created 10 years ago. Customers want seamless and immediate access to rental services from their smartphones, as well as innovation as part of their daily lives. Autonomous vehicles are the future; they will make car rental companies stand out and continue successfully. My vision is for ITIL Car Rental to pioneer this transformation and become the go-to name for car rentals worldwide. We will continue offering outstanding customer service while maintaining competitive car rental rates. After all, ITIL Car Rental is more than just a service. We are here to enhance the entire travel experience.

Governance:
ITIL Car Rental has branches in other countries, some of which are franchises. Each country may have its own regulations when it comes to the services offered by ICR. Although all services are focused on enhancing the entire travel experience, different services may be subjects to different regulation. For example, car-sharing is regulated differently, and self-driving cars cannot be introduced at all in some countries. ICR has adopted a governance approach that blends clear global direction with local autonomy, enabling the company to stay competitive in a fast-moving mobility landscape. As ICR continues to grow across regions and expand its portfolio, moving from traditional rentals to car-sharing and self-driving services, its governance structure ensures consistency, compliance, and customer-focused innovation. ICR’s approach to change is practical and adaptive. The company encourages experimentation and continual improvement as long as new ideas follow shared principles and meet regulatory expectations in each market. This balanced approach helps ICR introduce new digital features quickly while maintaining trust and reliability. The Board evaluates progress through a focused set of indicators, including commercial results, market share, innovation outcomes, cost efficiency, and customer satisfaction. Coordinated autonomy is a key feature of ICR’s governance.
While the Board defines the overall vision and strategic direction, local branches and service owners have freedom in how they achieve their goals. Market leaders and service-line managers work closely to tailor solutions to regional needs, ensuring that global standards remain compatible with local realities. Risk management reflects the diverse environments in which the company operates. Within heavily regulated domains, such as safety, traffic rules, and data protection, the company maintains a very low risk appetite and prioritizes prevention. In innovative settings, ICR accepts limited risks as long as they are identified early and controlled quickly. ICR’s operational context is constantly changing. Regulations evolve, cities introduce new environmental rules, and economic factors such as tariffs or sanctions may affect the business. To stay ahead, ICR continuously monitors these developments and adjusts its operations accordingly. To achieve this, the company relies on fast decision-making. Local teams and product groups can act independently within agreed principles and legal boundaries, allowing ICR to respond to customer needs and regulatory changes without delays. Compliance is an essential pillar of the governance model. Because requirements vary widely by region and service type, compliance responsibilities are distributed across the organization. Internal audit provides central oversight to ensure consistency and coherence using digital systems to standardize reporting and track evidence. ICR also serves a wide variety of stakeholders, ranging from city authorities to business clients and service partners. Their expectations differ by region, engagement approaches are adapted to local circumstances while staying aligned with ICR’s values and commitments. The company’s global reach demands broad governance oversight. Digital systems and processes are shared internationally but are tailored to each country’s regulations, customer behaviour, and available services. This combination helps ICR operate as a unified global brand while remaining locally relevant. Overall, ICR’s governance capabilities are well-established. Accountability is clear at board level, with defined responsibilities for central and local leaders. Regular audits and strong analytical tools support informed decision-making. As the company expands into new markets and introduces new mobility solutions, this governance foundation enables the company to grow responsibly, innovate confidently, and maintain a high standard of service for customers worldwide.

AI Governance:
Artificial Intelligence (AI) is increasingly embedded in ITIL Car Rental’s digital products and services. AI is used to support predictive maintenance, customer support, analytics, scheduling, and smart check-in and return processes. As ICR expands its service portfolio and geographic footprint, AI is expected to play a larger role in operational decision-making, customer experience, and service optimization. AI adoption creates new opportunities for ICR. AI-driven analytics can improve fleet utilization, sustainability performance, and cost efficiency. AI-enabled customer interaction can enhance responsiveness and personalization across markets. Automation and coordination capabilities can accelerate operational decisions and improve service reliability. These opportunities align with ICR’s strategic focus on digital experience, innovation, and sustainable growth. However, AI also introduces governance challenges. AI systems can act autonomously, operate at high speed, and learn over time, which challenges traditional approval-based decision structures. Risks related to explainability, bias, data protection, regulatory compliance, and accountability increase as AI influences customer-facing and safety-critical services. Differences in national regulation further complicate AI deployment across regions. ICR’s governance model combines clear global direction with local autonomy. The Board defines strategic objectives, risk appetite, and global principles, while local branches and service owners have flexibility in how they achieve outcomes within regulatory and legal boundaries. This governance pattern enables experimentation and innovation while maintaining compliance, consistency, and accountability. ICR’s existing governance both enables and constrains AI adoption. Strong compliance, audit, and risk management practices support trust and regulatory alignment but may slow adoption if applied too rigidly. Local autonomy supports innovation but requires stronger coordination to avoid fragmentation of AI practices and inconsistent customer experience. To address this, ICR is evolving its governance approach to AI. AI use cases are being classified by risk and impact, with governance intensity matched accordingly. Lower-risk AI solutions are enabled through local experimentation, while higher-risk applications require stronger oversight, clear accountability, explainability, and human-in-the-loop controls. Internal audit and reporting mechanisms are being extended to include AI-specific evidence and monitoring. Through this approach, ICR aims to enable responsible AI adoption that supports innovation, maintains trust, and aligns AI-enabled decisions with business objectives, regulatory requirements, and customer expectations.

Strategy:
ICR’s strategy centres on pioneering digital, sustainable mobility while growing globally and maintaining strong local responsiveness.

Vision statement:
“To be the world’s most trusted and innovative mobility partner, using digital technology and sustainable practices to enhance every journey for customers, wherever they travel.” This vision is realized through ICR’s strategy, which combines innovation, sustainability, a focus on customer experience, and sustainable growth. The company’s strategic direction has been transformed by the executive team into five strategic objectives, approved by the Board of Directors. Each objective has been further detailed into strategic initiatives. To implement these initiatives, many ICR teams will have to work together, involving external suppliers where additional resources and competencies are needed.

Objective 1: Lead in digital customer experience ICR aims to offer a seamless, app-first experience that makes renting, sharing, and returning vehicles effortless across all markets. Roll out a unified global mobile platform with localized features, languages, and payment options.
Embed AI-driven capabilities such as predictive maintenance, smart check-in/return, and proactive support into all core services. Establish continuous discovery and UX improvement cycles led by product and business analysis teams.

Objective 2: Innovate in autonomous and new mobility services ICR wants to be an early and trusted provider of self-driving and car-sharing services where regulations allow, integrating them into its mainstream portfolio. Launch regulated pilots for self-driving and car-sharing services in priority markets, starting with the US and expanding to EU and other markets. Build a standardized service design and safety framework for autonomous services, aligned with local laws and ICR’s low risk appetite in safety and data protection. Create joint innovation programmes between product, architecture, and operations to scale successful pilots globally.

Objective 3: Grow sustainably and profitably across markets ICR seeks to expand through franchising, mergers, and acquisitions while maintaining strong financial performance and customer loyalty. Maintain an up-to-date integration playbook covering governance, branding, systems, and supplier relationships for new acquisitions. Implement market- and service-level performance dashboards tracking revenue, market share, innovation progress, and customer satisfaction. Optimize fleet and cost structures using analytics to balance utilization, pricing, and sustainability targets.

Objective 4: Embed sustainability and social responsibility ICR intends to align its growth with environmental responsibility and evolving city and national regulations. Define clear sustainability targets (such as fleet emissions profile, use of EVs, or eco-options in the app) and report progress regularly. Cooperate with cities and regulators to adapt services to local environmental rules, parking policies, and low-emission zones. Design service offerings that reward sustainable choices, such as greener vehicle options or smarter routing.

Objective 5: Strengthen governance, risk, and capabilities ICR will maintain robust governance while allowing local autonomy, ensuring decisions are fast, compliant, and data-informed. Clarify and document global and local decision rights, principles, and escalation paths for all service lines. Enhance internal audit, compliance monitoring, and digital evidence-tracking across all countries and franchises. Invest in skills and certifications (ITIL, DevOps, data governance) for key roles such as CIO and office, product, delivery, and architecture. managers to support continual transformation.

Transformation:
ICR always looks for opportunities to expand the business to new markets. As part of this strategy, the company agreed an acquisition of a local rental company in a small, fast-developing country in Europe. The company being acquired has an established customer base and reputation in its home country. It is known in neighbouring countries, though it does not have branches in them. The government of the country where the company is based just passed a regulation approving use of self-diving vehicles, and ICR is keen to be the first provider of such a service in the region. The acquired company needs to be integrated into the ICR governance and management structure and information systems, including internal and customer-facing systems. The objective is to retain the existing customer base, provide reassurance that the acquisition will improve (rather than worsen) the quality of familiar rental services, and introduce new service lines (car-sharing, self-driving cars). The Board of Directors expects the integration to be completed within three months (including branding, information systems, governance, people, and relationships with local suppliers). ICR identified five transformational initiatives that need to be completed to fulfil the transformation:

1. Governance and structure integration ICR needs to integrate the acquired company into its existing governance model by aligning the local board reporting lines, decision rights, and accountability with ICR’s global principles, while preserving a high degree of local autonomy for market- and service-specific decisions. This includes defining how the local management team participates in ICR’s governance forums and how global policies, such as risk management and sustainability, are applied in the new country. ICR has gone through this many times and has an established playbook for governance and management integration, which proved to be effective during previous acquisitions.

2. Regulatory, risk, and compliance setup ICR must establish a comprehensive regulatory and compliance framework for the new market, with particular emphasis on the newly approved self-driving vehicle regulation and existing rules for rental and car-sharing services. This initiative should set up local controls and escalation paths consistent with ICR’s low risk appetite in safety, data protection, and traffic law. These controls and paths should be supported by internal audit oversight and appropriate reporting mechanisms. The company also has extensive experience in this area; however, every new country introduces new challenges which sometimes need to be addressed quickly.

3. Technology and platform integration ICR needs to migrate or integrate the acquired company’s systems into its global digital ecosystem, including customer-facing apps, booking platforms, fleet and maintenance systems, and analytics. During the transition period, ICR must ensure continuity of service for existing customers. AI-enabled capabilities such as predictive maintenance, smart check-in/return, and customer support should be progressively rolled out to the new operation, aligning with local regulations and infrastructure. Although the existing technology solutions of the acquired company were briefly assessed before the acquisition, there is a lot to explore, and the technology team should be ready for surprises.

4. Brand, customer, and stakeholder transition A coordinated rebranding and customer communication programme is required to transition the local brand to ICR within three months. This communication should clearly explain that familiar services will be maintained or improved and that new options like car-sharing and self-driving services will be introduced. In parallel, ICR should engage proactively with local authorities, business customers, partners, and suppliers to reinforce trust, clarity expectations, and position ICR as an innovative yet reliable mobility provider in the region. ICR has a playbook for such campaigns, but for it to be effective, detailed information about the customers, their expectations, and the ongoing relationships is needed.

5. Operating model, people, and service portfolio ICR should redesign the local operating model to match its global standards, including roles, responsibilities, and performance metrics, while retaining local knowledge and relationships that underpin the acquired company’s reputation. As part of this, the service portfolio in the new country should be structured to cover traditional rental, car-sharing, and self-driving services under a unified framework, with clear service ownership, targets for commercial performance and customer satisfaction, and mechanisms for rapid local decision-making. Although ICR has a large and positive experience of adapting the operating models of acquired companies, introduction of the self-driving cars to a new market is a new and challenging task. Together, these transformation efforts should allow ICR to enter the new region as a trusted, forward-looking mobility partner. Supported by strong governance, modern technology, and an effective integration approach, ICR is well positioned to deliver a reliable, future-ready travel experience to customers in its newest market.

Experience:
Understanding user experience as a strategic imperative
ICR recognizes that achieving a sustainable competitive advantage in modern mobility depends fundamentally on delivering exceptional user experience. Max articulated in his vision for the company that “customers want seamless and immediate access to rental services from their smartphones, as well as innovation as part of their daily lives.” This expectation applies not only to traditional car rental services but extends across the expanding portfolio of car-sharing and driverless tax offerings. The digital applications and web interfaces that customers interact with have become the primary touchpoints for the ICR brand, making digital experience inseparable from overall business success.
The customer journey across digital touchpoints
The user journey with ICR spans multiple critical steps, each mediated through digital applications and interfaces: Discovery and search begin when prospective customers evaluate their mobility options. Here, ICR’s digital presence must clearly communicate availability, pricing transparency, and service advantages over competitors, whether customers are considering traditional car rental, flexible car-sharing, or autonomous ride options. Registration and onboarding follow as users create profiles and establish trust with the platform. At this point they share their personal data, driving licence, and financial details with ICR. This makes this step particularly important for building trust and capturing customer preferences that will enhance future interactions. Selection and booking require intuitive navigation and clear presentation of options. The digital interface must accommodate the different decision-making patterns across the three service modes: the planning-focused car rental customer, the spontaneous car-sharing user, and the on-demand autonomous ride passenger. Payment processing must inspire confidence while remaining frictionless. Secure, flexible payment options that adapt to different service models strengthen customer trust and reduce transaction abandonment. This is a sensitive aspect of service interactions, as car rental users are often worried about unexpected security deposits, additional charges and costly insurance. Although this part of user journey often seems to be less important than the core service utility, it may have a significant and sometimes damaging impact on the overall experience. Check-in and vehicle access have evolved significantly with smart technologies. Digital applications now provide seamless vehicle access, reduced friction at pick-up, and immediate problem resolution when complications arise. In-journey support enables customers to address questions or concerns in real time.
Whether requesting roadside assistance, reporting issues, or seeking clarification, rapid response through integrated digital channels demonstrates the ICR’s commitment to the travel experience it has promised. Check-out and feedback close the transaction but open an opportunity for continual improvement. Digital interfaces capture usage data, soliciting feedback that informs service enhancements.
Differentiation across service models
While these touchpoints are universal, their expression differs significantly across ICR’s service offerings. Traditional car rental customers typically plan ahead, expecting detailed vehicle information and insurance clarity through structured booking flows. Car-sharing users demand spontaneity and simplicity, prioritizing booking speed and lock/unlock mechanisms. Driverless taxi passengers expect transparency about autonomous capabilities, safety systems, and real-time trip information without the complexity of vehicle selection.
Capturing, analysing, and improving user experience
Recognizing that understanding is a prerequisite to improvement, ICR has embedded experience measurement into the digital ecosystem. ICR applications capture behavioural data (interaction patterns, abandonment points, feature usage, and satisfaction signals), providing teams with rich insight into the customer journey and occurring points of friction.
This data flows into structured analysis processes. Maria, the Business Analyst, uses AI to identify patterns and trends that highlight experience bottlenecks and opportunities. Cross-functional collaboration between Anna’s product management, Sam’s product development oversight, and Omar’s service delivery team ensures that insights translate into rapid and noticeable improvements. The teams employ both quantitative metrics (completion rates, task duration, error frequency) and qualitative feedback mechanisms. Customer surveys, user testing sessions, and support interaction analysis combine with operational data to paint a complete picture of experience quality. Improvement cycles operate continuously, enabled by the ICR’s commitment to the end-to-end product and service lifecycle management and iterative development. The service enhancements are tested incrementally, which allows the teams to measure their impact and iterate rapidly. This approach ensures that ICR remains responsive to evolving customer expectations while maintaining the reliability and service quality that have defined the company’s reputation. By treating user experience as both a strategic priority and an operational discipline, ICR ensures that the company’s digital services serve their essential purpose: enabling customers to access mobility solutions effortlessly, building loyalty through consistent excellence, and positioning ICR as the thoughtful choice in an increasingly competitive and technologically sophisticated market.

Product:
ICR’s Unified Mobile App: A Product Lifecycle Journey
The challenge:
ITIL Car Rental’s vision for digital transformation demanded a bold move: consolidating traditional car rental, car-sharing, and emerging autonomous vehicle services into a single, seamless mobile application. This unified platform would serve millions of customers globally while adapting to diverse regulatory environments and local market conditions. The product team (led by Sam and guided by Anna’s product management expertise, Maria’s business analysis insight, and Alex’s architectural know-how) embarked on a comprehensive product lifecycle journey.

Discover: charting the course:
The team began by analysing the business context using the PESTLE method. Regulatory changes permitting autonomous vehicles in several markets, shifting customer expectations towards mobile-first experiences, and competitive pressures from ride-sharing services created both urgency and opportunity. Sam convened discovery sessions with stakeholders across the organization. Market analysis revealed fragmented customer expectations: traditional renters wanted clarity and planning capability; car-sharing users demanded spontaneity and speed; autonomous rice passengers expected transparency and trust. Maria identified critical patterns in user behaviour across regions, while Alex assessed the architectural implications of managing three distinct service models within a single platform. The team agreed strategic direction: create one app that intelligently presents rental, sharing, and autonomous options based on user context and local regulations. This vision was communicated across all product teams, establishing alignment and guiding subsequent activities. Investment in the initiative was secured, with clear timelines and resource commitments.

Design: shaping the experience:
Service design workshops brought together user research, human-centred design principles, and regulatory requirements. Anna led a detailed analysis of the customer journey across all three service models, identifying touchpoints, decision moments, and friction points. The design iterations incorporated feedback from early user testing. The team prototyped distinct user flows: a structured booking experience for renters planning days ahead; a rapid-access interface for car sharing users; and a transparent, safety-focused experience for autonomous ride passengers. Meanwhile, Alex developed target architecture blueprints ensuring that different service models could scale independently while sharing core infrastructure for authentication, payment, and support. Design specifications documented user interface, service interactions and operational requirements. The team designed for continuous improvement: metrics, feedback mechanisms, and analytics touchpoints were embedded into the design from the outset.

Acquire: securing resources:
With design specifications complete, the ‘acquire’ activity identified the required resources. Cloud infrastructure capable of handling peak demand across multiple regions; AI/machine learning services for predictive maintenance and smart routing; payment processing services compliant with regulations in each market; map and navigation services adapted to local conditions. The team assessed sourcing options, negotiating contracts with multiple cloud providers and service partners. Procurement was coordinated carefully to ensure integration readiness. Resource availability was confirmed before the ‘build’ phase began, preventing downstream delays.

Build: constructing the solution
The product development team, under Sam’s oversight, executed a phased build approach. The core app framework was developed first, establishing shared foundations for authentication, payment processing, and support channels. Feature teams then implemented the rental, sharing, and autonomous service modules in parallel, maintaining integration points and shared design patterns. Rigorous testing occurred throughout. Service validation teams ensured the app functioned flawlessly across devices, network conditions, and geographic regions. Integration testing verified that switching between service models felt seamless. Security testing confirmed compliance with data protection requirements in each market.
Supporting documentation, including user guides, service manuals, and operational runbooks, was developed alongside the software.

Transition: going live:
Before full launch, the team executed a carefully staged transition strategy. Soft launches in select markets allowed real users to interact with the new experience under controlled conditions. Omar, the IT Delivery Manager, coordinated the operational handover, ensuring monitoring systems captured live performance data and incident response procedures were operational. Supplier onboarding was critical: map service providers, payment processors, and cloud infrastructure teams needed to understand their roles in the live environment. Customer communication emphasized that familiar services would be enhanced, not disrupted. The team monitored the transition closely, ready to address any issues.

Operate: maintaining excellence:
With the app in live environments, the ‘operate’ activity ensured continuous, reliable performance. Infrastructure monitoring tracked application health, system performance, and availability across regions. The team managed routine updates, security patches, and scaling adjustments responding to demand fluctuations. Automated systems monitored performance metrics: response times, transaction completion rates, error frequencies.
When deviations appeared, such as unusual latency in a particular region or unexpected payment processing delays, alerts triggered investigation and rapid response.

Deliver: serving customers:
The ‘deliver’ activity brought the product to life for customers. Service delivery teams ensured seamless onboarding to new users, providing multiple languages, localized payment options, and support channels adapted to each market. Service level agreements committed to fast booking, reliable vehicle access, and responsive support. Customer service teams used the app’s built-in support features (in-app chat, knowledge bases, and contextual help) to address questions. Anna monitored service quality metrics and customer satisfaction indicators religiously. Usage patterns revealed which features resonated, where users abandoned workflows, and which regions had distinct preferences.

Support: resolving and learning:
Despite meticulous planning, incidents occurred. A payment processing outage in one market triggered rapid incident response: the support team engaged customers, offered alternatives, and restored service within hours.
When an unexpected interaction between autonomous ride features and local traffic regulations created user confusion, the team diagnosed the issue, implemented a fix, and deployed it to users within days. More importantly, each incident triggered investigation.
Why did it happen? What signals did we miss? How do we prevent recurrence? Post-mortem reviews informed improvements to both the app and the operational processes. Issues discovered in ‘support’ fed back into the ‘discover’ and ‘design’ cycles, continuously refining the product.

Continual improvement:
The journey from ‘discover’ to ‘support’ was not linear but cyclical. Feedback from ‘support’ informed new ‘discover’ iterations as market conditions evolved. Performance data from ‘operate’ fed into ‘deliver’ improvements. Customer insights from ‘deliver’ shaped strategic decisions about feature prioritization and regional adaptations. By embedding DPSM practices throughout this lifecycle, ICR’s unified mobile app became more than a technical achievement. It became a reflection of the company’s commitment to customers: reliable, innovative, responsive to local needs, and continuously improving. As Max envisioned, ITIL Car Rental had taken a bold step toward being the world’s most trusted mobility partner, delivering the vision through every customer interaction, every design decision, and every operational moment.

Service:
Implementing a global HR management service: an internal service lifecycle
The challenge:
ITIL Car Rental’s expansion across multiple regions and service lines created mounting complexity in workforce management. Different legal entities, varying employment regulations, localized payroll requirements, and regulatory compliance across jurisdictions had strained the company’s aging HR systems. The company’s executive team identified modernization of HR management services as essential to support ICR’s growth strategy whilst maintaining operational consistency and compliance across markets. Omar’s IT delivery team took ownership of implementing a new vendor-supplied HR management system, a solution that would run on ICR servers, integrate seamlessly with existing internal systems, and serve thousands of employees and contractors across dozens of countries.

Discover: understanding the landscape
The team began by organizing a comprehensive ‘discover’ iteration. Assessing the organizational context, the team analysed how ICR’s expansion strategy, new regulatory requirements in different markets, evolving workplace expectations, and the growing complexity of managing multiple legal entities across regions created both pressure and opportunity for modernization. Working closely with the HR business partner and Max’s office, Omar’s team gathered requirements from across the organization: HR representatives and business managers in each country, payroll departments, compliance officers, finance teams managing workforce costs, and executives overseeing the talent strategy. The discovery revealed critical patterns. European operations faced strict data protection and employment law requirements. Asia-Pacific branches needed sophisticated multi-currency payroll capabilities. The US and Canadian operations required integration with complex benefits administration systems. Every region needed consistency in talent management and performance tracking, yet each had distinct regulatory demands.
A business analyst from Omar’s team documented these needs systematically, whilst Alex, the Enterprise Architect, assessed the technical implications of supporting multiple legal entities, integrating with existing systems (payroll, finance, learning management, employee engagement platforms), and ensuring data security and regulatory compliance. The vendor’s product roadmap was evaluated against ICR’s requirements, revealing both strong alignment and specific gaps requiring customization. The team agreed on a clear direction: implement a core HR platform from a reputable software vendor as the system of record for employee master data, organizational structure, and talent management across all regions, while integrating specialized capabilities for payroll, benefits, compliance reporting, and data protection. Investment was secured with realistic timelines accounting for the complexity of multi-region deployment, and a formal steering committee was established to guide implementation.

Design: defining the solution:
With requirements agreed, Omar’s team began detailed design activities. Service design workshops brought together local HR representatives, payroll specialists, compliance officers, and technology architects. The team mapped existing HR processes in each region, identifying which would be standardized globally and which would require local customization. Design workshops revealed critical service interactions. HR teams needed intuitive interfaces for managing recruitment, onboarding, performance management, and learning across different employment models. Employees required easy access to personal information, benefits enrolment, and career development features. Payroll teams needed reliable data integration with local accounting systems and regulatory reporting tools. Compliance officers required audit trails, secure data management, and reporting to meet legal obligations in each jurisdiction. Alex developed detailed integration architecture, specifying how the HR system would communicate with existing payroll, finance, learning management, and employee engagement platforms. Data flows were mapped, ensuring that changes in one system were reliably distributed to dependent systems without manual intervention or data errors. Security and data protection requirements were designed into every integration point; this was particularly critical given GDPR, CCPA, and local data residency requirements. Data migration became one of the key design points. The team designed a phased deployment approach: implementation across ICR headquarters first, then staged rollout to major regional clusters, enabling learning and refinement before full global deployment. Supporting documentation, such as user guides for different roles, migration playbooks, and integration manuals, was planned in detail.

Acquire: securing resources:
With design specifications complete, Omar’s team identified required resources. The vendor’s licensing model (supporting anticipated growth); implementation consultant expertise (to guide customization and deployment); cloud infrastructure capacity for testing and staging environments; integration middleware (to connect the new HR system with existing enterprise systems); and data migration tools were all specified. The ‘acquire’ activity involved careful sourcing decisions. The vendor partnership was formalized, establishing support levels (the vendor providing third-line support, with first-line and specialist support to be provided by Omar’s team). External systems integrators with expertise in the vendor’s platform and multi-region HR implementations were evaluated and contracted. Cloud infrastructure capacity was procured, allowing for future growth. Service agreements included service level commitments and compliance obligations aligned with ICR’s governance standards. Resources were also identified internally: team members who would receive specialized training to support the system; members of Omar’s operations team who would provide day-to-day administration; security and compliance specialists to oversee implementation controls. Procurement was coordinated to ensure availability ahead of the ‘build’ phase.

Build: constructing the solution
Omar’s team established an implementation program, structured as a series of building activities. First, the core HR system was configured to match ICR’s organizational structure, employment classifications, and role hierarchies. Configuration activities addressed fundamental requirements: multi-legal entity support, multi-language and multi-currency capabilities, and foundational data structures. Parallel to core configuration, integration development began. The team, supported by the vendor and a vendor’s consulting partner, configured data flows from the HR system to payroll systems, ensuring employee changes (salary adjustments, location changes, benefits modifications) flowed reliably to payroll processing. Integration with the finance system ensured workforce costs were accurately captured. Learning management system connections ensured course assignments and certifications were synchronized. Security and compliance controls were embedded throughout, including audit logging, data encryption, access controls, and automated reporting for regulatory requirements. Extensive testing occurred throughout the ‘build’ phase. Functional testing verified that each configuration matched requirements. Integration testing validated that data flowed correctly between systems without errors or data loss. Security testing confirmed that sensitive personal data was protected and that access controls functioned as designed. Business process testing involved HR teams walking through common scenarios (such as hiring a new employee, transferring someone to a different country, or managing a separation), ensuring the system supported the complete workflow. User acceptance testing engaged representatives from different regions and roles. HR teams in Germany tested GDPR compliance features. Payroll teams in multiple countries verified that their specific regulatory requirements were met. Local compliance officers confirmed that reporting would support local legal obligations. Supporting documentation, such as operational runbooks for system administration, user guides tailored to different roles, and troubleshooting guides, was developed and reviewed. Apart from the HR teams, selected users from all affected teams were involved, testing the interfaces and workflows for requesting leave, conducting assessments, reserving training, of reporting HR incidents. These tests revealed the need for end-user training and onboarding during the new service roll-out. Transition plans were updated to allow time for this.

Transition: going live:
The team carefully prepared a transition strategy. Headquarters implementation was planned first, serving as a dress rehearsal. A parallel run, with both old and new systems operating simultaneously, was conducted for three weeks, allowing both systems to process payroll and generate reports for comparison. The payroll teams validated that the new system calculated amounts identically to the legacy system, detecting and resolving discrepancies before they affected employees. Omar coordinated the preparation activities. User training was delivered to HR teams, payroll specialists, managers, and employees. Help desks were staffed and trained. Communication plans explained the transition to all users, emphasizing continuity of services and highlighting new capabilities. Vendor support teams were onboarded, understanding their roles during the transition period. Data migration, which involved extracting employee master data from legacy systems, cleansing it, loading it into the new system, and validating completeness and accuracy, was carefully orchestrated and verified. Transition day at headquarters was carefully planned. The legacy system was frozen at a specific point, a final data extract was taken, loaded into the new system, and system access was switched over. The team remained staffed throughout the transition and into the following week, monitoring system performance closely, responding to questions, and resolving issues. Incident response procedures were in place, with escalation paths to the vendor’s support team available if needed. Following successful headquarters transition, the team planned regional deployments. Each regional cluster (Europe, Asia-Pacific, Americas) had a transition period, with lessons from earlier transitions incorporated and local considerations addressed. The staggered approach allowed the central team to support each region and enabled best practices to propagate from early transitions to later ones.

Operate: maintaining excellence:
With the system live across regions, Omar’s team shifted focus to reliable operations. Infrastructure monitoring tracked system health, performance, and availability across all deployment sites. Automated health checks, such as database integrity tests, integration validation, and backup verification, ran daily, alerting the team to any deviations from expected operation. The team established routine operational activities: security patches supplied by the vendor were tested in staging environments, then deployed to production overnight. Data backups were performed daily, with regular restoration tests confirming that recovery was possible. System performance was monitored, with growth projections ensuring sufficient capacity as employee counts increased. User access was reviewed every week, ensuring that accounts of employees that had left the company were promptly deactivated and that role changes were reflected in system permissions.
When issues appeared, monitoring detected these deviations and triggered investigation. The team maintained a problem backlog, working with the vendor to address underlying issues and implementing fixes or workarounds as appropriate.

Deliver: serving the organization
The ‘deliver’ activity brought the HR system into daily organizational use. Omar’s team established service level commitments: HR teams would have to access to the system 99.5% of the time; user support queries would be acknowledged within four hours; critical issues affecting payroll or compliance would be resolved within eight hours. The team was constrained by the respective commitments of the vendor and, although in many cases a higher service level was provided, it could not be formally committed to. A first-line support team knowledgeable about ICR’s specific configuration and trained on common issues responded to user questions. A knowledge base captured solutions to frequent issues, enabling self-service support. Employees received training on using the service: how to access their information, update personal details, enrol in benefits, and request time off through the HR portal. Delivery included routine service actions: onboarding new employees to the system (ensuring they were created with appropriate access and initial data); offboarding departing employees (deactivating access, generating final pay calculations, archiving records); managing organizational changes (updating reporting structures when teams were reorganized); conducting benefits enrolment campaigns (ensuring employees could select and modify coverage). The team monitored delivery metrics carefully: system availability, user satisfaction (gathered through surveys), processing timeliness (time from employee action to system reflection), and error rates (incorrect calculations, missing data). Service level reporting informed ongoing improvements and triggered escalations if service quality threatened to fall below the agreed level.

Support: resolving and learning:
Despite robust operational procedures, incidents occurred. A payroll integration process failed one month due to an unexpected data format in the finance system, causing a four-hour delay in the payroll. The support team immediately engaged payroll managers, communicating the issue and estimated resolution time. The technical team worked with the finance team and the vendor to understand the root cause, developed a fix to handle the unexpected data format, implemented the fix, reran the integration process, and verified accuracy. By the end of the day, normal payroll processing resumed. On another occasion, a regional compliance officer discovered that a localized tax calculation in one country was producing results that didn’t align with current regulations. The incident was escalated to the vendor’s specialist support team. Together, they analysed the regulation change, determined that a configuration parameter needed adjustment, updated the system, revalidated historical calculations, and rolled forward with correct calculations prospectively. Each incident triggered a post-mortem review, where the support team asked: why did the issue occur? Were there warning signs we missed? How do we prevent recurrence? Findings from post-mortems informed improvements to configuration, integration design, monitoring, documentation, and training. Particularly significant improvements, such as enhanced validation of finance system data before processing payroll, were incorporated into the ‘discover’ and ‘design’ phases to shape future improvements.

Continual improvement:
The journey from ‘discover’ to ‘support’ was cyclical. Feedback from ‘support’, including new issues and lessons learned, informed new ‘discover’ iterations as regulations evolved, ICR’s business expanded into new markets, or new compliance requirements emerged. Performance data from ‘operate’ informed design improvements when system bottlenecks were identified or user experience could be enhanced. User feedback from ‘deliver’, captured through surveys and support interactions, shaped priorities for new features and refinements.
When HR teams requested better reporting capabilities to support talent analytics, this feedback was captured, evaluated during ‘discover’ activities, and prioritized in design cycles. By embedding DPSM practices throughout this lifecycle, Omar’s team transformed HR management at ITIL Car Rental.
What had been a patchwork of legacy systems and manual processes became a unified, reliable platform supporting the company’s global growth. Compliance risks were reduced through automation and audit trails. HR teams gained visibility into workforce data and could respond quickly to business needs. Employees had instant access to their information and could manage their own preferences. The system provided a foundation for HR analytics, enabling data-driven decisions about talent, compensation, and organizational structure. As Max envisioned, ICR’s transformation extended beyond customer-facing products to the internal systems and processes that enabled the company to operate effectively. By treating internal HR services with the same rigor and discipline as external products, Omar’s team ensured that ITIL Car Rental’s greatest asset, its people, were supported by systems as reliable, responsive, and capable as the mobility services ICR offered to customers worldwide. Please refer to the ITIL Car Rental scenario for additional context when answering this question. ICR is enhancing its AI smart check-in feature for a newly acquired European market. Early analysis has revealed significantly different customer behaviours and unclear user flow dependencies compared to existing markets. Instead of detailed upfront planning, the team ran multiple small experiments with varied check-in prompts to observe behaviour and understand system responses before finalizing the workflow. Based on this approach, was the execution pattern applied appropriate?

  1. Yes, the team is correctly using Appraise:
    -> Plan:
    -> Do:
    -> Study:
    -> Act steps from the ‘implement’ pattern
  2. Yes, the team is correctly using Bound:
    -> Design:
    -> Run:
    -> Examine:
    -> Distil steps from the ‘discover’ pattern
  3. No, the team should use the ‘implement’ pattern because experimentation slows down delivery in new markets
  4. No, the team should use the ‘contain’ pattern because user-flow uncertainty indicates instability

Answer(s): B



Introduction to ITIL Car Rental:
Ten years ago, ITIL Car Rental (ICR) was launched in Seattle with the aim to provide convenient and affordable rental cars to customers around the world. After a relatively short time, ICR became a globally recognized company, with a wide network of franchising partners across Europe, the US, and Asia-Pacific, with approximately 400 direct employees. In the first few years of operation, repeat business accounted for nearly a third of all reservations. Shareholders saw steady growth, and the company earned a reputation for putting customers first. ICR quickly became a model of modern mobility: fast, reliable, and profitable. Following its early success, the company expanded through mergers and acquisitions to new markets and new services, including car sharing. ICR relies heavily on digital technology for internal operations and service delivery, using a mix of internal and external digital products. Customer-facing mobile applications are developed and run by the internal IT team. AI is increasingly used in internal and external products and services for predictive maintenance, customer support,
scheduling, smart check-in and return processes, and so on. As new competitors, such as car-sharing services, rideshare apps, and driverless cars, enter the market, customers now expect a seamless digital experience: quick bookings, app-based help, and flexible options that fit easily into their daily lives. At the same time, customers are paying more attention to companies that value social responsibility, sustainability, and environmental consciousness. These expectations are driving ICR to set clear and ambitious sustainability goals, as well as pursue further growth. The board members strongly believe that the company’s success in the years to come will be defined by innovation and the use of digital technology. For this reason, they appointed a new GIO, Max. Max was chosen for his experience in digitalization and his track record in successful, large-scale IT transformations. Max’s strong background in ITIL and ITSM indicates that he values ITIL certification, and his hiring policy reflects this. Having worked with Design Thinking, DevOps, and agile methods, he believes sustainable business requires a blended approach to digital product and service management. Max is keen to see how his team can redefine the car rental experience and ensure that ICR is the first choice for new and existing customers.

Meet the employees of ITIL Car Rental:
Max, Chief Information Officer (CIO):
Max is the new CIO. He is an experienced executive with a track record of leading digital transformations. He believes in an integrated approach to DPSM.

Anna, Product Manager:
Anna has been with ITIL Car Rental for five years. She focuses on commercial success and continual B2C development. She is detail-oriented, eco-conscious, and dedicated to improving overall customer experience.

Maria, Business Analyst:
Maria is a proactive communicator who ensures smooth collaboration between IT and business teams. She works mostly on discovery and planning activities, supporting continual improvement of the company’s digital products. She asks a lot of questions and is great at spotting patterns and trends.

Omar, IT Delivery Manager:
Omar manages ongoing service delivery. He applies ITIL practices to improve efficiency and customer satisfaction. However, Omar has had little experience with a blended or collaborative approach to product and service management.

Sam, Head of Product Development:
Sam has more than 10 years of experience in leading cross-functional product teams in the domains of mobility and automotive innovation. He oversees the entire product lifecycle at ITIL Car Rental from strategic vision to delivery and ensures that customer needs, market trends, and sustainability are all in sync.

Alex, Enterprise Architect:
Alex is responsible for ensuring that product design and technological strategy are aligned, sustainable, and future-proof. She provides architectural guidance across teams, works to identify systemic risks, and holds coherence in a fast-changing digital ecosystem. She is highly analytical with a strong intuition for patterns and risks.

The CIO’s vision for ITIL Car Rental Max:
We live in an era of rapid change, where all companies are going through some kind of digital transformation. Service expectations have changed drastically since ITIL Car Rental was created 10 years ago. Customers want seamless and immediate access to rental services from their smartphones, as well as innovation as part of their daily lives. Autonomous vehicles are the future; they will make car rental companies stand out and continue successfully. My vision is for ITIL Car Rental to pioneer this transformation and become the go-to name for car rentals worldwide. We will continue offering outstanding customer service while maintaining competitive car rental rates. After all, ITIL Car Rental is more than just a service. We are here to enhance the entire travel experience.

Governance:
ITIL Car Rental has branches in other countries, some of which are franchises. Each country may have its own regulations when it comes to the services offered by ICR. Although all services are focused on enhancing the entire travel experience, different services may be subjects to different regulation. For example, car-sharing is regulated differently, and self-driving cars cannot be introduced at all in some countries. ICR has adopted a governance approach that blends clear global direction with local autonomy, enabling the company to stay competitive in a fast-moving mobility landscape. As ICR continues to grow across regions and expand its portfolio, moving from traditional rentals to car-sharing and self-driving services, its governance structure ensures consistency, compliance, and customer-focused innovation. ICR’s approach to change is practical and adaptive. The company encourages experimentation and continual improvement as long as new ideas follow shared principles and meet regulatory expectations in each market. This balanced approach helps ICR introduce new digital features quickly while maintaining trust and reliability. The Board evaluates progress through a focused set of indicators, including commercial results, market share, innovation outcomes, cost efficiency, and customer satisfaction. Coordinated autonomy is a key feature of ICR’s governance.
While the Board defines the overall vision and strategic direction, local branches and service owners have freedom in how they achieve their goals. Market leaders and service-line managers work closely to tailor solutions to regional needs, ensuring that global standards remain compatible with local realities. Risk management reflects the diverse environments in which the company operates. Within heavily regulated domains, such as safety, traffic rules, and data protection, the company maintains a very low risk appetite and prioritizes prevention. In innovative settings, ICR accepts limited risks as long as they are identified early and controlled quickly. ICR’s operational context is constantly changing. Regulations evolve, cities introduce new environmental rules, and economic factors such as tariffs or sanctions may affect the business. To stay ahead, ICR continuously monitors these developments and adjusts its operations accordingly. To achieve this, the company relies on fast decision-making. Local teams and product groups can act independently within agreed principles and legal boundaries, allowing ICR to respond to customer needs and regulatory changes without delays. Compliance is an essential pillar of the governance model. Because requirements vary widely by region and service type, compliance responsibilities are distributed across the organization. Internal audit provides central oversight to ensure consistency and coherence using digital systems to standardize reporting and track evidence. ICR also serves a wide variety of stakeholders, ranging from city authorities to business clients and service partners. Their expectations differ by region, engagement approaches are adapted to local circumstances while staying aligned with ICR’s values and commitments. The company’s global reach demands broad governance oversight. Digital systems and processes are shared internationally but are tailored to each country’s regulations, customer behaviour, and available services. This combination helps ICR operate as a unified global brand while remaining locally relevant. Overall, ICR’s governance capabilities are well-established. Accountability is clear at board level, with defined responsibilities for central and local leaders. Regular audits and strong analytical tools support informed decision-making. As the company expands into new markets and introduces new mobility solutions, this governance foundation enables the company to grow responsibly, innovate confidently, and maintain a high standard of service for customers worldwide.

AI Governance:
Artificial Intelligence (AI) is increasingly embedded in ITIL Car Rental’s digital products and services. AI is used to support predictive maintenance, customer support, analytics, scheduling, and smart check-in and return processes. As ICR expands its service portfolio and geographic footprint, AI is expected to play a larger role in operational decision-making, customer experience, and service optimization. AI adoption creates new opportunities for ICR. AI-driven analytics can improve fleet utilization, sustainability performance, and cost efficiency. AI-enabled customer interaction can enhance responsiveness and personalization across markets. Automation and coordination capabilities can accelerate operational decisions and improve service reliability. These opportunities align with ICR’s strategic focus on digital experience, innovation, and sustainable growth. However, AI also introduces governance challenges. AI systems can act autonomously, operate at high speed, and learn over time, which challenges traditional approval-based decision structures. Risks related to explainability, bias, data protection, regulatory compliance, and accountability increase as AI influences customer-facing and safety-critical services. Differences in national regulation further complicate AI deployment across regions. ICR’s governance model combines clear global direction with local autonomy. The Board defines strategic objectives, risk appetite, and global principles, while local branches and service owners have flexibility in how they achieve outcomes within regulatory and legal boundaries. This governance pattern enables experimentation and innovation while maintaining compliance, consistency, and accountability. ICR’s existing governance both enables and constrains AI adoption. Strong compliance, audit, and risk management practices support trust and regulatory alignment but may slow adoption if applied too rigidly. Local autonomy supports innovation but requires stronger coordination to avoid fragmentation of AI practices and inconsistent customer experience. To address this, ICR is evolving its governance approach to AI. AI use cases are being classified by risk and impact, with governance intensity matched accordingly. Lower-risk AI solutions are enabled through local experimentation, while higher-risk applications require stronger oversight, clear accountability, explainability, and human-in-the-loop controls. Internal audit and reporting mechanisms are being extended to include AI-specific evidence and monitoring. Through this approach, ICR aims to enable responsible AI adoption that supports innovation, maintains trust, and aligns AI-enabled decisions with business objectives, regulatory requirements, and customer expectations.

Strategy:
ICR’s strategy centres on pioneering digital, sustainable mobility while growing globally and maintaining strong local responsiveness.

Vision statement:
“To be the world’s most trusted and innovative mobility partner, using digital technology and sustainable practices to enhance every journey for customers, wherever they travel.” This vision is realized through ICR’s strategy, which combines innovation, sustainability, a focus on customer experience, and sustainable growth. The company’s strategic direction has been transformed by the executive team into five strategic objectives, approved by the Board of Directors. Each objective has been further detailed into strategic initiatives. To implement these initiatives, many ICR teams will have to work together, involving external suppliers where additional resources and competencies are needed.

Objective 1: Lead in digital customer experience ICR aims to offer a seamless, app-first experience that makes renting, sharing, and returning vehicles effortless across all markets. Roll out a unified global mobile platform with localized features, languages, and payment options. Embed AI-driven capabilities such as predictive maintenance, smart check-in/return, and proactive support into all core services. Establish continuous discovery and UX improvement cycles led by product and business analysis teams.

Objective 2: Innovate in autonomous and new mobility services ICR wants to be an early and trusted provider of self-driving and car-sharing services where regulations allow, integrating them into its mainstream portfolio. Launch regulated pilots for self-driving and car-sharing services in priority markets, starting with the US and expanding to EU and other markets. Build a standardized service design and safety framework for autonomous services, aligned with local laws and ICR’s low risk appetite in safety and data protection. Create joint innovation programmes between product, architecture, and operations to scale successful pilots globally.

Objective 3: Grow sustainably and profitably across markets ICR seeks to expand through franchising, mergers, and acquisitions while maintaining strong financial performance and customer loyalty. Maintain an up-to-date integration playbook covering governance, branding, systems, and supplier relationships for new acquisitions. Implement market- and service-level performance dashboards tracking revenue, market share, innovation progress, and customer satisfaction. Optimize fleet and cost structures using analytics to balance utilization, pricing, and sustainability targets.

Objective 4: Embed sustainability and social responsibility ICR intends to align its growth with environmental responsibility and evolving city and national regulations. Define clear sustainability targets (such as fleet emissions profile, use of EVs, or eco-options in the app) and report progress regularly. Cooperate with cities and regulators to adapt services to local environmental rules, parking policies, and low-emission zones. Design service offerings that reward sustainable choices, such as greener vehicle options or smarter routing.

Objective 5: Strengthen governance, risk, and capabilities ICR will maintain robust governance while allowing local autonomy, ensuring decisions are fast, compliant, and data-informed. Clarify and document global and local decision rights, principles, and escalation paths for all service lines. Enhance internal audit, compliance monitoring, and digital evidence-tracking across all countries and franchises. Invest in skills and certifications (ITIL, DevOps, data governance) for key roles such as CIO and office, product, delivery, and architecture. managers to support continual transformation.

Transformation:
ICR always looks for opportunities to expand the business to new markets. As part of this strategy, the company agreed an acquisition of a local rental company in a small, fast-developing country in Europe. The company being acquired has an established customer base and reputation in its home country. It is known in neighbouring countries, though it does not have branches in them. The government of the country where the company is based just passed a regulation approving use of self-diving vehicles, and ICR is keen to be the first provider of such a service in the region. The acquired company needs to be integrated into the ICR governance and management structure and information systems, including internal and customer-facing systems. The objective is to retain the existing customer base, provide reassurance that the acquisition will improve (rather than worsen) the quality of familiar rental services, and introduce new service lines (car-sharing, self-driving cars). The Board of Directors expects the integration to be completed within three months (including branding, information systems, governance, people, and relationships with local suppliers). ICR identified five transformational initiatives that need to be completed to fulfil the transformation:

1. Governance and structure integration ICR needs to integrate the acquired company into its existing governance model by aligning the local board reporting lines, decision rights, and accountability with ICR’s global principles, while preserving a high degree of local autonomy for market- and service-specific decisions. This includes defining how the local management team participates in ICR’s governance forums and how global policies, such as risk management and sustainability, are applied in the new country. ICR has gone through this many times and has an established playbook for governance and management integration, which proved to be effective during previous acquisitions.

2. Regulatory, risk, and compliance setup ICR must establish a comprehensive regulatory and compliance framework for the new market, with particular emphasis on the newly approved self-driving vehicle regulation and existing rules for rental and car-sharing services. This initiative should set up local controls and escalation paths consistent with ICR’s low risk appetite in safety, data protection, and traffic law. These controls and paths should be supported by internal audit oversight and appropriate reporting mechanisms. The company also has extensive experience in this area; however, every new country introduces new challenges which sometimes need to be addressed quickly.

3. Technology and platform integration ICR needs to migrate or integrate the acquired company’s systems into its global digital ecosystem, including customer-facing apps, booking platforms, fleet and maintenance systems, and analytics. During the transition period, ICR must ensure continuity of service for existing customers. AI-enabled capabilities such as predictive maintenance, smart check-in/return, and customer support should be progressively rolled out to the new operation, aligning with local regulations and infrastructure. Although the existing technology solutions of the acquired company were briefly assessed before the acquisition, there is a lot to explore, and the technology team should be ready for surprises.

4. Brand, customer, and stakeholder transition A coordinated rebranding and customer communication programme is required to transition the local brand to ICR within three months. This communication should clearly explain that familiar services will be maintained or improved and that new options like car-sharing and self-driving services will be introduced. In parallel, ICR should engage proactively with local authorities, business customers, partners, and suppliers to reinforce trust, clarity expectations, and position ICR as an innovative yet reliable mobility provider in the region. ICR has a playbook for such campaigns, but for it to be effective, detailed information about the customers, their expectations, and the ongoing relationships is needed.

5. Operating model, people, and service portfolio ICR should redesign the local operating model to match its global standards, including roles, responsibilities, and performance metrics, while retaining local knowledge and relationships that underpin the acquired company’s reputation. As part of this, the service portfolio in the new country should be structured to cover traditional rental, car-sharing, and self-driving services under a unified framework, with clear service ownership, targets for commercial performance and customer satisfaction, and mechanisms for rapid local decision-making. Although ICR has a large and positive experience of adapting the operating models of acquired companies, introduction of the self-driving cars to a new market is a new and challenging task. Together, these transformation efforts should allow ICR to enter the new region as a trusted, forward-looking mobility partner. Supported by strong governance, modern technology, and an effective integration approach, ICR is well positioned to deliver a reliable, future-ready travel experience to customers in its newest market.

Experience:
Understanding user experience as a strategic imperative
ICR recognizes that achieving a sustainable competitive advantage in modern mobility depends fundamentally on delivering exceptional user experience. Max articulated in his vision for the company that “customers want seamless and immediate access to rental services from their smartphones, as well as innovation as part of their daily lives.” This expectation applies not only to traditional car rental services but extends across the expanding portfolio of car-sharing and driverless tax offerings. The digital applications and web interfaces that customers interact with have become the primary touchpoints for the ICR brand, making digital experience inseparable from overall business success.
The customer journey across digital touchpoints
The user journey with ICR spans multiple critical steps, each mediated through digital applications and interfaces: Discovery and search begin when prospective customers evaluate their mobility options. Here, ICR’s digital presence must clearly communicate availability, pricing transparency, and service advantages over competitors, whether customers are considering traditional car rental, flexible car-sharing, or autonomous ride options. Registration and onboarding follow as users create profiles and establish trust with the platform. At this point they share their personal data, driving licence, and financial details with ICR. This makes this step particularly important for building trust and capturing customer preferences that will enhance future interactions. Selection and booking require intuitive navigation and clear presentation of options. The digital interface must accommodate the different decision-making patterns across the three service modes: the planning-focused car rental customer, the spontaneous car-sharing user, and the on-demand autonomous ride passenger. Payment processing must inspire confidence while remaining frictionless. Secure, flexible payment options that adapt to different service models strengthen customer trust and reduce transaction abandonment. This is a sensitive aspect of service interactions, as car rental users are often worried about unexpected security deposits, additional charges and costly insurance. Although this part of user journey often seems to be less important than the core service utility, it may have a significant and sometimes damaging impact on the overall experience. Check-in and vehicle access have evolved significantly with smart technologies. Digital applications now provide seamless vehicle access, reduced friction at pick-up, and immediate problem resolution when complications arise. In-journey support enables customers to address questions or concerns in real time.
Whether requesting roadside assistance, reporting issues, or seeking clarification, rapid response through integrated digital channels demonstrates the ICR’s commitment to the travel experience it has promised. Check-out and feedback close the transaction but open an opportunity for continual improvement. Digital interfaces capture usage data, soliciting feedback that informs service enhancements.
Differentiation across service models
While these touchpoints are universal, their expression differs significantly across ICR’s service offerings. Traditional car rental customers typically plan ahead, expecting detailed vehicle information and insurance clarity through structured booking flows. Car-sharing users demand spontaneity and simplicity, prioritizing booking speed and lock/unlock mechanisms. Driverless taxi passengers expect transparency about autonomous capabilities, safety systems, and real-time trip information without the complexity of vehicle selection.
Capturing, analysing, and improving user experience
Recognizing that understanding is a prerequisite to improvement, ICR has embedded experience measurement into the digital ecosystem. ICR applications capture behavioural data (interaction patterns, abandonment points, feature usage, and satisfaction signals), providing teams with rich insight into the customer journey and occurring points of friction. This data flows into structured analysis processes. Maria, the Business Analyst, uses AI to identify patterns and trends that highlight experience bottlenecks and opportunities. Cross-functional collaboration between Anna’s product management, Sam’s product development oversight, and Omar’s service delivery team ensures that insights translate into rapid and noticeable improvements. The teams employ both quantitative metrics (completion rates, task duration, error frequency) and qualitative feedback mechanisms. Customer surveys, user testing sessions, and support interaction analysis combine with operational data to paint a complete picture of experience quality. Improvement cycles operate continuously, enabled by the ICR’s commitment to the end-to-end product and service lifecycle management and iterative development. The service enhancements are tested incrementally, which allows the teams to measure their impact and iterate rapidly. This approach ensures that ICR remains responsive to evolving customer expectations while maintaining the reliability and service quality that have defined the company’s reputation. By treating user experience as both a strategic priority and an operational discipline, ICR ensures that the company’s digital services serve their essential purpose: enabling customers to access mobility solutions effortlessly, building loyalty through consistent excellence, and positioning ICR as the thoughtful choice in an increasingly competitive and technologically sophisticated market.

Product:
ICR’s Unified Mobile App: A Product Lifecycle Journey
The challenge:
ITIL Car Rental’s vision for digital transformation demanded a bold move: consolidating traditional car rental, car-sharing, and emerging autonomous vehicle services into a single, seamless mobile application. This unified platform would serve millions of customers globally while adapting to diverse regulatory environments and local market conditions. The product team (led by Sam and guided by Anna’s product management expertise, Maria’s business analysis insight, and Alex’s architectural know-how) embarked on a comprehensive product lifecycle journey.

Discover: charting the course:
The team began by analysing the business context using the PESTLE method. Regulatory changes permitting autonomous vehicles in several markets, shifting customer expectations towards mobile-first experiences, and competitive pressures from ride-sharing services created both urgency and opportunity. Sam convened discovery sessions with stakeholders across the organization. Market analysis revealed fragmented customer expectations: traditional renters wanted clarity and planning capability; car-sharing users demanded spontaneity and speed; autonomous rice passengers expected transparency and trust. Maria identified critical patterns in user behaviour across regions, while Alex assessed the architectural implications of managing three distinct service models within a single platform. The team agreed strategic direction: create one app that intelligently presents rental, sharing, and autonomous options based on user context and local regulations. This vision was communicated across all product teams, establishing alignment and guiding subsequent activities. Investment in the initiative was secured, with clear timelines and resource commitments.

Design: shaping the experience:
Service design workshops brought together user research, human-centred design principles, and regulatory requirements. Anna led a detailed analysis of the customer journey across all three service models, identifying touchpoints, decision moments, and friction points. The design iterations incorporated feedback from early user testing. The team prototyped distinct user flows: a structured booking experience for renters planning days ahead; a rapid-access interface for car sharing users; and a transparent, safety-focused experience for autonomous ride passengers. Meanwhile, Alex developed target architecture blueprints ensuring that different service models could scale independently while sharing core infrastructure for authentication, payment, and support. Design specifications documented user interface, service interactions and operational requirements. The team designed for continuous improvement: metrics, feedback mechanisms, and analytics touchpoints were embedded into the design from the outset.

Acquire: securing resources:
With design specifications complete, the ‘acquire’ activity identified the required resources. Cloud infrastructure capable of handling peak demand across multiple regions; AI/machine learning services for predictive maintenance and smart routing; payment processing services compliant with regulations in each market; map and navigation services adapted to local conditions. The team assessed sourcing options, negotiating contracts with multiple cloud providers and service partners. Procurement was coordinated carefully to ensure integration readiness. Resource availability was confirmed before the ‘build’ phase began, preventing downstream delays.

Build: constructing the solution
The product development team, under Sam’s oversight, executed a phased build approach. The core app framework was developed first, establishing shared foundations for authentication, payment processing, and support channels. Feature teams then implemented the rental, sharing, and autonomous service modules in parallel, maintaining integration points and shared design patterns. Rigorous testing occurred throughout. Service validation teams ensured the app functioned flawlessly across devices, network conditions, and geographic regions. Integration testing verified that switching between service models felt seamless. Security testing confirmed compliance with data protection requirements in each market. Supporting documentation, including user guides, service manuals, and operational runbooks, was developed alongside the software.

Transition: going live:
Before full launch, the team executed a carefully staged transition strategy. Soft launches in select markets allowed real users to interact with the new experience under controlled conditions. Omar, the IT Delivery Manager, coordinated the operational handover, ensuring monitoring systems captured live performance data and incident response procedures were operational. Supplier onboarding was critical: map service providers, payment processors, and cloud infrastructure teams needed to understand their roles in the live environment. Customer communication emphasized that familiar services would be enhanced, not disrupted. The team monitored the transition closely, ready to address any issues.

Operate: maintaining excellence:
With the app in live environments, the ‘operate’ activity ensured continuous, reliable performance. Infrastructure monitoring tracked application health, system performance, and availability across regions. The team managed routine updates, security patches, and scaling adjustments responding to demand fluctuations. Automated systems monitored performance metrics: response times, transaction completion rates, error frequencies.
When deviations appeared, such as unusual latency in a particular region or unexpected payment processing delays, alerts triggered investigation and rapid response.

Deliver: serving customers:
The ‘deliver’ activity brought the product to life for customers. Service delivery teams ensured seamless onboarding to new users, providing multiple languages, localized payment options, and support channels adapted to each market. Service level agreements committed to fast booking, reliable vehicle access, and responsive support. Customer service teams used the app’s built-in support features (in-app chat, knowledge bases, and contextual help) to address questions. Anna monitored service quality metrics and customer satisfaction indicators religiously. Usage patterns revealed which features resonated, where users abandoned workflows, and which regions had distinct preferences.

Support: resolving and learning:
Despite meticulous planning, incidents occurred. A payment processing outage in one market triggered rapid incident response: the support team engaged customers, offered alternatives, and restored service within hours.
When an unexpected interaction between autonomous ride features and local traffic regulations created user confusion, the team diagnosed the issue, implemented a fix, and deployed it to users within days. More importantly, each incident triggered investigation.
Why did it happen? What signals did we miss? How do we prevent recurrence? Post-mortem reviews informed improvements to both the app and the operational processes. Issues discovered in ‘support’ fed back into the ‘discover’ and ‘design’ cycles, continuously refining the product.

Continual improvement:
The journey from ‘discover’ to ‘support’ was not linear but cyclical. Feedback from ‘support’ informed new ‘discover’ iterations as market conditions evolved. Performance data from ‘operate’ fed into ‘deliver’ improvements. Customer insights from ‘deliver’ shaped strategic decisions about feature prioritization and regional adaptations. By embedding DPSM practices throughout this lifecycle, ICR’s unified mobile app became more than a technical achievement. It became a reflection of the company’s commitment to customers: reliable, innovative, responsive to local needs, and continuously improving. As Max envisioned, ITIL Car Rental had taken a bold step toward being the world’s most trusted mobility partner, delivering the vision through every customer interaction, every design decision, and every operational moment.

Service:
Implementing a global HR management service: an internal service lifecycle
The challenge:
ITIL Car Rental’s expansion across multiple regions and service lines created mounting complexity in workforce management. Different legal entities, varying employment regulations, localized payroll requirements, and regulatory compliance across jurisdictions had strained the company’s aging HR systems. The company’s executive team identified modernization of HR management services as essential to support ICR’s growth strategy whilst maintaining operational consistency and compliance across markets. Omar’s IT delivery team took ownership of implementing a new vendor-supplied HR management system, a solution that would run on ICR servers, integrate seamlessly with existing internal systems, and serve thousands of employees and contractors across dozens of countries.

Discover: understanding the landscape
The team began by organizing a comprehensive ‘discover’ iteration. Assessing the organizational context, the team analysed how ICR’s expansion strategy, new regulatory requirements in different markets, evolving workplace expectations, and the growing complexity of managing multiple legal entities across regions created both pressure and opportunity for modernization. Working closely with the HR business partner and Max’s office, Omar’s team gathered requirements from across the organization: HR representatives and business managers in each country, payroll departments, compliance officers, finance teams managing workforce costs, and executives overseeing the talent strategy. The discovery revealed critical patterns. European operations faced strict data protection and employment law requirements. Asia-Pacific branches needed sophisticated multi-currency payroll capabilities. The US and Canadian operations required integration with complex benefits administration systems. Every region needed consistency in talent management and performance tracking, yet each had distinct regulatory demands. A business analyst from Omar’s team documented these needs systematically, whilst Alex, the Enterprise
Architect, assessed the technical implications of supporting multiple legal entities, integrating with existing systems (payroll, finance, learning management, employee engagement platforms), and ensuring data security and regulatory compliance. The vendor’s product roadmap was evaluated against ICR’s requirements, revealing both strong alignment and specific gaps requiring customization. The team agreed on a clear direction: implement a core HR platform from a reputable software vendor as the system of record for employee master data, organizational structure, and talent management across all regions, while integrating specialized capabilities for payroll, benefits, compliance reporting, and data protection. Investment was secured with realistic timelines accounting for the complexity of multi-region deployment, and a formal steering committee was established to guide implementation.

Design: defining the solution:
With requirements agreed, Omar’s team began detailed design activities. Service design workshops brought together local HR representatives, payroll specialists, compliance officers, and technology architects. The team mapped existing HR processes in each region, identifying which would be standardized globally and which would require local customization. Design workshops revealed critical service interactions. HR teams needed intuitive interfaces for managing recruitment, onboarding, performance management, and learning across different employment models. Employees required easy access to personal information, benefits enrolment, and career development features. Payroll teams needed reliable data integration with local accounting systems and regulatory reporting tools. Compliance officers required audit trails, secure data management, and reporting to meet legal obligations in each jurisdiction. Alex developed detailed integration architecture, specifying how the HR system would communicate with existing payroll, finance, learning management, and employee engagement platforms. Data flows were mapped, ensuring that changes in one system were reliably distributed to dependent systems without manual intervention or data errors. Security and data protection requirements were designed into every integration point; this was particularly critical given GDPR, CCPA, and local data residency requirements. Data migration became one of the key design points. The team designed a phased deployment approach: implementation across ICR headquarters first, then staged rollout to major regional clusters, enabling learning and refinement before full global deployment. Supporting documentation, such as user guides for different roles, migration playbooks, and integration manuals, was planned in detail.

Acquire: securing resources:
With design specifications complete, Omar’s team identified required resources. The vendor’s licensing model (supporting anticipated growth); implementation consultant expertise (to guide customization and deployment); cloud infrastructure capacity for testing and staging environments; integration middleware (to connect the new HR system with existing enterprise systems); and data migration tools were all specified. The ‘acquire’ activity involved careful sourcing decisions. The vendor partnership was formalized, establishing support levels (the vendor providing third-line support, with first-line and specialist support to be provided by Omar’s team). External systems integrators with expertise in the vendor’s platform and multi-region HR implementations were evaluated and contracted. Cloud infrastructure capacity was procured, allowing for future growth. Service agreements included service level commitments and compliance obligations aligned with ICR’s governance standards. Resources were also identified internally: team members who would receive specialized training to support the system; members of Omar’s operations team who would provide day-to-day administration; security and compliance specialists to oversee implementation controls. Procurement was coordinated to ensure availability ahead of the ‘build’ phase.

Build: constructing the solution
Omar’s team established an implementation program, structured as a series of building activities. First, the core HR system was configured to match ICR’s organizational structure, employment classifications, and role hierarchies. Configuration activities addressed fundamental requirements: multi-legal entity support, multi-language and multi-currency capabilities, and foundational data structures. Parallel to core configuration, integration development began. The team, supported by the vendor and a vendor’s consulting partner, configured data flows from the HR system to payroll systems, ensuring employee changes (salary adjustments, location changes, benefits modifications) flowed reliably to payroll processing. Integration with the finance system ensured workforce costs were accurately captured. Learning management system connections ensured course assignments and certifications were synchronized. Security and compliance controls were embedded throughout, including audit logging, data encryption, access controls, and automated reporting for regulatory requirements. Extensive testing occurred throughout the ‘build’ phase. Functional testing verified that each configuration matched requirements. Integration testing validated that data flowed correctly between systems without errors or data loss. Security testing confirmed that sensitive personal data was protected and that access controls functioned as designed. Business process testing involved HR teams walking through common scenarios (such as hiring a new employee, transferring someone to a different country, or managing a separation), ensuring the system supported the complete workflow. User acceptance testing engaged representatives from different regions and roles. HR teams in Germany tested GDPR compliance features. Payroll teams in multiple countries verified that their specific regulatory requirements were met. Local compliance officers confirmed that reporting would support local legal obligations. Supporting documentation, such as operational runbooks for system administration, user guides tailored to different roles, and troubleshooting guides, was developed and reviewed. Apart from the HR teams, selected users from all affected teams were involved, testing the interfaces and workflows for requesting leave, conducting assessments, reserving training, of reporting HR incidents. These tests revealed the need for end-user training and onboarding during the new service roll-out. Transition plans were updated to allow time for this.

Transition: going live:
The team carefully prepared a transition strategy. Headquarters implementation was planned first, serving as a dress rehearsal. A parallel run, with both old and new systems operating simultaneously, was conducted for three weeks, allowing both systems to process payroll and generate reports for comparison. The payroll teams validated that the new system calculated amounts identically to the legacy system, detecting and resolving discrepancies before they affected employees. Omar coordinated the preparation activities. User training was delivered to HR teams, payroll specialists, managers, and employees. Help desks were staffed and trained. Communication plans explained the transition to all users, emphasizing continuity of services and highlighting new capabilities. Vendor support teams were onboarded, understanding their roles during the transition period. Data migration, which involved extracting employee master data from legacy systems, cleansing it, loading it into the new system, and validating completeness and accuracy, was carefully orchestrated and verified. Transition day at headquarters was carefully planned. The legacy system was frozen at a specific point, a final data extract was taken, loaded into the new system, and system access was switched over. The team remained staffed throughout the transition and into the following week, monitoring system performance closely, responding to questions, and resolving issues. Incident response procedures were in place, with escalation paths to the vendor’s support team available if needed. Following successful headquarters transition, the team planned regional deployments. Each regional cluster (Europe, Asia-Pacific, Americas) had a transition period, with lessons from earlier transitions incorporated and local considerations addressed. The staggered approach allowed the central team to support each region and enabled best practices to propagate from early transitions to later ones.

Operate: maintaining excellence:
With the system live across regions, Omar’s team shifted focus to reliable operations. Infrastructure monitoring tracked system health, performance, and availability across all deployment sites. Automated health checks, such as database integrity tests, integration validation, and backup verification, ran daily, alerting the team to any deviations from expected operation. The team established routine operational activities: security patches supplied by the vendor were tested in staging environments, then deployed to production overnight. Data backups were performed daily, with regular restoration tests confirming that recovery was possible. System performance was monitored, with growth projections ensuring sufficient capacity as employee counts increased. User access was reviewed every week, ensuring that accounts of employees that had left the company were promptly deactivated and that role changes were reflected in system permissions.
When issues appeared, monitoring detected these deviations and triggered investigation. The team maintained a problem backlog, working with the vendor to address underlying issues and implementing fixes or workarounds as appropriate.

Deliver: serving the organization
The ‘deliver’ activity brought the HR system into daily organizational use. Omar’s team established service level commitments: HR teams would have to access to the system 99.5% of the time; user support queries would be acknowledged within four hours; critical issues affecting payroll or compliance would be resolved within eight hours. The team was constrained by the respective commitments of the vendor and, although in many cases a higher service level was provided, it could not be formally committed to. A first-line support team knowledgeable about ICR’s specific configuration and trained on common issues responded to user questions. A knowledge base captured solutions to frequent issues, enabling self-service support. Employees received training on using the service: how to access their information, update personal details, enrol in benefits, and request time off through the HR portal. Delivery included routine service actions: onboarding new employees to the system (ensuring they were created with appropriate access and initial data); offboarding departing employees (deactivating access, generating final pay calculations, archiving records); managing organizational changes (updating reporting structures when teams were reorganized); conducting benefits enrolment campaigns (ensuring employees could select and modify coverage). The team monitored delivery metrics carefully: system availability, user satisfaction (gathered through surveys), processing timeliness (time from employee action to system reflection), and error rates (incorrect calculations, missing data). Service level reporting informed ongoing improvements and triggered escalations if service quality threatened to fall below the agreed level.

Support: resolving and learning:
Despite robust operational procedures, incidents occurred. A payroll integration process failed one month due to an unexpected data format in the finance system, causing a four-hour delay in the payroll. The support team immediately engaged payroll managers, communicating the issue and estimated resolution time. The technical team worked with the finance team and the vendor to understand the root cause, developed a fix to handle the unexpected data format, implemented the fix, reran the integration process, and verified accuracy. By the end of the day, normal payroll processing resumed. On another occasion, a regional compliance officer discovered that a localized tax calculation in one country was producing results that didn’t align with current regulations. The incident was escalated to the vendor’s specialist support team. Together, they analysed the regulation change, determined that a configuration parameter needed adjustment, updated the system, revalidated historical calculations, and rolled forward with correct calculations prospectively. Each incident triggered a post-mortem review, where the support team asked: why did the issue occur? Were there warning signs we missed? How do we prevent recurrence? Findings from post-mortems informed improvements to configuration, integration design, monitoring, documentation, and training. Particularly significant improvements, such as enhanced validation of finance system data before processing payroll, were incorporated into the ‘discover’ and ‘design’ phases to shape future improvements.

Continual improvement:
The journey from ‘discover’ to ‘support’ was cyclical. Feedback from ‘support’, including new issues and lessons learned, informed new ‘discover’ iterations as regulations evolved, ICR’s business expanded into new markets, or new compliance requirements emerged. Performance data from ‘operate’ informed design improvements when system bottlenecks were identified or user experience could be enhanced. User feedback from ‘deliver’, captured through surveys and support interactions, shaped priorities for new features and refinements.
When HR teams requested better reporting capabilities to support talent analytics, this feedback was captured, evaluated during ‘discover’ activities, and prioritized in design cycles. By embedding DPSM practices throughout this lifecycle, Omar’s team transformed HR management at ITIL Car Rental.
What had been a patchwork of legacy systems and manual processes became a unified, reliable platform supporting the company’s global growth. Compliance risks were reduced through automation and audit trails. HR teams gained visibility into workforce data and could respond quickly to business needs. Employees had instant access to their information and could manage their own preferences. The system provided a foundation for HR analytics, enabling data-driven decisions about talent, compensation, and organizational structure. As Max envisioned, ICR’s transformation extended beyond customer-facing products to the internal systems and processes that enabled the company to operate effectively. By treating internal HR services with the same rigor and discipline as external products, Omar’s team ensured that ITIL Car Rental’s greatest asset, its people, were supported by systems as reliable, responsive, and capable as the mobility services ICR offered to customers worldwide. Please refer to the ITIL Car Rental scenario for additional context when answering this question. Customer feedback has shown rising expectations for faster mobile booking and personalized features. ICR has recognized this market-driven need but wants to objectively assess whether current product management, development, and service operations practices have sufficient capability to deliver expected performance levels before planning specific improvements.
Which tool BEST supports this assessment?

  1. ITIL Maturity Model
  2. Stakeholder mapping
  3. Complexity thinking
  4. Cost of Delay

Answer(s): A



Introduction to ITIL Car Rental:
Ten years ago, ITIL Car Rental (ICR) was launched in Seattle with the aim to provide convenient and affordable rental cars to customers around the world. After a relatively short time, ICR became a globally recognized company, with a wide network of franchising partners across Europe, the US, and Asia-Pacific, with approximately 400 direct employees. In the first few years of operation, repeat business accounted for nearly a third of all reservations. Shareholders saw steady growth, and the company earned a reputation for putting customers first. ICR quickly became a model of modern mobility: fast, reliable, and profitable. Following its early success, the company expanded through mergers and acquisitions to new markets and new services, including car sharing. ICR relies heavily on digital technology for internal operations and service delivery, using a mix of internal and external digital products. Customer-facing mobile applications are developed and run by the internal IT team. AI is increasingly used in internal and external products and services for predictive maintenance, customer support, scheduling, smart check-in and return processes, and so on. As new competitors, such as car-sharing services, rideshare apps, and driverless cars, enter the market, customers now expect a seamless digital experience: quick bookings, app-based help, and flexible options that fit easily into their daily lives. At the same time, customers are paying more attention to companies that value social responsibility, sustainability, and environmental consciousness. These expectations are driving ICR to set clear and ambitious sustainability goals, as well as pursue further growth. The board members strongly believe that the company’s success in the years to come will be defined by innovation and the use of digital technology. For this reason, they appointed a new GIO, Max. Max was chosen for his experience in digitalization and his track record in successful, large-scale IT transformations. Max’s strong background in ITIL and ITSM indicates that he values ITIL certification, and his hiring policy reflects this. Having worked with Design Thinking, DevOps, and agile methods, he believes sustainable business requires a blended approach to digital product and service management. Max is keen to see how his team can redefine the car rental experience and ensure that ICR is the first choice for new and existing customers.

Meet the employees of ITIL Car Rental:
Max, Chief Information Officer (CIO):
Max is the new CIO. He is an experienced executive with a track record of leading digital transformations. He believes in an integrated approach to DPSM.

Anna, Product Manager:
Anna has been with ITIL Car Rental for five years. She focuses on commercial success and continual B2C development. She is detail-oriented, eco-conscious, and dedicated to improving overall customer experience.

Maria, Business Analyst:
Maria is a proactive communicator who ensures smooth collaboration between IT and business teams. She works mostly on discovery and planning activities, supporting continual improvement of the company’s digital products. She asks a lot of questions and is great at spotting patterns and trends.

Omar, IT Delivery Manager:
Omar manages ongoing service delivery. He applies ITIL practices to improve efficiency and customer satisfaction. However, Omar has had little experience with a blended or collaborative approach to product and service management.

Sam, Head of Product Development:
Sam has more than 10 years of experience in leading cross-functional product teams in the domains of mobility and automotive innovation. He oversees the entire product lifecycle at ITIL Car Rental from strategic vision to delivery and ensures that customer needs, market trends, and sustainability are all in sync.

Alex, Enterprise Architect:
Alex is responsible for ensuring that product design and technological strategy are aligned, sustainable, and future-proof. She provides architectural guidance across teams, works to identify systemic risks, and holds coherence in a fast-changing digital ecosystem. She is highly analytical with a strong intuition for patterns and risks.

The CIO’s vision for ITIL Car Rental Max:
We live in an era of rapid change, where all companies are going through some kind of digital transformation. Service expectations have changed drastically since ITIL Car Rental was created 10 years ago. Customers want seamless and immediate access to rental services from their smartphones, as well as innovation as part of their daily lives. Autonomous vehicles are the future; they will make car rental companies stand out and continue successfully. My vision is for ITIL Car Rental to pioneer this transformation and become the go-to name for car rentals worldwide. We will continue offering outstanding customer service while maintaining competitive car rental rates. After all, ITIL Car Rental is more than just a service. We are here to enhance the entire travel experience.

Governance:
ITIL Car Rental has branches in other countries, some of which are franchises. Each country may have its own regulations when it comes to the services offered by ICR. Although all services are focused on enhancing the entire travel experience, different services may be subjects to different regulation. For example, car-sharing is regulated differently, and self-driving cars cannot be introduced at all in some countries. ICR has adopted a governance approach that blends clear global direction with local autonomy, enabling the company to stay competitive in a fast-moving mobility landscape. As ICR continues to grow across regions and expand its portfolio, moving from traditional rentals to car-sharing and self-driving services, its governance structure ensures consistency, compliance, and customer-focused innovation. ICR’s approach to change is practical and adaptive. The company encourages experimentation and continual improvement as long as new ideas follow shared principles and meet regulatory expectations in each market. This balanced approach helps ICR introduce new digital features quickly while maintaining trust and reliability. The Board evaluates progress through a focused set of indicators, including commercial results, market share, innovation outcomes, cost efficiency, and customer satisfaction. Coordinated autonomy is a key feature of ICR’s governance.
While the Board defines the overall vision and strategic direction, local branches and service owners have freedom in how they achieve their goals. Market leaders and service-line managers work closely to tailor solutions to regional needs, ensuring that global standards remain compatible with local realities. Risk management reflects the diverse environments in which the company operates. Within heavily regulated domains, such as safety, traffic rules, and data protection, the company maintains a very low risk appetite and prioritizes prevention. In innovative settings, ICR accepts limited risks as long as they are identified early and controlled quickly. ICR’s operational context is constantly changing. Regulations evolve, cities introduce new environmental rules, and economic factors such as tariffs or sanctions may affect the business. To stay ahead, ICR continuously monitors these developments and adjusts its operations accordingly. To achieve this, the company relies on fast decision-making. Local teams and product groups can act independently within agreed principles and legal boundaries, allowing ICR to respond to customer needs and regulatory changes without delays. Compliance is an essential pillar of the governance model. Because requirements vary widely by region and service type, compliance responsibilities are distributed across the organization. Internal audit provides central oversight to ensure consistency and coherence using digital systems to standardize reporting and track evidence. ICR also serves a wide variety of stakeholders, ranging from city authorities to business clients and service partners. Their expectations differ by region, engagement approaches are adapted to local circumstances while staying aligned with ICR’s values and commitments. The company’s global reach demands broad governance oversight. Digital systems and processes are shared internationally but are tailored to each country’s regulations, customer behaviour, and available services. This combination helps ICR operate as a unified global brand while remaining locally relevant. Overall, ICR’s governance capabilities are well-established. Accountability is clear at board level, with defined responsibilities for central and local leaders. Regular audits and strong analytical tools support informed decision-making. As the company expands into new markets and introduces new mobility solutions, this governance foundation enables the company to grow responsibly, innovate confidently, and maintain a high standard of service for customers worldwide.

AI Governance:
Artificial Intelligence (AI) is increasingly embedded in ITIL Car Rental’s digital products and services. AI is used to support predictive maintenance, customer support, analytics, scheduling, and smart check-in and return processes. As ICR expands its service portfolio and geographic footprint, AI is expected to play a larger role in operational decision-making, customer experience, and service optimization. AI adoption creates new opportunities for ICR. AI-driven analytics can improve fleet utilization, sustainability performance, and cost efficiency. AI-enabled customer interaction can enhance responsiveness and personalization across markets. Automation and coordination capabilities can accelerate operational decisions and improve service reliability. These opportunities align with ICR’s strategic focus on digital experience, innovation, and sustainable growth. However, AI also introduces governance challenges. AI systems can act autonomously, operate at high speed, and learn over time, which challenges traditional approval-based decision structures. Risks related to explainability, bias, data protection, regulatory compliance, and accountability increase as AI influences customer-facing and safety-critical services. Differences in national regulation further complicate AI deployment across regions. ICR’s governance model combines clear global direction with local autonomy. The Board defines strategic objectives, risk appetite, and global principles, while local branches and service owners have flexibility in how they achieve outcomes within regulatory and legal boundaries. This governance pattern enables experimentation and innovation while maintaining compliance, consistency, and accountability. ICR’s existing governance both enables and constrains AI adoption. Strong compliance, audit, and risk management practices support trust and regulatory alignment but may slow adoption if applied too rigidly. Local autonomy supports innovation but requires stronger coordination to avoid fragmentation of AI practices and inconsistent customer experience. To address this, ICR is evolving its governance approach to AI. AI use cases are being classified by risk and impact, with governance intensity matched accordingly. Lower-risk AI solutions are enabled through local experimentation, while higher-risk applications require stronger oversight, clear accountability, explainability, and human-in-the-loop controls. Internal audit and reporting mechanisms are being extended to include AI-specific evidence and monitoring. Through this approach, ICR aims to enable responsible AI adoption that supports innovation, maintains trust, and aligns AI-enabled decisions with business objectives, regulatory requirements, and customer expectations.

Strategy:
ICR’s strategy centres on pioneering digital, sustainable mobility while growing globally and maintaining strong local responsiveness.

Vision statement:
“To be the world’s most trusted and innovative mobility partner, using digital technology and sustainable practices to enhance every journey for customers, wherever they travel.” This vision is realized through ICR’s strategy, which combines innovation, sustainability, a focus on customer experience, and sustainable growth. The company’s strategic direction has been transformed by the executive team into five strategic objectives, approved by the Board of Directors. Each objective has been further detailed into strategic initiatives. To implement these initiatives, many ICR teams will have to work together, involving external suppliers where additional resources and competencies are needed.

Objective 1: Lead in digital customer experience ICR aims to offer a seamless, app-first experience that makes renting, sharing, and returning vehicles effortless across all markets. Roll out a unified global mobile platform with localized features, languages, and payment options. Embed AI-driven capabilities such as predictive maintenance, smart check-in/return, and proactive support into all core services. Establish continuous discovery and UX improvement cycles led by product and business analysis teams.

Objective 2: Innovate in autonomous and new mobility services
ICR wants to be an early and trusted provider of self-driving and car-sharing services where regulations allow, integrating them into its mainstream portfolio. Launch regulated pilots for self-driving and car-sharing services in priority markets, starting with the US and expanding to EU and other markets. Build a standardized service design and safety framework for autonomous services, aligned with local laws and ICR’s low risk appetite in safety and data protection. Create joint innovation programmes between product, architecture, and operations to scale successful pilots globally.

Objective 3: Grow sustainably and profitably across markets ICR seeks to expand through franchising, mergers, and acquisitions while maintaining strong financial performance and customer loyalty. Maintain an up-to-date integration playbook covering governance, branding, systems, and supplier relationships for new acquisitions. Implement market- and service-level performance dashboards tracking revenue, market share, innovation progress, and customer satisfaction. Optimize fleet and cost structures using analytics to balance utilization, pricing, and sustainability targets.

Objective 4: Embed sustainability and social responsibility ICR intends to align its growth with environmental responsibility and evolving city and national regulations. Define clear sustainability targets (such as fleet emissions profile, use of EVs, or eco-options in the app) and report progress regularly. Cooperate with cities and regulators to adapt services to local environmental rules, parking policies, and low-emission zones. Design service offerings that reward sustainable choices, such as greener vehicle options or smarter routing.

Objective 5: Strengthen governance, risk, and capabilities ICR will maintain robust governance while allowing local autonomy, ensuring decisions are fast, compliant, and data-informed. Clarify and document global and local decision rights, principles, and escalation paths for all service lines. Enhance internal audit, compliance monitoring, and digital evidence-tracking across all countries and franchises. Invest in skills and certifications (ITIL, DevOps, data governance) for key roles such as CIO and office, product, delivery, and architecture. managers to support continual transformation.

Transformation:
ICR always looks for opportunities to expand the business to new markets. As part of this strategy, the company agreed an acquisition of a local rental company in a small, fast-developing country in Europe. The company being acquired has an established customer base and reputation in its home country. It is known in neighbouring countries, though it does not have branches in them. The government of the country where the company is based just passed a regulation approving use of self-diving vehicles, and ICR is keen to be the first provider of such a service in the region. The acquired company needs to be integrated into the ICR governance and management structure and information systems, including internal and customer-facing systems. The objective is to retain the existing customer base, provide reassurance that the acquisition will improve (rather than worsen) the quality of familiar rental services, and introduce new service lines (car-sharing, self-driving cars). The Board of Directors expects the integration to be completed within three months (including branding, information systems, governance, people, and relationships with local suppliers). ICR identified five transformational initiatives that need to be completed to fulfil the transformation:

1. Governance and structure integration ICR needs to integrate the acquired company into its existing governance model by aligning the local board reporting lines, decision rights, and accountability with ICR’s global principles, while preserving a high degree of local autonomy for market- and service-specific decisions. This includes defining how the local management team participates in ICR’s governance forums and how global policies, such as risk management and sustainability, are applied in the new country. ICR has gone through this many times and has an established playbook for governance and management integration, which proved to be effective during previous acquisitions.

2. Regulatory, risk, and compliance setup ICR must establish a comprehensive regulatory and compliance framework for the new market, with particular emphasis on the newly approved self-driving vehicle regulation and existing rules for rental and car-sharing services. This initiative should set up local controls and escalation paths consistent with ICR’s low risk appetite in safety, data protection, and traffic law. These controls and paths should be supported by internal audit oversight and appropriate reporting mechanisms. The company also has extensive experience in this area; however, every new country introduces new challenges which sometimes need to be addressed quickly.

3. Technology and platform integration ICR needs to migrate or integrate the acquired company’s systems into its global digital ecosystem, including customer-facing apps, booking platforms, fleet and maintenance systems, and analytics. During the transition period, ICR must ensure continuity of service for existing customers. AI-enabled capabilities such as predictive maintenance, smart check-in/return, and customer support should be progressively rolled out to the new operation, aligning with local regulations and infrastructure. Although the existing technology solutions of the acquired company were briefly assessed before the acquisition, there is a lot to explore, and the technology team should be ready for surprises.


4. Brand, customer, and stakeholder transition A coordinated rebranding and customer communication programme is required to transition the local brand to ICR within three months. This communication should clearly explain that familiar services will be maintained or improved and that new options like car-sharing and self-driving services will be introduced. In parallel, ICR should engage proactively with local authorities, business customers, partners, and suppliers to reinforce trust, clarity expectations, and position ICR as an innovative yet reliable mobility provider in the region. ICR has a playbook for such campaigns, but for it to be effective, detailed information about the customers, their expectations, and the ongoing relationships is needed.

5. Operating model, people, and service portfolio ICR should redesign the local operating model to match its global standards, including roles, responsibilities, and performance metrics, while retaining local knowledge and relationships that underpin the acquired company’s reputation. As part of this, the service portfolio in the new country should be structured to cover traditional rental, car-sharing, and self-driving services under a unified framework, with clear service ownership, targets for commercial performance and customer satisfaction, and mechanisms for rapid local decision-making. Although ICR has a large and positive experience of adapting the operating models of acquired companies, introduction of the self-driving cars to a new market is a new and challenging task. Together, these transformation efforts should allow ICR to enter the new region as a trusted, forward-looking mobility partner. Supported by strong governance, modern technology, and an effective integration approach, ICR is well positioned to deliver a reliable, future-ready travel experience to customers in its newest market.

Experience:
Understanding user experience as a strategic imperative
ICR recognizes that achieving a sustainable competitive advantage in modern mobility depends fundamentally on delivering exceptional user experience. Max articulated in his vision for the company that “customers want seamless and immediate access to rental services from their smartphones, as well as innovation as part of their daily lives.” This expectation applies not only to traditional car rental services but extends across the expanding portfolio of car-sharing and driverless tax offerings. The digital applications and web interfaces that customers interact with have become the primary touchpoints for the ICR brand, making digital experience inseparable from overall business success.
The customer journey across digital touchpoints
The user journey with ICR spans multiple critical steps, each mediated through digital applications and interfaces: Discovery and search begin when prospective customers evaluate their mobility options. Here, ICR’s digital presence must clearly communicate availability, pricing transparency, and service advantages over competitors, whether customers are considering traditional car rental, flexible car-sharing, or autonomous ride options. Registration and onboarding follow as users create profiles and establish trust with the platform. At this point they share their personal data, driving licence, and financial details with ICR. This makes this step particularly important for building trust and capturing customer preferences that will enhance future interactions. Selection and booking require intuitive navigation and clear presentation of options. The digital interface must accommodate the different decision-making patterns across the three service modes: the planning-focused car rental customer, the spontaneous car-sharing user, and the on-demand autonomous ride passenger. Payment processing must inspire confidence while remaining frictionless. Secure, flexible payment options that adapt to different service models strengthen customer trust and reduce transaction abandonment. This is a sensitive aspect of service interactions, as car rental users are often worried about unexpected security deposits, additional charges and costly insurance. Although this part of user journey often seems to be less important than the core service utility, it may have a significant and sometimes damaging impact on the overall experience. Check-in and vehicle access have evolved significantly with smart technologies. Digital applications now provide seamless vehicle access, reduced friction at pick-up, and immediate problem resolution when complications arise. In-journey support enables customers to address questions or concerns in real time.
Whether requesting roadside assistance, reporting issues, or seeking clarification, rapid response through integrated digital channels demonstrates the ICR’s commitment to the travel experience it has promised. Check-out and feedback close the transaction but open an opportunity for continual improvement. Digital interfaces capture usage data, soliciting feedback that informs service enhancements.
Differentiation across service models
While these touchpoints are universal, their expression differs significantly across ICR’s service offerings. Traditional car rental customers typically plan ahead, expecting detailed vehicle information and insurance clarity through structured booking flows. Car-sharing users demand spontaneity and simplicity, prioritizing booking speed and lock/unlock mechanisms. Driverless taxi passengers expect transparency about autonomous capabilities, safety systems, and real-time trip information without the complexity of vehicle selection.
Capturing, analysing, and improving user experience
Recognizing that understanding is a prerequisite to improvement, ICR has embedded experience measurement into the digital ecosystem. ICR applications capture behavioural data (interaction patterns, abandonment points, feature usage, and satisfaction signals), providing teams with rich insight into the customer journey and occurring points of friction. This data flows into structured analysis processes. Maria, the Business Analyst, uses AI to identify patterns and trends that highlight experience bottlenecks and opportunities. Cross-functional collaboration between Anna’s product management, Sam’s product development oversight, and Omar’s service delivery team ensures that insights translate into rapid and noticeable improvements.
The teams employ both quantitative metrics (completion rates, task duration, error frequency) and qualitative feedback mechanisms. Customer surveys, user testing sessions, and support interaction analysis combine with operational data to paint a complete picture of experience quality. Improvement cycles operate continuously, enabled by the ICR’s commitment to the end-to-end product and service lifecycle management and iterative development. The service enhancements are tested incrementally, which allows the teams to measure their impact and iterate rapidly. This approach ensures that ICR remains responsive to evolving customer expectations while maintaining the reliability and service quality that have defined the company’s reputation. By treating user experience as both a strategic priority and an operational discipline, ICR ensures that the company’s digital services serve their essential purpose: enabling customers to access mobility solutions effortlessly, building loyalty through consistent excellence, and positioning ICR as the thoughtful choice in an increasingly competitive and technologically sophisticated market.

Product:
ICR’s Unified Mobile App: A Product Lifecycle Journey
The challenge:
ITIL Car Rental’s vision for digital transformation demanded a bold move: consolidating traditional car rental, car-sharing, and emerging autonomous vehicle services into a single, seamless mobile application. This unified platform would serve millions of customers globally while adapting to diverse regulatory environments and local market conditions. The product team (led by Sam and guided by Anna’s product management expertise, Maria’s business analysis insight, and Alex’s architectural know-how) embarked on a comprehensive product lifecycle journey.

Discover: charting the course:
The team began by analysing the business context using the PESTLE method. Regulatory changes permitting autonomous vehicles in several markets, shifting customer expectations towards mobile-first experiences, and competitive pressures from ride-sharing services created both urgency and opportunity. Sam convened discovery sessions with stakeholders across the organization. Market analysis revealed fragmented customer expectations: traditional renters wanted clarity and planning capability; car-sharing users demanded spontaneity and speed; autonomous rice passengers expected transparency and trust. Maria identified critical patterns in user behaviour across regions, while Alex assessed the architectural implications of managing three distinct service models within a single platform. The team agreed strategic direction: create one app that intelligently presents rental, sharing, and autonomous options based on user context and local regulations. This vision was communicated across all product teams, establishing alignment and guiding subsequent activities. Investment in the initiative was secured, with clear timelines and resource commitments.

Design: shaping the experience:
Service design workshops brought together user research, human-centred design principles, and regulatory requirements. Anna led a detailed analysis of the customer journey across all three service models, identifying touchpoints, decision moments, and friction points. The design iterations incorporated feedback from early user testing. The team prototyped distinct user flows: a structured booking experience for renters planning days ahead; a rapid-access interface for car sharing users; and a transparent, safety-focused experience for autonomous ride passengers. Meanwhile, Alex developed target architecture blueprints ensuring that different service models could scale independently while sharing core infrastructure for authentication, payment, and support. Design specifications documented user interface, service interactions and operational requirements. The team designed for continuous improvement: metrics, feedback mechanisms, and analytics touchpoints were embedded into the design from the outset.

Acquire: securing resources:
With design specifications complete, the ‘acquire’ activity identified the required resources. Cloud infrastructure capable of handling peak demand across multiple regions; AI/machine learning services for predictive maintenance and smart routing; payment processing services compliant with regulations in each market; map and navigation services adapted to local conditions. The team assessed sourcing options, negotiating contracts with multiple cloud providers and service partners. Procurement was coordinated carefully to ensure integration readiness. Resource availability was confirmed before the ‘build’ phase began, preventing downstream delays.

Build: constructing the solution
The product development team, under Sam’s oversight, executed a phased build approach. The core app framework was developed first, establishing shared foundations for authentication, payment processing, and support channels. Feature teams then implemented the rental, sharing, and autonomous service modules in parallel, maintaining integration points and shared design patterns. Rigorous testing occurred throughout. Service validation teams ensured the app functioned flawlessly across devices, network conditions, and geographic regions. Integration testing verified that switching between service models felt seamless. Security testing confirmed compliance with data protection requirements in each market. Supporting documentation, including user guides, service manuals, and operational runbooks, was developed alongside the software.

Transition: going live:
Before full launch, the team executed a carefully staged transition strategy. Soft launches in select markets allowed real users to interact with the new experience under controlled conditions. Omar, the IT Delivery Manager, coordinated the operational handover, ensuring monitoring systems captured live performance data and incident response procedures were operational. Supplier onboarding was critical: map service providers, payment processors, and cloud infrastructure teams needed to understand their roles in the live environment. Customer communication emphasized that familiar services would be enhanced, not disrupted. The team monitored the transition closely, ready to address any issues.

Operate: maintaining excellence:
With the app in live environments, the ‘operate’ activity ensured continuous, reliable performance. Infrastructure monitoring tracked application health, system performance, and availability across regions. The team managed routine updates, security patches, and scaling adjustments responding to demand fluctuations. Automated systems monitored performance metrics: response times, transaction completion rates, error frequencies.
When deviations appeared, such as unusual latency in a particular region or unexpected payment processing delays, alerts triggered investigation and rapid response.

Deliver: serving customers:
The ‘deliver’ activity brought the product to life for customers. Service delivery teams ensured seamless onboarding to new users, providing multiple languages, localized payment options, and support channels adapted to each market. Service level agreements committed to fast booking, reliable vehicle access, and responsive support. Customer service teams used the app’s built-in support features (in-app chat, knowledge bases, and contextual help) to address questions. Anna monitored service quality metrics and customer satisfaction indicators religiously. Usage patterns revealed which features resonated, where users abandoned workflows, and which regions had distinct preferences.

Support: resolving and learning:
Despite meticulous planning, incidents occurred. A payment processing outage in one market triggered rapid incident response: the support team engaged customers, offered alternatives, and restored service within hours.
When an unexpected interaction between autonomous ride features and local traffic regulations created user confusion, the team diagnosed the issue, implemented a fix, and deployed it to users within days. More importantly, each incident triggered investigation.
Why did it happen? What signals did we miss? How do we prevent recurrence? Post-mortem reviews informed improvements to both the app and the operational processes. Issues discovered in ‘support’ fed back into the ‘discover’ and ‘design’ cycles, continuously refining the product.

Continual improvement:
The journey from ‘discover’ to ‘support’ was not linear but cyclical. Feedback from ‘support’ informed new ‘discover’ iterations as market conditions evolved. Performance data from ‘operate’ fed into ‘deliver’ improvements. Customer insights from ‘deliver’ shaped strategic decisions about feature prioritization and regional adaptations. By embedding DPSM practices throughout this lifecycle, ICR’s unified mobile app became more than a technical achievement. It became a reflection of the company’s commitment to customers: reliable, innovative, responsive to local needs, and continuously improving. As Max envisioned, ITIL Car Rental had taken a bold step toward being the world’s most trusted mobility partner, delivering the vision through every customer interaction, every design decision, and every operational moment.

Service:
Implementing a global HR management service: an internal service lifecycle
The challenge:
ITIL Car Rental’s expansion across multiple regions and service lines created mounting complexity in workforce management. Different legal entities, varying employment regulations, localized payroll requirements, and regulatory compliance across jurisdictions had strained the company’s aging HR systems. The company’s executive team identified modernization of HR management services as essential to support ICR’s growth strategy whilst maintaining operational consistency and compliance across markets. Omar’s IT delivery team took ownership of implementing a new vendor-supplied HR management system, a solution that would run on ICR servers, integrate seamlessly with existing internal systems, and serve thousands of employees and contractors across dozens of countries.

Discover: understanding the landscape
The team began by organizing a comprehensive ‘discover’ iteration. Assessing the organizational context, the team analysed how ICR’s expansion strategy, new regulatory requirements in different markets, evolving workplace expectations, and the growing complexity of managing multiple legal entities across regions created both pressure and opportunity for modernization. Working closely with the HR business partner and Max’s office, Omar’s team gathered requirements from across the organization: HR representatives and business managers in each country, payroll departments, compliance officers, finance teams managing workforce costs, and executives overseeing the talent strategy. The discovery revealed critical patterns. European operations faced strict data protection and employment law requirements. Asia-Pacific branches needed sophisticated multi-currency payroll capabilities. The US and Canadian operations required integration with complex benefits administration systems. Every region needed consistency in talent management and performance tracking, yet each had distinct regulatory demands. A business analyst from Omar’s team documented these needs systematically, whilst Alex, the Enterprise Architect, assessed the technical implications of supporting multiple legal entities, integrating with existing systems (payroll, finance, learning management, employee engagement platforms), and ensuring data security and regulatory compliance. The vendor’s product roadmap was evaluated against ICR’s requirements, revealing both strong alignment and specific gaps requiring customization. The team agreed on a clear direction: implement a core HR platform from a reputable software vendor as the system of record for employee master data, organizational structure, and talent management across all regions, while integrating specialized capabilities for payroll, benefits, compliance reporting, and data protection. Investment was secured with realistic timelines accounting for the complexity of multi-region deployment, and a formal steering committee was established to guide implementation.

Design: defining the solution:
With requirements agreed, Omar’s team began detailed design activities. Service design workshops brought together local HR representatives, payroll specialists, compliance officers, and technology architects. The team mapped existing HR processes in each region, identifying which would be standardized globally and which would require local customization. Design workshops revealed critical service interactions. HR teams needed intuitive interfaces for managing recruitment, onboarding, performance management, and learning across different employment models. Employees required easy access to personal information, benefits enrolment, and career development features. Payroll teams needed reliable data integration with local accounting systems and regulatory reporting tools. Compliance officers required audit trails, secure data management, and reporting to meet legal obligations in each jurisdiction. Alex developed detailed integration architecture, specifying how the HR system would communicate with existing payroll, finance, learning management, and employee engagement platforms. Data flows were mapped, ensuring that changes in one system were reliably distributed to dependent systems without manual intervention or data errors. Security and data protection requirements were designed into every integration point; this was particularly critical given GDPR, CCPA, and local data residency requirements. Data migration became one of the key design points. The team designed a phased deployment approach: implementation across ICR headquarters first, then staged rollout to major regional clusters, enabling learning and refinement before full global deployment. Supporting documentation, such as user guides for different roles, migration playbooks, and integration manuals, was planned in detail.

Acquire: securing resources:
With design specifications complete, Omar’s team identified required resources. The vendor’s licensing model (supporting anticipated growth); implementation consultant expertise (to guide customization and deployment); cloud infrastructure capacity for testing and staging environments; integration middleware (to connect the new HR system with existing enterprise systems); and data migration tools were all specified. The ‘acquire’ activity involved careful sourcing decisions. The vendor partnership was formalized, establishing support levels (the vendor providing third-line support, with first-line and specialist support to be provided by Omar’s team). External systems integrators with expertise in the vendor’s platform and multi-region HR implementations were evaluated and contracted. Cloud infrastructure capacity was procured, allowing for future growth. Service agreements included service level commitments and compliance obligations aligned with ICR’s governance standards. Resources were also identified internally: team members who would receive specialized training to support the system; members of Omar’s operations team who would provide day-to-day administration; security and compliance specialists to oversee implementation controls. Procurement was coordinated to ensure availability ahead of the ‘build’ phase.

Build: constructing the solution
Omar’s team established an implementation program, structured as a series of building activities. First, the core HR system was configured to match ICR’s organizational structure, employment classifications, and role hierarchies. Configuration activities addressed fundamental requirements: multi-legal entity support, multi-language and multi-currency capabilities, and foundational data structures. Parallel to core configuration, integration development began. The team, supported by the vendor and a vendor’s consulting partner, configured data flows from the HR system to payroll systems, ensuring employee changes (salary adjustments, location changes, benefits modifications) flowed reliably to payroll processing. Integration with the finance system ensured workforce costs were accurately captured. Learning management system connections ensured course assignments and certifications were synchronized. Security and compliance controls were embedded throughout, including audit logging, data encryption, access controls, and automated reporting for regulatory requirements. Extensive testing occurred throughout the ‘build’ phase. Functional testing verified that each configuration matched requirements. Integration testing validated that data flowed correctly between systems without errors or data loss. Security testing confirmed that sensitive personal data was protected and that access controls functioned as designed. Business process testing involved HR teams walking through common scenarios (such as hiring a new employee, transferring someone to a different country, or managing a separation), ensuring the system supported the complete workflow. User acceptance testing engaged representatives from different regions and roles. HR teams in Germany tested GDPR compliance features. Payroll teams in multiple countries verified that their specific regulatory requirements were met. Local compliance officers confirmed that reporting would support local legal obligations. Supporting documentation, such as operational runbooks for system administration, user guides tailored to different roles, and troubleshooting guides, was developed and reviewed. Apart from the HR teams, selected users from all affected teams were involved, testing the interfaces and workflows for requesting leave, conducting assessments, reserving training, of reporting HR incidents. These tests revealed the need for end-user training and onboarding during the new service roll-out. Transition plans were updated to allow time for this.

Transition: going live:
The team carefully prepared a transition strategy. Headquarters implementation was planned first, serving as a dress rehearsal. A parallel run, with both old and new systems operating simultaneously, was conducted for three weeks, allowing both systems to process payroll and generate reports for comparison. The payroll teams validated that the new system calculated amounts identically to the legacy system, detecting and resolving discrepancies before they affected employees. Omar coordinated the preparation activities. User training was delivered to HR teams, payroll specialists, managers, and employees. Help desks were staffed and trained. Communication plans explained the transition to all users, emphasizing continuity of services and highlighting new capabilities. Vendor support teams were onboarded, understanding their roles during the transition period. Data migration, which involved extracting employee master data from legacy systems, cleansing it, loading it into the new system, and validating completeness and accuracy, was carefully orchestrated and verified. Transition day at headquarters was carefully planned. The legacy system was frozen at a specific point, a final data extract was taken, loaded into the new system, and system access was switched over. The team remained staffed throughout the transition and into the following week, monitoring system performance closely, responding to questions, and resolving issues. Incident response procedures were in place, with escalation paths to the vendor’s support team available if needed. Following successful headquarters transition, the team planned regional deployments. Each regional cluster (Europe, Asia-Pacific, Americas) had a transition period, with lessons from earlier transitions incorporated and local considerations addressed. The staggered approach allowed the central team to support each region and enabled best practices to propagate from early transitions to later ones.

Operate: maintaining excellence:
With the system live across regions, Omar’s team shifted focus to reliable operations. Infrastructure monitoring tracked system health, performance, and availability across all deployment sites. Automated health checks, such as database integrity tests, integration validation, and backup verification, ran daily, alerting the team to any deviations from expected operation. The team established routine operational activities: security patches supplied by the vendor were tested in staging environments, then deployed to production overnight. Data backups were performed daily, with regular restoration tests confirming that recovery was possible. System performance was monitored, with growth projections ensuring sufficient capacity as employee counts increased. User access was reviewed every week, ensuring that accounts of employees that had left the company were promptly deactivated and that role changes were reflected in system permissions.
When issues appeared, monitoring detected these deviations and triggered investigation. The team maintained a problem backlog, working with the vendor to address underlying issues and implementing fixes or workarounds as appropriate.

Deliver: serving the organization
The ‘deliver’ activity brought the HR system into daily organizational use. Omar’s team established service level commitments: HR teams would have to access to the system 99.5% of the time; user support queries would be acknowledged within four hours; critical issues affecting payroll or compliance would be resolved within eight hours. The team was constrained by the respective commitments of the vendor and, although in many cases a higher service level was provided, it could not be formally committed to. A first-line support team knowledgeable about ICR’s specific configuration and trained on common issues responded to user questions. A knowledge base captured solutions to frequent issues, enabling self-service support. Employees received training on using the service: how to access their information, update personal details, enrol in benefits, and request time off through the HR portal. Delivery included routine service actions: onboarding new employees to the system (ensuring they were created with appropriate access and initial data); offboarding departing employees (deactivating access, generating final pay calculations, archiving records); managing organizational changes (updating reporting structures when teams were reorganized); conducting benefits enrolment campaigns (ensuring employees could select and modify coverage). The team monitored delivery metrics carefully: system availability, user satisfaction (gathered through surveys), processing timeliness (time from employee action to system reflection), and error rates (incorrect calculations, missing data). Service level reporting informed ongoing improvements and triggered escalations if service quality threatened to fall below the agreed level.

Support: resolving and learning:
Despite robust operational procedures, incidents occurred. A payroll integration process failed one month due to an unexpected data format in the finance system, causing a four-hour delay in the payroll. The support team immediately engaged payroll managers, communicating the issue and estimated resolution time. The technical team worked with the finance team and the vendor to understand the root cause, developed a fix to handle the unexpected data format, implemented the fix, reran the integration process, and verified accuracy. By the end of the day, normal payroll processing resumed. On another occasion, a regional compliance officer discovered that a localized tax calculation in one country was producing results that didn’t align with current regulations. The incident was escalated to the vendor’s specialist support team. Together, they analysed the regulation change, determined that a configuration parameter needed adjustment, updated the system, revalidated historical calculations, and rolled forward with correct calculations prospectively. Each incident triggered a post-mortem review, where the support team asked: why did the issue occur? Were there warning signs we missed? How do we prevent recurrence? Findings from post-mortems informed improvements to configuration, integration design, monitoring, documentation, and training. Particularly significant improvements, such as enhanced validation of finance system data before processing payroll, were incorporated into the ‘discover’ and ‘design’ phases to shape future improvements.

Continual improvement:
The journey from ‘discover’ to ‘support’ was cyclical. Feedback from ‘support’, including new issues and lessons learned, informed new ‘discover’ iterations as regulations evolved, ICR’s business expanded into new markets, or new compliance requirements emerged. Performance data from ‘operate’ informed design improvements when system bottlenecks were identified or user experience could be enhanced. User feedback from ‘deliver’, captured through surveys and support interactions, shaped priorities for new features and refinements.
When HR teams requested better reporting capabilities to support talent analytics, this feedback was captured, evaluated during ‘discover’ activities, and prioritized in design cycles. By embedding DPSM practices throughout this lifecycle, Omar’s team transformed HR management at ITIL Car Rental.
What had been a patchwork of legacy systems and manual processes became a unified, reliable platform supporting the company’s global growth. Compliance risks were reduced through automation and audit trails. HR teams gained visibility into workforce data and could respond quickly to business needs. Employees had instant access to their information and could manage their own preferences. The system provided a foundation for HR analytics, enabling data-driven decisions about talent, compensation, and organizational structure. As Max envisioned, ICR’s transformation extended beyond customer-facing products to the internal systems and processes that enabled the company to operate effectively. By treating internal HR services with the same rigor and discipline as external products, Omar’s team ensured that ITIL Car Rental’s greatest asset, its people, were supported by systems as reliable, responsive, and capable as the mobility services ICR offered to customers worldwide. Please refer to the ITIL Car Rental scenario for additional context when answering this question. To retain existing customers of the acquired rental company, ICR collected detailed information about the market, customer expectations, and ongoing relationships. The team used this information when following the existing playbook for brand, customer, and stakeholder transition.
What metrics should ICR use to assess the outcomes of this transition?

  1. Focus on transformation initiative metrics such as schedule performance index and cost performance index
  2. Focus on management practices effectiveness metrics such as number of tickets processed on time and stakeholder satisfaction with configuration data
  3. Focus on business performance metrics such as customer retention and market share
  4. Focus on product and service metrics such as service availability and cost per user

Answer(s): C



Introduction to ITIL Car Rental:
Ten years ago, ITIL Car Rental (ICR) was launched in Seattle with the aim to provide convenient and affordable rental cars to customers around the world. After a relatively short time, ICR became a globally recognized company, with a wide network of franchising partners across Europe, the US, and Asia-Pacific, with approximately 400 direct employees. In the first few years of operation, repeat business accounted for nearly a third of all reservations. Shareholders saw steady growth, and the company earned a reputation for putting customers first. ICR quickly became a model of modern mobility: fast, reliable, and profitable. Following its early success, the company expanded through mergers and acquisitions to new markets and new services, including car sharing. ICR relies heavily on digital technology for internal operations and service delivery, using a mix of internal and external digital products. Customer-facing mobile applications are developed and run by the internal IT team. AI is increasingly used in internal and external products and services for predictive maintenance, customer support, scheduling, smart check-in and return processes, and so on. As new competitors, such as car-sharing services, rideshare apps, and driverless cars, enter the market, customers now expect a seamless digital experience: quick bookings, app-based help, and flexible options that fit easily into their daily lives. At the same time, customers are paying more attention to companies that value social responsibility, sustainability, and environmental consciousness. These expectations are driving ICR to set clear and ambitious sustainability goals, as well as pursue further growth.
The board members strongly believe that the company’s success in the years to come will be defined by innovation and the use of digital technology. For this reason, they appointed a new GIO, Max. Max was chosen for his experience in digitalization and his track record in successful, large-scale IT transformations. Max’s strong background in ITIL and ITSM indicates that he values ITIL certification, and his hiring policy reflects this. Having worked with Design Thinking, DevOps, and agile methods, he believes sustainable business requires a blended approach to digital product and service management. Max is keen to see how his team can redefine the car rental experience and ensure that ICR is the first choice for new and existing customers.

Meet the employees of ITIL Car Rental:
Max, Chief Information Officer (CIO):
Max is the new CIO. He is an experienced executive with a track record of leading digital transformations. He believes in an integrated approach to DPSM.

Anna, Product Manager:
Anna has been with ITIL Car Rental for five years. She focuses on commercial success and continual B2C development. She is detail-oriented, eco-conscious, and dedicated to improving overall customer experience.

Maria, Business Analyst:
Maria is a proactive communicator who ensures smooth collaboration between IT and business teams. She works mostly on discovery and planning activities, supporting continual improvement of the company’s digital products. She asks a lot of questions and is great at spotting patterns and trends.

Omar, IT Delivery Manager:
Omar manages ongoing service delivery. He applies ITIL practices to improve efficiency and customer satisfaction. However, Omar has had little experience with a blended or collaborative approach to product and service management.

Sam, Head of Product Development:
Sam has more than 10 years of experience in leading cross-functional product teams in the domains of mobility and automotive innovation. He oversees the entire product lifecycle at ITIL Car Rental from strategic vision to delivery and ensures that customer needs, market trends, and sustainability are all in sync.

Alex, Enterprise Architect:
Alex is responsible for ensuring that product design and technological strategy are aligned, sustainable, and future-proof. She provides architectural guidance across teams, works to identify systemic risks, and holds coherence in a fast-changing digital ecosystem. She is highly analytical with a strong intuition for patterns and risks.

The CIO’s vision for ITIL Car Rental Max:
We live in an era of rapid change, where all companies are going through some kind of digital transformation. Service expectations have changed drastically since ITIL Car Rental was created 10 years ago. Customers want seamless and immediate access to rental services from their smartphones, as well as innovation as part of their daily lives. Autonomous vehicles are the future; they will make car rental companies stand out and continue successfully. My vision is for ITIL Car Rental to pioneer this transformation and become the go-to name for car rentals worldwide. We will continue offering outstanding customer service while maintaining competitive car rental rates. After all, ITIL Car Rental is more than just a service. We are here to enhance the entire travel experience.

Governance:
ITIL Car Rental has branches in other countries, some of which are franchises. Each country may have its own regulations when it comes to the services offered by ICR. Although all services are focused on enhancing the entire travel experience, different services may be subjects to different regulation. For example, car-sharing is regulated differently, and self-driving cars cannot be introduced at all in some countries. ICR has adopted a governance approach that blends clear global direction with local autonomy, enabling the company to stay competitive in a fast-moving mobility landscape. As ICR continues to grow across regions and expand its portfolio, moving from traditional rentals to car-sharing and self-driving services, its governance structure ensures consistency, compliance, and customer-focused innovation. ICR’s approach to change is practical and adaptive. The company encourages experimentation and continual improvement as long as new ideas follow shared principles and meet regulatory expectations in each market. This balanced approach helps ICR introduce new digital features quickly while maintaining trust and reliability. The Board evaluates progress through a focused set of indicators, including commercial results, market share, innovation outcomes, cost efficiency, and customer satisfaction. Coordinated autonomy is a key feature of ICR’s governance.
While the Board defines the overall vision and strategic direction, local branches and service owners have freedom in how they achieve their goals. Market leaders and service-line managers work closely to tailor solutions to regional needs, ensuring that global standards remain compatible with local realities. Risk management reflects the diverse environments in which the company operates. Within heavily regulated domains, such as safety, traffic rules, and data protection, the company maintains a very low risk appetite and prioritizes prevention. In innovative settings, ICR accepts limited risks as long as they are identified early and controlled quickly. ICR’s operational context is constantly changing. Regulations evolve, cities introduce new environmental rules, and economic factors such as tariffs or sanctions may affect the business. To stay ahead, ICR continuously monitors these developments and adjusts its operations accordingly. To achieve this, the company relies on fast decision-making. Local teams and product groups can act independently within agreed principles and legal boundaries,
allowing ICR to respond to customer needs and regulatory changes without delays. Compliance is an essential pillar of the governance model. Because requirements vary widely by region and service type, compliance responsibilities are distributed across the organization. Internal audit provides central oversight to ensure consistency and coherence using digital systems to standardize reporting and track evidence. ICR also serves a wide variety of stakeholders, ranging from city authorities to business clients and service partners. Their expectations differ by region, engagement approaches are adapted to local circumstances while staying aligned with ICR’s values and commitments. The company’s global reach demands broad governance oversight. Digital systems and processes are shared internationally but are tailored to each country’s regulations, customer behaviour, and available services. This combination helps ICR operate as a unified global brand while remaining locally relevant. Overall, ICR’s governance capabilities are well-established. Accountability is clear at board level, with defined responsibilities for central and local leaders. Regular audits and strong analytical tools support informed decision-making. As the company expands into new markets and introduces new mobility solutions, this governance foundation enables the company to grow responsibly, innovate confidently, and maintain a high standard of service for customers worldwide.

AI Governance:
Artificial Intelligence (AI) is increasingly embedded in ITIL Car Rental’s digital products and services. AI is used to support predictive maintenance, customer support, analytics, scheduling, and smart check-in and return processes. As ICR expands its service portfolio and geographic footprint, AI is expected to play a larger role in operational decision-making, customer experience, and service optimization. AI adoption creates new opportunities for ICR. AI-driven analytics can improve fleet utilization, sustainability performance, and cost efficiency. AI-enabled customer interaction can enhance responsiveness and personalization across markets. Automation and coordination capabilities can accelerate operational decisions and improve service reliability. These opportunities align with ICR’s strategic focus on digital experience, innovation, and sustainable growth. However, AI also introduces governance challenges. AI systems can act autonomously, operate at high speed, and learn over time, which challenges traditional approval-based decision structures. Risks related to explainability, bias, data protection, regulatory compliance, and accountability increase as AI influences customer-facing and safety-critical services. Differences in national regulation further complicate AI deployment across regions. ICR’s governance model combines clear global direction with local autonomy. The Board defines strategic objectives, risk appetite, and global principles, while local branches and service owners have flexibility in how they achieve outcomes within regulatory and legal boundaries. This governance pattern enables experimentation and innovation while maintaining compliance, consistency, and accountability. ICR’s existing governance both enables and constrains AI adoption. Strong compliance, audit, and risk management practices support trust and regulatory alignment but may slow adoption if applied too rigidly. Local autonomy supports innovation but requires stronger coordination to avoid fragmentation of AI practices and inconsistent customer experience. To address this, ICR is evolving its governance approach to AI. AI use cases are being classified by risk and impact, with governance intensity matched accordingly. Lower-risk AI solutions are enabled through local experimentation, while higher-risk applications require stronger oversight, clear accountability, explainability, and human-in-the-loop controls. Internal audit and reporting mechanisms are being extended to include AI-specific evidence and monitoring. Through this approach, ICR aims to enable responsible AI adoption that supports innovation, maintains trust, and aligns AI-enabled decisions with business objectives, regulatory requirements, and customer expectations.

Strategy:
ICR’s strategy centres on pioneering digital, sustainable mobility while growing globally and maintaining strong local responsiveness.

Vision statement:
“To be the world’s most trusted and innovative mobility partner, using digital technology and sustainable practices to enhance every journey for customers, wherever they travel.” This vision is realized through ICR’s strategy, which combines innovation, sustainability, a focus on customer experience, and sustainable growth. The company’s strategic direction has been transformed by the executive team into five strategic objectives, approved by the Board of Directors. Each objective has been further detailed into strategic initiatives. To implement these initiatives, many ICR teams will have to work together, involving external suppliers where additional resources and competencies are needed.

Objective 1: Lead in digital customer experience ICR aims to offer a seamless, app-first experience that makes renting, sharing, and returning vehicles effortless across all markets. Roll out a unified global mobile platform with localized features, languages, and payment options. Embed AI-driven capabilities such as predictive maintenance, smart check-in/return, and proactive support into all core services. Establish continuous discovery and UX improvement cycles led by product and business analysis teams.

Objective 2: Innovate in autonomous and new mobility services ICR wants to be an early and trusted provider of self-driving and car-sharing services where regulations allow, integrating them into its mainstream portfolio. Launch regulated pilots for self-driving and car-sharing services in priority markets, starting with the US and expanding to EU and other markets. Build a standardized service design and safety framework for autonomous services, aligned with local laws and ICR’s low risk appetite in safety and data protection. Create joint innovation programmes between product, architecture, and operations to scale successful pilots globally.

Objective 3: Grow sustainably and profitably across markets ICR seeks to expand through franchising, mergers, and acquisitions while maintaining strong financial performance and customer loyalty. Maintain an up-to-date integration playbook covering governance, branding, systems, and supplier relationships for new acquisitions. Implement market- and service-level performance dashboards tracking revenue, market share, innovation progress, and customer satisfaction. Optimize fleet and cost structures using analytics to balance utilization, pricing, and sustainability targets.

Objective 4: Embed sustainability and social responsibility ICR intends to align its growth with environmental responsibility and evolving city and national regulations. Define clear sustainability targets (such as fleet emissions profile, use of EVs, or eco-options in the app) and report progress regularly. Cooperate with cities and regulators to adapt services to local environmental rules, parking policies, and low-emission zones. Design service offerings that reward sustainable choices, such as greener vehicle options or smarter routing.

Objective 5: Strengthen governance, risk, and capabilities ICR will maintain robust governance while allowing local autonomy, ensuring decisions are fast, compliant, and data-informed. Clarify and document global and local decision rights, principles, and escalation paths for all service lines. Enhance internal audit, compliance monitoring, and digital evidence-tracking across all countries and franchises. Invest in skills and certifications (ITIL, DevOps, data governance) for key roles such as CIO and office, product, delivery, and architecture. managers to support continual transformation.

Transformation:
ICR always looks for opportunities to expand the business to new markets. As part of this strategy, the company agreed an acquisition of a local rental company in a small, fast-developing country in Europe. The company being acquired has an established customer base and reputation in its home country. It is known in neighbouring countries, though it does not have branches in them. The government of the country where the company is based just passed a regulation approving use of self-diving vehicles, and ICR is keen to be the first provider of such a service in the region. The acquired company needs to be integrated into the ICR governance and management structure and information systems, including internal and customer-facing systems. The objective is to retain the existing customer base, provide reassurance that the acquisition will improve (rather than worsen) the quality of familiar rental services, and introduce new service lines (car-sharing, self-driving cars). The Board of Directors expects the integration to be completed within three months (including branding, information systems, governance, people, and relationships with local suppliers). ICR identified five transformational initiatives that need to be completed to fulfil the transformation:

1. Governance and structure integration ICR needs to integrate the acquired company into its existing governance model by aligning the local board reporting lines, decision rights, and accountability with ICR’s global principles, while preserving a high degree of local autonomy for market- and service-specific decisions. This includes defining how the local management team participates in ICR’s governance forums and how global policies, such as risk management and sustainability, are applied in the new country. ICR has gone through this many times and has an established playbook for governance and management integration, which proved to be effective during previous acquisitions.

2. Regulatory, risk, and compliance setup ICR must establish a comprehensive regulatory and compliance framework for the new market, with particular emphasis on the newly approved self-driving vehicle regulation and existing rules for rental and car-sharing services. This initiative should set up local controls and escalation paths consistent with ICR’s low risk appetite in safety, data protection, and traffic law. These controls and paths should be supported by internal audit oversight and appropriate reporting mechanisms. The company also has extensive experience in this area; however, every new country introduces new challenges which sometimes need to be addressed quickly.

3. Technology and platform integration ICR needs to migrate or integrate the acquired company’s systems into its global digital ecosystem, including customer-facing apps, booking platforms, fleet and maintenance systems, and analytics. During the transition period, ICR must ensure continuity of service for existing customers. AI-enabled capabilities such as predictive maintenance, smart check-in/return, and customer support should be progressively rolled out to the new operation, aligning with local regulations and infrastructure. Although the existing technology solutions of the acquired company were briefly assessed before the acquisition, there is a lot to explore, and the technology team should be ready for surprises.

4. Brand, customer, and stakeholder transition A coordinated rebranding and customer communication programme is required to transition the local brand to ICR within three months. This communication should clearly explain that familiar services will be maintained or improved and that new options like car-sharing and self-driving services will be introduced. In parallel, ICR should engage proactively with local authorities, business customers, partners, and suppliers to reinforce trust, clarity expectations, and position ICR as an innovative yet reliable mobility provider in the region. ICR has a playbook for such campaigns, but for it to be effective, detailed information about the customers, their expectations, and the ongoing relationships is needed.

5. Operating model, people, and service portfolio ICR should redesign the local operating model to match its global standards, including roles, responsibilities, and performance metrics, while retaining local knowledge and relationships that underpin the acquired company’s reputation. As part of this, the service portfolio in the new country should be structured to cover traditional rental, car-sharing, and self-driving services under a unified framework, with clear service ownership, targets for commercial performance and customer satisfaction, and mechanisms for rapid local decision-making. Although ICR has a large and positive experience of adapting the operating models of acquired companies, introduction of the self-driving cars to a new market is a new and challenging task. Together, these transformation efforts should allow ICR to enter the new region as a trusted, forward-looking mobility partner. Supported by strong governance, modern technology, and an effective integration approach, ICR is well positioned to deliver a reliable, future-ready travel experience to customers in its newest market.

Experience:
Understanding user experience as a strategic imperative
ICR recognizes that achieving a sustainable competitive advantage in modern mobility depends fundamentally on delivering exceptional user experience. Max articulated in his vision for the company that “customers want seamless and immediate access to rental services from their smartphones, as well as innovation as part of their daily lives.” This expectation applies not only to traditional car rental services but extends across the expanding portfolio of car-sharing and driverless tax offerings. The digital applications and web interfaces that customers interact with have become the primary touchpoints for the ICR brand, making digital experience inseparable from overall business success.
The customer journey across digital touchpoints
The user journey with ICR spans multiple critical steps, each mediated through digital applications and interfaces: Discovery and search begin when prospective customers evaluate their mobility options. Here, ICR’s digital presence must clearly communicate availability, pricing transparency, and service advantages over competitors, whether customers are considering traditional car rental, flexible car-sharing, or autonomous ride options. Registration and onboarding follow as users create profiles and establish trust with the platform. At this point they share their personal data, driving licence, and financial details with ICR. This makes this step particularly important for building trust and capturing customer preferences that will enhance future interactions. Selection and booking require intuitive navigation and clear presentation of options. The digital interface must accommodate the different decision-making patterns across the three service modes: the planning-focused car rental customer, the spontaneous car-sharing user, and the on-demand autonomous ride passenger. Payment processing must inspire confidence while remaining frictionless. Secure, flexible payment options that adapt to different service models strengthen customer trust and reduce transaction abandonment. This is a sensitive aspect of service interactions, as car rental users are often worried about unexpected security deposits, additional charges and costly insurance. Although this part of user journey often seems to be less important than the core service utility, it may have a significant and sometimes damaging impact on the overall experience. Check-in and vehicle access have evolved significantly with smart technologies. Digital applications now provide seamless vehicle access, reduced friction at pick-up, and immediate problem resolution when complications arise. In-journey support enables customers to address questions or concerns in real time.
Whether requesting roadside assistance, reporting issues, or seeking clarification, rapid response through integrated digital channels demonstrates the ICR’s commitment to the travel experience it has promised. Check-out and feedback close the transaction but open an opportunity for continual improvement. Digital interfaces capture usage data, soliciting feedback that informs service enhancements.
Differentiation across service models
While these touchpoints are universal, their expression differs significantly across ICR’s service offerings. Traditional car rental customers typically plan ahead, expecting detailed vehicle information and insurance clarity through structured booking flows. Car-sharing users demand spontaneity and simplicity, prioritizing booking speed and lock/unlock mechanisms. Driverless taxi passengers expect transparency about autonomous capabilities, safety systems, and real-time trip information without the complexity of vehicle selection.
Capturing, analysing, and improving user experience
Recognizing that understanding is a prerequisite to improvement, ICR has embedded experience measurement into the digital ecosystem. ICR applications capture behavioural data (interaction patterns, abandonment points, feature usage, and satisfaction signals), providing teams with rich insight into the customer journey and occurring points of friction. This data flows into structured analysis processes. Maria, the Business Analyst, uses AI to identify patterns and trends that highlight experience bottlenecks and opportunities. Cross-functional collaboration between Anna’s product management, Sam’s product development oversight, and Omar’s service delivery team ensures that insights translate into rapid and noticeable improvements. The teams employ both quantitative metrics (completion rates, task duration, error frequency) and qualitative feedback mechanisms. Customer surveys, user testing sessions, and support interaction analysis combine with operational data to paint a complete picture of experience quality.
Improvement cycles operate continuously, enabled by the ICR’s commitment to the end-to-end product and service lifecycle management and iterative development. The service enhancements are tested incrementally, which allows the teams to measure their impact and iterate rapidly. This approach ensures that ICR remains responsive to evolving customer expectations while maintaining the reliability and service quality that have defined the company’s reputation. By treating user experience as both a strategic priority and an operational discipline, ICR ensures that the company’s digital services serve their essential purpose: enabling customers to access mobility solutions effortlessly, building loyalty through consistent excellence, and positioning ICR as the thoughtful choice in an increasingly competitive and technologically sophisticated market.

Product:
ICR’s Unified Mobile App: A Product Lifecycle Journey
The challenge:
ITIL Car Rental’s vision for digital transformation demanded a bold move: consolidating traditional car rental, car-sharing, and emerging autonomous vehicle services into a single, seamless mobile application. This unified platform would serve millions of customers globally while adapting to diverse regulatory environments and local market conditions. The product team (led by Sam and guided by Anna’s product management expertise, Maria’s business analysis insight, and Alex’s architectural know-how) embarked on a comprehensive product lifecycle journey.

Discover: charting the course:
The team began by analysing the business context using the PESTLE method. Regulatory changes permitting autonomous vehicles in several markets, shifting customer expectations towards mobile-first experiences, and competitive pressures from ride-sharing services created both urgency and opportunity. Sam convened discovery sessions with stakeholders across the organization. Market analysis revealed fragmented customer expectations: traditional renters wanted clarity and planning capability; car-sharing users demanded spontaneity and speed; autonomous rice passengers expected transparency and trust. Maria identified critical patterns in user behaviour across regions, while Alex assessed the architectural implications of managing three distinct service models within a single platform. The team agreed strategic direction: create one app that intelligently presents rental, sharing, and autonomous options based on user context and local regulations. This vision was communicated across all product teams, establishing alignment and guiding subsequent activities. Investment in the initiative was secured, with clear timelines and resource commitments.

Design: shaping the experience:
Service design workshops brought together user research, human-centred design principles, and regulatory requirements. Anna led a detailed analysis of the customer journey across all three service models, identifying touchpoints, decision moments, and friction points. The design iterations incorporated feedback from early user testing. The team prototyped distinct user flows: a structured booking experience for renters planning days ahead; a rapid-access interface for car sharing users; and a transparent, safety-focused experience for autonomous ride passengers. Meanwhile, Alex developed target architecture blueprints ensuring that different service models could scale independently while sharing core infrastructure for authentication, payment, and support. Design specifications documented user interface, service interactions and operational requirements. The team designed for continuous improvement: metrics, feedback mechanisms, and analytics touchpoints were embedded into the design from the outset.

Acquire: securing resources:
With design specifications complete, the ‘acquire’ activity identified the required resources. Cloud infrastructure capable of handling peak demand across multiple regions; AI/machine learning services for predictive maintenance and smart routing; payment processing services compliant with regulations in each market; map and navigation services adapted to local conditions. The team assessed sourcing options, negotiating contracts with multiple cloud providers and service partners. Procurement was coordinated carefully to ensure integration readiness. Resource availability was confirmed before the ‘build’ phase began, preventing downstream delays.

Build: constructing the solution
The product development team, under Sam’s oversight, executed a phased build approach. The core app framework was developed first, establishing shared foundations for authentication, payment processing, and support channels. Feature teams then implemented the rental, sharing, and autonomous service modules in parallel, maintaining integration points and shared design patterns. Rigorous testing occurred throughout. Service validation teams ensured the app functioned flawlessly across devices, network conditions, and geographic regions. Integration testing verified that switching between service models felt seamless. Security testing confirmed compliance with data protection requirements in each market. Supporting documentation, including user guides, service manuals, and operational runbooks, was developed alongside the software.

Transition: going live:
Before full launch, the team executed a carefully staged transition strategy. Soft launches in select markets allowed real users to interact with the new experience under controlled conditions. Omar, the IT Delivery Manager, coordinated the operational handover, ensuring monitoring systems captured live performance data and incident response procedures were operational.
Supplier onboarding was critical: map service providers, payment processors, and cloud infrastructure teams needed to understand their roles in the live environment. Customer communication emphasized that familiar services would be enhanced, not disrupted. The team monitored the transition closely, ready to address any issues.

Operate: maintaining excellence:
With the app in live environments, the ‘operate’ activity ensured continuous, reliable performance. Infrastructure monitoring tracked application health, system performance, and availability across regions. The team managed routine updates, security patches, and scaling adjustments responding to demand fluctuations. Automated systems monitored performance metrics: response times, transaction completion rates, error frequencies.
When deviations appeared, such as unusual latency in a particular region or unexpected payment processing delays, alerts triggered investigation and rapid response.

Deliver: serving customers:
The ‘deliver’ activity brought the product to life for customers. Service delivery teams ensured seamless onboarding to new users, providing multiple languages, localized payment options, and support channels adapted to each market. Service level agreements committed to fast booking, reliable vehicle access, and responsive support. Customer service teams used the app’s built-in support features (in-app chat, knowledge bases, and contextual help) to address questions. Anna monitored service quality metrics and customer satisfaction indicators religiously. Usage patterns revealed which features resonated, where users abandoned workflows, and which regions had distinct preferences.

Support: resolving and learning:
Despite meticulous planning, incidents occurred. A payment processing outage in one market triggered rapid incident response: the support team engaged customers, offered alternatives, and restored service within hours.
When an unexpected interaction between autonomous ride features and local traffic regulations created user confusion, the team diagnosed the issue, implemented a fix, and deployed it to users within days. More importantly, each incident triggered investigation.
Why did it happen? What signals did we miss? How do we prevent recurrence? Post-mortem reviews informed improvements to both the app and the operational processes. Issues discovered in ‘support’ fed back into the ‘discover’ and ‘design’ cycles, continuously refining the product.

Continual improvement:
The journey from ‘discover’ to ‘support’ was not linear but cyclical. Feedback from ‘support’ informed new ‘discover’ iterations as market conditions evolved. Performance data from ‘operate’ fed into ‘deliver’ improvements. Customer insights from ‘deliver’ shaped strategic decisions about feature prioritization and regional adaptations. By embedding DPSM practices throughout this lifecycle, ICR’s unified mobile app became more than a technical achievement. It became a reflection of the company’s commitment to customers: reliable, innovative, responsive to local needs, and continuously improving. As Max envisioned, ITIL Car Rental had taken a bold step toward being the world’s most trusted mobility partner, delivering the vision through every customer interaction, every design decision, and every operational moment.

Service:
Implementing a global HR management service: an internal service lifecycle
The challenge:
ITIL Car Rental’s expansion across multiple regions and service lines created mounting complexity in workforce management. Different legal entities, varying employment regulations, localized payroll requirements, and regulatory compliance across jurisdictions had strained the company’s aging HR systems. The company’s executive team identified modernization of HR management services as essential to support ICR’s growth strategy whilst maintaining operational consistency and compliance across markets. Omar’s IT delivery team took ownership of implementing a new vendor-supplied HR management system, a solution that would run on ICR servers, integrate seamlessly with existing internal systems, and serve thousands of employees and contractors across dozens of countries.

Discover: understanding the landscape
The team began by organizing a comprehensive ‘discover’ iteration. Assessing the organizational context, the team analysed how ICR’s expansion strategy, new regulatory requirements in different markets, evolving workplace expectations, and the growing complexity of managing multiple legal entities across regions created both pressure and opportunity for modernization. Working closely with the HR business partner and Max’s office, Omar’s team gathered requirements from across the organization: HR representatives and business managers in each country, payroll departments, compliance officers, finance teams managing workforce costs, and executives overseeing the talent strategy. The discovery revealed critical patterns. European operations faced strict data protection and employment law requirements. Asia-Pacific branches needed sophisticated multi-currency payroll capabilities. The US and Canadian operations required integration with complex benefits administration systems. Every region needed consistency in talent management and performance tracking, yet each had distinct regulatory demands. A business analyst from Omar’s team documented these needs systematically, whilst Alex, the Enterprise Architect, assessed the technical implications of supporting multiple legal entities, integrating with existing systems (payroll, finance, learning management, employee engagement platforms), and ensuring data security and regulatory compliance. The vendor’s product roadmap was evaluated against ICR’s requirements, revealing both strong alignment and specific gaps requiring customization. The team agreed on a clear direction: implement a core HR platform from a reputable software vendor as the system of record for employee master data, organizational structure, and talent management across all regions,
while integrating specialized capabilities for payroll, benefits, compliance reporting, and data protection. Investment was secured with realistic timelines accounting for the complexity of multi-region deployment, and a formal steering committee was established to guide implementation.

Design: defining the solution:
With requirements agreed, Omar’s team began detailed design activities. Service design workshops brought together local HR representatives, payroll specialists, compliance officers, and technology architects. The team mapped existing HR processes in each region, identifying which would be standardized globally and which would require local customization. Design workshops revealed critical service interactions. HR teams needed intuitive interfaces for managing recruitment, onboarding, performance management, and learning across different employment models. Employees required easy access to personal information, benefits enrolment, and career development features. Payroll teams needed reliable data integration with local accounting systems and regulatory reporting tools. Compliance officers required audit trails, secure data management, and reporting to meet legal obligations in each jurisdiction. Alex developed detailed integration architecture, specifying how the HR system would communicate with existing payroll, finance, learning management, and employee engagement platforms. Data flows were mapped, ensuring that changes in one system were reliably distributed to dependent systems without manual intervention or data errors. Security and data protection requirements were designed into every integration point; this was particularly critical given GDPR, CCPA, and local data residency requirements. Data migration became one of the key design points. The team designed a phased deployment approach: implementation across ICR headquarters first, then staged rollout to major regional clusters, enabling learning and refinement before full global deployment. Supporting documentation, such as user guides for different roles, migration playbooks, and integration manuals, was planned in detail.

Acquire: securing resources:
With design specifications complete, Omar’s team identified required resources. The vendor’s licensing model (supporting anticipated growth); implementation consultant expertise (to guide customization and deployment); cloud infrastructure capacity for testing and staging environments; integration middleware (to connect the new HR system with existing enterprise systems); and data migration tools were all specified. The ‘acquire’ activity involved careful sourcing decisions. The vendor partnership was formalized, establishing support levels (the vendor providing third-line support, with first-line and specialist support to be provided by Omar’s team). External systems integrators with expertise in the vendor’s platform and multi-region HR implementations were evaluated and contracted. Cloud infrastructure capacity was procured, allowing for future growth. Service agreements included service level commitments and compliance obligations aligned with ICR’s governance standards. Resources were also identified internally: team members who would receive specialized training to support the system; members of Omar’s operations team who would provide day-to-day administration; security and compliance specialists to oversee implementation controls. Procurement was coordinated to ensure availability ahead of the ‘build’ phase.

Build: constructing the solution
Omar’s team established an implementation program, structured as a series of building activities. First, the core HR system was configured to match ICR’s organizational structure, employment classifications, and role hierarchies. Configuration activities addressed fundamental requirements: multi-legal entity support, multi-language and multi-currency capabilities, and foundational data structures. Parallel to core configuration, integration development began. The team, supported by the vendor and a vendor’s consulting partner, configured data flows from the HR system to payroll systems, ensuring employee changes (salary adjustments, location changes, benefits modifications) flowed reliably to payroll processing. Integration with the finance system ensured workforce costs were accurately captured. Learning management system connections ensured course assignments and certifications were synchronized. Security and compliance controls were embedded throughout, including audit logging, data encryption, access controls, and automated reporting for regulatory requirements. Extensive testing occurred throughout the ‘build’ phase. Functional testing verified that each configuration matched requirements. Integration testing validated that data flowed correctly between systems without errors or data loss. Security testing confirmed that sensitive personal data was protected and that access controls functioned as designed. Business process testing involved HR teams walking through common scenarios (such as hiring a new employee, transferring someone to a different country, or managing a separation), ensuring the system supported the complete workflow. User acceptance testing engaged representatives from different regions and roles. HR teams in Germany tested GDPR compliance features. Payroll teams in multiple countries verified that their specific regulatory requirements were met. Local compliance officers confirmed that reporting would support local legal obligations. Supporting documentation, such as operational runbooks for system administration, user guides tailored to different roles, and troubleshooting guides, was developed and reviewed. Apart from the HR teams, selected users from all affected teams were involved, testing the interfaces and workflows for requesting leave, conducting assessments, reserving training, of reporting HR incidents. These tests revealed the need for end-user training and onboarding during the new service roll-out. Transition plans were updated to allow time for this.
Transition: going live:
The team carefully prepared a transition strategy. Headquarters implementation was planned first, serving as a dress rehearsal. A parallel run, with both old and new systems operating simultaneously, was conducted for three weeks, allowing both systems to process payroll and generate reports for comparison. The payroll teams validated that the new system calculated amounts identically to the legacy system, detecting and resolving discrepancies before they affected employees. Omar coordinated the preparation activities. User training was delivered to HR teams, payroll specialists, managers, and employees. Help desks were staffed and trained. Communication plans explained the transition to all users, emphasizing continuity of services and highlighting new capabilities. Vendor support teams were onboarded, understanding their roles during the transition period. Data migration, which involved extracting employee master data from legacy systems, cleansing it, loading it into the new system, and validating completeness and accuracy, was carefully orchestrated and verified. Transition day at headquarters was carefully planned. The legacy system was frozen at a specific point, a final data extract was taken, loaded into the new system, and system access was switched over. The team remained staffed throughout the transition and into the following week, monitoring system performance closely, responding to questions, and resolving issues. Incident response procedures were in place, with escalation paths to the vendor’s support team available if needed. Following successful headquarters transition, the team planned regional deployments. Each regional cluster (Europe, Asia-Pacific, Americas) had a transition period, with lessons from earlier transitions incorporated and local considerations addressed. The staggered approach allowed the central team to support each region and enabled best practices to propagate from early transitions to later ones.

Operate: maintaining excellence:
With the system live across regions, Omar’s team shifted focus to reliable operations. Infrastructure monitoring tracked system health, performance, and availability across all deployment sites. Automated health checks, such as database integrity tests, integration validation, and backup verification, ran daily, alerting the team to any deviations from expected operation. The team established routine operational activities: security patches supplied by the vendor were tested in staging environments, then deployed to production overnight. Data backups were performed daily, with regular restoration tests confirming that recovery was possible. System performance was monitored, with growth projections ensuring sufficient capacity as employee counts increased. User access was reviewed every week, ensuring that accounts of employees that had left the company were promptly deactivated and that role changes were reflected in system permissions.
When issues appeared, monitoring detected these deviations and triggered investigation. The team maintained a problem backlog, working with the vendor to address underlying issues and implementing fixes or workarounds as appropriate.

Deliver: serving the organization
The ‘deliver’ activity brought the HR system into daily organizational use. Omar’s team established service level commitments: HR teams would have to access to the system 99.5% of the time; user support queries would be acknowledged within four hours; critical issues affecting payroll or compliance would be resolved within eight hours. The team was constrained by the respective commitments of the vendor and, although in many cases a higher service level was provided, it could not be formally committed to. A first-line support team knowledgeable about ICR’s specific configuration and trained on common issues responded to user questions. A knowledge base captured solutions to frequent issues, enabling self-service support. Employees received training on using the service: how to access their information, update personal details, enrol in benefits, and request time off through the HR portal. Delivery included routine service actions: onboarding new employees to the system (ensuring they were created with appropriate access and initial data); offboarding departing employees (deactivating access, generating final pay calculations, archiving records); managing organizational changes (updating reporting structures when teams were reorganized); conducting benefits enrolment campaigns (ensuring employees could select and modify coverage). The team monitored delivery metrics carefully: system availability, user satisfaction (gathered through surveys), processing timeliness (time from employee action to system reflection), and error rates (incorrect calculations, missing data). Service level reporting informed ongoing improvements and triggered escalations if service quality threatened to fall below the agreed level.

Support: resolving and learning:
Despite robust operational procedures, incidents occurred. A payroll integration process failed one month due to an unexpected data format in the finance system, causing a four-hour delay in the payroll. The support team immediately engaged payroll managers, communicating the issue and estimated resolution time. The technical team worked with the finance team and the vendor to understand the root cause, developed a fix to handle the unexpected data format, implemented the fix, reran the integration process, and verified accuracy. By the end of the day, normal payroll processing resumed. On another occasion, a regional compliance officer discovered that a localized tax calculation in one country was producing results that didn’t align with current regulations. The incident was escalated to the vendor’s specialist support team. Together, they analysed the regulation change, determined that a configuration parameter needed adjustment, updated the system, revalidated historical calculations, and rolled forward with correct calculations prospectively.
Each incident triggered a post-mortem review, where the support team asked: why did the issue occur? Were there warning signs we missed? How do we prevent recurrence? Findings from post-mortems informed improvements to configuration, integration design, monitoring, documentation, and training. Particularly significant improvements, such as enhanced validation of finance system data before processing payroll, were incorporated into the ‘discover’ and ‘design’ phases to shape future improvements.

Continual improvement:
The journey from ‘discover’ to ‘support’ was cyclical. Feedback from ‘support’, including new issues and lessons learned, informed new ‘discover’ iterations as regulations evolved, ICR’s business expanded into new markets, or new compliance requirements emerged. Performance data from ‘operate’ informed design improvements when system bottlenecks were identified or user experience could be enhanced. User feedback from ‘deliver’, captured through surveys and support interactions, shaped priorities for new features and refinements.
When HR teams requested better reporting capabilities to support talent analytics, this feedback was captured, evaluated during ‘discover’ activities, and prioritized in design cycles. By embedding DPSM practices throughout this lifecycle, Omar’s team transformed HR management at ITIL Car Rental.
What had been a patchwork of legacy systems and manual processes became a unified, reliable platform supporting the company’s global growth. Compliance risks were reduced through automation and audit trails. HR teams gained visibility into workforce data and could respond quickly to business needs. Employees had instant access to their information and could manage their own preferences. The system provided a foundation for HR analytics, enabling data-driven decisions about talent, compensation, and organizational structure. As Max envisioned, ICR’s transformation extended beyond customer-facing products to the internal systems and processes that enabled the company to operate effectively. By treating internal HR services with the same rigor and discipline as external products, Omar’s team ensured that ITIL Car Rental’s greatest asset, its people, were supported by systems as reliable, responsive, and capable as the mobility services ICR offered to customers worldwide. Please refer to the ITIL Car Rental scenario for additional context when answering this question. ICR has completed the first iteration of enhancements to its mobile booking platform. After release of these enhancements, performance metrics showed mixed results across regions, some branches reported faster booking completion times, while others saw no measurable improvement. The transformation lead has gathered cross-functional teams to review what happened, discuss why outcomes differed, identify insights, and consolidate learnings that may guide adjustments for the next release.
Which stage of the ‘learning’ layer is ICR performing in this situation?

  1. Study
  2. Observe
  3. Integrate
  4. Reflect

Answer(s): A



A service provider is planning improvements to an existing service. The team reviews how the service supports business activities, examines outcomes achieved by different user groups, and considers how changes might affect both results and user perception.
Which ITIL Guiding Principle is MOST clearly demonstrated in this scenario?

  1. Focus on value
  2. Start where you are
  3. Progress iteratively with feedback
  4. Collaborate and promote visibility

Answer(s): A



An organization is introducing a new digital operating model that changes how teams are structured, how services are delivered, and how customers interact with the business. This initiative impacts multiple departments and requires new capabilities, processes, and ways of working. How should this initiative be categorized?

  1. An improvement addressed through the ITIL Continual Improvement Model
  2. An activity performed as part of business-as-usual operations
  3. A significant change affecting the organization’s value system
  4. A minor adjustment within an existing management practice

Answer(s): C



Share your comments for ITIL ITIL V5 Transformation exam with other users:

A
AI Tutor Explanation
7/21/2026 5:23:40 PM

Question 366:
Question 366 asks how to apply an Application Security Group (ASG1) to VM1. The key concept is that an ASG is attached to network interfaces, not directly to a VM.

  • Correct answer: A. Associate NIC1 to ASG1
  • Why: An ASG is used to group NICs so NSG rules can target the group. To apply ASG1 to VM1, you must attach VM1’s NIC (NIC1) to ASG1. Merely modifying the ASG’s properties or modifying NSG1 does not attach the VM’s NIC to the ASG.
  • Why others are wrong:
- B: “Modify the properties of ASG1” does not attach it to the NIC. - C: “Modify the properties of NSG1” changes NSG settings, but not ASG associations.
Quick note:
  • After associating NIC1 with ASG1, you can reference ASG1 in NSG rules as a source or destination to control traffic for VM1’s NIC. Example commands (CLI) or portal steps involve adding the NIC to the ASG.

A
AI Tutor Explanation
7/20/2026 9:43:58 AM

Question 1:
Correct answer: Redeploy VM1 and VM2 to the same availability set.
Why:

  • A Basic Load Balancer’s backend pool must consist of VMs that are in the same Availability Set. If VM1 and VM2 are in different AVSets (or one isn’t in an AVSet), you can’t add both to LB1’s backend pool. Redeploying/moving both VMs into the same Availability Set resolves this.
  • If you needed cross-AVSet load balancing, you would use a Standard Load Balancer instead.

What to do next (high level):
  • Create or choose a single Availability Set.
  • Move VM1 and VM2 into that AVSet.
  • Add both VMs to LB1’s backend pool.

A
AI Tutor Explanation
7/18/2026 4:50:31 PM

Question 1:
Here’s a targeted explanation of Question 1.

  • The scenario: You’re deploying several new VMs on on-prem Hyper-V (Windows Server 2012 R2). You’ve got PowerShell scripts to configure VMs after deployment and want them to run automatically on each new VM.

  • Options brief:
- SetupComplete.cmd in %windir%\setup\scripts - A GPO to run as logon scripts - A GPO to run as startup scripts - Put the scripts on a new VHD
  • Why A is the best choice here:
- SetupComplete.cmd runs during Windows Setup (after the OS is installed and before the first logon). If you base new VMs on a generalized image, the script will execute automatically on first boot, ensuring the VM is configured right away without requiring domain login or user interaction. - GPO startup/logon scripts require the machine to be domain-joined and the GPO to be processed at boot or user logon, which adds timing and dependency considerations and may not run reliably during first boot from a generalized image. - Putting scripts on a VHD won’t automatically execute anything unless you explicitly configure a startup process, which is less reliable than using SetupComplete.cmd for first-boot customization.
  • Implementation tip:
- Place a file named SetupComplete.cmd in %WINDIR%\Setup\Scripts\ with your PowerShell commands (calling powershell.exe -NoProfile -ExecutionPolicy Bypass -File YourScript.ps1, for example). This file runs once when Windows Setup completes on each new VM created from your image.
Note: The explanation in the provided ans

A
AI Tutor Explanation
7/1/2026 9:25:07 AM

Question 1:
The correct answer is C.
Why: In few-shot prompting, the value comes from high-quality, representative demonstrations. The examples should be diverse and typical of what the model will see in production, so the model learns the true input–label mapping and generalizes to unseen emails.
Why the other options are less appropriate:

  • A: Using random, unrelated examples does not reflect the actual task distribution and won’t help the model generalize to real inputs.
  • B: “Always use more than 10 examples” isn’t a universal rule; quantity without quality and relevance can add noise.
  • D: Intentionally incorrect labels would mislead the model and degrade performance; you want correct, coherent mappings.

Practical tip: ensure the examples cover common cases and edge cases, use the same input–output format, and keep labels consistent with the task (e.g., Spam vs. Work).

A
Anu
6/30/2026 1:05:52 PM

AWESOME and Thanku

A
AI Tutor Explanation
6/27/2026 6:40:26 AM

Question 24:
Question 24 asks which three actions are needed to set up intercompany accounting between two legal entities.
The three correct actions are:

  • A) Select intercompany journal names.
  • C) Create intercompany main accounts to use for the due to and due from accounting entries.
  • D) Define intercompany accounting setup by creating legal entity pairs defining originating and destination companies.

Why these are correct:
  • D defines the actual pairing and direction (which entity is originating and which is destination). Without defined pairs, there is no enabled intercompany relationship.
  • C establishes the main GL accounts used for the due-to and due-from postings between the entities, enabling correct cross-entity accounting and audit trails.
  • A standardizes and identifies intercompany postings via dedicated journal names, aiding tracking and reporting.

Why the other options aren’t part of the three actions:
  • B (Configure intercompany accounting in both the originating and destination entities) is not listed as one of the three actions in this question’s solution.
  • E (Configure intercompany accounting in the destination entity only) would be insufficient on its own.

A
AI Tutor Explanation
6/27/2026 1:32:13 AM

Question 1:
The correct answer is Enabling team.

  • In SAFe, enabling teams are designed to assist other teams by providing specialized capabilities, coaching, and help with adopting new technologies or practices. They focus on enabling proficiency across teams rather than delivering features themselves.
  • Platform teams provide shared services across teams (not primarily about coaching on new tech).
  • Stream-aligned teams are value-stream–oriented and deliver features to customers.
  • Complicated subsystem teams handle a part of the system that requires deep expertise, but not primarily to uplift other teams’ capabilities.

A
AI Tutor Explanation
6/22/2026 8:23:02 AM

Question 1:

  • Answer: A

  • Why: For a Snowball Edge data-transfer job, the device rental covers the use of the appliance for the initial 10-day period at no extra charge. After those 10 days, AWS charges a daily rental fee for continued use. Data transfer activities (in or out of the appliance) and ongoing use beyond the initial window typically incur separate charges, so options B, C, and D would involve costs. In short, the only option that’s free is using the appliance for the first 10 days.

A
AI Tutor Explanation
6/22/2026 5:20:17 AM

Question 1:
The best solution is A: Configure a SetupComplete.cmd batch file in the %windir%\setup\scripts directory.
Why this is correct:

  • SetupComplete.cmd runs automatically during Windows setup after OS deployment from a generalized image. When you create new VMs from that image, the script executes on first boot, applying your post-deployment configuration without requiring user interaction.
  • This approach is appropriate for on-prem Hyper-V environments where you’re building and deploying VMs from a prepared image.

Why the other options are less suitable:
  • B (logon scripts): Run only after a user logs on; not guaranteed for first boot or for machines without interactive logon.
  • C (startup scripts via GPO): Can run at startup, but requires domain policy application and may run multiple times or fail if the machine isn’t in a ready state.
  • D (place scripts in a new VHD): Not a scalable or automated method; requires manual steps and doesn’t ensure consistent execution on every new VM.

Note: The provided explanation in the bank references a Azure VM Custom Script Extension, which is not applicable to on-prem Hyper-V. That extension is for Azure VMs, not for local Hyper-V deployments.

A
AI Tutor Explanation
6/22/2026 4:11:47 AM

Question 9:
Question 9 asks about how GitHub Copilot identifies public code matches when the public code filter is on.

  • Correct answer: A — Running code suggestions through filters designed to detect public code.

  • Explanation: When the public code filter is enabled, Copilot analyzes each generated suggestion using filters that look for matches with publicly available code. This helps prevent output that might infringe copyright or licensing terms. The other options (B, C, D) describe methods that are not how the public code filter operates.

A
AI Tutor Explanation
6/15/2026 6:26:53 PM

Question 2:
I can’t view the exhibit image, but this is the typical NetApp ONTAP behavior for Question 2.

  • The correct answer is D: Add HOST 3's IP address to the NFS export policy.
  • Why: NFS access is controlled by export-policy rules. If the new ESXi host’s IP isn’t listed in the NFS export policy, the host cannot mount the NFS datastore, even if the volume and LUN are configured correctly.
  • Why the other options don’t solve it:
- A (Add NFSv4 to access protocols): Simply enabling NFSv4 doesn’t grant access if the host isn’t allowed by the export policy. - B (Enable Kerberos in the export policy): Kerberos is related to NFSv4 security, not to basic host access if the host’s IP is blocked. - C (Add SMB/CIFS to the access protocols): SMB/CIFS is unrelated to NFS mounts.
So, ensure the new host’s IP (HOST 3) is allowed by the NFS export policy to fix the mounting issue.

A
AI Tutor Explanation
6/13/2026 3:10:11 AM

Question 23:
Question 23 describes a multimodal model where users can upload unsafe images that could contain hidden instructions. The goal is to implement controls to mitigate this risk.
Key points to understand

  • Prompt shield for documents: Highly effective. It scans text extracted from inputs (including image text) before it’s sent to the LLM to catch hidden instructions or jailbreaking tries embedded in documents or image-derived text.
  • Prompt shield for user prompts: Partially effective. It blocks direct jailbreak attempts written in the user’s prompt, but doesn’t catch everything, especially content coming from image text.
  • Image moderation: Highly effective. Blocks unsafe or harmful images before they reach the model, preventing many attacks at the source.
  • Protected Material Detection: Not helpful here. It’s designed to detect copyrighted material in outputs, not to protect against inputs that try to manipulate the model.

Why this matters
  • The strongest defense is defense in depth: combine image moderation with both types of prompt shields. The document/text shield catches hidden instructions in extracted image text; the user-prompt shield mitigates jailbreak attempts in user-provided prompts; image moderation stops unsafe images before processing.

On the provided solution note
  • The stated answer (A: “configure a prompt shield for user prompts”) would help, but it alone does not fully meet the goal. A more robust approach is to apply all three controls (document prompt shield, user prompt shield, and image moderation) to achieve stronger risk mitigation.

M
mo
6/11/2026 9:00:16 AM

beautiful exams

A
AI Tutor Explanation
6/2/2026 6:10:04 AM

You need to implement the date dimension in the data store. The solution must meet the technical requirements. What are two ways to achieve the goal? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point. Populate the date dimension table by using a dataflow. Populate the date dimension table by using a Copy activity in a pipeline. Populate the date dimension view by using T-SQL. Populate the date dimension table by using a Stored procedure activity in a pipeline.Please answer

  • The two correct options: A and D.

  • Why:
- A. Populate the date dimension table by using a dataflow. A dataflow can generate and load the date dimension data into OneLake (Delta format) as part of the AnalyticsPOC data store, meeting the requirement to load data in one area before modeling, and it supports scheduling for ongoing updates. - D. Populate the date dimension table by using a Stored procedure activity in a pipeline. A pipeline with a Stored Procedure activity can run a T-SQL routine that materializes the date dimension table (2010 through the end of the current year), aligning with the need for deterministic population and orchestration.
  • Note: B (Copy in a pipeline) would require a source, and C (date dimension view via T-SQL) is feasible but not selected here; the two stated options are the ones identified as correct for this question.

A
AI Tutor Explanation
6/1/2026 6:15:05 AM

Question 14:

  • Correct selections: B and E

Why:
  • B. Admin access to the deployment pipeline: This gives the developers the ability to manage and run deployments within the pipeline, enabling them to deploy content to the Development and Test stages.
  • E. Contributor access to the Development and Test workspaces: This level allows them to deploy items into the Development and Test workspaces as required, while preventing deployments to Production.

Notes:
  • If you also need the developers to view Production, grant them Viewer access to the Production workspace (not part of the two required options, but needed to satisfy the “view Production” requirement).

A
AI Tutor Explanation
6/1/2026 5:32:19 AM

Question 5:
Question 5 asks how to identify min and max values for each column in a Dataflow result.
Correct options: B and E.

  • B. Enable column profile: This turns on column profiling, which computes descriptive statistics for each column, including min and max values.
  • E. Enable details pane: With the details pane enabled, you can view the per-column profile data (including min and max) when you select a column.

Notes:
  • A (Show column value distribution) is not required for min/max; it's for distribution histograms.
  • C (Show column profile in details pane) is optional. If the details pane is already enabled (E) and column profiling is on (B), you can view the profile without explicitly enabling C.

A
AI Tutor Explanation
6/1/2026 2:03:00 AM

Question 18:
Question 18: Why not A?

  • The two recommended strategies are B and D (per the answer key):
- B: Migrate users in phases based on their functions, with parallel use of legacy and Salesforce. - D: Use a full sandbox environment and run data migration tests with real legacy data.
  • Why not A: A focuses on identifying the data to migrate and planning scripts for verifying data integrity. While important, it’s primarily a preparation/validation activity, not an active risk-mitigation step during the migration itself. The question asks for strategies that directly mitigate migration risks in practice, such as staged rollout (B) and thorough testing in a sandbox with real data (D). A does not address go-live risk, user adoption, or testing of the migration process in a controlled environment.

A
AI Tutor Explanation
5/16/2026 7:04:20 AM

Question 4:
Question 4 is about when to use batch processing.

  • Answer key: A (the option related to “When to use batch processing”).
  • Core idea: Batch processing is used when you can tolerate some delay and don’t need results instantly. Data is collected over a period, then processed together in a batch.

Why this is correct:
  • Latencies are expected with batch jobs. The system processes data in groups rather than as soon as data arrives.
  • The processes are often not mission-critical at the exact moment they run, so delays don’t impact operations.

Key concepts to know:
  • Batch processing vs real-time processing: Batch processes collect data and run at scheduled times or when resources are available, whereas real-time processing handles data immediately.
  • When to use batch processing:
- High-volume data where immediate results aren’t required - Tasks that can be scheduled (e.g., nightly ETL, end-of-day payroll, bulk reports) - When cost or resource utilization is optimized by processing in groups
Examples: nightly data aggregation, batch payroll processing, end-of-day reconciliations.
If you want, I can walk through how to identify the right scenario for batch vs real-time in practice.

A
AI Tutor Explanation
5/15/2026 9:49:16 AM

Question 5:
I can’t see the [Image] in Question 5, but I can explain the likely reasoning.

  • Correct components: SAS adapter and disk (options B and D).
  • Why: This question is about diagnosing a storage-path issue inside the node. The SAS adapter connects disks to the controller, and the disks themselves are where I/O problems or failures usually originate. The cluster switches and network interface cards are more related to the network path rather than the direct storage path, unless the symptom points to a network fault.

How to examine these two components:
  • SAS adapter
- Check link status and port mapping. - Verify firmware version and compatibility. - Inspect cabling to disk shelves and any expanders. - Look for adapter errors in system logs.
  • Disk
- Check health status for each disk (fail/degraded, SMART data). - Inspect LEDs on the disk and shelf. - Review reallocation, pending operations, and overall disk state with storage commands/logs. - Confirm hot spares and disk replacement readiness.
If you want, I can walk through the exact commands you’d use in ONTAP or a CLI.

A
AI Tutor Explanation
5/14/2026 11:59:47 AM

Question 12:
Here’s why Question 12’s correct choices are C and D.

  • C (Azure DevOps, build and upload to asset library)
- What it means: Create a deployable package from a branch in Azure DevOps, then use an LCS asset upload step to push that package into the Dynamics 365 F&O asset library. - Why it’s valid: This is a standard path to prepare and publish a deployable package to LCS for deployment.
  • D (Visual Studio, create deployment package and upload)
- What it means: Use Visual Studio to generate a Dynamics 365 deployment package, then upload that package to the LCS asset library. - Why it’s valid: Visual Studio can produce the deployable package, which is what LCS expects in the asset library.
Why A and B are not correct:
  • A: Visual Studio export the project and upload to asset library
- You don’t export a project to the asset library; you export a deployable package and upload that.
  • B: Azure DevOps, queue a build and upload the model to the asset library
- The asset library stores deployable packages, not models. You upload a package, not a model.

A
AI Tutor Explanation
5/14/2026 11:49:11 AM

Question 3:
Question 3 asks for two valid ways to meet the purchase order creation validation (warn if the vendor is on the exclusion list for the customer/product and block/alert accordingly).
Correct answers: C and D

  • C: In Application Explorer, create a form extension and implement validation.
- Extend the Purchase Order creation form and add validation logic (e.g., before save/submit) to check VendExclusions for the customer/item and show a warning or block the PO as needed.
  • D: Implement Chain of Command (CoC) and method wrapping by creating a form extension class.
- Use CoC to wrap the target PO creation method, perform the exclusion check after calling super(), and enforce the rule (warning or prevent creation).
Why not A or B?
  • A (class with a form data source event handler) is not the standard pattern for this UI-level validation scenario and is less direct for enforcing creation-time behavior.
  • B (table extension with validation) cannot sufficiently enforce the UI-level workflow or trigger user-facing warnings during PO creation.

So, the two valid techniques are C and D, reflecting the recommended form-extension patterns: direct form validation and CoC-based method wrapping.

A
AI Tutor Explanation
5/14/2026 11:42:28 AM

Question 12:
Here’s how to understand question 12.

  • What the question asks: Two valid ways to prepare and deploy a software deployable package to a test environment (via the asset library in LCS).

  • The correct options: C and D.

- C: In Azure DevOps, queue a build from the corresponding branch to produce a deployable package, then upload that package to the LCS asset library. This uses a release/build workflow and requires an LCS connection set up in Azure DevOps.
- D: In Visual Studio, create a Dynamics 365 deployment package using the dev tools, then upload that deployable package to the LCS asset library. This is the Visual Studio–based path to generate and publish a deployable package.
  • Why A and B are not correct:

- A: Exporting the project from Visual Studio and uploading the project itself to the asset library isn’t the correct artifact; the asset library expects a deployable package, not a raw project export.
- B: Queuing a build and “uploading the model” to the asset library isn’t the standard deployable package workflow; the target artifact should be a deployable package, not a model file.
Key concept: Deployable packages are published to the LCS Asset Library, and you can create them either from Visual Studio or from Azure DevOps as part of a build/release pipeline.

A
AI Tutor Explanation
5/13/2026 11:23:34 PM

Question 6:
Here’s how question 6 works.
Key constraint: All new and extended objects must be in an existing model named FinanceExt. Creating a brand-new model is not allowed.
Why the two correct options work:

  • B. Overlay the existing FinanceExt model and populate the solution definition.
- This keeps all changes inside FinanceExt by overlaying the base model with your solution details.
  • C. Extend the existing FinanceExt model and populate the project model definition.
- This uses the extension approach to add your changes while still residing in FinanceExt, organized via the project model definition.
Why the other options are not correct:
  • A. Create a new model that extends the existing FinanceExt model.
- Not allowed, since no new models may be created.
  • D. Modify DefaultModelForNewProject and name the model FinanceExt.
- The goal is to place changes in FinanceExt, not to name or create a new model via config; this doesn’t describe a valid way to satisfy the constraint.
In short: use B or C; both keep changes inside the existing FinanceExt model.

A
AI Tutor Explanation
5/13/2026 11:00:29 PM

Question 2:
I don’t have the text for Question 2 here. Please paste the exact Question 2 (including all answer choices) or describe the topic it covers.
Once I have it, I’ll:

  • Identify the exam objective it targets.
  • Break down the stem and each option.
  • Use elimination and key concepts to justify why options are correct or incorrect.
  • Give the final answer with a concise explanation of the reasoning.

If there’s an image in Question 2, describe it or transcribe any text shown.

A
AI Tutor Explanation
5/10/2026 12:51:57 AM

Which statement is true about using default environment variables? The environment variables can be read in workflows using the ENV: variable_name syntax. The environment variables created should be prefixed with GITHUB_ to ensure they can be accessed in workflows The environment variables can be set in the defaults: sections of the workflow The GITHUB_WORKSPACE environment variable should be used to access files from within the runner.
Correct answer: The statement "The GITHUB_WORKSPACE environment variable should be used to access files from within the runner." is true.
Why the others are false:

  • ENV: variable_name syntax is not how you read env vars in workflows. Use ${{ env.VARIABLE }} in expressions or $VARIABLE in a shell.
  • Environment variables don’t need a GITHUB_ prefix. Custom vars can have any name; GITHUB_ is only for built-in, predefined vars.
  • defaults: cannot set environment variables. It configures defaults for run steps (like shell or working-directory), not env vars.

Extra tip:
  • GITHUB_WORKSPACE (or ${{ github.workspace }}) is the root path on the runner where the repository is checked out. Use it to access files, e.g., $GITHUB_WORKSPACE/... or ${{ github.workspace }}/....

A
AI Tutor Explanation
5/7/2026 11:34:48 PM

As an administrator for this subscription, you have been tasked with recommending a solution that prohibits users from copying corporate information from managed applications installed on unmanaged devices. Which of the following should you recommend? Windows Virtual Desktop. Microsoft Intune. Windows AutoPilot. Azure AD Application Proxy.

  • Microsoft Intune

Reason: Intune can enforce app protection policies (MAM) on managed apps, even on unmanaged devices, to prevent data leakage (e.g., restricting copy/paste, saving to non-approved apps, etc.). The other options don’t address data protection within apps on unmanaged devices.

A
AI Tutor Explanation
5/4/2026 2:43:10 AM

Question 34:

  • Question 34 asks: Which role(s) has the capability to create Policies? Choose two.
  • Likely correct roles: Compliance Manager and Compliance admin (A and B). These roles typically have policy governance rights to create and manage policies.
  • Why not the others: Compliance User is usually a limited user, not allowed to create policies. Risk Manager focuses on risks, not policy creation in standard setups.
  • Note on the provided key: The answer shown is “C” (Compliance User), which conflicts with “Choose two.” This is probably a key error. In practice, verify against your instance’s ACLs or official docs.
  • Quick check tip: In ServiceNow, review the ACLs and role permissions for the Policy records to see which roles can create policies.

A
AI Tutor Explanation
4/29/2026 11:59:58 PM

function of appnav in sdwan

  • AppNav (Application Navigation) is the Cisco SD-WAN feature that provides application-level visibility and control.
  • It maintains a catalog of applications (AppIDs) with attributes (ports/protocols, categories) and classifies traffic accordingly.
  • It allows policy authors to reference apps by name in policies, enabling application-aware routing, QoS, and service chaining based on the app’s requirements.
  • The SD-WAN fabric uses AppNav data to steer traffic along the best path, improving user experience for critical apps while optimizing WAN usage.

A
AI Tutor Explanation
4/29/2026 5:25:25 AM

Question 1:

  • Correct answer: C. Extract the hardware ID information of each computer to a CSV file and upload the file from the Microsoft Intune admin center.

  • Why this is correct

A
AI Tutor Explanation
4/29/2026 5:23:14 AM

Question 5:

  • Correct answer: A. User4 and User1 only

  • Why this is correct:
- The Automatic Enrollment setting in Intune has MDM user scope: GroupA. Only users in GroupA can enroll devices via MDM auto-enrollment. - Device6 will be enrolled via Windows Autopilot and Intune, so enrollment is allowed only for users in GroupA. - Based on the group memberships in the scenario, User4 and User1 are in GroupA, while User2 and User3 are not. Therefore only User4 and User1 can enroll Device6.
  • Quick tip for the exam:
- Remember: MDM user scope determines who can auto-enroll devices; MAM scope controls app protection enrollment. When a new Autopilot device is enrolled, the signing-in user must be in the MDM scope.

A
AI Tutor Explanation
4/29/2026 5:17:10 AM

Why this is correct

  • Correct answer: C. Extract the hardware ID information of each computer to a CSV file and upload the file from the Microsoft Intune admin center.

  • Why this is correct:
- Windows Autopilot requires devices to be registered by their hardware IDs (hash) before Autopilot can deploy Windows 10 Enterprise. - Collect the hardware IDs from the new Phoenix machines, save them in a CSV, and upload that CSV in the Intune/Windows Autopilot area. This maps each device to an Autopilot deployment profile. - After registration, you can assign Autopilot profiles (Windows 10 Enterprise, etc.). Other options (serial number CSV, generalizing, or Mobility settings) are not the initial Autopilot registration steps.

A
AI Tutor Explanation
4/25/2026 1:53:46 PM

Question 7:

  • Correct answer: B — A risk score is computed based on the number of remediations needed compared to the industry peer average.

Explanation:
  • Risk360 uses a remediation-based score. It benchmarks how many actions are required to fix issues against peers, giving a relative risk posture.
  • Why not the others:
- A: Not just total risk events by location. - C: Time to mitigate isn’t the primary scoring method. - D: Not a four-stage breach scoring approach.
Note: The page text shows a mismatch (it lists D as the answer), but the study guide describes the remediation-based scoring (B) as the correct concept.

A
AI Tutor Explanation
4/25/2026 1:42:20 PM

Question 104:

  • Correct answer: D) Multi-Terabyte (TB) Range

  • Brief explanation:
- clustering keys organize data into micro-partitions to improve pruning when queries filter on those columns. - The performance benefit is most significant for very large tables; for small tables the overhead of maintaining clustering outweighs gains. - Therefore, as a best practice, define clustering keys on tables at the TB scale.

C
Community Helper
4/25/2026 2:03:10 AM

Q23: Fabric Admin is correct. Because Domain admin cannot create domains. Only Fabric Admin can among the given options. Q51: Wrapping @pipeline.parameter.param1 inside {} will return a string. But question requires the expression to return Int, so correct answer should be @pipeline.parameter.param1 (no {})

AI Tutor 👋 I’m here to help!