ITIL: The Rulebook of IT Service Management
- ITIL
- ITSM
- incident management
- problem management
- change management
- priority
- impact
- urgency
ITIL - The Rulebook Every IT Department Runs On 🎫
The scene. Your model is live. At 3 a.m. it stops responding. Who gets called? How is the outage tracked? Once it's fixed, who makes sure it never happens again? In any serious company the answer is one framework: ITIL - the playbook that turns "everything is on fire" into a calm, repeatable process.
What it stands for: ITIL = IT Infrastructure Library. It is not software you install - it is a globally adopted framework of best practices for ITSM (IT Service Management): how an organisation delivers and supports IT as a dependable service.
🧠 The mental model: a hospital for IT
A hospital never improvises when a patient arrives - it has triage, departments, and procedures. ITIL gives IT that same discipline: every issue is logged, prioritised, routed, and resolved by a known process, so nothing depends on the one hero who happens to remember the fix.
The practices you'll actually hear named
| Practice | Its one-line job | Example |
|---|---|---|
| Incident Management | restore service fast | "the trading app is down - get it back now" |
| Problem Management | find the root cause so it never recurs | "why did it crash? fix that" |
| Change Management | review risky changes before they ship | "approve this database upgrade" |
| Service Request | handle routine asks | "please grant me access to the reporting tool" |
🔑 The distinction interviewers love - Incident vs Problem: An incident is a single outage - you restore service (a workaround counts). A problem is the underlying cause behind one or more incidents - you eliminate it. Restarting the server to get users working = incident handling. Finding the memory leak so it never crashes again = problem management.
Priority = Impact × Urgency
ITIL does not fix tickets first-come-first-served. Each ticket gets a priority from two questions:
- Impact - how much of the business is affected? (everyone vs one person)
- Urgency - how fast must it be fixed? (right now vs whenever)
A bank-wide outage (high impact, high urgency) is a P1. A single broken printer (low, low) is a P4. Real ITIL reads priority off an impact × urgency matrix (a lookup table); this lesson approximates that by simply adding the two 1–3 scores - so a higher combined score means a higher priority.
🔧 You already use ITIL-shaped tools
A Jira or ServiceNow ticket, a status page, an on-call rota - those are ITIL practices made concrete. You have met the framework without knowing its name.
Your Task
Score a queue of tickets the ITIL way: combine impact and urgency into a priority, and label each one P1 / P2 / P3. Predict first: which ticket is the P1?