ITIL in non-IT environments: how ITIL helped a healthcare organization create accountability, consistency, and continual improvement beyond IT

Farooq Hussain – IT operations and service delivery leader

Does ITIL have a role beyond providing a practical, globally recognized framework for managing IT services, product and service lifecycles and governing AI? After asking the ITIL community for their experiences, we found it does.

Farooq Hussain – IT operations and service delivery leader and ITIL Master – explains how the adoption of ITIL during a large-scale ITSM transformation program also migrated to non-IT functions in a major Middle East healthcare organization:

A healthcare authority responsible for operating hospitals and more than 60 primary healthcare facilities in the Middle East was adopting ITIL during a large-scale ITSM transformation program.

But the role of ITIL didn’t end there. The CIOs involved became interested in how it could be applied more widely in the organization.

Consequently, ITIL principles were adopted not only within IT but also embedded into clinical support services, patient-facing service operations, and facility management workflows to create a unified, service-oriented operating model across the organization.

This broader adoption reflects a shift many organizations are experiencing today. As services become increasingly interconnected, challenges such as accountability, process consistency, performance visibility, and continual improvement are no longer confined to IT departments. ITIL provides a common framework for managing these challenges across any function responsible for delivering services and supporting organizational outcomes.

While ITIL is probably best known for supporting the work of IT service management-related activities, how did the framework become the go-to approach for other, non-IT functions?

Service lifecycle thinking

The organization was trying to manage a fragmented service environment across numerous hospitals. This meant inconsistent escalation paths, no standardized request fulfillment process, and limited visibility into service performance outside of IT.

Clinical support teams were experiencing operational pain points that mirrored those normally seen in IT: unresolved requests, unclear ownership and reactive rather than proactive service cultures.

Directors of HR and facilities management equally wanted to see improvements to the existing manual, paper-based working and lack of accountability in teams.

These decision makers recognized that ITIL's service lifecycle thinking — particularly incident management, service request fulfillment and continual improvement — offered a language and structure applicable far beyond IT.

Therefore, we created a three-year vision, with the first phase involving a service catalog for HR, containing all the services the department delivered, then designing and implementing workflows.

In that context, ITIL offered a proven, adaptable framework to bring structure and accountability to any service-delivering function, not just technology. While often associated with IT service management, ITIL's underlying principles of value delivery, service ownership, governance and continual improvement are relevant wherever organizations need to deliver consistent, measurable services to customers, employees or stakeholders.

Translating ITIL for non-IT professionals

As IT administrator, involved from inception to closure of the transformation program, it was my responsibility to educate non-IT people about ITIL.

Initially, this was difficult: people were accustomed to the existing systems and, naturally, they questioned the need for ITIL principles.

For example, a customer service agent for the HR team asked why it was necessary to log employee queries, such as requests for salary slips. I asked her: “At the end of a period, how do you measure your performance, KPIs, SLAs when email platforms and spreadsheets won’t do it for you?” She immediately understood the concept.

So, we involved HR managers and directors to create a small project team, drill down into existing processes and define how things could be improved by automating processes based on customer service performance and including initiatives like recognizing employees of the month. It took a few months to see the value of ITIL, but then it was taken forward.

Turning ITIL theory into practicality

The success of the initiative depended less on introducing ITIL terminology and more on translating its principles into practical behaviors and day-to-day routines. Rather than asking teams to adopt an IT framework, the focus was on solving operational challenges while creating greater visibility, accountability and consistency.

The right approach to use was helping the department adopt ITIL principles by turning them into practical ways of working rather than presenting them as a formal IT framework.

This meant bringing structure to a complex program involving clinical, workforce, procurement, compliance, vendor, and technology teams. I supported this by:

• •  Helping define the service outcomes
• •  Clarifying roles and responsibilities
• •  Documenting key processes
• •  Identifying handoffs
• •  Surfacing risks and dependencies
• •  Ensuring decisions were captured and actioned.

I also used ITIL-aligned thinking in workshops, governance discussions, vendor engagement and implementation planning. For example, I encouraged teams to consider service ownership, demand management, change impact, operational readiness, reporting, support responsibilities and continual improvement from the beginning, rather than treating these as post-implementation issues.

When changing existing processes, newer employees were the first to embrace ITIL and were ultimately recognized as employees of the month. Eventually, all teams adopted these changes as the new ways of working.

To help ITIL continue as part of operations, I focused on embedding the principles into program artifacts and routines, including process maps, decision registers, risk logs, governance packs, meeting actions, service design discussions and operational readiness planning.

Ownership, accountability and continual improvement

Adopting ITIL principles across clinical support and operations delivered measurable outcomes for the organization:

• •  Standardized request fulfillment reduced informal, verbal requests and introduced trackable workflows with defined service level agreements (SLAs) for facilities, supplies, and patient support services.
• •  Incident categorization was applied to operational disruptions (equipment failures, bed management issues, supply chain delays), enabling faster escalation and resolution.
• •  A culture of ownership and accountability replaced the previous reactive, siloed approach. Staff understood their role within a service chain rather than viewing work as isolated tasks.
• •  Continual improvement thinking was embedded in team reviews, with departments tracking their own performance metrics, mirroring what IT teams had been doing for years.
• •  Cross-functional collaboration improved significantly as clinical and IT teams began speaking the same service management language, reducing friction during joint incidents.

The key factor was making ITIL usable for non-IT stakeholders. By avoiding heavy terminology and using plain language around value, ownership, consistency, accountability, risk, service quality and improvement, this helped business teams apply the principles in their own context and continue using them as part of the way they designed and managed services.