The most expensive sentence I have heard inside an ITIL transformation is the one a steering committee says when the rollout is officially complete. The sentence is some variant of: we have implemented ITIL 4. It is usually accompanied by a slide deck, a CIO email to the organization, and a small reduction in the cadence of the transformation working group. None of those things are wrong on their own. They are wrong together. They are the formal beginning of the year-two failure pattern that most ITSM transformations never recover from.
If you have been part of an ITIL transformation that quietly stalled in month fifteen, you already know the shape of this. The framework is in place. The tools are configured. The processes exist on paper. Adoption looks healthy in the dashboard the program team built to measure adoption. And yet the operating model is gradually drifting back toward whatever it was before the rollout started. This essay is about why that happens and what the discipline of year two actually requires.
What usually breaks in months 12 to 18
The breakage is almost never visible from the dashboard. The breakage shows up in the conversations the dashboard does not capture. The first sign is that incident reviews start running short, because there is less to review, because tickets are being closed faster, because the team is under pressure to keep the green numbers green. The second sign is that change advisory board meetings shift from substantive to procedural. The third sign is that someone, usually a senior service owner, starts asking out loud whether a particular process step is "really necessary anymore." The fourth sign is the one nobody notices in real time: process documents stop being updated. The framework is now ornamental.
None of those four signs would show up in an ITIL maturity assessment. The framework is still in place. The processes still exist. The platform is still configured. The only thing that has changed is that nobody is governing the framework as a living instrument. They are operating inside it as a fixed asset.
Why process governance dies without outcome governance
The reason year two breaks down has very little to do with the framework itself. It has to do with what gets governed at the executive level after the rollout is declared complete. In year one, the executive committee governs the project. In year two, if nobody redirects that governance toward outcomes, it simply disappears. The transformation becomes invisible at the level of the organization that funds it.
The fix is not to extend project governance into year two. Project governance is the wrong instrument for an operating model. The fix is to replace project governance with outcome governance: a standing quarterly review where service owners report on the business outcomes their services produce, not the technical compliance of the processes that produce them. Outcome governance is where the framework earns the right to keep existing. Without it, the framework calcifies.
The role of service owners versus process owners in year two
Most ITIL transformations assign process owners during the rollout. That is correct. What most transformations do not do is assign service owners, distinct from process owners, with authority over the end-to-end outcome of the service rather than the operational fidelity of a particular process. When year two starts to wobble, the gap between process ownership and service ownership is almost always where the wobble lives.
A process owner can tell you whether incident management is performing within SLA. A service owner can tell you whether the service those incidents are interrupting is producing value for the business. Those are different jobs. Most ITSM transformations conflate them in year one because the rollout demands process-level accountability. The transformations that survive year two are the ones that decouple them by month thirteen.
What the second year actually requires
Year two of an ITIL transformation is a culture project. It is not a process project. The processes are mostly in place by month twelve. What is not in place is the operating discipline of running the organization through those processes when the project team is no longer running the meetings, the executive sponsor is no longer attending the standups, and the consultants who originally facilitated the workshops are no longer in the building. The vacuum that opens up in month thirteen is the entire test of whether the transformation took.
The leaders who pass that test do four things in year two that the leaders who fail it do not. They assign service owners with real authority. They run quarterly outcome reviews, not quarterly process reviews. They revise processes on a published cadence rather than on a complaint-driven cadence. And they make a habit of retiring processes that are no longer earning their keep, which is the single most counter-intuitive discipline of a healthy ITSM operating model. A framework that only adds is a framework that will eventually be too heavy to lift.
The transformations that win at ITSM treat year one as the infrastructure play and year two as the culture play. Most organizations confuse the two, declare victory after rollout, and watch the framework calcify into a compliance exercise.
What I would do differently if I were starting an ITIL transformation today
I would name the service owners before I named the process owners. I would book the year-two outcome reviews into the executive committee calendar on the same day I closed the year-one rollout. I would write a retirement plan for at least one process I knew we would no longer need by month eighteen, and I would publish it, so the organization understood that the framework was meant to evolve. None of that is hard. All of it requires being honest in year one about what year two will actually look like, which is the part most transformations skip.
If you rolled out ITIL 4 in the last two years, I would love to hear what you are doing in year two. That is where the real work lives.