Home
As ITIL keeps growing your people needs simplicity & guidance
ITIL version 5 is here. Another version, another stack of diagrams, another certification logo for the slide deck. But on Monday morning, your teams still have the same question: "How do we actually run this in practice?"
This article gives a quick tour through the history of ITIL, why many practitioners are struggling more and more with each version, and how the USM method gives exactly the practical, simple operating model the industry has been longing for. It also explains how TransparIT and MetierWestergaard now bring USM courses to the Danish market.
A short history of ITIL: From 30+ books to complexity overload
In the mid-1980s, the UK government's Central Computer and Telecommunications Agency (CCTA) set out to solve a real problem: public sector IT was expensive, inconsistent, and notoriously difficult to govern. Different ministries ran IT their own way, procurement was wasteful, and nobody could agree on even the most basic operating standards. The answer was a library of documented good practices – initially called GITIM (Government IT Infrastructure Management) before being renamed the more universally appealing Information Technology Infrastructure Library, or ITIL.
ITIL Version 1
The first version was very much "government-style": more than 30 thin volumes, each covering a specific domain – help desk operations, capacity planning, network management, environmental infrastructure, you name it. There was no single "core", no lifecycle, no guiding narrative. Organizations picked the books relevant to them and left the rest on the shelf. Comprehensive, yes. Digestible, decidedly not. Still, ITIL v1 accomplished something significant: it shifted the conversation from technology management to process-based service management – a conceptual leap that set the tone for everything that followed.
ITIL Version 2
ITIL v2 cleaned this up by rationalizing the sprawling library into a far smaller, coherent set built around a single organizing principle: some processes support services day-to-day, others deliver them over time. The result was seven core books – with "Service Support" (the Blue Book: Incident, Problem, Change, Release, Configuration Management, and Service Desk) and "Service Delivery" (the Red Book: Availability, Capacity, Continuity, Financial Management, and Service Level Management) as the undisputed stars of the show. Supporting titles covered ICT Infrastructure Management, Application Management, Security Management, and crucially: Planning to Implement Service Management – the first official answer to the question "but where do we actually start?"
For the first time, practitioners could read ITIL over a weekend and recognize their own work in it. This is when ITIL Foundation courses really took off and when the framework began its global expansion far beyond UK government corridors. v2 also gave ITIL real institutional weight: it became the primary reference for BS 15000, which later became ISO/IEC 20000 – the international standard for IT service management. For a decade, "doing ITIL" effectively meant implementing the v2 process clusters, and organizations around the world did exactly that.
ITIL Version 3 (2007)
With ITIL v3, the lifecycle took center stage: Service Strategy, Service Design, Service Transition, Service Operation, and Continual Service Improvement – five core books, roughly 26 processes, and four functions. The conceptual message was sound: "Think in lifecycles, not silos." For the first time, ITIL explicitly connected IT operations back to business strategy and forward to structured improvement. The Continual Service Improvement book gave organizations a repeatable measurement-and-maturity engine, and the 2011 update refined the content significantly – elevating Business Relationship Management and Strategy Management to formal processes, tightening terminology, and resolving inconsistencies that practitioners had been complaining about since day one.
But the framework also became considerably heavier. The five books grew thick with theory, and many organizations found themselves able to recite the lifecycle fluently while struggling to translate it into concrete day-to-day work instructions. The gap between "the framework says" and "so here is what we actually do" widened noticeably.
To address this, AXELOS released the ITIL Practitioner Guidance in 2016 – an unofficial acknowledgement that possessing a well-structured library does not automatically tell you how to change. It introduced nine guiding principles (Focus on value, Start where you are, Progress iteratively with feedback…) and provided practical toolkits for organizational change management, communication, and measurement. Practitioner was arguably the most useful publication in the entire portfolio for practitioners in the field. It was also, quietly, a signal of things to come.
ITIL Version 4 (2019)
Then came ITIL 4, introducing a more holistic – and arguably more academic – Service Value System, seven guiding principles, a six-activity Service Value Chain, and a portfolio of 34 management practices deliberately aligned with Agile, DevOps, and Lean thinking. The strategic realignment was overdue and intellectually honest. But the structure became even more fragmented: one Foundation book, five higher-level Managing Professional and Strategic Leader publications (Create, Deliver & Support; Drive Stakeholder Value; High-velocity IT; Direct, Plan & Improve; Digital & IT Strategy), plus 34 individual practice guides delivered as separate PDFs rather than a single physical reference library.
Great thinking – but considerably less concrete for the practitioner who simply wants to know: "Who does what, when, and with which tool?"
To make it even more fun, the ITIL Foundation course was reduced from three days to two, while attempting to cover more content at a higher conceptual level. The result in many organizations: rich new vocabulary, a sharper strategic lens, and a very real difficulty designing a clear operating model, a sensible service catalogue, or workable handovers between teams from the ground up.
ITIL (Version 5)
Now ITIL (Version 5) arrives on top of that, extending the conversation into even broader territory: ecosystem thinking, sustainability, AI governance, and platform operating models. That is genuinely valuable at the strategic and architectural level. But it does not resolve the fundamental tension that has been building since v3: the framework keeps expanding upward and outward – which is intellectually honest about the real complexity of digital service management – while the distance between "the framework says…" and "so here is exactly what we do on Monday morning" has never been greater.
Which raises the question worth sitting with: is that a problem with ITIL – or a problem with how organizations consume and implement it?
Why many ITIL trainings no longer feel "foundational"
If you talk to practitioners, a pattern appears:
  • Foundations are packed with theory and terminology, but do not leave enough time to design how work actually flows in their organisation. Modern ITIL Foundation courses, while introducing valuable concepts like the Service Value System, guiding principles, and a vast array of practices, have become increasingly theoretical. Practitioners often find themselves grappling with a new vocabulary without clear instructions on how to translate these abstract ideas into tangible, actionable steps within their own teams. The focus shifts towards understanding 'what' ITIL is, rather than 'how' to apply it, creating a growing gap between certification achievement and actual practical implementation.
  • Intermediate / practitioner level courses exist, but participation is modest and the link to concrete implementation is often weak. Many organizations hesitate to invest in these higher-level courses due to their significant cost, time commitment, and a perceived lack of immediate return on investment. The content, while more detailed, frequently continues to emphasize theoretical knowledge over practical application, lacking the specific tools, templates, or guided workshops needed to bridge the gap between classroom learning and real-world operational changes. This results in low uptake and a feeling among practitioners that these courses don't sufficiently address their day-to-day challenges.
  • Meanwhile, the need for real guidance is higher than ever: more suppliers, more cloud, more compliance, and more demanding business stakeholders. Today’s IT landscapes are incredibly complex. We're operating in multi-cloud and hybrid environments, managing numerous third-party suppliers, adopting rapid DevOps and Agile methodologies, and facing stringent regulatory requirements. This dynamic environment desperately calls for practical, implementable operating models, clear handovers, and efficient service catalog design. Traditional training, which often focuses on abstract frameworks, falls short in providing the concrete, step-by-step guidance needed to navigate these contemporary challenges effectively.
In other words: the demand for pragmatic, ITIL-based guidance that answers "Who does what, when, and with which tool?" is higher than ever. However, the supply from traditional training of simple, implementable structures – complete with clear roles, responsibilities, and workflows – is not keeping up. This creates a significant gap between what practitioners learn and what they desperately need to apply. That is exactly the gap USM is designed to fill.
USM: Your Practical Operating Model for ITIL
ITIL provides excellent best practices, but translating theory into day-to-day operations can be challenging. Unified Service Management (USM) acts as the practical blueprint to structure your ITIL implementation, offering simplicity and clear guidance where it's needed most.
Enter USM: The Operating Model to structure your ITIL implementation
Unified Service Management (USM) is a structured method that makes ITIL implementations easier and much more effective in practice. It does not replace ITIL – it acts as the architectural blueprint and implementation method for the best practices ITIL describes.
USM starts from the idea that every service organisation, regardless of size or sector, can be controlled with the same simple architecture.
Instead of navigating dozens of separate processes and practices, you get one coherent structure where every activity has a clear place and purpose.
USM also begins where many ITIL initiatives quietly skip a step: with a precise, shared Service Definition. It defines how services are identified, described, documented and maintained across the organisation, so everyone talks about services in the same way. Without this, "service catalogue", "SLAs" and "value streams" quickly become buzzwords instead of management tools.
Principles that become real design rules
ITIL 4 talks a lot about principles – focus on value, start where you are, think and work holistically. USM takes the same kind of principles and bakes them directly into the design of your Service Management System.
Instead of abstract ideals, USM turns principles into concrete questions:
  • Where is value created in this service?
  • What information must be transparent to which roles?
  • How do changes, incidents and requests connect in one flow?
This leads to a Service Management System that actually hangs together: processes, people, technology and information are designed as one whole, not as isolated process "modules" or tool workflows. Your ITSM tool becomes an implementation detail of your architecture, not the architecture itself.
Clear roles, three layers and no overlaps
One of the most painful side effects of ITIL complexity is unclear responsibilities: who decides, who executes, who just gets spammed in CC?
USM tackles this by structuring work in three simple layers:
Processes (What)
Define what must be done at a high level.
Procedures (Who)
Allocate who is responsible for which steps.
Work Instructions (How)
Describe how tasks are carried out in practice.
This layered approach prevents overlapping roles, reduces handover chaos and makes it crystal clear how Incident Management connects to Change, Problem and all the other practices you know from ITIL. Instead of drawing new swimlane diagrams for every process, you get one stable backbone that the whole organisation can understand.
Tool‑ready by design, not by accident
USM also helps you specify exactly what your ITSM tooling must support – based on your processes and service definitions, not on a glossy vendor demo. You know which data you must register, how services must be structured in the CMDB / service portfolio, and which workflows actually matter.
That means:
No more retrofitting
No more implementing a tool first and then trying to retrofit your way of working into it.
Unified view
No more "Incident in one system, Requests in another, changes somewhere in a DevOps board, and nobody sees the whole picture".
Easier tool changes
A much easier time when you change tools, because the operating model is stable and independent of the product.
USM works just as well alongside ITIL in a large enterprise as it does as a standalone method in a smaller organisation that wants a practical approach without heavyweight framework complexity.
How USM makes ITIL more usable
For organizations that already "speak ITIL," USM isn't just another shiny new framework; it's the essential wiring that connects the sprawling, theoretical ITIL blueprint to a practical, functioning machine. It takes those brilliant best practices and shows you exactly where to plug them in, translating abstract ideas into real-world action:
  • ITIL gives you the library of best practices.
  • USM gives you the architecture and the concrete way to put them into practice.
The five USM processes give a home to the familiar topics:
AGREE
Where demand, service definition, expectations and service levels are aligned – the natural place for service portfolio, catalogue and SLAs.
CHANGE
Covers the control, planning, analysing and implementaion coordination of the change, so everything is under control.
RECOVER
Structures how you restore service when something goes wrong – the logical home for Incident and knowledge management.
OPERATE
About running the daily operation: monitoring, access, routine tasks, events.
IMPROVE
Ensures continual learning and optimisation instead of treating improvement and threats as a side project.
This way, your people no longer have to memorise dozens of separate practices. They learn one simple model and can immediately translate ITIL content into concrete roles, activities and information flows in your organisation.
TransparIT + MetierWestergaard: Bringing USM courses to you
All of this is only useful if people can actually learn and apply it. That is why TransparIT now offers Unified Service Management (USM) training in collaboration with MetierWestergaard.
Together, these courses combine:
USM's Clear Architecture
Principle-based architecture for service management.
Practical Experience
Real implementations – what works, what doesn't, and why.
Hands-on Exercises
Focus on your real service environment, not just theory slides.
In q2 - 2026, the first USM Foundation courses are launched in Denmark, targeted at IT professionals who want a solid, practical foundation: sharp service definitions, effective support and clear control of service delivery. Participants learn how to build a coherent service management system, see how ITIL practices fit into it and how to start small and scale based on concrete needs, rather than framework hype.
You can find the current dates and details here: USM Foundation Courses.
ITIL will probably keep evolving, and version 6 will arrive one day with new diagrams and new terminology. With USM in place, you can relax a bit: your service management system will already be simple, coherent and ready to absorb whatever the next version brings.