ITIL Foundation (Version 5): Managing Digital Products and Services

A digital product rarely stays within the boundaries of one traditional IT service. Customers may discover a capability through an app, use it on several devices, share information with partners, receive automated support and see its features change continuously. ITIL Foundation (Version 5) updates the entry-level service-management perspective to account more directly for digital products, services, experiences and their lifecycle. The aim is still value co-creation, but the decisions covered increasingly cross product design, operation, governance and responsible technology use.

PeopleCert's official ITIL Foundation (Version 5) product page lists 40 multiple-choice questions, 60 minutes, a 65% passing mark, and a closed-book examination. PeopleCert is rolling out the wider Version 5 qualification scheme in phases rather than requiring all ITIL 4 holders to abandon their certifications. Candidates preparing for Version 5 should distinguish its digital product-and-service lifecycle emphasis from the objectives assessed in ITIL 4 Foundation; the two syllabuses are not interchangeable even while PeopleCert supports both routes.

Begin with the product-service relationship and outcomes

Digital products bring together capabilities that can be reused and evolved; services are means of enabling value through those capabilities. An online appointment system might include a scheduling application, identity integration, notification services, payment flows and operational support. The customer experiences a coordinated journey, not a separate purchase of each technical component. Managing only whether a database is running misses whether appointments can actually be booked, changed or cancelled as promised.

Value co-creation involves service providers, consumers and other stakeholders making contributions and accepting responsibilities. A provider may operate the platform, but a customer may choose access roles, establish rules for personal data and train employees. This means both outcome achievement and risk allocation need explicit attention. An appealing feature that increases fraud exposure or excludes users with accessibility needs may damage value despite high usage metrics.

The provider's Version 5 Foundation learning outcomes explicitly discuss outcomes, costs, risks, experience and sustainability. Those dimensions make decision-making more demanding than maximizing adoption or releasing features faster. A delivery choice that saves development time but creates excessive operational waste may be unattractive in the long term. Likewise, a support policy that reduces staffing cost while greatly increasing customer effort may harm the overall experience.

This perspective allows teams to distinguish product capability from the quality of its ongoing service. A new function can be technically complete but not operationally ready if monitoring, knowledge, support paths, incident response or responsible data handling are missing. A service must be designed as an enduring relationship, not only a launch milestone.

Use four dimensions to expose hidden dependencies

ITIL (Version 5) retains the holistic view through organizations and people, information and technology, partners and suppliers, and value streams and processes. These dimensions prevent an apparently local decision from ignoring the operating environment that makes it successful. A customer-facing application may rely on internal teams, cloud providers, data-processing vendors and regulatory requirements. Its real outcome depends on how these parts cooperate.

Organizations and people include decision rights, responsibilities, culture, capability and communication. An AI-supported service desk cannot be managed effectively if no one owns escalation decisions or reviews uncertain output. Information and technology include the tools, data, security controls and architecture necessary to deliver value. Even a sophisticated platform can produce incorrect outcomes when its source information is unreliable.

Partners and suppliers contribute contracts, specialist operations and external dependencies. A service that promises a four-hour recovery time may fail if a critical supplier has no comparable response obligation. Value streams and processes explain how work moves through these arrangements. Mapping customer actions alongside internal activities reveals rework, waiting, missing handoffs and gaps in accountability.

The dimensions should be investigated together. For example, an organization might introduce a chatbot that improves first-response speed but sends complex issues to overloaded humans without context. The technology works in a narrow sense, while the people dimension and value stream remain broken. The meaningful question is whether end-to-end outcomes and experiences actually improve.

Read the ITIL value system as a guide to coordination

Version 5 Foundation emphasizes the ITIL Value System, including guiding principles, governance, value-chain activities, management practices and continual improvement. A value system is not a fixed list of process stages to follow in sequence. It describes capabilities that organizations configure to respond to opportunities and demand. Governance evaluates, directs and monitors; management practices contribute resources and expertise; value streams connect activities to produce outcomes.

Guiding principles support decisions when requirements and constraints compete. Focusing on value asks whether a feature improves real outcomes. Starting where you are encourages observation of current workflows before redesign. Iteration with feedback reduces the risks of large untested assumptions. Collaboration and visibility help teams see dependencies; holistic thinking prevents local optimization; simplicity avoids unnecessary steps; optimization and automation make clarified work more reliable.

These principles can make a practical difference in product development. Consider a company extending an online claims service to a new region. Rather than copying the old approval process blindly, the team should examine the different customers, data obligations, partners and languages involved. It can test a limited rollout, monitor the claims that fail, consult support teams and refine the service before wider release. Governance still sets acceptable risk and decision rights.

Value stream mapping and management are explicit Version 5 Foundation topics. The focus is on understanding actual work and reducing waiting, errors and disconnected activity. Tools can display the flow, but a useful map should include decisions that humans make, third-party responses, user touchpoints and the information each stage requires.

Manage the product and service lifecycle as continuous work

The official Version 5 outline highlights a product and service lifecycle with activities spanning discovery and design through operation, delivery and support. Teams need to understand how those activities connect rather than imagining that a product becomes the support department's problem after release. Evidence gathered in operation should inform design priorities and future investment; customer expectations identified in discovery should influence monitoring and support readiness.

Discovery establishes what users need, which outcomes matter and where current solutions fail. Design determines service interactions, security, dependencies, capacity and accessible experiences. Build or acquisition choices must consider suppliers and technical constraints. Deployment and release need controls that match the change's risk. Operation must address incidents, requests, observability and the cost of maintaining the service. Continual improvement evaluates whether the product still delivers useful value.

A service team can contribute early by identifying the symptoms users will report and the telemetry engineers must retain. Likewise, product managers should understand the recurring issues that consume support capacity. If an integration failure creates hundreds of tickets every week, solving the root design problem may deliver more value than automating responses to those tickets. Operational knowledge is a design input, not merely aftercare.

The same principle applies to retirement and replacement. A product nearing end of life may need reliable data export, contractual communication and support for users moving to a successor. The organization's lifecycle responsibilities do not stop when new development ends. A lifecycle-oriented view helps prevent stranded customers and unmanaged data retention.

Make experience, sustainability and AI governance concrete

Version 5 gives more explicit attention to experience and responsible AI adoption. Experience covers what customers and users actually encounter across their interactions: confusion, waiting, confidence, accessibility and trust can affect value as much as task completion. A service can meet internal performance targets and still be frustrating when error messages are unclear or the same user must repeatedly explain a problem.

AI may help route support requests, summarize knowledge, forecast demand or assist operations. Yet the organization remains responsible for the reliability and appropriateness of outcomes. It should decide what information the system may use, how uncertain recommendations are handled, what records are retained, and when a person must intervene. An automated change recommendation that appears plausible is not, by itself, evidence that the change is safe.

Sustainability can influence architecture choices, energy consumption, procurement, hardware lifecycle and how operations are scaled. It should be considered alongside reliability, security and user outcomes rather than reduced to a decorative policy statement. Improving efficiency without shifting hidden costs to another stakeholder can be genuinely valuable. Documentation of trade-offs helps leaders decide whether that value is durable.

Older practice-focused material such as ITIL 4 management practices can still explain useful functions—for instance, request fulfillment, incident restoration and continual improvement—but candidates should use Version 5's own official learning outcomes to understand the new framing. Historical ITIL terminology is valuable background, not a replacement for the active syllabus.

Choose a transition route that respects existing qualifications

PeopleCert states that holders of ITIL 4 Foundation do not need to repeat the Version 5 Foundation exam merely to progress into higher Version 5 modules. It provides an optional ITIL Foundation Bridge (Version 5) for certified professionals who want an explicit update to Foundation knowledge. The broader qualification scheme is being released in stages, and older certificates are not automatically invalidated by the appearance of a newer syllabus.

For someone new to ITIL, Version 5 Foundation is a direct starting point for the current product-and-service-management approach. For a professional who already holds ITIL 4, the relevant question is whether the bridge, a targeted advanced module or current work experience would best close a knowledge gap. The decision should reflect career responsibilities and provider rules, not fear that old certificates ceased to exist overnight.

PeopleCert's public FAQ currently describes an intention to sunset ITIL 4 modules later in the transition period. Such timelines and voucher availability are subject to update, so a candidate should confirm the active schedule and language with PeopleCert before purchasing an exam. Similarly, the existence of ITIL 4 Create, Deliver and Support as an advanced ITIL 4 route does not mean it is the same curriculum as any named Version 5 advanced module.

An effective preparation exercise is to trace a digital product from user need through release, operations, experience and improvement. Identify the parties that contribute value, the four dimensions affected, governance decisions, risks, lifecycle feedback and suitable indicators. If the analysis stops at a technology inventory or a list of practice names, it has not yet captured the lifecycle-centered reasoning the newer Foundation emphasizes.