Is your IT team constantly firefighting but rarely getting ahead? Continual Improvement—the backbone of ITIL v4’s approach to evolving IT services—helps you shift from reactive to proactive. Instead of just keeping the lights on, it’s about asking: how can we do this better?
Whether it’s reducing ticket volumes, speeding up response times, or aligning more closely with business goals, Continual Improvement gives your organisation the tools and mindset to evolve continuously.
Contents
What Is Continual Improvement?
In ITIL v4, Continual Improvement is the structured, ongoing effort to make services, processes, and practices more effective, efficient, and aligned with business needs.
Improvements come in two main forms:
- Incremental: Small, steady changes (think: simplifying a helpdesk workflow).
- Breakthrough: Larger, transformative changes (e.g. adopting a new ITSM platform or switching from on-prem to cloud).
The key idea? Improvement isn’t something you do once and forget. It’s a repeatable cycle baked into the way your IT organisation works, ensuring services stay relevant and valuable as the business evolves.
ITIL doesn’t treat improvement as a bonus—it treats it as a core responsibility.
Why Continual Improvement Matters
Improvement isn’t just about tweaking things for the sake of it.
In ITIL v4, the purpose of Continual Improvement is to consistently align IT services with changing business needs—whether that means saving money, increasing reliability, or responding faster to customer demands.
What’s the Value?
Here’s what a well-run Continual Improvement practice can deliver:
Better Service Quality
Spot problems early. Streamline clunky processes. Catch things before they fail. Over time, your services become smoother, more reliable, and more user-friendly.
Happier Customers
By regularly acting on feedback and adjusting how services are delivered, you build trust—and loyalty. Customers notice when things work better.
Lower Costs
Improved processes often lead to reduced waste, fewer incidents, and better use of people’s time. That translates to real savings.
Strategic Alignment
Improvement isn’t random—it’s guided by business goals. So you’re not just fixing things, you’re improving what matters most.
Innovation Mindset
Done right, Continual Improvement fosters a culture where people feel safe to suggest better ways of working. It becomes normal to ask, how could we do this smarter?
Competitive Advantage
Organisations that improve continuously are more agile. They adapt faster and outperform slower-moving competitors.
Example
In my early days, my IT Helpdesk team used to manually assign all tickets. A small automation change and rationalisation of categories and options saved hours every week and sped up response times, simplifying the process and making it better for those trying to run it. It wasn’t a big project—but it made a big difference to those people to free them up for tasks that were more challenging and a better use of their skills.
The Building Blocks of Continual Improvement
Continual Improvement isn’t just a mindset—it’s backed by tools, processes, and roles that make it work day-to-day. Here are the core components you need to make it more than just a buzzword.
The Continual Improvement Model
This is ITIL’s step-by-step guide to improvement. Think of it as a structured cycle:
- What’s our vision?
Tie improvements to business goals. - Where are we now?
Get a clear, honest baseline. - Where do we want to be?
Define measurable targets. - How do we get there?
Build a practical plan. - Take action
Implement the changes. - Did we get there?
Measure results and learn. - How do we keep moving?
Feed insights into the next round.
This model makes sure your improvement efforts are strategic, not scattergun.
The Improvement Register
This is your log of improvement ideas—big or small. It tracks:
- What the opportunity is
- Who owns it
- Status and progress
- Potential impact
It helps prioritise, avoid duplication, and maintain momentum.
Measurement and Metrics
There’s an old saying in business; “You can’t improve what you don’t measure”. Metrics should be:
- Relevant to your goals
- Actionable (you can respond to them)
- Consistent (tracked over time)
Examples include incident volumes, change success rates, or customer satisfaction scores—whatever gives you visibility into performance.
My advice is always to start small, and build out. Metrics / KPIs should be meaningful and actionable. They should tell you something, which you can then do something about.
Governance
Improvement must be aligned with wider goals and comply with standards or policies. Governance ensures:
- You’re improving the right things
- Risks are managed
- Results are reviewed and communicated
It also stops pet projects from eating up resources without delivering value.
Culture
Tools and frameworks are useless if no one’s on board. The hardest—and most important—part is building a culture that:
- Encourages feedback
- Supports learning from failure
- Rewards initiative
- Treats improvement as everyone’s responsibility
In a nutshell
These components create the structure that supports an improvement mindset. The model gives you steps, the register tracks opportunities, metrics show results, governance keeps it aligned, and culture brings it to life.
How Continual Improvement Happens in Practice
Continual Improvement isn’t a once-a-year workshop—it’s a cycle that runs continuously behind the scenes. Here’s how it typically works in an ITIL-aligned environment.
Step 1: Spot Opportunities
Start by identifying areas where things could be better. Sources might include:
- Feedback from users or customers
- Service desk data (e.g. recurring incidents)
- Performance metrics
- Audits or compliance reviews
- Team observations (“We’re always chasing this ticket type…”)
Don’t wait for something to go wrong—look for what could work better.
Step 2: Define the Target
Once you’ve found an opportunity, define what success looks like. Use SMART objectives:
- Specific: What exactly are we changing?
- Measurable: How will we know it worked?
- Achievable: Can we do this with the time and resources we have?
- Relevant: Does this align with business or IT goals?
- Time-bound: When will it be done?
Example: “Reduce password reset ticket volume by 25% in the next three months.”
Step 3: Plan the Change
Map out how you’ll achieve the goal. This might include:
- Assigning responsibilities
- Estimating time and cost
- Managing risks
- Getting buy-in from stakeholders
- Communicating with affected teams
The more clearly you plan, the smoother the implementation.
Step 4: Implement the Improvement
This is the action stage—make the change happen. Depending on the scope, this might involve:
- Updating a process
- Introducing a new tool
- Automating a manual task
- Providing training
Be sure to track progress and keep stakeholders informed.
Step 5: Review the Results
Once the change is in place, evaluate its impact:
- Did it achieve the target?
- Were there any unintended side effects?
- What went well, and what didn’t?
Even “failed” improvements can offer valuable lessons—don’t skip this step.
Step 6: Lock It In and Learn
If it worked, make the improvement part of your standard way of working. Update documentation, train people, and share the success across teams.
If it didn’t, document why—not every idea will land, but every effort should teach you something.
These six steps form a loop, not a line. As soon as one improvement cycle finishes, another can begin. That’s what makes the process continual.
How Continual Improvement Connects With Other ITIL Practices
In ITIL v4, Continual Improvement is everyone’s responsibility. It doesn’t run in isolation—it enhances and supports all other practices. Here’s how it integrates with some of the most common ones:
Service Level Management
SLAs (Service Level Agreements) set expectations—but meeting them isn’t enough if customer needs are evolving.
Continual Improvement ensures that SLAs are reviewed regularly and updated based on changing priorities or customer feedback. If response times are falling short, or a service consistently under-delivers, improvement actions can be targeted there.
Change Enablement (formerly Change Control)
Every improvement creates change, and change needs to be managed.
Improvement initiatives often trigger changes—new tools, revised processes, automation, etc. Continual Improvement works hand-in-hand with Change Enablement to ensure those changes are planned, approved, and implemented with minimal disruption.
Incident and Problem Management
Firefighting incidents can reveal what’s broken underneath.
Continual Improvement can spot recurring incidents or root causes of major problems. It helps prioritise actions that reduce ticket volumes and improve service stability. It also uses incident and problem data to steer long-term enhancements.
Knowledge Management
Improvement efforts often uncover new ways of working.
When improvements are implemented, new knowledge should be captured—what worked, what didn’t, what changed. Continual Improvement feeds the knowledge base and uses it to guide future cycles.
Service Design
Every new or changed service should build on past lessons.
Continual Improvement feeds insights from operational experience back into the design phase—so that new services are more robust, efficient, and aligned with business needs from the outset.
In short
Continual Improvement should sit in the background of everything you do, nudging each practice towards better performance, alignment, and value delivery.
Who’s Involved in Continual Improvement?
You don’t need a massive team to do Continual Improvement well—but you do need clarity on who does what. Here are the key roles that help make it happen.
Continual Improvement Manager
Main job: Owns the improvement process.
This person keeps the cycle moving—identifying opportunities, coordinating across teams, tracking progress, and reporting results.
They’re not expected to fix everything themselves, but they do make sure improvements don’t get forgotten or buried under day-to-day work.
Process Owners
Main job: Make sure their process gets better over time.
Every major process (like incident management or change enablement) should have someone responsible for keeping it fit for purpose—and that includes planning and leading improvements.
Service Owners
Main job: Own the quality and performance of a specific IT service.
They identify weak spots, listen to feedback, and help drive improvement initiatives that directly impact the user experience.
Improvement Teams
Main job: Implement the change.
These are cross-functional groups brought together to deliver specific improvement initiatives. The makeup depends on the project—maybe a developer, a service desk analyst, a data analyst, and a stakeholder from the business side.
Data Analysts (or someone acting in that role)
Main job: Provide the evidence.
Improvement efforts need data—on service performance, customer feedback, incident trends, etc. Whether it’s a dedicated analyst or a team member with reporting skills, someone needs to provide insight, not just information.
Important note:
In smaller organisations, one person might wear several hats. That’s fine—as long as the roles and responsibilities are clear and the improvement work gets done.
Measuring What Matters: KPIs for Continual Improvement
You can’t improve what you don’t measure—and you certainly can’t prove the value of improvement without data. ITIL encourages tracking metrics that show whether your efforts are making a difference.
Here are some of the most useful KPIs to track in a Continual Improvement context:
Customer Satisfaction Score (CSAT)
What it tells you: Are users happier after the change?
How to measure: Survey users before and after major improvements. Track trends over time.
Cost of Service Delivery
What it tells you: Did the change save money?
How to measure: Compare total cost before and after an improvement (including people, time, tools).
Incident / Problem Volume
What it tells you: Are fewer things going wrong?
How to measure: Compare incident or problem counts pre- and post-change. Look for trends.
Service Performance
What it tells you: Are services faster, more reliable, or more available?
How to measure: Uptime, response times, completion rates—depending on the service in question.
Number of Improvements Implemented
What it tells you: Are we taking action or just talking about improvement?
How to measure: Count completed initiatives that met their objectives.
Time to Implement Improvements
What it tells you: Are we efficient at delivering change?
How to measure: Average time from identifying an improvement to completing it.
Employee Engagement
What it tells you: Are staff involved in and energised by improvement?
How to measure: Internal surveys or informal feedback after improvement initiatives.
Return on Investment (ROI)
What it tells you: Was the improvement worth it financially?
How to measure: (Financial gain – cost of improvement) ÷ cost of improvement.
Not all of these will be relevant for every organisation. Pick the ones that align with your goals—and track them consistently.
Key Advice for Making Continual Improvement Stick
Having the model and metrics is great—but real improvement happens when it becomes part of your culture, not just a task list. Here are some tips for turning the theory into results.
1. Prioritise Improvements That Matter
Don’t try to fix everything at once. Focus on changes that will have the most impact on customers, staff, or business goals. Use your improvement register to assess:
- Value (What’s the benefit?)
- Effort (How hard is it?)
- Risk (What could go wrong?)
- Urgency (Does it need fixing now?)
Quick wins are fine—but make sure they support a bigger picture.
2. Listen to Feedback (Then Act on It)
Ask frontline staff, users, and customers what’s not working. They’re often sitting on goldmines of insight. But feedback is only valuable if it leads to change. Show people that speaking up leads to action.
3. Use Data—but Don’t Drown in It
Track a handful of useful metrics that actually show progress. Don’t collect data for the sake of it. A good metric helps you:
- Spot problems early
- Measure the effect of changes
- Justify decisions to stakeholders
4. Tie Improvements to Strategy
Every improvement should support a business goal—even if indirectly. Otherwise, it risks becoming a distraction. Ask: How will this help us serve customers better, faster, or cheaper?
5. Improve the Improvement Process
Yes—this process itself should evolve too. Ask questions like:
- Are we tracking too many low-value ideas?
- Are improvements getting stuck in planning?
- Do we celebrate wins (and learn from failures)?
Keep refining your approach over time.
6. Make It a Habit, Not a Project
The biggest shift comes when people no longer see improvement as “extra work”. Encourage teams to build it into retrospectives, reviews, service reporting, and even 1-to-1s. Keep it visible. Keep it simple.
Further Reading
https://www.axelos.com/resource-hub/white-paper/itil-guiding-principles-for-continual-improvement
FAQs
What’s the difference between Continual Improvement and a one-off project?
A one-off project is a fixed initiative with a defined end—like launching a new ticketing tool.
Continual Improvement is an ongoing cycle of making things better across services, processes, and performance. It’s not a phase, it’s a mindset—baked into the day-to-day.
Think of it this way: Projects change the landscape. Continual Improvement keeps it evolving in the right direction.
Do we need a dedicated Continual Improvement Manager?
No — but someone needs to own the process.
In smaller teams, this role might sit with a Service Manager, Process Owner, or IT Lead. The important thing is to have:
– Clear accountability
– A way to log and prioritise improvement ideas
– Someone driving progress and reporting impact
It’s fine to start small—just don’t let improvement become “everyone’s job” and nobody’s responsibility.
How do we decide which improvements to prioritise?
Use a simple scoring model based on:
– Value (How much benefit will it bring?)
– Effort (How hard is it to do?)
– Risk (What could go wrong?)
– Urgency (Does it need fixing now?)
Many teams use a traffic-light system or a scoring grid to help with this. And don’t underestimate the power of quick wins—small improvements with visible impact can build momentum and confidence.
How does Continual Improvement link to Agile or DevOps?
They’re aligned in spirit and practice. Like ITIL, Agile and DevOps promote fast feedback loops, learning, and iteration.
Continual Improvement gives your ITSM processes the same muscle: review, reflect, adapt. The difference is:
– Agile focuses on development
– DevOps on delivery and operations
– Continual Improvement cuts across all practices, including service desk, change, and knowledge management
Together, they make your organisation faster, smarter, and more responsive.
What if an improvement fails?
Then it’s still useful—as long as you learn from it.
Improvement isn’t about perfection—it’s about progress. If something doesn’t deliver the intended results:
– Analyse what happened
– Document the lessons
– Share it so others avoid the same misstep
Celebrate learning just as much as success. That’s how you build a resilient, improvement-led culture.
