ITIL Foundation Version 5 is easiest to learn when the study order follows how the framework connects value, lifecycle decisions, governance, practices, and improvement. The current ITIL Foundation Version 5 exam gives candidates 60 minutes to answer 40 closed-book multiple-choice questions, with 65% required to pass. PeopleCert’s public Version 5 learning areas do not publish percentage weights, so preparation should follow the official structure rather than inventing a domain ranking.
A practical sequence begins with digital products and services, then value co-creation, the four dimensions, the ITIL Value System, guiding principles, lifecycle activities, management practices, continual improvement, and value-stream mapping. That order creates one coherent management model instead of a glossary.
Phase one: learn the language of digital products, services, and value
Start with the distinction between products and services and the idea that value is co-created with customers, users, partners, and other stakeholders. Include outcomes, costs, risks, experience, and sustainability in the discussion.
Use one familiar digital service—online banking, a collaboration platform, or an internal HR portal—and describe what product capabilities exist behind it and what value the service enables for users.
Phase two: use the four dimensions as a completeness check
Study Organizations and People, Value Streams and Processes, Information and Technology, and Partners and Suppliers. Apply all four to the same example.
For each dimension, identify one failure mode. A product can fail because skills are missing, information quality is poor, supplier lead time is weak, or the value stream contains unnecessary handoffs even when the technology itself works.
Phase three: build the ITIL Value System from memory
Draw the Value System and connect guiding principles, governance, value-chain activities, management practices, and continual improvement. Explain how demand or opportunity enters and how the system supports sustainable value.
The point is not artistic accuracy. The exercise should make clear that practices and lifecycle work happen inside an organizational management system rather than in isolation.
Phase four: learn the guiding principles through decisions
Apply the principles to short scenarios instead of memorizing slogans. Ask how focus on value, starting where you are, iterative progress, collaboration and visibility, holistic thinking, simplicity, and optimization/automation would change a real decision.
Principles become useful when they help choose between several plausible actions.
Phase five: study lifecycle activities as connected work
PeopleCert’s Version 5 Foundation page emphasizes activities from discovery and design through delivery, operation, and support. Build one lifecycle for a new digital product and another for an improvement to an existing service.
Notice how decisions made during discovery or design can create technical debt, support burden, or continuity risk later. Lifecycle thinking is about consequences across time.
Phase six: learn management practices by purpose
Do not begin by memorizing detailed procedures. Group practices by what capability they provide: governance, security, relationship, supplier, delivery, support, change, measurement, or improvement.
Foundation-level understanding is strongest when you can recognize which practice capability supports the scenario and why.
Phase seven: connect continual improvement to ordinary work
Use the continual improvement model on one current process. Define the desired outcome, current state, target state, actions, measurement, and how improvements will be sustained.
Version 5 frames improvement as everyday behavior across products, services, practices, and value streams rather than a special project performed only after failure.
Phase eight: practice Value Stream Mapping and Management
Choose an end-to-end service request or product change and map every handoff, wait, rework step, supplier dependency, and feedback loop. Mark where value is created and where work sits idle.
This exercise makes the Version 5 emphasis on flow visible and helps prevent local optimization that makes the overall experience worse.
Phase nine: compare ITIL 4 knowledge with Version 5 carefully
If you already hold ITIL 4, create a separate list of concepts that carry forward and concepts whose framing or terminology has changed. PeopleCert offers a dedicated Foundation Bridge for eligible ITIL 4 holders precisely because the update is not a simple renaming exercise.
Do not merge the two versions casually in notes. Study the version tied to the exam route you actually booked.
Finish with timed scenario practice
Use mixed 40-question sets and classify each problem before answering: value, lifecycle, dimension, principle, governance, practice, improvement, or value stream. Then explain why the closest distractor is weaker.
Keep one product/service example through the entire sequence. A customer portal, internal collaboration service, digital commerce platform, or employee application works well because it has clear users, suppliers, information, technology, support needs, and improvement opportunities. Reusing one example prevents the framework from becoming abstract. Each new concept should change how you see the same product: its value, flow, governance, lifecycle, practices, and improvement model.
During the value phase, write three perspectives on the same service: customer, user, and provider. The customer may care about business outcome and risk, the user about experience and reliability, and the provider about sustainable operation and cost. This exercise reinforces co-creation because value is not defined from one viewpoint alone. It also prepares you for scenario questions where several stakeholders have legitimate but different priorities.
During the four-dimensions phase, include dependencies that are easy to overlook. Organizations and People should include skills, incentives, communication, and capacity. Information and Technology should include data quality and integration, not only tools. Partners and Suppliers should include contracts and continuity. Value Streams and Processes should include handoffs and wait time. If your analysis contains only technology, the framework is not being used holistically.
When learning the Value System, explain how governance differs from management. Governance evaluates, directs, and monitors; management organizes and performs work within that direction. Keeping those roles separate helps with scenario questions where leadership sets policy or risk appetite while delivery teams decide how to implement the work operationally.
When studying the guiding principles, avoid searching for a single “correct” principle in every situation. Several can apply at once. A large transformation can benefit from starting where you are, progressing iteratively with feedback, collaborating visibly, and keeping the solution simple. The exam-relevant skill is recognizing which principle most directly addresses the problem described, not claiming the others are irrelevant.
During lifecycle study, explicitly track technical debt. A shortcut in discovery or design can reduce delivery time but increase later operation, support, or improvement cost. Version 5’s lifecycle emphasis is useful because it makes those delayed consequences visible. Record where a decision saves time today and where it creates future obligations.
During practice study, keep purpose statements concise. A practice exists to provide a capability or achieve an objective; it is not defined by one workflow, tool, or team. Create a one-sentence purpose and a concrete example for every practice in your notes. This helps prevent a common Foundation mistake: recognizing the activity but selecting the wrong practice because two practices collaborate on the same case.
During continual improvement, distinguish evidence from opinion. Baseline data, customer feedback, flow metrics, incident patterns, support demand, and outcome measures can justify priorities. Improvement becomes less effective when the loudest stakeholder automatically defines the next action. Version 5’s value-focused framing rewards teams that connect proposed change to measurable outcome.
During value-stream mapping, mark both processing time and waiting time. Many digital workflows spend more time waiting between teams, approvals, suppliers, or environments than they spend in active work. Those waits are often better improvement opportunities than automating already-fast technical steps. The map should expose where work stops and why.
Before final mocks, build a one-page Version 5 sheet containing the product/service framing, value dimensions, four dimensions, Value System components, lifecycle stages, guiding principles, practice role, continual improvement, and value-stream thinking. Recreate it from memory. Any section you cannot explain in plain language belongs back in focused review rather than prompting another full read-through.
During final review, compare product management and service management explicitly. A product roadmap may prioritize features, market fit, and technical evolution, while service management emphasizes reliable value realization, support, continuity, stakeholder experience, and operational governance. Version 5 connects these views instead of treating them as separate professions. Candidates should be able to explain how one product decision affects the associated service lifecycle.
Use a simple error log for mock questions. For each mistake, classify whether you confused value, a dimension, the Value System, a principle, lifecycle activity, practice purpose, continual improvement, or value-stream thinking. Review the category, not just the individual question. This prevents the same conceptual misunderstanding from appearing again under different wording.
Keep terminology version-specific in the final week. If an older ITIL 4 note uses language that conflicts with your Version 5 official material, annotate the difference rather than blending them. The bridge route exists because the update requires explicit learning. Consistency is especially important in a closed-book multiple-choice exam where small wording differences can distinguish the best answer.
Before the exam, explain the entire framework in two minutes: stakeholder demand enters a value system, teams manage digital products and services across a lifecycle, all four dimensions are considered, principles guide choices, practices provide capability, governance directs, value streams show flow, and continual improvement changes the system based on evidence. If that explanation is coherent, the study sequence has done its job.
Keep the last evening light: review your Version 5 map, error log, and a few representative cases rather than opening another resource. A concise mental model is more useful than last-minute volume in a closed-book Foundation exam.
Within the broader ITIL certification scheme, Foundation provides shared language. You are ready when you can use that language to explain a real digital product or service without turning the framework into a rigid process checklist.