ITIL Foundation Version 5: Managing Digital Products and Services

ITIL Foundation (Version 5) is PeopleCert's updated entry point to ITIL, reflecting the management of digital products and services in increasingly interconnected and AI-enabled organizations. PeopleCert describes the Foundation examination as 40 multiple-choice questions in 60 minutes, closed book, with a 65 percent minimum passing mark. The version is not a simple renumbering of an old exam; candidates should use the official version 5 learning materials and glossary rather than assume that all ITIL 4 phrases carry over unchanged. Existing ITIL 4 Foundation holders remain recognized for progression to higher-level version 5 qualifications, and PeopleCert provides optional transition routes. The decision to pursue a new Foundation certificate should therefore consider existing credentials and career goals.

Start with the product and service outcomes

Modern organizations often operate products whose value emerges through several services, internal capabilities and external partners. A banking app is a product experience that depends on identity, payment, data, notifications, customer support and regulatory processes. Customers do not care which internal team owns a component when the app stops working. ITIL version 5 places strong emphasis on managing these connected experiences and making decisions around outcomes. Define who uses the product, what need it addresses and which parts of its lifecycle can create or erode value.

Distinguish what the customer is trying to accomplish from the outputs a delivery team produces. A successful feature release may increase adoption but overload support; a redesigned support workflow may reduce effort but prevent a critical user group from reaching essential services. Governance should balance these effects. The product and service lifecycle connects design, launch, operation, improvement and retirement within one accountable system.

Coordinate demand, capabilities and value creation

Demand enters organizations through requests, incidents, projects, changing regulations and strategic opportunities. A digital product team must decide how to allocate capacity between new features, reliability work, security and maintenance. Value cannot be equated with activity. Shipping ten features may be less useful than repairing a recurring login failure affecting most users. Effective planning makes trade-offs visible and assigns ownership for the customer-facing result. The guiding ideas of collaboration, feedback and continual improvement remain valuable, but they must be applied to the broader product and service context.

Map value streams to identify delays, duplicated handoffs and missing evidence. An application access request may move through HR, identity management, the application owner and support. Improvement could come from clearer eligibility rules or better information exchange rather than a new technology. Use baseline performance, test changes iteratively and measure whether the end-to-end outcome improved. The organization should retain visibility into cost, risk and user impact alongside speed.

Adapt governance and responsibilities to a digital organization

Governance sets direction, risk boundaries and accountability. Management designs and operates capabilities that serve those boundaries. A product owner can prioritize work, but should not silently accept regulatory risk beyond the authority delegated to the role. ITIL thinking encourages coherent responsibilities across products, services and value streams rather than narrow departmental optimization. When a cloud platform, outsourcing partner and internal application team jointly deliver one user journey, someone must be accountable for communications and recovery across all of them.

Clarify the difference between policy, decision rights and operational procedure. A security policy may require strong authentication, while a procedure defines how support agents verify identity before resetting credentials. If the process changes because an AI assistant is introduced, both the tool permissions and human review responsibilities must be evaluated. A committee that approves every trivial request is not effective governance; neither is a wholly autonomous tool that executes consequential changes without a control boundary.

Integrate AI-enabled work without surrendering accountability

Automation and AI can support incident triage, knowledge discovery and routine request handling, but generated answers may be inaccurate or manipulated. Establish which tasks an assistant can suggest, which it can perform and which require a person with appropriate authority. A chatbot that recommends a service workaround should not be allowed to reset privileged permissions by interpreting arbitrary user text as policy. Use independent authorization, logging, escalation and validation. Measure whether AI improves outcomes instead of relying on response speed or user enthusiasm alone.

The application of ITIL principles to AI-enabled work matters because new tools create new dependencies and failure modes. A model update may change advice without changing the surrounding interface. Plan monitoring and rollback, train support staff to identify incorrect generated instructions and preserve safe manual paths when the system is unavailable. An organization should know who owns the AI service and how users can challenge a decision or obtain human support.

Manage service quality, experience and risk together

Availability, capacity, continuity, security and user experience jointly determine whether a service is fit for purpose. A platform can report near-perfect uptime while users struggle with inaccessible forms or slow workflows. Measure services from the perspective of the people depending on them, with technical indicators as supporting evidence. Incident response must coordinate restoration and communication; problem analysis identifies recurring causes; change management prevents a fix from creating broader disruption. Knowledge and configuration information help teams make decisions under pressure.

Consider a cloud payroll service that becomes slow at the end of each month. The immediate incident team restores responsiveness, but a product-and-service view investigates demand patterns, third-party limits, the interface's behavior during delays and whether employees receive useful status information. Improvement may involve capacity changes, redesigned workflows, better monitoring or clearer communication. Compare options by benefit and risk, not by whichever team offers the fastest individual task closure.

Understand the transition from ITIL 4

PeopleCert explicitly recognizes ITIL 4 Foundation as an entry prerequisite for higher-level ITIL version 5 certifications. A professional already holding ITIL 4 Foundation therefore does not automatically need to resit the full Foundation exam to progress. The optional Foundation Bridge focuses on changes introduced by the new version. Professionals with advanced ITIL 4 credentials should review the issuer's published transition and recognition rules before choosing modules. Do not confuse the continued value of existing qualifications with a claim that every old examination will be sold indefinitely.

Organizations can also transition gradually. Existing incident, request, change and continual-improvement practices need not be discarded solely to adopt new terminology. Assess where value streams, product ownership, experience measurement and AI governance are underdeveloped, then adapt the operating model. An effective transition changes decision-making and outcomes, not just diagrams or course certificates. The ITIL 4-to-version-5 transition can help distinguish conceptual continuity from genuinely new emphasis.

Evaluate a digital product as both a product and an ongoing service

A university launches a mobile application for course registration. The product team celebrates on-time release and strong initial adoption, but students encounter failed enrollment during peak demand and receive inconsistent support across channels. A version 5 Foundation perspective asks whether the digital product creates the expected experience throughout its lifecycle. Product capabilities, service support, data quality, identity, infrastructure and communication form one value-delivery system. An app that performs well in demonstration but cannot withstand enrollment week has not yet delivered its promised value.

Map stakeholder outcomes before choosing metrics. Students need reliable enrollment and clear confirmation; academic staff need accurate class capacity; IT needs sustainable operations; leadership needs compliance and manageable costs. Product measures such as feature use and release frequency do not replace service measures such as completion rate, availability at critical times and resolution quality. Segment failures by device, network condition and process step so that a favorable overall average does not hide a high-impact group of affected students. Link improvement priorities to those observed outcomes instead of approving the largest feature request automatically.

AI-enabled support can help students navigate policies, but it changes the operational model. The assistant may summarize timetable rules or propose next steps, yet it must not invent enrollment entitlements, reveal another student's record or execute high-impact changes without independent authorization. Define knowledge ownership, retrieval controls, escalation to a qualified human and testing for ambiguous or adversarial requests. Treat vendor updates and model behavior changes as service changes requiring evaluation. A technology team should be able to disable an unsafe automation while preserving a workable alternative for students.

Recovery planning needs the same lifecycle view. During a registration surge, capacity changes, rollback, queue management, communication and supplier response must be coordinated with academic business owners. Practice the failure scenario before the critical week, and distinguish a technically restored service from one that has reconciled incomplete enrollment transactions. Continual improvement should compare results against targets and feed observations back into product planning. This ties governance, value creation, service quality and responsible automation together in a concrete way—and helps candidates reason about version 5 concepts rather than memorize a promotional description of digital transformation.

A version change also affects learning plans. Staff who hold ITIL 4 Foundation should check PeopleCert's official transition and recognition arrangements before buying duplicate training. Teams can continue applying established service-management practices while learning the updated vocabulary and expanded product-oriented emphasis. The value is not in renaming an incident or adding a new diagram. It is in asking better questions about product ownership, service relationships, measurable outcomes and the way digital capabilities evolve after release.

Prepare for the official version 5 Foundation exam

Use PeopleCert's current version 5 learning materials and sample questions to master terms, products and services, lifecycle management, governance, value and continual improvement. Build a case around a customer-facing digital service and ask which value stream, roles, risks and measures influence a particular decision. Practice choosing the best action when a technical improvement undermines experience or a proposed automation bypasses accountability. Since Foundation is closed book, understand the principles well enough to recognize their use without relying on a reference. Check PeopleCert's current schedule, language choices and eligibility rules shortly before booking; version transitions can affect available paths and resources.