5.4 The Continual Improvement Model

Why a Model for Improvement

Continual improvement is one of the five components of the SVS and is meant to be everyone's responsibility. To make it repeatable rather than ad hoc, ITIL 4 provides the continual improvement model — a high-level, structured approach that can be applied to any improvement effort, from a small process tweak to a large transformation. The model keeps improvement aligned to the organization's vision and to a clear, measurable understanding of value.

The model is iterative: it is not run once and finished. Each pass produces a result, and the final step deliberately sets up the next iteration. It also embodies several guiding principles, especially Start where you are (you must understand the current state before changing it) and Progress iteratively with feedback (improve in small, measurable steps).

The Seven Steps in Order

1. What is the vision? — Define the overall vision and objectives. Each improvement must support the organization's goals and explain how it links to creating value. Without a shared vision, improvements pull in different directions.
2. Where are we now? — Assess and baseline the current state with objective measurements. You cannot tell whether you have improved if you never measured where you started, so this step captures the as-is position honestly and factually.
3. Where do we want to be? — Define the target state — the measurable objectives for this iteration. Targets close the gap between the current baseline and the vision, and they must be specific so success can be judged.
4. How do we get there? — Create a plan or roadmap of actions to move from the current state to the target. There may be more than one viable route; this step chooses the approach for the improvement.
5. Take action — Execute the plan. This is where the improvement actually happens — implementing changes, which may use experimentation, an agile approach, or a more traditional structured project, as appropriate.
6. Did we get there? — Check the results against the targets defined earlier, using measurement. Compare the new state to the baseline from step 2 to confirm whether the intended outcome was actually achieved; if not, decide what further action is needed.
7. How do we keep the momentum going? — If the improvement succeeded, reinforce and embed it (marketing the success, sharing knowledge) so the gains stick. Then begin the next iteration. This step prevents organizations from sliding back to old behaviours.

Baselines and Measurement: The Backbone of the Model

Two steps form the measurement backbone of the model, and the exam often pairs them. "Where are we now?" establishes the baseline — the agreed starting measurement of the current state. "Did we get there?" uses measurement again to check the achieved state against the targets, comparing it directly to that baseline. Skipping the baseline makes the later check meaningless: with no starting point, you cannot prove improvement. This is why ITIL stresses honest, objective current-state assessment over optimistic assumptions.

How the Model Ties into the SVS

The continual improvement model is not a standalone tool — it threads through the whole service value system in two important ways:

In short, continual improvement appears at three levels of ITIL 4: as an SVS component, as a practice, and as a value-chain activity — and the continual improvement model is the common seven-step method that connects all three. Mastering the order and meaning of the seven steps, and the role of baselines and measurement, is reliably worth marks on the Foundation exam.

Common Traps and Exam Tips

A few distinctions are tested repeatedly:

• "Where do we want to be?" vs "How do we get there?": The first defines the target state (the destination); the second creates the plan or roadmap to reach it (the route). Candidates often swap these.
• "Did we get there?" is a checkpoint, not the end: It verifies results against the targets. If the answer is no, the organization revisits earlier steps rather than declaring victory.
• "How do we keep the momentum going?" is about embedding success: It reinforces the gains — sharing knowledge, marketing the win — so the organization does not regress, and it launches the next iteration.

Remember that the model is deliberately iterative: each pass should be a relatively small, manageable improvement with feedback, in line with Progress iteratively with feedback. Large initiatives are broken into iterations, each cycling through the seven steps. Finally, do not confuse the seven-step model with anything else that has seven items; the steps always begin with What is the vision? and end with How do we keep the momentum going?, with the baseline (Where are we now?) and the verification (Did we get there?) as the measurement anchors in between.