Continual Improvement

Overview

Continual improvement occurs across all organizational areas and levels, from strategic to operational. Everyone managing products and services should identify improvement opportunities. In the ITIL Value System, it applies to the entire value system, products, services, components, practices, and relationships.

Definition

Continual improvement is the practice of continually improving products, services, practices, or any element involved in the management of products and services.

What the ITIL VS Provides for Improvement

To support improvement at all levels, the ITIL VS includes:

The ITIL continual improvement model (structured approach)
The Continual improvement management practice for day-to-day improvement
Broader transformation guidance linked to the overall system

The model increases success likelihood, maintains focus on stakeholder value, and links effort to organizational vision. It supports iteration by breaking work into manageable pieces with incremental goals.

⚠️

Important: Steps are not always linear. You may revisit earlier steps. Use logic and common sense; scope and detail vary by topic.

The ITIL Continual Improvement Model

The Seven Steps

Step 1: What is the vision?

Link the initiative to organizational goals. Translate vision and objectives for the relevant unit or team. Ensure high-level direction is understood, stakeholders and roles are clear, expected value is agreed, and the next owner has authority to proceed.

Skipping this risks local optimization or low-visibility improvements.

Step 2: Where are we now?

Define the starting point (Point A). Use objective measurement where possible for a baseline; supplement with stakeholder stories when metrics are thin.

Skipping this leaves no baseline for later comparison.

Step 3: Where do we want to be?

Define the next target or desirable state (Point B): clear objectives with metrics, or less tangible cues. Use SMART objectives where possible. In uncertainty, define direction and criteria to assess experiments.

Skipping this blurs the destination.

Critical success factor (CSF): A necessary precondition for achieving intended results.

Key performance indicator (KPI): A metric used to evaluate success in meeting an objective.

Step 4: How do we get there?

Build a plan from vision plus current and target states. May be straightforward or experimental (hypotheses and tests). Often use iterations with checkpoints.

Skipping this leads to execution that flounders.

Step 5: Take action

Execute the plan: actions and experiments may be sequential or parallel. Agile-style iteration is common; you may return to steps 4 or even 3. Focus on measurement toward the vision, risk, and visibility.

Practices such as organizational change management, measurement and reporting, risk management, and continual improvement support this step. The result is a new current state.

Step 6: Are we getting there?

Compare the new state to agreed targets and the baseline. Check both progress (objectives achieved?) and value (objectives still relevant?). If results fall short, plan another iteration. If SMART targets were impossible earlier, assess whether things improved versus the old state and whether you need to revisit step 2 or 3.

Skipping validation loses lessons and false confidence.

Step 7: How do we keep the improvements relevant?

Improvements generate lessons; the portfolio of initiatives must stay relevant as context changes. Continuous learning may change, stop, or reprioritize work.

On success, use organizational change management and knowledge management to embed changes and avoid reversion. On failure, analyze transparently, document lessons, and avoid blame so future improvement keeps support.

Skipping this risks isolated initiatives and lost momentum.