ITIL Is Not a Process Library (And Never Was)
For as long as Iâve worked in IT and ITSM, Iâve heard the same statement repeated in different forms:
âWe need to implement ITIL.â
What usually follows is a hunt for process diagrams, templates, and approval gates often lifted straight from a book, a consultantâs slide deck, or a previous organisation. Before long, teams are drowning in documentation, delivery slows down, and frustration grows.
Then ITIL gets blamed.
Hereâs the uncomfortable truth: ITIL was never meant to be a process library and when we treat it like one, we miss its real value entirely.
ďťż
Where the Myth Came From
Earlier versions of ITIL were heavily process focused. Many of us learned ITIL through structured lifecycle stages, defined roles, and detailed process flows. That history matters, but it also explains why the myth persists.
Over time, âdoing ITILâ became synonymous with:
- Implementing every process
- Adding controls before understanding value
The result? ITIL became associated with bureaucracy, red tape, and slow decision-making, especially in fast-moving environments.
But even then, ITIL was never intended to be followed blindly. And ITIL v5 makes that explicit.
ďťż
What ITIL Actually Is
At its core, ITIL is a management framework designed to help organisations create value.
It is:
¡ AI native which enables organisations tackle AI complexity with confidence.
¡ Practical by nature; it turns strategy into outstanding results.
¡ A connector for digital product and service management.
¡ For IT - and now also for every role across the business. For every organization, large and small. For all.
It is not:
¡ Compliance.
¡ Documentation.
¡ Processes for the sake of processes.
ITIL 5 reframes the conversation entirely:
From processes to practices
From outputs to outcomes
From control to co-creation of value
Practices are intentionally flexible. They describe what needs to be considered, not exactly how it must be done. Two organisations can both be âusing ITILâ and look completely different and thatâs by design.
If your ITIL implementation looks identical to someone elseâs, youâre probably doing it wrong.
ďťż
The Damage Caused by Treating ITIL as a Process Library
When ITIL is reduced to a checklist of processes, a few predictable things happen:
1. Teams Stop Thinking: If success is defined as âfollowing the process,â critical thinking disappears. People optimise for compliance instead of outcomes.
2. Change Becomes Heavy and Risk-Averse: Change management turns into change prevention. Approval layers multiply, delivery slows, and teams look for ways around the system.
3. Incidents Become Transactional: The focus shifts to logging, categorising, and closing tickets, rather than restoring service quickly or learning from failure.
4. People Lose Trust: When ITIL is used as a blunt instrument, it feels imposed rather than enabling. Engagement drops. Talent leaves. Once trust is gone, no framework will save you.
ďťż
âBut We Need Consistency and Controlâ
This is where many leaders push back, and fairly so.
Yes, organisations need governance. Yes, we need consistency where it matters. Yes, risk must be managed.
But control without context creates fragility. ITIL does not say âremove governance.â It says:
- Design governance intentionally
- Apply controls proportionate to risk
- Continually evaluate value
For example, A lightweight change model for low-risk work and a more rigorous one for high-risk changes is far more aligned with ITIL than a single, rigid process applied to everything.
ďťż
The Shift That Actually Unlocks Value
The organisations that get the most value from ITIL make a critical mindset shift:
They stop asking: âHow do we implement this process?â
And start asking: âWhat problem are we trying to solve?â
They use the ITIL guiding principles, especially Start where you are, Focus on value, and Think and work holistically as decision filters, not slogans.
Processes become tools, not rules.
ďťż
A Simple Test
If you want to know whether ITIL is being used as a framework or a process library in your organisation, ask this question:
âIf this process no longer delivered value, could we change or remove it?â
If the answer is no because âthatâs how ITIL says it should be done,â then ITIL has already been misunderstood.
ďťż
Final Thought
ITIL doesnât fail organisations. Misinterpretation does.
When ITIL is treated as a static set of processes, it becomes heavy and ineffective. When itâs treated as a flexible, value-focused framework, it becomes a powerful enabler of better decisions, better outcomes, and better experiences for customers and teams.
ITIL was never a process library, the moment we stop treating it like one is the moment it starts delivering what it always promised.
ďťż
