Most ITIL adoption programmes start well. There is a kick-off, a few energetic workshops, some new process diagrams and a sense that things are finally going to improve.
Then, a few months in, momentum fades. Meetings get cancelled. The new process exists, but people still work the old way. Before long, the programme is “on hold”, and everyone quietly moves on.
We have seen this pattern many times, and it is rarely because ITIL does not work. It is almost always down to a handful of predictable causes. The good news is that each one can be avoided.
1. The scope is too big
Trying to adopt a dozen practices at once is the most common reason programmes stall. Everyone is stretched, nothing gets finished properly, and progress becomes hard to see.
What helps: start with two or three practices that address your most visible pain points. For many organisations that means incident, change and service level management. Get those working well, show the results, then expand.
2. Nobody really owns it
A programme sponsored by “IT” in general is sponsored by nobody in particular. When priorities clash, as they always do, adoption work loses.
What helps: name a sponsor with real authority, and give every practice a named owner. Ownership does not mean doing all the work. It means being accountable for the practice working, and having the time to make that happen.
3. It is all documents and no doing
It is surprisingly easy to spend months writing process documents that nobody reads. The documentation looks impressive, but daily work does not change.
What helps: keep documents short and practical, and spend more effort on how work actually flows. Walk through real tickets with the teams who handle them. Ask where they get stuck. Design around reality rather than an ideal.
4. The tool does not match the process
If your ITSM tool still reflects the old way of working, people will follow the tool, not the new process. A new change approval step that does not exist in the tool is a step nobody takes.
What helps: treat tool configuration as part of the adoption, not a separate project for later. Update workflows, forms, categories and reports alongside the process design, so the easiest way to work is also the right way.
5. Success is never measured
Without measures, nobody can tell whether the programme is helping. That makes it an easy target when budgets tighten.
What helps: agree a small number of meaningful measures at the start, such as time to restore service, change success rate or user satisfaction, and report on them regularly. Even modest improvements, shown clearly, protect the programme and keep people motivated.
6. People are told, not involved
Practices imposed on teams tend to be resisted, worked around or ignored. Practices that teams helped to shape tend to stick.
What helps: involve the people who will use the practice in designing it. Run short workshops, test drafts with real cases, and act on the feedback. It takes a little longer at the start and saves a great deal of time later.
Keeping your programme moving
None of these fixes is complicated. What they have in common is a focus on how work really happens, rather than how it looks on paper. Keep the scope tight, give it clear ownership, align your tool, measure what matters and bring your teams with you.
If your adoption programme has already stalled, it is rarely too late. A short review of where things stand, followed by a smaller and sharper plan, is often enough to get it moving again.
Is your ITIL adoption losing momentum? Book a free scoping call and we will help you get it back on track.
