The New ITIL Version 5: What It Means in the Real World of Digital Services
I have worked with ITIL in one form or another for most of my career. Like many people in service management, I learned it as a set of processes, diagrams, and defined roles. Over time, it became a shared language that helped me have clearer conversations with colleagues, suppliers, and senior leaders.
The problem is that the world ITIL was originally designed for no longer exists in quite the same way. When I look at my own environment in higher education, we are operating in a landscape dominated by cloud platforms, integrated ecosystems, and services that are always on. Students expect digital tools to work seamlessly, and when they do not, the impact is immediate and very visible.In that context, simply polishing existing processes was never going to be enough. ITIL Version 5 feels like a natural evolution rather than a radical overhaul. It respects the foundations that many of us built our careers on, but it updates the guidance so it actually reflects how modern digital teams work today.
Why this matters, especially now
PeopleCert has always had an important role in stewarding ITIL as a credible body of best practice. From my perspective, Version 5 continues that responsibility, but in a much more contemporary context.
What I particularly value is that this is not just a rebranding exercise. It is a genuine attempt to align ITIL with the way organisations are already operating. In many universities, public sector bodies, and large enterprises, teams are already thinking in terms of products, experiences, and outcomes. Version 5 gives that thinking a clearer framework.
For professionals, this matters because service management cannot stand still. Certification should not be a one-off achievement. It should reflect current practice. For organisations, it matters because outdated approaches can slow decision-making, create unnecessary friction, and ultimately damage the experience of the people we are supposed to be supporting.
What actually feels different in ITIL Version 5
The biggest shift I see in Version 5 is the move away from treating ITIL primarily as a process framework. In previous versions, many organisations interpreted ITIL as a set of procedures to implement and audit against. That sometimes led to box ticking rather than meaningful improvement.
Version 5 reframes things around products and services. Instead of seeing services as outputs of processes, they are treated as enduring products with lifecycles, owners, and long-term value. That might sound like semantics, but in practice, it changes how teams think.In my own world, when we talk about something like a student information system or a virtual learning environment as a product, the conversation shifts. We stop asking only whether incidents are being resolved within SLA. We start asking whether the service is reliable, usable, and genuinely helping students and staff do their jobs. That is a more mature and more useful way of thinking.Another important change is the stronger focus on experience. Version 5 is much clearer that value is co-created with users. That resonates with me because in higher education, the quality of digital services has a direct impact on teaching, learning, and student satisfaction.
This means we need to look beyond internal metrics. A service might meet all its technical targets, but if students are frustrated or staff find it difficult to use, we cannot really call that a success. Version 5 encourages teams to take that broader perspective seriously.I also think Version 5 sits more comfortably alongside modern ways of working. Many of the teams I work with use agile approaches, work in sprints, and collaborate closely with suppliers. ITIL is not trying to replace that. Instead, it provides a shared language around risk, governance, and value that complements those ways of working rather than conflicting with them.
What this looks like in practice
Where Version 5 really comes alive is when you apply it to real services. In higher education, a core student information system is a good example.
In a more traditional ITIL mindset, we might have focused heavily on incident volumes, change success rates, and process compliance. Those things still matter, but they do not tell the full story.With a Version 5 lens, the team starts asking different questions. Are students able to access the system at peak times, particularly during critical periods like Clearing or assessment windows? Does the service actually support academic processes effectively? Are we making improvements that reduce friction for users rather than just fixing faults?
That shift leads to better conversations with stakeholders and, ultimately, better decisions about where to invest time and effort.
Major Incidents also take on a slightly different meaning. In the past, the priority was often purely technical resolution. That is still vital, but Version 5 reminds us that these are also experience events. When a core system fails, the impact on students, academics, and professional services staff can be significant.
In my view, that makes communication, empathy, and clarity just as important as technical troubleshooting. Getting the technology back online is only part of the job.
Continual improvement feels more natural in Version 5 as well. Instead of being treated as a separate activity that happens occasionally, it becomes part of how service owners and delivery teams operate day to day. Improvements are driven by real evidence, user feedback, and ongoing performance rather than just periodic reviews.
Learning, development, and certification
From a professional perspective, Version 5 is a chance to refresh and deepen our understanding of service management. PeopleCert’s updated certification pathways reflect this evolution, helping practitioners bridge the gap between earlier versions and the new approach.
Importantly, this is not about throwing away what we already know. Many of the core ideas in ITIL remain relevant, particularly around risk, governance, and structured decision-making. What has changed is how those ideas are framed within a more product-centred, experience-focused model.
For organisations, encouraging teams to engage with Version 5 can support cultural change as much as technical capability. When everyone shares a common understanding of products, services, and value, collaboration becomes easier and conversations with stakeholders become more productive.
My view on where this leaves us
ITIL Version 5 does not pretend to solve every challenge in modern digital service management. It does not remove complexity or replace the need for strong leadership and skilled teams. What it does offer is a more relevant and practical way of thinking about services in today’s world.
For leaders, the opportunity is to use this guidance as a framework for better conversations rather than a rigid rulebook. For practitioners, it is an invitation to move beyond process compliance and focus more deeply on outcomes and experience.Having spent many years working with earlier versions of ITIL, I see Version 5 as a natural next step. It builds on what has worked in the past while recognising that our context has changed.
In that sense, the new ITIL is not just an update. It is a reflection of how our profession has matured, and how digital services have become central to almost everything our organisations do.
