ITIL Is a Shared Language for Tickets

ITIL is a shared language for tickets. ITIL 4, the 2019 revision, still sells the same useful nouns: incident, problem, change, service.¹ The desk can say “this is an incident” and mean a restore, not a root cause, and the change board can say “this needs enablement” without inventing a dialect per team. That is the product worth keeping.

I do not hold ITIL Foundation. Dark Heart Labs does not run a service desk. mystic-bytes ships markdown. I still hear the words in other people’s queues, from Auckland, because the language leaked into every tool that copied a ticket form.

The honest product is the glossary. A problem is not a pile of incidents with a louder subject line. Change is not a Slack thumbs-up. When an org is large enough that the person who writes the fix is not the person who answers the phone, you need English that survives a shift handover. ITIL 4 wrapped that English in a Service Value System and a list of practices. The wrapper is optional. The nouns are not.

The failure is process English as a substitute for shipping. You can have a perfect incident record and a frozen change calendar and still not restore the thing. Foundation is a two-day vocabulary course wearing a certificate. Buy the vocabulary if your desk is real. Do not buy the ceremony as proof the service improved.

— JV · Dark Heart Labs.

References

AXELOS / PeopleCert, ITIL 4 (2019) and ITIL 4 Foundation, https://www.peoplecert.org/browse-certifications/it-governance-and-service-management/ITIL-1. Incident, problem, and change as shared ticket English; the Service Value System as the wrapper, not a syllabus. ↩