InnovationTemplate / formModelAccessible

Information Technology Infrastructure Library (ITIL®)

How can information technology infrastructure library (itil®) support strategic choice or positioning?

AccessibleStrategicTeam2 min read

Contents

The Information Technology Infrastructure Library (ITIL®) is a framework for designing the governance and service processes within an IT organisation.

The Information Technology Infrastructure Library (ITIL®) is a body of guidance for managing IT-enabled products and services. It helps organisations connect service management with stakeholder value, governance, risk, continual improvement and day-to-day delivery.

When to use it

Use ITIL when digital services depend on repeatable management practices across people, partners, technology and workflows. It is relevant when an organisation needs to improve service quality, clarify ownership, manage incidents and changes, align technology work with business outcomes or create a common service-management language.

ITIL can complement rather than replace other frameworks and standards, including:

COBIT for governance and control
Six sigma for quality improvement
TOGAF for enterprise architecture
ISO 27000 for information security
ISO/IEC 20000 for service-management systems.

The comparison with ISO 9000 is limited: ITIL offers adaptable guidance, while ISO standards define requirements that may support formal conformity assessment. Adopting ITIL language or certificates does not by itself certify an organisation’s service-management system.

Origins

The UK government’s Central Computer and Telecommunications Agency began developing ITIL in the 1980s to improve public-sector IT management. The guidance expanded and was adopted internationally. Version 3 appeared in 2007 and was revised in 2011. Ownership and certification arrangements later changed; the current generation is ITIL four, administered through PeopleCert, and it replaces the earlier lifecycle-centred architecture with a service value system.

What it is

ITIL is flexible guidance, not a mandatory process manual. The current service value system connects guiding principles, governance, a service value chain, management practices and continual improvement. It also asks practitioners to consider four dimensions: organisations and people; information and technology; partners and suppliers; and value streams and processes.

The historical version 3 lifecycle, released in 2007 and updated in 2011, organised guidance around strategy, design, transition, operation and continual improvement. Those concepts remain useful context, but an organisation starting now should use the current guidance rather than treating the old lifecycle as the latest edition.

How to use it

Begin with the service, its consumers and the value or outcome to improve. Map the current value stream, failure demand, constraints, risks and measures. Select only the ITIL practices that address those needs, then adapt roles, controls and workflows to the organisation’s size and regulatory context.

The earlier five-volume lifecycle issued in 2011 described:

Service strategy – defining customers, needs, offerings, capabilities and value.
Service design – designing services, architecture, processes, measures and controls.
Service transition – building, testing and introducing new or changed services.
Service operation – running services, restoring disruptions, fulfilling requests and controlling access.
Continual service improvement – reviewing outcomes and improving services and management practices.

The historical edition described 26 processes and functions supported by standards, cases, templates, scaling guidance, qualifications and governance methods. Current ITIL practice guidance goes beyond process steps to include stakeholders, responsibilities, technology, knowledge, communication and value streams.

Implement iteratively. Establish a baseline, choose a measurable service outcome, co-design the change with the people doing and receiving the work, run a limited improvement, measure effects and adjust. Preserve effective local practice instead of forcing terminology. Integrate security, architecture, product, agile and supplier-management approaches where they add value.

Final analysis

ITIL can improve consistency, shared understanding, service reliability and learning. Benefits depend on adoption quality, leadership support and fit with culture. Heavy documentation, certification theatre or copying another organisation’s process can increase bureaucracy without improving a service.

Continual improvement is strongest when it applies to the management system itself. Review whether each practice still helps users and service outcomes, not merely whether staff comply with its procedure.

Top practical tip

The five lifecycle volumes published in 2011 remain useful history, but use the current ITIL service value system and practices for new adoption. Start from a service outcome and tailor the guidance.

Top pitfall

Do not turn ITIL into a rigid process overlay. Without cultural fit, ownership and outcome measures, added controls can slow teams while leaving customer experience unchanged.