Overview
This category explains how an organization turns opportunity and demand into value using the ITIL Value System. The syllabus splits it into six topics: the components of the value system, the seven guiding principles, governance, the value chain, management practices, and the continual improvement model. The value chain topic also carries a long list of terms to define, from incident, event and release to observability, site reliability engineering, problem, known error and operating model.
Version 5 renames the ITIL 4 Service Value System as the ITIL Value System. The seven guiding principles are unchanged, and the 34 management practices keep their names, but the practices are regrouped into two families: general management practices and product and service management practices, replacing the three ITIL 4 groups. The continual improvement model still has seven steps, and the value chain now enables the eight-activity Product and Service Lifecycle rather than standing as six separate activities.
How it's tested
Expect the widest mix of question styles here. Principles are tested with short scenarios, value chain terms with definition matching and problem versus known error distinctions, practices with recall of the two families and of metrics, and the improvement model with step ordering or matching an activity to a step.
-
Which principle applies?
A team's behaviour or plan is described and you pick the guiding principle it applies or ignores, such as start where you are before replacing a working tool.
-
Define the value chain term
A definition is paraphrased and you choose among incident, event, problem, known error, release, observability or service request.
-
Improvement step
An activity such as baselining current performance is described and you identify its step in the continual improvement model.
A stem says a team plans to replace its entire monitoring setup, even though the current tool works for most needs, and asks which principle they should apply first. Optimize and automate tempts because monitoring is technical, but the issue is discarding what already works. Start where you are says to assess existing services and reuse what is useful before building anew, so it is the best answer.
Syllabus topics 6
Official syllabus topics from the PeopleCert outline, in outline order.
4.1 Components of the ITIL Value SystemThe five components of the value system and its purpose.
- What it means
- The ITIL Value System describes how the components and activities of an organization work together to create value through products and services. Its five components are the guiding principles, governance, the value chain, management practices, and continual improvement. Opportunity and demand enter the system and value comes out.
- What to understand
- The purpose of the value system is to make every part of the organization work together rather than in silos, so value creation is coordinated and flexible. Version 5 uses the name ITIL Value System where ITIL 4 said Service Value System, reflecting the wider product and service scope. Know the five components by name, and do not confuse them with the four dimensions or the eight lifecycle activities.
- How it shows up
- Recall of the five components, often with a dimension or lifecycle activity planted as a distractor.
- Common confusion
- Listing value streams or the four dimensions as components of the value system.
4.2 ITIL Guiding PrinciplesThe seven guiding principles and how they interact.
- What it means
- Guiding principles are recommendations that guide an organization in all circumstances, whatever its goals, strategy or structure. The seven are: focus on value; start where you are; progress iteratively with feedback; collaborate and promote visibility; think and work holistically; keep it simple and practical; and optimize and automate.
- What to understand
- Know what each principle asks for. Focus on value ties every activity to value for stakeholders. Start where you are reuses what already works after measuring it directly. Progress iteratively with feedback breaks work into small, manageable pieces. Collaborate and promote visibility involves the right people and makes work transparent. Think and work holistically considers the whole system and all four dimensions. Keep it simple and practical removes anything that adds no value. Optimize and automate improves work before automating it, and keeps humans involved where judgement matters. The principles interact and should be applied together, not one at a time.
- How it shows up
- A described behaviour is matched to a principle, or you choose the principle being ignored.
- Common confusion
- Automating a broken process under optimize and automate; the principle says to optimize first.
4.3 GovernanceWhat governance is, how it enables the organization, and what governance activities involve.
- What it means
- Governance is the means by which an organization is directed and controlled. In the value system it sets direction, approves policies and holds management to account. The syllabus asks you to define governance and to explain that it is enabling rather than simply restrictive.
- What to understand
- Governance activities are commonly described as evaluating the organization's position and options, directing through strategy and policy, and monitoring performance against that direction. Good governance gives teams clear boundaries so they can act with confidence and speed, which is why Version 5 stresses its enabling role. In Version 5, governance also absorbs much of the planning work that ITIL 4 placed in a separate plan value chain activity.
- How it shows up
- A definition question, or a statement asking which describes the role of governance in the value system.
- Common confusion
- Equating governance with management; governance directs and oversees, management plans and runs.
4.4 Value chainValue chain terms and success metrics, and how the value chain supports purpose and operating model.
- What it means
- The value chain is the set of interconnected activities that enable the lifecycle of products and services. The syllabus asks you to define a long list of terms used in value chain work: product specification and product prototype, incident and event, release and test, continuous integration, continuous delivery and continuous deployment, reliability, site reliability engineering and observability, service request, disaster, problem, error and known error, and operating model.
- What to understand
- Anchor definitions: an incident is an unplanned interruption or reduction in quality of a service; an event is any change of state significant for management; a problem is a cause or potential cause of incidents; a known error is a problem that has been analysed but not resolved; a service request is a user request for an action agreed as normal service delivery; a release is a version made available for use. Continuous delivery keeps changes ready to deploy, while continuous deployment releases them automatically. Observability is the ability to understand internal state from external outputs. Also understand success metrics for value chain activities and how the operating model and practices support the organization's purpose.
- How it shows up
- Definition matching, especially problem versus error versus known error, and continuous delivery versus continuous deployment.
- Common confusion
- Calling a user's request for a new laptop an incident; nothing is broken, so it is a service request.
4.5 Management practicesWhat a practice is, the two practice families, practice guides, and metrics and critical success factors.
- What it means
- A management practice is a set of organizational resources designed for performing work or accomplishing an objective. Version 5 keeps the 34 ITIL practices but groups them into general management practices and product and service management practices. The ITIL 4 technical management group no longer exists, and practices such as deployment management and infrastructure and platform management move into the product and service family.
- What to understand
- Practices contribute to value chain activities; no single practice owns one activity. The ITIL Practice Guides describe each practice in a common structure that helps organizations assess and improve it. Recall the definitions of a metric, a measurement used to track performance, and a critical success factor, a condition necessary for a practice or organization to succeed. Know how practices fit in the value system and why the common structure is useful.
- How it shows up
- Recall of the two practice families, or a statement about the role of practices in the value system.
- Common confusion
- Citing the three ITIL 4 groups, including technical management practices, as the Version 5 grouping.
4.6 ITIL Continual Improvement ModelThe steps of the continual improvement model and its role in the organization.
- What it means
- Continual improvement is a component of the value system and operates at every level, from single practices to the whole organization. The Version 5 continual improvement model is a seven-step, question-led loop that moves from understanding the vision, through assessing the current state and defining a target, to planning, acting, checking results and sustaining momentum.
- What to understand
- In ITIL 4 wording the steps are: what is the vision; where are we now; where do we want to be; how do we get there; take action; did we get there; and how do we keep the momentum going. Version 5 keeps a seven-step structure with revised presentation, so learn the logic of each step as well as its label. Understand that improvement is everyone's responsibility and that the model can be used for small fixes and large transformations alike.
- How it shows up
- An improvement activity, such as setting a baseline, is matched to its step, or steps are put in order.
- Common confusion
- Placing baseline measurement in did we get there; baselining belongs to where are we now.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Five value system components
Guiding principles, governance, value chain, management practices, continual improvement.
- Remember
- Opportunity and demand go in, value comes out.
- Tested as
- Recall and odd-one-out questions.
- Trap
- Adding the four dimensions as a component.
-
Seven guiding principles
Focus on value; start where you are; progress iteratively with feedback; collaborate and promote visibility; think and work holistically; keep it simple and practical; optimize and automate.
- Remember
- Unchanged from ITIL 4; applied together.
- Tested as
- Nine criteria make this the largest single topic in the paper.
- Trap
- Treating them as a sequence to follow.
-
Governance
The means by which an organization is directed and controlled.
- Remember
- Enabling, not only restrictive.
- Tested as
- Definition and role questions.
- Trap
- Choosing a definition that describes day-to-day management.
-
Incident vs problem
An incident is an interruption or quality reduction; a problem is a cause or potential cause of incidents.
- Remember
- Fixing the incident does not remove the problem.
- Tested as
- Definition swaps between the two are common.
- Trap
- Calling a recurring outage a problem only once it has been fixed.
-
Error vs known error
An error is a flaw that can cause incidents; a known error is a problem that has been analysed but not resolved.
- Remember
- Known error status comes after analysis.
- Tested as
- The syllabus asks you to distinguish problem, error and known error.
- Trap
- Thinking a known error means the fix is deployed.
-
Service request
A user request for an action agreed as a normal part of service delivery.
- Remember
- Password resets and equipment requests are typical examples.
- Tested as
- Classify a described request as incident or service request.
- Trap
- Logging routine requests as incidents.
-
Continuous delivery vs deployment
Delivery keeps every change ready for release; deployment releases passing changes automatically.
- Remember
- Deployment removes the manual release decision.
- Tested as
- Definition matching among CI and CD terms.
- Trap
- Treating the two as synonyms.
-
Observability and SRE
Observability is understanding internal state from outputs; SRE applies software engineering to operations and reliability.
- Remember
- Both are new value chain recall terms in Version 5.
- Tested as
- Definition questions on modern operations terms.
- Trap
- Equating observability with basic monitoring alerts.
-
Two practice families
General management practices and product and service management practices.
- Remember
- The ITIL 4 technical group is gone; 34 practices remain.
- Tested as
- Recall of the grouping.
- Trap
- Answering with three groups.
-
Metric and CSF
A metric is a measurement; a critical success factor is a condition needed for success.
- Remember
- CSFs are tracked using metrics.
- Tested as
- Definition recall from the practices topic.
- Trap
- Swapping the two definitions.
-
Continual improvement model
A seven-step loop from vision to sustaining momentum.
- Remember
- Baselining happens at the current-state step.
- Tested as
- Step order and activity matching.
- Trap
- Measuring results before defining targets.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Problem, error and known error
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Problem | A cause or potential cause of one or more incidents | Focuses on underlying cause | Calling the visible outage a problem |
| Error | A flaw or vulnerability that may cause incidents | The defect itself | Assuming every error has caused an incident |
| Known error | A problem that has been analysed but not resolved | Cause understood, fix not yet applied | Assuming the fix is already deployed |
Incident, event and service request
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Incident | Unplanned interruption or reduction in quality | Something is broken or degraded | Logging a routine request as an incident |
| Event | A change of state significant for management | Most events need no action | Treating every event as an incident |
| Service request | A request for an agreed normal service action | Nothing is broken | Raising it as a change |
Practice grouping: ITIL 4 vs Version 5
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| ITIL 4 | General, service and technical management practices | Three groups | Using this list on the Version 5 exam |
| Version 5 | General management and product and service management practices | Two groups; technical practices absorbed | Assuming practices were renamed too |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Automate first
- What candidates pick
- Optimize and automate as a reason to automate a process immediately.
- Why it looks right
- Automation sounds like the modern answer.
- Why it's wrong
- The principle says to simplify and optimize before automating, otherwise waste is automated.
Clue to watch for The stem describes a messy or inconsistent process.
-
Start from scratch
- What candidates pick
- Replacing an existing service entirely to apply best practice.
- Why it looks right
- A clean start feels like progress.
- Why it's wrong
- Start where you are asks for direct observation and reuse of what works before discarding anything.
Clue to watch for The stem mentions parts that already work.
-
Known error equals fixed
- What candidates pick
- Known error to describe a problem whose fix has been deployed.
- Why it looks right
- The word known suggests the matter is closed.
- Why it's wrong
- A known error has been analysed but not resolved; once fixed it is no longer an open known error.
Clue to watch for Look for whether a resolution is in place.
-
Three practice groups
- What candidates pick
- General, service and technical management practices.
- Why it looks right
- This is the ITIL 4 grouping many sources still show.
- Why it's wrong
- Version 5 uses two families, general management and product and service management practices.
Clue to watch for The question references Version 5 or the ITIL Value System.
-
Governance as management
- What candidates pick
- Governance described as planning and running daily operations.
- Why it looks right
- Both are about control.
- Why it's wrong
- Governance directs and oversees through evaluate, direct and monitor; management plans and executes within that direction.
Clue to watch for Words like oversight, accountability or direction.
-
Delivery equals deployment
- What candidates pick
- Continuous delivery for automatic release to production.
- Why it looks right
- The terms differ by one word.
- Why it's wrong
- Continuous delivery keeps changes releasable; continuous deployment pushes them live automatically.
Clue to watch for Whether a human release decision remains.
Answer framework
Use this sequence to handle the wide range of question styles in the largest category.
- Identify the topic: component recall, guiding principle, governance, value chain term, practice structure or improvement model.
- For principle scenarios, ask what the team is doing wrong or right, then choose the principle that addresses that exact behaviour rather than a broadly sensible one.
- For value chain terms, apply the anchor test: broken now means incident, cause means problem, analysed but unfixed means known error, routine ask means service request.
- For practices and governance, use Version 5 structures only: two practice families, governance as evaluate, direct and monitor, and the five value system components.
- For improvement questions, place the activity in the seven-step loop by asking whether it defines vision, measures now, sets targets, plans, acts, checks or sustains.
Practice question
Want more like this? The ITIL 5 Foundation practice test has questions for every domain.
Checklist
0 of 14
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Give this category the largest block of your study time, around a third of the total. Begin with the guiding principles, because they produce the most scenario questions. For each principle write one sentence on what it asks and one example of a team ignoring it. Then quiz yourself with scenarios until you can name the principle without looking at the list.
Next, turn the value chain term list into flashcards. There are roughly twenty terms, and they reward simple repetition. Group them into families: development and release terms, operational terms, and problem terms. Spend extra time on the three-way split between problem, error and known error, which the syllabus calls out for explanation.
After that, learn the structures that changed in Version 5: the value system name, the two practice families, and how governance and continual improvement take on planning and improvement work. Finish with the seven improvement steps, practising both order and matching. Run timed sets of 16 questions from this category alone in the last week before the exam.
FAQ
How many questions come from The ITIL Value System?
The ITIL Value System is weighted at 40%, so about 16 of the 40 questions. It is the largest category on the Version 5 paper, and PeopleCert publishes the weighting as a percentage.
Have the guiding principles changed in Version 5?
No. The seven principles carry over from ITIL 4 unchanged, so existing knowledge applies. Expect them to be tested through short scenarios.
Why are incident and problem definitions in the value chain topic?
The Version 5 syllabus collects key operational and development terms under the value chain topic instead of under individual practices, and adds newer ones such as observability and site reliability engineering.
Do I need to know all 34 practices?
The syllabus asks for the practice definition, the two families, the role of practices, the Practice Guides structure, and metrics and critical success factors. It does not list individual practices for recall.
Is the continual improvement model the same as in ITIL 4?
It still has seven steps and the same logic from vision to momentum. Version 5 presents it somewhat differently, so check the wording in the official Version 5 book.
What happened to plan and improve?
They are no longer value chain activities. Governance covers direction and planning, and the continual improvement component and model cover improvement.
What is the operating model in this syllabus?
It describes how an organization is set up to deliver its purpose. The syllabus asks you to explain how value chain activities and practices support the purpose and operating model.
Other Enterprise Architecture & IT Governance certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 4 knowledge
Check that you can apply the seven guiding principles to scenarios, define the value chain terms precisely and order the continual improvement steps under exam timing.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the ITIL 5 Foundation AI tutor Get any concept explained your way