4.4 Governance & the Continual Improvement Model

Governance and Continual Improvement: Direction and Adaptation

Two components of the ITIL Value System keep the whole system pointed in the right direction and continuously improving: governance and continual improvement. Both are reliable exam topics.

What governance is

Governance is the means by which an organization is directed and controlled. In the Value System its purpose is to ensure that products, services, and behavior stay aligned with the organization's objectives, policies, risk appetite, and stakeholder needs. Governance is usually described through three activities, often remembered as EDM:

The local exam wording sometimes phrases this as direct, monitor, and evaluate, but the three verbs are the same. The key idea is that governance is continuous and cyclical: it evaluates, then directs, then monitors, and feeds monitoring back into the next evaluation.

Governance versus management

A classic exam distinction is governance versus management. Governance sets direction and oversight, deciding what the organization should achieve and within what constraints. Management plans, designs, builds, operates, supports, and improves products and services within that direction, deciding how to get there. Confusing the two causes real damage: over-directed teams with no room to execute, or well-run teams with no clear direction. Two nuances matter. First, Agile ways of working still need governance, appropriate to context, governance is not optional just because a team is fast.

Second, effective governance delegates decision rights; it does not require every decision to be escalated to the board. Governance clarifies accountability rather than removing it.

The continual improvement model

Continual improvement is both a component of the Value System and a management practice. To make improvement repeatable, ITIL provides the continual improvement model, a seven-step approach that applies to any scope, a service, a practice, a team, or the whole organization.

Several points are heavily tested. Vision comes first because without a clear vision, improvement has no direction and no way to judge whether a change is actually an improvement; the vision aligns the work to organizational strategy and value. Where are we now? establishes a factual baseline through direct measurement, echoing the guiding principle start where you are; skipping it makes later results impossible to evaluate. Where do we want to be? defines the measurable target so the gap can be sized, and How do we get there? plans the route that Take action then carries out.

The final two steps are distinct and both required: Did we get there? validates outcomes against targets (whether the result was positive, partial, or negative), while How do we keep the momentum going? embeds successful changes, communicates learning, and identifies the next improvement. Crucially, the model is iterative, step 7 loops back to step 1 as the vision and context evolve, so continual improvement never truly finishes.

Worked example

A support team wants to cut slow ticket resolution. Vision: effortless, trusted support aligned to the company's customer-first strategy. Where are we now? average resolution is 3 days; first-contact resolution is 42%. Where do we want to be? resolution under 1 day and first-contact resolution above 65% within two quarters. How do we get there? add a knowledge base, triage automation, and training. Take action: deliver in small increments. Did we get there? measure against the targets. Keep momentum: standardize what worked and pick the next bottleneck. Each step is concrete because the vision anchored it.

How CI links to the guiding principles

The continual improvement model is where the guiding principles become action. Focus on value shapes the vision and targets; start where you are drives the honest baseline; progress iteratively with feedback governs how actions are delivered and checked; and keep it simple and practical keeps the improvement from collapsing under its own process. In fact, ITIL explicitly recommends applying the guiding principles to every step of the model.

That linkage, principles guiding the improvement steps, is a common exam theme, so remember that continual improvement is not a standalone ritual but the engine that keeps the entire Value System adapting.

Metrics, CSFs, and governance oversight

Governance and continual improvement both depend on measurement, which is why Version 5 lists metrics and critical success factors (CSFs) among the Value System elements. A CSF is a condition that must be true for success (for example, incidents resolved within agreed times), while a metric is a measured value used to track progress toward it (for example, average resolution time of 4.2 hours). Governance uses these measures in its monitor activity to check that management is delivering the agreed direction, and continual improvement uses them at Where are we now? and Did we get there?.

Confusing a CSF (the what-must-go-well) with a metric (the measurement) is a frequent exam trap, so keep the two roles distinct.