ITIL, Charted for Anyone Who's Ever Sailed Through a Ticket Queue

5 hours ago

2 min read

Every IT team has a story that starts with "we've always done it this way." ITIL is the navigation chart that gets you out of that story.

ITIL (Information Technology Infrastructure Library) treats IT as a service, not a pile of tickets and servers. ITIL 4 rests on one idea: technology exists to create value for the people who depend on it.

Here's how to read the chart.

Note: ITIL Version 5 launched in January 2026, but all 34 management practices carry over, so everything below still holds.

The Compass: 7 Guiding Principles

Focus on value: If it doesn't help the person on the other end, question it.
Start where you are: Don't scuttle a ship that still floats.
Progress iteratively: Small course corrections beat one giant turn.
Collaborate and promote visibility: Silos are where problems hide.
Think and work holistically: Services are whole ecosystems, not parts.
Keep it simple and practical: Cut every step that adds weight but no value.
Optimize and automate: Fix the process first, then automate it.

Example: Your laptop refresh has 14 approval steps. Keep it simple: audit them and cut the ones that add delay, like with the MDT. Then automate what's left.

The Voyage: The Service Value Chain

Six activities carry demand from idea to delivered value: Plan, Improve, Engage, Design & Transition, Obtain/Build, and Deliver & Support.

Example: launching a new VPN

Plan: Remote access is now mission-critical.
Engage: Ask users what they need before you buy anything.
Design & Transition: Pilot with one department first.
Obtain/Build: Procure and configure.
Deliver & Support: Train staff and brief the help desk.
Improve: Collect feedback and tune.

The Crew: Key Practices

ITIL names 34 practices, and these are the ones you'll use often:

Incident Management: Restore service fast. A clinic can't log in, so you apply a workaround and get them working.
Problem Management: Find the root cause. Why did logins fail? An expired certificate nobody tracked. Fix it for good.
Change Enablement: Change safely. A firewall update gets a risk assessment, approval, and a rollback plan.
Service Request Management: Handle routine asks cleanly. A new hire gets an account and a laptop through one standard workflow.
Service Level Management: Set expectations you can keep. "P1 incidents get a response in 15 minutes."

The Siren's Take

Incident management is the fire response, problem management is fire prevention, and change enablement is the building code. A mature shop does all three.

ITIL isn't a rulebook to follow word for word. Take what fits your waters, leave what doesn't, and keep improving. Teams that treat it as scripture get stuck in process. Teams that treat it as a chart reach the destination.

Reference Links

Want more breakdowns like this? Subscribe to The Siren's Briefing and follow @sirenofthecybersea.