SkarpChapter 7 of 14
Continual Improvement: Keeping Services Moving Forward
Shift from one-off projects to a culture of ongoing enhancement, using the ITIL continual improvement model to drive better services over time.
1. Why Continual Improvement Matters in ITIL 4
Continual Improvement in ITIL 4
In ITIL 4, continual improvement is a core practice that runs through the whole Service Value System. It is the habit of regularly asking how we can do better, then acting on it, not a one-off project.
Purpose (Simple Wording)
The purpose of continual improvement is to keep services and practices aligned with changing business needs by identifying, prioritizing, and acting on improvement opportunities.
Link to Guiding Principles
Guiding principles such as "Focus on value" and "Progress iteratively with feedback" shape how improvements are chosen and carried out. They give direction to continual improvement work.
Link to the Service Value Chain
The Service Value Chain has an "Improve" activity, but continual improvement also appears inside every other activity: Plan, Engage, Design & Transition, Obtain/Build, and Deliver & Support.
Mindset Shift
Instead of thinking "We improved the service last year", ITIL 4 expects organizations to ask: "How are we improving this service right now, and what is next?" This continuous mindset is often tested in exams.
2. Continual Improvement vs Incidents vs Projects
Three Related but Different Ideas
To avoid exam confusion, separate incident management, project delivery, and continual improvement. They all change services, but in different ways, with different goals and timeframes.
Incident Management
Incident management restores normal service quickly after an unplanned interruption. It is short term and reactive, such as restarting a crashed database or re-routing tickets.
Project Delivery
Projects deliver a defined output by a certain date and budget. They have a clear start and end, such as implementing a new HR system or migrating to a new data center.
Continual Improvement
Continual improvement gradually enhances value, performance, and experience. It is ongoing with no fixed end date, such as reducing resolution times or improving a self-service portal.
Exam Clues
Fixing a specific failure now points to incident management. Delivering a new system with a set end date points to a project. Ongoing small, repeated enhancements point to continual improvement.
3. The ITIL Continual Improvement Model: Overview
Model Logic
The ITIL continual improvement model follows a simple logic: understand where you are and where you want to be, then move in small, controlled steps while checking your results.
Seven Steps (List)
The model is usually described in seven steps: 1) What is the vision? 2) Where are we now? 3) Where do we want to be? 4) How do we get there? 5) Take action. 6) Did we get there? 7) How do we keep the momentum going?
Personal Analogy
Improving exam scores uses the same pattern: define your vision, check current grades, set a target, plan study methods, study, check results, then adjust and continue improving.
Scope of Application
In ITIL 4, this model can be applied to services, processes, teams, tools, or even the whole Service Value System. It is a reusable thinking pattern for structured change.
4. Walking Through the Model Step by Step
Scenario Setup
Example: A university IT help desk gets many complaints that email issues take too long to resolve. We will apply the seven-step continual improvement model to this situation.
Steps 1–3: Vision and Targets
Vision: reliable digital communication for students and staff. Now: 16-hour average resolution, 3.2/5 satisfaction. Target: 8-hour resolution and 4.2/5 satisfaction.
Step 4: How Do We Get There?
Improvement ideas: standard troubleshooting scripts, short training for first-line agents, and a self-service password reset. Choose options based on cost, risk, and impact.
Steps 5–6: Action and Check
Take action: implement self-service reset, run 2-hour training, update knowledge articles. Check results: after one month, resolution time is 9 hours and satisfaction is 4.0/5.
Step 7: Keep Momentum
Because targets are not fully met, plan another cycle. Consider chat support or refined scripts. Record these as new improvement opportunities instead of stopping after one round.
5. The Continual Improvement Register (CIR) and Roles
What Is the CIR?
The Continual Improvement Register (CIR) is a single, central list of improvement ideas and initiatives. It helps an organization track and manage improvements in a structured way.
What the CIR Stores
Each CIR entry usually has a description, source, expected benefits, priority, risk, status (such as in progress or completed), and an owner responsible for that improvement.
Exam Clues for CIR
If a question mentions a central log or list of improvements, or tracking improvement ideas from many teams, it is pointing to the Continual Improvement Register.
Key Roles
Typical roles: a practice owner who defines the approach, a manager or lead who maintains the CIR, improvement owners for specific changes, and all staff as idea contributors.
Real-World Tools
In practice, organizations often implement the CIR using simple tools: a shared spreadsheet, a Kanban board, or records in a service management platform like Jira or ServiceNow.
6. Spot the Continual Improvement Activity
6. Spot the Continual Improvement Activity
Read each mini-scenario and decide whether it mainly shows incident management, project delivery, or continual improvement.
- The database server crashes at 10:00. The on-call engineer restarts it and restores service by 10:20.
- The organization plans a 9-month initiative to replace the legacy CRM system with a cloud-based platform.
- A team reviews monthly incident data and decides to create new knowledge articles to reduce repeat tickets.
Your task:
- Write down (mentally or on paper) which practice fits each scenario.
- Then check the answers below.
Answers (do not peek first):
- Incident management – unplanned interruption, quick restore.
- Project delivery – defined output, fixed timeframe.
- Continual improvement – data-driven change to reduce future incidents.
Notice how scenario 3 is not about fixing a single failure, and it is not a one-time big project. It is about ongoing enhancement based on feedback.
7. Quick Check: Purpose and Model
Test your understanding of the purpose of continual improvement and the logic of the model.
Which option best describes the role of the continual improvement practice in the ITIL 4 Service Value System?
- To restore normal service operation as quickly as possible after incidents occur.
- To deliver large-scale changes through time-limited projects with fixed scope and budget.
- To ensure services and practices are continually aligned with changing business needs by identifying and acting on improvement opportunities.
- To design and build new services from scratch based on detailed requirements.
Show Answer
Answer: C) To ensure services and practices are continually aligned with changing business needs by identifying and acting on improvement opportunities.
Continual improvement focuses on keeping services and practices aligned with changing business needs by regularly identifying, prioritizing, and implementing improvements. Restoring service quickly is incident management, time-limited large changes are projects, and designing new services is part of service design and transition.
8. Quiz: Applying the Continual Improvement Model
Apply the seven-step continual improvement model to a short scenario.
A support team has already defined its vision and measured its current performance. It has also set a target for where it wants to be. According to the continual improvement model, what should the team do NEXT?
- Start implementing random changes as quickly as possible.
- Plan how to get from the current state to the target state, selecting suitable improvement actions.
- Close the improvement initiative because the target is already defined.
- Update the service catalog to reflect the new target.
Show Answer
Answer: B) Plan how to get from the current state to the target state, selecting suitable improvement actions.
Once the vision is clear, the current state is known, and the target state is set, the next step in the continual improvement model is to decide "How do we get there?" This means planning and selecting appropriate improvement actions before executing them.
9. Flashcards: Key Terms Review
Flip these cards (mentally) to review the most important terms for exams and practice.
- Continual improvement (practice) – simple definition
- An ongoing organizational activity that identifies, prioritizes, and implements improvements to ensure services and practices stay aligned with changing business needs.
- Continual Improvement Register (CIR)
- A central log or list used to record and manage improvement opportunities and initiatives, including their priority, status, and ownership.
- Key question: What is the vision?
- First step of the continual improvement model; clarifies the high-level direction and desired value so improvements support the organization’s goals.
- Difference: Incident vs continual improvement
- Incident management restores normal service quickly after an unplanned interruption. Continual improvement focuses on preventing issues and enhancing value over time.
- Difference: Project vs continual improvement
- Projects are time-limited efforts with a defined output and end date. Continual improvement is an ongoing cycle of smaller changes that may never fully end.
- Step: Did we get there?
- A check in the continual improvement model where results are measured against the target state to see whether the improvement was successful.
10. Design a Tiny Improvement Cycle
10. Design a Tiny Improvement Cycle
Apply the continual improvement model to your own study or work.
Task (2–3 minutes):
- What is the vision?
- Example: "Be more consistent in submitting assignments on time."
- Where are you now?
- Example: "I submit 60% of assignments on time."
- Where do you want to be?
- Example: "Submit 95% on time this semester."
- How do you get there?
- Brainstorm 2–3 concrete actions (calendar reminders, study group, earlier drafts).
- Take action
- Choose one small action you can start this week.
- Did you get there?
- Decide how you will measure (e.g. track due dates vs submission dates).
- Keep momentum
- Plan when to review progress (e.g. in 4 weeks) and adjust.
You have just created a personal continual improvement cycle. The same logic is used in ITIL 4 for services and practices.
Key Terms
- Project
- A temporary organization created to deliver one or more outputs according to an agreed business case, with a defined start and end.
- Improvement owner
- The person responsible for planning, coordinating, and completing a specific improvement initiative recorded in the CIR.
- Guiding principles
- Recommendations in ITIL 4 that guide an organization in all circumstances, such as "Focus on value" and "Progress iteratively with feedback".
- Incident management
- The practice focused on minimizing the negative impact of incidents by restoring normal service operation as quickly as possible.
- Service Value Chain
- The core set of activities within the SVS (Plan, Improve, Engage, Design & Transition, Obtain/Build, Deliver & Support) that convert demand into value.
- Continual improvement
- An ongoing practice that identifies, prioritizes, and implements improvements to ensure services and practices stay aligned with changing business needs.
- Service Value System (SVS)
- The ITIL 4 framework that describes how all components and activities of an organization work together as a system to enable value creation.
- Continual Improvement Register (CIR)
- A central log or repository where improvement opportunities and initiatives are recorded, prioritized, tracked, and reviewed.