Seven Principles, One Improvement Loop: ITIL v5 in Practice
How ITIL v5's guiding principles work together, what automation and AI depend on, and the continual improvement model's new step 7, with an M365 example.
On Monday I covered the ITIL® Value System and governance. Two of its components are left: the guiding principles and continual improvement. Both carry over from ITIL 4, but v5 puts the emphasis on how the principles work together, and adds one small but testable change to the improvement model.
The seven principles (unchanged)
ITIL's guiding principles are recommendations that can guide an organization in all circumstances, whatever changes in its goals, strategy, type of work or structure:
- Focus on value
- Start where you are
- Progress iteratively with feedback
- Collaborate and promote visibility
- Think and work holistically
- Keep it simple and practical
- Optimize and automate
How they work together
This is what the Bridge focuses on. The modules make four points:
- The principles interact with and depend on each other.
- Don't rely on just one or two. Consider all of them, and how they complement each other.
- There's no fixed order or hierarchy. They're all equally important.
- In practice, some matter more in a given situation than others.
Automating password resets is a good example. Focus on value: fewer tickets and faster help for users. Start where you are: look at the current reset tickets before buying anything. Keep it simple: use self-service password reset that's already in Entra ID. Progress iteratively: pilot it with one team first. Then optimize and automate. No single principle gets you there.
Automation, AI, and what they depend on
Optimize and automate now explicitly covers AI:
- Automation is technology performing steps correctly and consistently, with little or no human intervention.
- AI enhances automation with AI tools, data insights, intelligent workflows and chatbots.
- Both depend on three things: good data, optimized workflows and strong governance.
That last point is the one I'd underline for anyone rolling out Copilot. If your data is messy and your permissions are loose, AI amplifies the mess.
Continual improvement
Continual improvement is a recurring activity, performed at all levels of the organization, so that it keeps meeting stakeholders' expectations. It applies to the entire ITIL Value System: products, services, practices and relationships.
The ITIL Continual Improvement Model has seven steps:
- What is the vision?
- Where are we now?
- Where do we want to be?
- How do we get there?
- Take action
- Are we getting there?
- How do we keep the improvements relevant?
Step 7 is the change. In ITIL 4 it was "How do we keep the momentum going?" The new wording is about whether an improvement still matters, not just keeping it going.
The same password reset example runs through the model neatly:
- The vision: users get unblocked without waiting for the service desk.
- Where we are now: count today's reset tickets.
- Where we want to be: a clear target for fewer tickets.
- How we get there: plan an SSPR pilot.
- Take action: run the pilot.
- Are we getting there? Compare against the baseline.
- Keeping it relevant: review it later, in case MFA changes or passwordless sign-in make it obsolete.
What I'm taking into the exam
- The 7 principles, with no fixed order or hierarchy. They interact and should be used together.
- Automation and AI depend on good data, optimized workflows and strong governance.
- Continual improvement applies to the whole ITIL VS, at all levels.
- The 7 steps in order, with the new step 7: "How do we keep the improvements relevant?"
ITIL® is a registered trademark of PeopleCert group. This post contains my personal study notes and interpretation, not official ITIL guidance.