ITILFND V5: Study Plan: What to Practice

ITIL Foundation Version 5 is a 40-question, 60-minute, closed-book exam with a 65% passing mark. The ITILFND V5 exam covers digital product and service management, value co-creation, the four dimensions, the ITIL Value System, guiding principles, lifecycle thinking, management practices, continual improvement, and value-stream management.

A useful study plan should make those elements work together. Instead of memorizing one chapter at a time, choose one digital product or service and repeatedly apply the framework to it. This makes the terminology easier to retain and prepares you for questions that ask what a concept means in practice.

Days 1–2: learn the product, service, and value model

Start with the relationship among products, services, service offerings, utility, warranty, outcomes, costs, risks, experience, and value. Explain the concepts using one service you know well.

Then write what the provider contributes and what the consumer contributes to value co-creation. If your explanation makes value something the provider “delivers” unilaterally, revisit the model.

Add one deliberately poor service example and explain why it fails to create value even though the technical utility is present. Perhaps the service works but is unreliable, difficult to access, too expensive, or creates unacceptable risk.

This helps separate utility from warranty and value from feature count. Foundation questions are much easier when you can explain why an outcome matters to the consumer rather than repeating a definition.

Days 3–4: master the four dimensions

Create a four-column worksheet for Organizations and People, Information and Technology, Partners and Suppliers, and Value Streams and Processes. For your chosen service, list dependencies and risks in each column.

Change one assumption—outsourcing a component, adopting AI, moving to cloud, or reorganizing a team—and update the worksheet. This shows how a single strategic decision can affect several dimensions at once.

Add an AI-enabled feature to the service and reassess all four dimensions. People may need new skills, information quality may become more important, suppliers may provide models or platforms, and the value stream may need human review or new controls.

This exercise matches Version 5’s modern digital context and prevents AI from being treated as only a technology choice.

Days 5–6: draw the ITIL Value System from memory

The Value System connects guiding principles, governance, value-chain activities, practices, and continual improvement. Reconstruct it without notes until the relationships are comfortable.

Do not stop at the diagram. For each component, explain what would go wrong if it were absent. This turns memory into understanding and prepares you for distractors that use correct terminology in the wrong role.

Connect governance to the Value System explicitly. Ask who sets direction, evaluates performance, and ensures the organization remains aligned with strategy while value-chain activities and practices perform day-to-day work.

Then place continual improvement around the system rather than at the end. Improvement can target governance, practices, products, processes, suppliers, experience, or technology at any point.

Days 7–8: apply the guiding principles to one decision

Take a service problem such as slow onboarding or repeated incidents and apply each guiding principle. What does focus on value change? What existing data can you start from? How could you progress iteratively? Which stakeholders need visibility?

The same problem should produce different useful actions under different principles. That is the point: the principles guide behavior; they are not a checklist where only one principle can be correct.

Write one deliberately bad application of each principle and explain why it is wrong. For example, ‘start where you are’ does not mean never change anything, and ‘keep it simple and practical’ does not mean remove controls that protect value.

Understanding the limits of a principle makes distractors easier to identify because exam choices often use correct phrases in a way that does not fit the situation.

Days 9–10: follow the product and service lifecycle

Map your service from discovery through design, delivery, operation, support, and improvement. Identify where requirements, experience, risk, technical debt, supplier dependencies, and measurement appear.

Version 5 emphasizes lifecycle thinking because digital products evolve continuously. Practice identifying which lifecycle activity should own the next decision instead of throwing every problem at operations.

Days 11–13: learn practices through scenarios

Study important practices by their purpose and contribution to value. Use incidents, recurring problems, changes, service requests, supplier issues, service-level expectations, knowledge, monitoring, and other common situations.

The ITILFND V4 exam remains useful historical context because many practice concepts continue across the transition. Use Version 5 official material to confirm current terminology and emphasis rather than studying V4 as the active syllabus.

Use paired scenarios to distinguish related practices. An incident may need rapid restoration while problem management investigates recurrence. A change may need enablement and risk assessment while deployment management coordinates release into the environment.

The exam becomes easier when you can explain the purpose of each practice and why another practice participates without owning the same outcome.

Days 14–15: practice continual improvement

Use the improvement model on a measurable problem. Define the vision, current state, target state, path, actions, measurements, and feedback. Avoid vague goals such as “improve service quality.”

Select a metric that reflects the outcome rather than only team activity. Faster ticket closure may be meaningless if the same incidents return; a useful measure might include restoration time, recurrence, user experience, or business interruption.

Include a baseline measure before changing the process. Without a current-state metric, the team cannot show whether the improvement worked or whether variation simply made the result look better.

Keep improvement backlog items small enough to test. Large transformation goals should be broken into measurable changes that produce feedback and can be adjusted before the organization invests heavily.

Days 16–17: map a value stream

Choose a request such as employee onboarding or production incident resolution. Draw each step, owner, information handoff, wait state, approval, and rework loop.

Then identify where improvement creates end-to-end value. Removing ten minutes from one task does not matter if the request waits two days for an approval elsewhere. Value-stream thinking is about flow across the system.

Calculate waiting time separately from working time in the value stream. A five-minute task surrounded by two days of queueing is not improved meaningfully by making the task four minutes.

Look for rework and information loss at handoffs. Many service problems come from incomplete context moving between teams rather than from the technical complexity of the task itself.

Days 18–19: compare Version 5 with your older ITIL knowledge

If you already know ITIL 4, list what feels familiar and what Version 5 emphasizes differently: digital products and services, lifecycle framing, modern AI-enabled environments, stronger product thinking, and updated terminology or structure.

The internal article on ITIL Foundation Version 4 can support the comparison. PeopleCert also offers a formal Foundation Bridge for existing ITIL 4 Foundation holders who need only the Version 5 changes.

If you do not know ITIL 4 already, skip the historical comparison and spend the time on current Version 5 material. The transition matters only when prior knowledge can accelerate preparation; it should not create an extra syllabus for new candidates.

If you do know ITIL 4, focus on changed framing and emphasis rather than restudying every familiar practice from the beginning.

Days 20–21: switch from notes to timed decisions.

Complete official-style practice questions under time, then explain every wrong answer in terms of the framework. Was the concept wrong, the lifecycle stage wrong, the practice wrong, or the answer simply less aligned with value?

The ITIL Foundation Version 5 certification should feel coherent by the final days. Use the role and syllabus to check whether your understanding connects the framework rather than just recalling terms.

The ITIL certification inventory is useful for navigation. Exam readiness comes from applying the framework to practical digital product and service decisions without relying on the book.

Aim to finish practice sets with time left to review uncertain questions. Mark the few items where two answers remain plausible and revisit them after completing the rest instead of spending several minutes on one term.

After the practice session, categorize mistakes by concept, application, or reading error. A definition mistake needs revision; a scenario mistake needs more applied practice; a reading mistake may need slower attention to words such as best, first, most appropriate, or primary.

Finish with one blank-page exercise: write the four dimensions, Value System components, guiding principles, lifecycle, improvement model, and five practices you understand best. Any part you cannot place or explain becomes the final review target.

Do one final scenario without using ITIL terminology at first. Describe the business problem, desired outcome, stakeholders, flow, and evidence in plain language; then map the ITIL concepts onto it. If the framework clarifies the problem instead of replacing it with jargon, you are using Version 5 the way it is intended.

Finish with current PeopleCert sample materials rather than older Version 4 question banks.

Use the framework, then trust your preparation.

A strong candidate can explain the framework clearly without turning every workplace problem into a wall of ITIL terminology.

• Category: All Certifications Certifications