What Is ITIL and ITSM? A Beginner’s Guide to IT Service Management

Every time you reset a password, request a laptop, report a slow application or wait for a system to come back after an outage, you are on the receiving end of IT service management. Behind a smooth experience there is usually a set of agreed practices; behind a chaotic one there usually is not. ITIL is the best-known body of good practice for running IT services well. This lesson opens a 27-part series that takes you from the basic vocabulary through every major practice to implementation, tools, certification and interview preparation.

What Is IT Service Management (ITSM)?

IT service management is the way an organisation designs, delivers, supports and improves the IT services its customers and employees rely on. The key word is service. Users do not want servers, licences or code for their own sake; they want email that works, an HR portal they can log in to and a payment system that does not fall over. ITSM focuses on delivering those outcomes reliably, rather than on managing technology components in isolation.

What Is ITIL?

ITIL (originally the Information Technology Infrastructure Library) is a framework of good practice for ITSM. It began in the 1980s as guidance written for the UK government, grew into ITIL v2 and ITIL v3 (2007), and was reworked as ITIL 4 in 2019 to fit Agile, DevOps and digital ways of working. Since 2021 it has been owned by PeopleCert. A new edition, ITIL (Version 5), was introduced in early 2026, with its Foundation syllabus published in February 2026.; the core ideas you learn here carry across, and lesson 25 explains how the two versions relate.

Two points often confuse beginners. First, ITIL is guidance, not law: nobody “certifies your company as ITIL compliant”. Second, certifications are for individuals. Organisations that want a certifiable management-system standard usually look at ISO/IEC 20000 instead.

Why Organisations Use ITIL

Without shared practicesWith adopted ITSM practices
Requests arrive by email, chat and phone; some are lostOne front door, every request recorded and tracked
The same outage returns every monthRoot causes are investigated and removed
Changes break production unexpectedlyChanges are assessed, scheduled and reviewed
Users do not know what to expectService targets are agreed and reported
Knowledge lives in a few headsSolutions are captured and reused

How ITIL Compares With Other Approaches

ApproachWhat it isHow it relates to ITIL
ISO/IEC 20000International standard for a service management system, certifiable for organisationsOften adopted alongside ITIL, which supplies practical guidance
COBITGovernance and management framework for enterprise ITWorks at the governance level; ITIL works at the service level
DevOpsCulture and practices that join development and operationsITIL 4 explicitly aims to work with it (see ITIL with Agile, DevOps and SRE)
SREEngineering approach to reliability, with targets and error budgetsComplements service level management

What You Will Learn in This Series

  • Lessons 1 to 6: the concepts: the service value system, guiding principles, four dimensions, value chain and key terms.
  • Lessons 7 to 20: the practices, from Incident Management and Change Enablement to availability, supplier and security management.
  • Lessons 21 to 27: ITIL with Agile and DevOps, tools, metrics, implementation, certification, interview questions and templates.

A Short Example

A 300-person company runs IT through a shared mailbox. Requests are sometimes forgotten, outages are fixed with no record of what was done and nobody knows how many tickets arrive each week. The IT manager begins small: a ticketing tool, three request categories, a simple priority scheme and a weekly review of repeat issues. Within a quarter, she can show how many incidents occur, which ones recur and how long fixes take. That is ITSM in practice: not a big-bang programme, but a handful of sensible habits that grow.

Common Myths

  • “ITIL means lots of paperwork.” Done well, it removes confusion; heavy paperwork is a sign of poor adaptation.
  • “ITIL is only for big companies.” The ideas scale down; a team of five can use incident, request and change practices in a lightweight form.
  • “ITIL is a tool.” Tools support the practices; they are not the practices.
  • “You must implement everything.” ITIL is a library to choose from, not a checklist to complete.

Common Mistakes

  • Buying a tool first and designing the practices later.
  • Copying the framework word for word instead of adapting it to your size and culture.
  • Measuring activity (tickets closed) instead of outcomes (users able to work).
Key takeaways
  • ITSM is about delivering reliable services that produce outcomes users care about.
  • ITIL is a framework of good practice: guidance to adapt, not a law or a tool.
  • ITIL 4 (2019) modernised the framework; ITIL (Version 5) followed in February 2026 and builds on the same foundations.
  • Start small, adapt to your context and improve continually.

Related Lessons