Practicing the value system, governance and continual improvement

The ITIL value system is the largest area of the Version 5 syllabus, worth about 40 % of the exam, or sixteen questions. It includes the guiding principles (lesson 4), the value chain and value streams (lesson 7) and the practices (lessons 8 and 9). This lesson covers the rest of the system: what it is, its inputs and outputs, its components, governance and the continual improvement model. In ITIL 4 the same content is called the service value system; the components and logic are the same.

What the value system is for

The value system describes how all the components and activities of an organization work together to enable value creation. Its input is opportunity and demand; its output is value. Opportunity represents options or possibilities to add value for stakeholders or otherwise improve the organization. Demand is the need or desire for products and services among internal and external consumers. Opportunities and demand do not always become work: the organization decides which to pursue.

The purpose of the value system is to ensure that the organization continually co-creates value with all stakeholders through the use and management of products and services. ITIL also uses the value system to explain why silos are harmful. When teams work in isolation, information and resources do not flow, and value suffers. The value system is a model for breaking silos down by connecting everything to the flow from demand to value.

The five components

The value system has five components. Memorize them exactly: guiding principles, governance, the value chain, practices and continual improvement. In ITIL 4 the third component is called the service value chain. A favorite list question offers these components mixed with things that are not components, such as service level agreements, the service desk, configuration items or the four dimensions.

Two traps recur. First, the four dimensions are not a component of the value system; they apply to it. Second, a single practice is not a component; the practices as a whole are. If a question lists 'the service desk' or 'incident management' as a possible component, treat it as wrong unless the option says 'practices'.

Governance

Governance is the means by which an organization is directed and controlled. In ITIL, the governing body, such as a board of directors or an executive group, is accountable for the organization's compliance with policies and external regulations. Governance activities are often summarized by three verbs: evaluate, direct and monitor. The governing body evaluates the organization, its strategy and its portfolios; directs by assigning responsibility and setting policies; and monitors performance against those policies and directions.

ITIL stresses that governance applies across the whole value system and must align with the guiding principles and the organization's objectives. Governance is also distinct from management. Governance sets direction and oversight; management plans, builds, runs and monitors activities within that direction. A question might describe a board approving a policy on AI use and ask which component this belongs to: governance.

Continual improvement as a component

Continual improvement takes place in all areas of the organization and at all levels, from strategic to operational. ITIL 4 describes it in three places: as a component of the value system, as one of the activities of the value chain (improve), and as a practice (the continual improvement practice). Version 5 guides describe the improve activity as moving up into the continual improvement component, so improvement is still everywhere, but it is no longer listed as a separate value chain activity. Questions on the ITIL 4 exam sometimes ask where continual improvement appears; there the best answer mentions all three.

As a component, continual improvement is supported by a model that guides improvement initiatives. The model has seven steps, each phrased as a question or instruction. Learning these steps in order is one of the most reliable ways to collect marks.

The continual improvement model

Questions on the model usually test order ('Which step comes after where do we want to be?'), the content of a step ('In which step is a baseline assessment performed?') or the step a scenario describes. The commonest mistake is to place the baseline in step 3 instead of step 2. Remember: step 2 describes the current state; step 3 describes the target. Another trap is step 1: the vision step links to the organization's vision, not to the vision of a single team.

The model also connects to the guiding principles. Step 2 applies start where you are. Steps 4 and 5 often apply progress iteratively with feedback. Step 1 applies focus on value. If a question asks which principle is most relevant to a step, these pairings help.

The continual improvement register

ITIL recommends recording improvement ideas in a continual improvement register (CIR), a database or structured document that tracks and manages improvement ideas from identification to final action. The register lets the organization prioritize ideas, see who owns them and track progress. A missing word question might describe 'a database or structured document used to track and manage improvement ideas' and ask for its name.

ITIL also stresses that continual improvement is everyone's responsibility. Some organizations have a dedicated team that coordinates improvement and coaches others, but the work itself is spread across all teams. A distractor such as 'continual improvement is the responsibility of a dedicated improvement team only' uses extreme wording and should be rejected.

# Order drill for the continual improvement model, plus a self-check on step contents
model = [
    "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?",
    "How do we keep the momentum going?",
]
questions = {
    "A baseline assessment of current performance is made": 2,
    "Measurable targets are agreed": 3,
    "Results are compared with the targets": 6,
    "Success is communicated and the change embedded": 7,
    "The initiative is linked to the organization's objectives": 1,
}
for activity, step in questions.items():
    print(f"Step {step}: {model[step - 1]:<36} <- {activity}")
print("Step after 'Where do we want to be?':", model[model.index("Where do we want to be?") + 1])

Step 2: Where are we now?                    <- A baseline assessment of current performance is made
Step 3: Where do we want to be?              <- Measurable targets are agreed
Step 6: Did we get there?                    <- Results are compared with the targets
Step 7: How do we keep the momentum going?   <- Success is communicated and the change embedded
Step 1: What is the vision?                  <- The initiative is linked to the organization's objectives
Step after 'Where do we want to be?': How do we get there?

Practice set

Common question patterns for the value system

Value system questions fall into a handful of patterns. Recall questions ask for the components, the inputs or the output. Missing word questions give the definition of governance, opportunity, demand or the value system itself. Scenario questions describe a board, a policy or an improvement initiative and ask which component or which step of the continual improvement model is involved. Order questions ask which continual improvement step comes before or after another.

For each pattern, the same small set of facts decides the answer: five components, opportunity and demand in, value out, evaluate, direct and monitor for governance, and seven ordered steps for continual improvement. Kofi made a single index card with exactly these facts and read it aloud before every study session for two weeks. It sounds simple, but it lifted his value system accuracy in mock exams from about 60 % to about 80 %, because so many questions turned on one of these facts.

One more pattern is worth knowing. Some questions ask why the value system matters, and the expected answer is about integration and flexibility: the value system helps the organization work as a whole, avoid silos and respond to changing demand. Options that describe the value system as a rigid process or a reporting structure are distractors. Remember that ITIL describes it as flexible, adaptable to many working methods and organizations of any size.