Pragmatic ITIL for a Small Team

"Do you follow ITIL?" The question arrives from an auditor with a checklist, a new manager with a slide, or a customer's security questionnaire. It lands on the one person in the building who runs the desk. The honest answer is usually "we follow Dana", which is a process, just not a published one. ITIL is a published framework of good practice for managing IT as a set of services. It was written with large departments in mind, and the shelf it occupies is taller than most small IT teams. The question that matters for a desk of one to five people is not whether to follow it. It is which parts to take.

This series is the plain answer. It is written for the administrator who has heard "we should be doing ITIL" and wants to know what that means. They want to know before anyone buys a binder, prints a process diagram, or convenes a change advisory board for two people. The series covers what ITIL is and is not, in plain words, with the ten terms worth learning. It covers the five ideas a small desk should steal and the smallest version of each. It covers the processes that will drown a three-person team and how to cut them without losing what they were for. Then comes a thirty-day plan for adopting the useful parts on the tool you already have. It covers whether the certification is worth an administrator's time. And it covers how to describe what you actually do in framework language without lying.

Articles in This Series

• ITIL in Plain Words
  What the framework is and is not; the ten terms worth learning, in a table; and the five ideas underneath the vocabulary. Covers what a three-person team can safely ignore, and how to answer the auditor honestly.
• The Five ITIL Ideas Worth Stealing
  Incidents versus requests, the known-error list, a note before every change, a one-page catalog and one improvement a month. Covers the smallest version of each, what it looks like in a ticket tool, and a one-page starter sheet.
• The ITIL Processes That Drown a Small Team
  The weekly change board, the forty-field form, the eighty-entry catalog, the twenty-cell SLA matrix, the eleven-title role chart and the review of the review. Covers how to recognize them, the cuts, and a process-diet checklist.
• A Lightweight ITIL Implementation in Thirty Days
  Week by week on the tool you have: separate the work, start the known-error list, add the change note, read the first numbers. Covers five one-page documents, three numbers, and the honest sentence for day thirty.
• Is ITIL Certification Worth It for an Admin?
  What the entry-level certificate teaches and does not, what it signals to employers, and the honest cost in days. Covers when it is worth it and when a scripting or security certification pays faster, with a decision table.
• Talking ITIL With Management Without Lying
  Why the question comes up, and a translation table from what you do to the framework phrase and the evidence for it. Covers what never to claim, and a one-page "how we work" statement for the audit conversation.

Explore More Topics

This series is part of the QuerySolv helpdesk topic library. It covers the foundations, processes, communication, knowledge, tooling, metrics, classic ticket domains, people and strategy behind a support desk that works. The library pairs well with the software we build: QuerySolv. It is a self-hosted help desk that runs as one Windows service on your own network. It is licensed once per installation, not per agent per month.