Automation Isn't Replacing ITIL Work. It's Finally Creating Time for It

# ITIL

# Service Management

# AI

How removing repetitive work creates space for continual improvement, better services and greater value.

October 15, 2026

Helen Clarke

Automation Isn't Replacing ITIL Work. It's Finally Creating Time for It

If you've worked in service management for any length of time, you've probably attended a meeting where somebody said: "We need to spend more time on continual improvement." Everyone nods in agreement. Then everyone goes back to their overflowing queues, monitoring alerts, reports, emails, incidents, meetings, and operational demands. The reality is that most support teams don't struggle because they lack improvement ideas. They struggle because they don't have enough capacity to act on them. That's why I believe one of the most important conversations in modern service management isn't about AI, automation, or tooling in isolation. It's about capacity. Because automation isn't replacing ITIL work. It's finally creating time for it.

The Operational Trap Many IT teams have become incredibly efficient at processing work.

We close tickets faster.

We route requests automatically.

We collect more metrics than ever before.

We generate dashboards in seconds.

Yet despite all of this, many teams still find themselves stuck in a reactive cycle. We're so busy managing the work that we rarely have time to improve how the work gets done. This is something I've experienced firsthand. Across support operations, service management practices, reporting functions, and continual improvement initiatives, I repeatedly see talented people spending significant amounts of time on activities that, while necessary, don't directly move services forward.

Producing reports.

Manually compiling metrics.

Triaging mailbox requests.

Reconciling data from multiple systems.

Investigating recurring issues that everyone already knows exist.

None of these activities are inherently bad. The problem is that they consume the very capacity needed for improvement.

What ITIL (Version 5) Gets Right One of the things I appreciate about ITIL (Version 5) is its stronger focus on managing digital products and services in increasingly complex and AI-enabled environments. The framework continues to recognise the importance of value creation, continual improvement, governance, and the ITIL Value System, but it also acknowledges a reality many of us face every day: Modern organisations are becoming more complex.

Data volumes are increasing.

Automation is accelerating.

AI is becoming embedded into operational workflows.

Customers expect faster outcomes and better experiences.

Against that backdrop, continual improvement cannot remain an activity that teams undertake "when they have time." It has to become part of how we work. And to achieve that, we need capacity.

From Processing Work to Creating Value One of the concepts reinforced in ITIL (Version 5) is value co-creation. Value is not created simply because we close a ticket or complete a change. Value is created when service providers, customers, suppliers, and stakeholders achieve meaningful outcomes together. That sounds obvious. Yet many organisations still primarily measure operational success through activity metrics:

Tickets closed

Requests completed

Alerts processed

Emails answered

These metrics can provide useful operational insight, but they don't always tell us whether we are improving customer outcomes. Over recent years I've started asking a different question: What effort can we remove completely? Not reduce. Not optimise. Remove. Because every hour we eliminate from repetitive operational work becomes an hour that can be invested in improving services.

The Most Valuable Automation Is Usually Boring When people hear the word automation, they often think about advanced AI capabilities or major technology transformations. In practice, some of the most valuable improvements are remarkably simple.

Automating operational reports.

Improving data quality.

Removing duplicate administration.

Reducing alert noise.

Eliminating manual spreadsheet updates.

Automatically collecting service metrics.

These projects rarely generate headlines. Nobody gets excited about automating a weekly report. Yet the cumulative impact can be enormous. A weekly operational report is a good example. When people manually gather data, reconcile different sources, update spreadsheets, and format the results, the report can consume hours before anyone begins analysing it. Automating that preparation does more than save time. It produces consistent information, reveals patterns earlier, and allows the team to focus on what the data is telling them and what action they should take. A few saved hours each week quickly become days. Days become weeks. And suddenly operational teams have enough capacity to focus on things they have struggled to prioritise for years.

Problem management.

Knowledge improvement.

Service reviews.

Customer engagement.

Continual improvement initiatives.

Activities that directly contribute to value creation.

AI Still Needs Governance As organisations embrace AI-enabled operations, there is a temptation to focus solely on efficiency gains. However, increased automation also increases the importance of governance. Good governance ensures that automation remains aligned with organisational objectives, customer expectations, risk management requirements, and ethical considerations. AI can help us make decisions faster. It doesn't automatically help us make better decisions. That's why I see governance and automation as two sides of the same coin. Governance should not become another layer of unnecessary bureaucracy. Its purpose is to establish clear ownership, protect data, validate outputs, and ensure people remain accountable for decisions. Done well, governance enables organisations to adopt automation with confidence rather than slowing it down. One creates speed. The other creates confidence. ITIL (Version 5) acknowledges this balancing act well. As automation becomes increasingly embedded in service management practices, governance becomes more important, not less. Optimise Before You Automate Experience has shown me that automating a poor process rarely produces a good outcome. It simply allows the organisation to execute that poor process more efficiently. Before automating anything, I encourage teams to ask some simple questions:

Why does this activity exist?

What value does it provide?

Can it be simplified?

Can it be removed entirely?

Is automation the best solution?

Sometimes the best improvement is not automating a process. It's stopping it. The greatest efficiencies I've seen have often come from eliminating unnecessary effort rather than accelerating it.

Creating Space for Continual Improvement Every support team I've worked with contains people who know where improvements should happen.

They know which alerts create noise.

They know which reports provide little value.

They know which recurring issues frustrate customers.

They know where effort is being wasted.

The challenge is rarely identifying opportunities.

The challenge is creating enough space to address them.

When automation reduces operational overhead, something interesting happens. Teams begin looking beyond today's workload:

They become more proactive.

Patterns become easier to identify.

Customer experience becomes easier to improve.

Conversations shift from managing queues to improving services.

In my view, that's where the real promise of service management exists. A useful place to start is with one recurring activity that consumes more capacity than it should. Ask whether it still provides value, whether it can be simplified, and whether it should be automated or stopped altogether. Small changes can create the space needed for more meaningful improvement.

Final Thoughts For many years, IT organisations have measured success by how effectively they manage operational work. I believe the next evolution is measuring how effectively we reduce unnecessary operational work. Not because less work is the goal. But because creating capacity allows us to focus on the activities that matter most.

Continual improvement.

Governance.

Customer experience.

Value creation.

The effective management of digital products and services.

Automation is not the destination. It is the enabler. And perhaps the most exciting thing about today's automation capabilities is not that they can perform work for us. It's that they can finally give us enough time to do the work ITIL has been encouraging us to do all along.

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.