ITIL Continual Improvement: The Improvement Model, Register and Retrospectives
Services do not stay good by themselves. Technology changes, users’ needs evolve and yesterday’s solution becomes tomorrow’s bottleneck. The continual improvement practice aligns the organisation’s practices and services with changing business needs through the ongoing identification and improvement of services, service components, practices or any element involved in the management of products and services. In ITIL 4 it is both a practice and a component of the service value system: everyone, at every level, is expected to contribute.
The Continual Improvement Model
ITIL provides a model of seven steps to structure any improvement effort, from a single process tweak to a large programme:
| Step | Question | What you do |
|---|---|---|
| 1 | What is the vision? | Link the improvement to organisational goals |
| 2 | Where are we now? | Assess the current state with data and observation |
| 3 | Where do we want to be? | Set measurable targets |
| 4 | How do we get there? | Plan steps, options and owners |
| 5 | Take action | Do the work, in small iterations |
| 6 | Did we get there? | Check results against the targets |
| 7 | How do we keep the momentum going? | Embed what worked and choose the next improvement |
Steps 2 and 6 are often skipped. Without a baseline you cannot show improvement, and without a check you cannot know whether the effort worked.
The Improvement Register
A continual improvement register is a simple, visible list of ideas and actions. Each entry records:
- A short description and the problem it addresses.
- Who raised it and who owns it.
- Expected benefit and rough effort.
- Priority and status (idea, approved, in progress, done, rejected).
- The outcome measured after completion.
Sources of ideas include incident and problem reviews, user feedback, staff suggestions, audit findings, supplier reports and retrospectives. Keep the register short and active; a list of three hundred items that no one reads is a graveyard.
Prioritising Improvements
You cannot do everything. A simple scoring approach rates each idea on benefit, effort and risk, and favours those with high benefit and low effort first (“quick wins”) while planning larger items. Link priorities to the organisation’s strategy: an improvement that helps a strategic goal outranks one that is merely interesting.
| Idea | Benefit | Effort | Decision |
|---|---|---|---|
| Add password reset to self-service portal | High (30% of contacts) | Medium | Do now |
| Redesign ticket categories | Medium | Low | Do now |
| Replace the ticketing tool | High | High | Plan as a project |
| Change colour of portal banner | Low | Low | Defer |
Retrospectives and Reviews
A retrospective is a short meeting after an incident, release, project or period of work in which the team discusses what went well, what did not and what to change. Keep it blameless and end with a small number of agreed actions that enter the register. Post-incident reviews (see Incident Management) and lessons-learned sessions are forms of the same idea.
Everyone Contributes
ITIL 4 stresses that improvement is not only the task of a quality team. Front-line staff see the friction first. Leaders support improvement by giving time, listening to ideas and showing that suggestions lead to action. Recognising improvement publicly encourages more of it.
Worked Example
A service desk notices that password resets are 30% of all contacts. Vision: let users solve simple issues themselves. Where are we now? 900 resets a month at about eight minutes each. Target: cut manual resets to 300 within three months. Plan: enable self-service reset with multi-factor verification and add a portal link and knowledge article. Action: pilot with one department, then roll out. Check: after three months manual resets are 280 a month and user satisfaction has risen. Momentum: the team adds “account unlock” to the register as the next candidate.
Measuring Improvement
- Baseline and result for the targeted measure (time, volume, cost, satisfaction).
- Number of improvements completed per quarter.
- Share of completed improvements that met their target.
- Staff participation, such as ideas raised per team.
Common Mistakes
- Starting improvements without a baseline measure.
- Running improvement as an occasional project instead of a habit.
- Letting the register grow without prioritisation or pruning.
- Collecting ideas but never reporting what was done.
- Continual improvement is both a practice and a component of the service value system, with everyone contributing.
- The seven-step model starts with vision and baseline, and ends with checking results and keeping momentum.
- Use an improvement register and prioritise by benefit, effort and strategic fit.
- Run blameless retrospectives and measure whether each improvement worked.