ITIL Foundation Version 5 is best understood as one digital product and service management system. Stakeholder needs create demand and opportunities. Teams co-create value across a product-and-service lifecycle. The four dimensions keep decisions holistic. Guiding principles shape behavior. Governance directs the organization. Value-chain activities and management practices provide capability. Continual improvement changes the system. Value-stream mapping makes end-to-end flow visible.
The public PeopleCert page for the current ITIL Foundation Version 5 does not publish exam-domain percentages, so the map below follows the official learning areas rather than inventing weights.
Digital products and services are the center of the map
Version 5 frames ITIL around managing digital products and services across their lifecycle. Products create or package capabilities; services enable customers and users to realize value from those capabilities.
The Foundation candidate should think beyond a support desk or process and see the full product/service system.
Value co-creation connects providers, consumers, and stakeholders
Value is created through interaction among multiple parties and is evaluated through outcomes, costs, risks, experience, and sustainability. Different stakeholders can experience the same product differently.
The map should keep value at the center because all other ITIL structures exist to improve value creation.
The four dimensions surround every lifecycle decision
Organizations and People asks whether skills, culture, roles, and capacity fit the work. Value Streams and Processes examines end-to-end flow. Information and Technology examines data and enabling systems. Partners and Suppliers examines external capability and dependency.
A decision that ignores one dimension can create hidden operational debt.
The ITIL Value System provides the organizing framework
The Value System connects guiding principles, governance, value-chain activities, management practices, and continual improvement.
Think of it as the structure that helps an organization convert demand and opportunity into sustainable value across products and services.
Guiding principles influence every other component
Principles should shape discovery, design, delivery, support, optimization, governance, and improvement. They provide flexible guidance when the framework does not prescribe one exact process.
That makes them cross-cutting rather than one stage in the lifecycle.
Lifecycle activities connect strategy with operation
PeopleCert’s public Version 5 scope explicitly covers activities from discovery and design through operation, delivery, and support. These activities should be connected rather than managed as independent silos.
A product decision made during discovery can create technical debt or support consequences much later in the lifecycle.
Management practices provide reusable capability
Practices bring together resources, knowledge, people, tools, partners, and ways of working needed to accomplish objectives. They can support several lifecycle activities and value streams.
A practice is useful because it contributes capability to the product/service system, not because it owns one isolated queue.
Value streams show how work actually moves
Value Stream Mapping and Management helps teams see sequence, handoffs, delay, waste, visibility, and outcome across the full flow from demand to value.
The map should include feedback loops because work and information often move in more than one direction.
Continual improvement provides the learning loop
Improvement uses evidence about current performance, target outcomes, changes, and results to evolve products, services, practices, and value streams.
In Version 5, continual improvement supports the lifecycle mindset rather than sitting outside normal work.
AI-enabled complexity increases the value of lifecycle thinking
PeopleCert explicitly frames Version 5 for modern digital and AI-enabled environments. AI can change product behavior, operational risk, stakeholder experience, data dependencies, and speed of change.
The framework’s value is not AI-specific technology guidance; it is a management system that helps organizations keep value, governance, flow, and improvement visible as technology changes.
The map also explains the bridge from ITIL 4.
Existing ITIL 4 holders can take a shorter Version 5 bridge because much foundational knowledge carries forward while terminology, product/service framing, lifecycle emphasis, and other enhancements change.
The map should also show outcomes, costs, risks, experience, and sustainability around the value center. These are not separate departments; they are perspectives stakeholders use to judge whether the product or service is creating worthwhile value. A local efficiency gain can reduce overall value if it increases risk or damages user experience elsewhere.
Discovery should be placed near the front of lifecycle thinking because teams need to understand problems, stakeholders, constraints, and desired outcomes before committing to a design. A weak discovery phase can produce a technically sound product that solves the wrong need.
Design connects discovered needs with the organization, technology, suppliers, and value streams required to realize them. The four dimensions are especially useful here because they force the team to consider skills, information, partners, and process alongside the product architecture.
Delivery and operation should be shown as connected rather than as a handoff where product teams stop caring. Operational feedback, incidents, service performance, customer behavior, and technical debt all influence later product decisions. Lifecycle thinking keeps delivery teams connected to real use.
Support belongs on the same lifecycle because user questions, incidents, requests, and feedback are direct evidence about whether the product or service is realizing value. Support data should feed improvement and design rather than remain trapped in an operational queue.
Governance belongs above the lifecycle as directional oversight. It helps evaluate conditions, direct priorities, and monitor results. The precise governance practices can vary, but the map should distinguish oversight from day-to-day management activity.
Management practices should be drawn as reusable capabilities that can support several lifecycle activities. One practice may help discovery, delivery, operation, and improvement in different ways. This prevents the map from turning practices into isolated departments.
Value-stream mapping should cross organizational boundaries. A product may move through business, design, engineering, security, operations, and supplier steps before a user receives value. Mapping only one team’s work misses the delays and rework created at handoffs.
Continual improvement should also feed discovery. Improvements can reveal new needs, changing stakeholder expectations, technical-debt limits, or opportunities for a different product direction. That makes the lifecycle iterative rather than a one-way path.
Use the map during Foundation practice by taking a scenario and identifying the central value question, affected lifecycle activity, relevant dimension, useful guiding principle, management practice, and improvement feedback. This structured classification makes Version 5 terminology easier to apply without forcing every scenario into one rigid process.
Technical debt should be drawn across lifecycle activities because a short-term design or delivery decision can create later operational and improvement cost. Lifecycle thinking helps teams make that trade-off visible rather than treating debt as a purely engineering concern.
Sustainability should also sit near value rather than in a separate box. Resource use, supplier choices, architecture, lifecycle, and operating practices can all affect sustainability. The important Foundation idea is that sustainability can influence stakeholder value and long-term decisions.
Experience belongs on the same value map because users can receive the intended functional outcome while still experiencing confusing, slow, or frustrating interactions. Product and service management should therefore combine outcome and experience rather than treating satisfaction as a cosmetic measure.
Partners and suppliers create external flow across the value stream. Contract lead time, vendor reliability, shared responsibilities, and third-party technology can become bottlenecks or risks. Value-stream mapping is useful because those external handoffs are visible alongside internal ones.
The bridge route also fits the map as a transition mechanism for people, not for products. ITIL 4 holders already know much of the foundational system, so the bridge focuses on updated language, lifecycle emphasis, digital/AI context, and refined value concepts. New learners build the full map from the beginning.
Collaboration should be drawn across the map because value streams cross organizational boundaries. Product, service, engineering, operations, security, suppliers, and customers contribute different information and capabilities. Visibility reduces the risk that one group optimizes its own activity while harming end-to-end value.
Metrics belong on the feedback paths rather than at the center. Teams should measure what helps them decide whether outcomes, flow, experience, quality, risk, or improvement targets are being achieved. Measurement is useful because it informs action, not because every activity needs its own dashboard.
Lifecycle thinking also connects to technical debt and continuity. A design choice can speed delivery now while increasing later support or recovery difficulty. Version 5 encourages teams to anticipate those consequences across the lifecycle instead of treating them as someone else’s future problem.
The finished map is a practical study tool: start from any scenario, identify the stakeholder value concern, lifecycle activity, affected dimension, relevant principle, practice capability, value-stream issue, and improvement feedback. That sequence makes the public Version 5 learning areas work together as one system.
The map should also make product and service distinct but connected. A product can bundle resources and capabilities, while services create a way for stakeholders to realize value from those capabilities. Digital organizations often manage both simultaneously, so lifecycle decisions should consider how product change affects service experience and support.
Value-stream mapping belongs between governance and improvement because it reveals how policy and local decisions affect flow. A governance rule can protect risk but create delay; a supplier contract can introduce waiting; an automated step can reduce handoff. Mapping makes those consequences visible enough to improve deliberately.
The ITIL Value System should be viewed as adaptable rather than a prescriptive sequence. Guiding principles, practices, governance, lifecycle activities, and improvement provide structure, but organizations still choose how to apply them according to context. That flexibility is important in fast-changing digital environments.
Use the final map to compare Version 5 with an ITIL 4 memory without forcing one vocabulary onto the other. Carry forward enduring ideas such as value, dimensions, principles, governance, practices, and continual improvement, then learn the Version 5 product/service lifecycle emphasis and updated language explicitly.
Within the broader ITIL certification path, the strongest preparation keeps Version 5 terminology consistent and uses the Value System, dimensions, lifecycle, practices, and value streams as one connected model.