From Service Management to Enterprise Strategy: What ITIL (Version 5) Makes Possible

# AI

# ITIL

# Service Management

How ITIL leaders can bridge IT, OT, AI governance and enterprise strategy.

September 10, 2026

Andrea Haddad

From Service Management to Enterprise Strategy: What ITIL (Version 5) Makes Possible

Technology is no longer simply a support function. It has become a strategic capability that shapes how organizations compete and succeed.

When I became an ITIL practitioner, the conversation was about process. How do we standardize incident management? How do we build a change advisory board that actually works? How do we measure service levels in a way that means something to the business?

Those were the right questions for that moment. They still matter. But the moment has shifted, and the questions the business is asking of technology leaders have shifted with it.

Today, it is less about the process and more about the strategy. Not "how does IT manage services?" but "how does technology shape the enterprise's ability to compete, adapt, and grow?" Not "what is our MTTR?" but "what is our AI readiness, and what will it cost us if we are not ready?" In manufacturing and regulated industry environments, that second question carries an additional weight: what will it cost us in safety exposure, regulatory scrutiny, and operational resilience if we deploy intelligence without the governance to back it up?

ITIL has always had an answer to the second set of questions. Most of us have just been too focused on the first set to notice. ITIL (Version 5) changes that by naming the second set of questions directly.

The Gap Between IT and Enterprise Strategy

There is a structural problem in most organizations that almost no one talks about directly: technology strategy and enterprise strategy are developed in separate rooms.

Enterprise strategy is owned by the CEO, CFO, and the strategy function. It sets the direction, markets, capabilities, capital allocation, the next three to five years. Technology strategy is owned by the CIO and the IT leadership team. In theory it supports enterprise strategy. In practice it often runs slightly behind it, responding to business requests rather than shaping them.

In manufacturing organizations, this gap is compounded by a third separation: OT strategy. The plant floor has its own investment cycles, its own standards bodies, its own risk calculus. IT and OT have historically operated in parallel rather than in concert, connected at the edges but not integrated at the governance level. Industry 5.0 closes that separation whether organizations

are ready for it or not, because AI and digital twins and IIoT platforms do not respect the line between the corporate network and the plant floor.

I have watched the consequence of that gap play out in practice. An organization I worked with had a mature IT governance structure and a capable OT engineering team. They were not integrated. When an AI-assisted scheduling system was introduced that touched both enterprise resource planning and plant floor execution, there was no single governance body that could make decisions across both domains. The system went live. Problems emerged at the integration point between ERP and MES. The IT team owned one side. The OT team owned the other. The AI service is owned by neither. Resolving the issue took three times longer than it should have because the governance structure had never been built for a system that lived in both worlds simultaneously. Industry 5.0 produces exactly these systems. The governance gap is not theoretical. It has operational consequences every time.

The Three Shifts ITIL (Version 5) Asks of Its Leaders

Based on what I have seen in organizations navigating AI transformation and Industry 5.0, there are three specific shifts that distinguish ITIL leaders who operate at the enterprise strategy level from those who remain in the service management layer.

The first is moving from output to outcome. Traditional ITIL metrics are output-focused: availability, mean time to resolve, change success rate. These are necessary but not sufficient. In manufacturing environments specifically, the output metrics of IT mean nothing to a CFO or a COO unless they connect to batch yield, cycle time, compliance cost, or safety performance. The shift to enterprise strategy thinking requires ITIL leaders to make those translations fluently and consistently. When you can connect an infrastructure investment to an EBITDA impact, you are in a different conversation with leadership.

The second is moving from reactive to anticipatory. Service management is fundamentally reactive. A service exists, it has issues, ITIL helps manage those issues well. Enterprise strategy is anticipatory. It asks what capabilities the organization will need before the business has finished asking for them. In the context of Industry 5.0, this means understanding where AI and human collaboration is heading in your industry before your operations team has submitted a request, and being the person who brings that conversation to the table rather than waiting to be invited.

The third is moving from compliance to influence. ITIL governance done well is about shaping which changes get made, in what order, with what resources, toward what outcomes. In manufacturing environments where IT and OT decisions intersect, this requires the ability to operate across functional boundaries, to speak the language of risk, return, and safety, and to earn the trust of OT leaders who have historically viewed IT governance with some skepticism. That trust is not given. It is built through demonstrated respect for OT authority, safety engineering, and the reality that on the plant floor, the consequences of a governance failure are not a service disruption but a safety event.

AI and Industry 5.0 Are the Test

Everything I have described above is being tested right now by AI in manufacturing.

Industry 5.0 does not define success by how smart the machines are. It defines success by how clearly humans remain in control of the decisions those machines inform, and how confidently an organization can demonstrate that accountability to regulators, auditors, and the workforce whose trust the system depends on.

That requires ITIL practitioners who can do more than manage services well. It requires leaders who can design governance structures for AI that preserve human authority, build infrastructure investment cases that connect to business strategy, and operate at the intersection of IT, OT, and enterprise direction with the credibility that comes from deep technical grounding and genuine strategic fluency.

ITIL (Version 5) is the framework that makes this possible. The Strategy pathway, the Transformation module, the explicit guidance on AI-native organizations, these are not additions to the curriculum. They are the framework's recognition that the profession has outgrown the problem it started with and is ready for the problems the next decade will bring. Before you publish, I would recommend verifying the precise names of the Version 5 qualification modules against the current PeopleCert documentation, as the framework continues to evolve and naming conventions may have been updated since this article was written.

The Invitation

To my fellow practitioners and ambassadors: the conversation about enterprise AI governance is happening right now at the highest levels of organizations in every industry. In manufacturing specifically, that conversation carries stakes that are higher than most, because the systems we are governing influence physical outcomes, human safety, and regulatory standing simultaneously.

We have the framework. We have the credential. We have, many of us, the operational experience to know exactly where the governance gap is and what it costs when it is not closed.

What the moment asks of us is the confidence to bring ITIL into the rooms where those conversations are happening, and the language to make clear that service governance and enterprise strategy are not different disciplines. They are the same discipline at different altitudes.

The next evolution of ITIL leadership is not about better incident tickets. It is about better enterprises, safer operations, and more trustworthy intelligence.

We are ready for it.

Enjoyed this post? Join the conversation by leaving a comment or sharing your thoughts below, we’d love to hear your experiences and perspectives. Don’t forget to explore our upcoming events for more opportunities to learn and connect, and visit the forum to continue the discussion.

Where conversation, connection, and real-world practices come together.