Is ITIL Certification Worth It for an Admin?

The certificate is on the wall. It is framed, which took longer than the exam. The fee is on last month's expense report, approved. And the study guide is on the shelf with a bookmark two-thirds of the way through, where the practice questions begin. It is Tuesday. The queue looks exactly as it did on the Tuesday before the exam: forty-one open, two urgent, one waiting on a supplier since the office moved. Nothing about the certificate has touched the queue, and nobody promised it would. That is the thing to understand before you book it.

ITIL is a published framework of good practice for managing IT services. It is a vocabulary and a set of ideas about running IT as services people rely on, rather than as a collection of machines. It is not software and not a law, and an organization cannot be certified in it; a person can. The entry-level certificate, usually called the foundation level, says its holder has learned the vocabulary and the main ideas and passed a multiple-choice exam about them. Whether that is worth a working administrator's days is the question this article tries to answer plainly, as part of our Pragmatic ITIL series. Some of the answer is fact and some is my opinion, and I will say which is which.

It covers what the foundation certificate teaches and how long that takes, and what it does not teach. Then it covers what it signals to an employer and how that changes with the size of the organization. Next come the honest cost, when it is worth it and when it is not, and what else the same days could buy. A decision table follows, along with a worked example of studying for it without losing a month. It finishes with a war story about the one thing a certificate turned out to be good for.

What the Foundation Certificate Teaches

The foundation certificate teaches the vocabulary. A service is something IT provides that people rely on; an incident is something broken. A request is something wanted; a problem is the underlying cause of incidents. A known error is a problem you understand but have not fixed; a change is a deliberate alteration to production. A service level is a promise about speed or availability; continual improvement is changing how you work on purpose. The exam checks that you can tell these apart and know which practice owns each one. That is most of the syllabus. The same terms, with the help-desk words that ITIL leaves out, are in The Help Desk Glossary.

It also teaches the ideas underneath the words, which are the useful part. Separate the kinds of work. Write down what you offer. Learn from repeats instead of re-diagnosing them. Change with a note and a brain. Improve from numbers, in small steps. The framework wraps those ideas in a lifecycle, from deciding what to offer through running it to retiring it, and in a list of named practices. The certificate asks you to recognize the shape, not to have run any of it.

The time it takes is modest. Most working administrators need a few days of reading, or a short course, and the exam itself takes about an hour. People who have run a desk find the material familiar and the vocabulary slightly strange, like hearing your own house described by a real estate agent. The exam measures whether you can tell an incident from a problem under mild time pressure. Most people can.

What It Does Not Teach

It does not teach how to run your desk. Nothing in the syllabus covers triage at 09:00 or the three-line resolution note. It does not cover how to decline a forty-field ticket form, or which of the framework's processes will drown a three-person team. The framework is written to fit every organization, which means it is written to fit none of them exactly. Your size is a footnote. The adaptation to a small desk, the part that decides whether any of it helps, is left to you, and it is the hard part.

It does not teach your tool. The exam will not tell you that your ticket system's SLA clock keeps running while a ticket is on hold. It will not tell you that your knowledge base has an agents-only state where a known-error list can live. QuerySolv's documentation, for instance, states plainly that its SLA clock does not pause on hold and excludes only non-working hours and holidays. That is the kind of fact you learn from a manual and a bad afternoon, not from a syllabus. A certificate holder who has not read their own tool's limits page knows the word for what went wrong and nothing about why.

It does not teach judgment, which is what the vocabulary is for. Knowing that a slow login is a problem rather than an incident is worth nothing until someone decides it is worth two days to fix. I passed the exam some years ago and went back the next morning to a queue that had not read the syllabus. The queue was unmoved. The vocabulary helped me describe it, which is a smaller thing than fixing it, and still a real thing.

What It Signals to Employers

To an employer, the certificate signals two things: familiarity with the vocabulary, and a willingness to study for and take an exam. Both are real signals and neither is large. The first matters where the organization already speaks the language, which means larger IT departments, public-sector bodies, managed-service providers, and anywhere with a service management team. The second matters everywhere and is cheap to send in other ways.

The weight varies with the size of the organization, and it varies a lot. In a large organization, a job advertisement for a service desk analyst may list the certificate as required. The recruitment system may filter on the word before a human reads anything. In a thirty-person company, the hiring manager wants to know what you fixed last month and whether you can be left alone with the file server. Most small-shop interviewers have heard of the certificate and do not ask about it. Some have not heard of it and still do not ask.

Be honest with yourself about what kind of signal it is. It is a line on a résumé that passes a filter and matches the vocabulary of the interview. It is not a demonstration that you can run a desk, and an interviewer who has run one will test that separately. Certificate culture tends to forget this. The wall is where the certificate does its best work.

The Honest Cost

The honest cost is a few days and an exam fee. The days are study time, in evenings or on a course. The exam is about an hour, booked in advance, sometimes with a renewal expected some years later. Some employers pay the fee and give the days; many will if asked and shown a reason. No prices here, because they change and because the fee is not the expensive part.

The expensive part is what the same days could have bought instead. A few days is a scripting course that returns an hour a week forever. It is the thirty-day plan for one of its weeks. It is half the study for a security certificate that small-shop interviews ask about more often. The question is never "is it worth it", which has no answer. It is "worth it compared with what", which does.

When It Is Worth It

It is worth it when you are moving toward a larger organization. If the next job is in a department of forty, a public body, or a managed-service provider, the certificate is expected furniture. In that case, not having it costs you the filter stage before anyone sees what you can do. The same applies when you are moving toward a service management role: service desk lead or service delivery manager. It applies to anything with "service" in the title and a reporting line to someone who has the certificate too.

It is worth it when you must speak to auditors, customers' security reviewers, or a board that uses the words. The certificate does not make your desk better, but it lets you describe your desk in the language the listener expects, with confidence. And that is worth something at the moment the question is asked. How to do that without overclaiming is the subject of Talking ITIL With Management Without Lying. The vocabulary is the entry ticket to the conversation.

It is worth it when your employer pays, gives you the days, and asks. Declining free knowledge on principle is a strange hill. Say yes, read the vocabulary chapter twice, pass, and spend the saved anxiety on something else.

When It Is Not

It is not worth it when the next five years are hands-on at a small shop and you want them to be. The vocabulary will not shorten the queue, and the shop will not ask for it. A scripting course, a security certificate or deep knowledge of the one tool you run all day will each return more, sooner. Each will be asked about in more interviews at organizations your size.

It is not worth it when what you want is for the desk to get better. A certificate is a description of good practice. The desk improves when practice changes. Practice changes through the field, the page and the habit, not through the exam. If a manager has asked for "ITIL" from the desk by the end of the quarter, the answer is A Lightweight ITIL Implementation in Thirty Days, which changes the desk, and not a certificate, which changes the wall.

It is not worth it when you are paying for it yourself and your evenings are scarce. The study is pleasant enough, and the vocabulary is available free in this series and elsewhere. The part you pay for is the exam and the line on the résumé. If that line is not going to be read by anyone who weighs it, you have bought a frame.

The Alternatives for the Same Days

The alternatives are better than the certificate for most small-shop administrators, and they are not secret. Read the framework's ideas in plain words, starting with ITIL in Plain Words, which gives you the vocabulary in an afternoon with no exam at the end. Run the thirty-day plan, which gives you five one-page documents and three numbers that answer any auditor better than a certificate does. Take a scripting course, which returns time every week. Study for a security or cloud certificate, which interviews at small organizations ask about more often and which touches work you do every day.

The best alternative of all is to learn the corners of the tool you already run. Every ticket system has reports nobody opens, visibility states nobody set, and limits nobody read until they mattered. A day with the manual and the limits page returns more to a small desk than a week with the framework, because the tool is where the desk lives. The framework is where the desk is described.

The Decision Table

The table below puts the same few days against the situations administrators actually find themselves in. Find your row. The right-hand column is the honest spend, and it is the certificate in fewer rows than certificate culture would like.

Two rows deserve a note. The service-role row says the certificate first, because recruiters for those roles look for it before they look at you. It says the thirty-day plan second, because the interview will ask what you have actually done. The last row is the one most experienced small-shop administrators belong in, and it is the row that costs nothing and gets skipped most.

A Worked Example: Five Evenings at Bluewater Bank

Marcus ran branch IT for Bluewater Bank, a desk of two covering six branches. He was moving to a service desk lead role at headquarters, where the job description listed the certificate. The bank paid the fee and gave him nothing else, which is the usual arrangement. He gave the study five evenings, ninety minutes each, and refused to let it take the weekend.

Monday was the vocabulary: the ten terms, written on one page in his own words beside the framework's words. Tuesday was the ideas and the lifecycle shape, which took forty minutes. The rest was reading the chapter on practices with the branch desk in mind. Wednesday was a practice exam, scored at 62 percent, with every wrong answer noted. Thursday was a second practice exam at 78 percent and a list of the six terms he kept confusing. All of them were about the difference between a practice and a process. Friday was those six terms and nothing else. The exam was the following Tuesday at 10:00, took forty minutes, and he passed with margin. The whole thing cost eight and a half hours, which is less than one bad week of the branch print server.

What changed afterward is the instructive part. The branch queue did not change. The interview did. When asked how the branch handled recurring faults, Marcus said "we keep a known-error list and treat it as the lightweight end of problem management". That is exactly what the branch did and exactly what the interviewer wanted to hear said in those words. He also rewrote the branch's one-page how-we-work note with both vocabularies, the branch's and the framework's, side by side. His successor still uses it. That page did more for the branch than the certificate, and the certificate did more for Marcus.

A Short War Story: Dana at Northgate Retail

Dana ran the desk at Northgate Retail for six years before the company asked her to take the foundation exam ahead of an audit, and paid for it. She studied for four evenings, passed, and framed nothing. When the auditor asked whether the desk followed ITIL, she answered that it ran incident and request handling through one ticket queue. She said it kept a known-error page, wrote a note before every change, published a one-page catalog, and read three numbers monthly. The auditor wrote it down and moved on. Afterward Dana said the useful part of the exam had been learning the names for what the desk already did. That way, she could say them out loud without hedging. The desk itself was the same desk it had been in the spring.

I have watched that happen more than once: the certificate changes the sentence, not the desk. That is a smaller benefit than the brochure implies and a larger one than the skeptics allow. Which side you land on depends on how often someone asks you the sentence.

My Opinion, Labeled as Such

Here is my opinion, and it is only that. For most administrators at small organizations, the foundation certificate is a decent thing to have paid for by someone else and a poor thing to pay for yourself. The vocabulary is worth learning regardless, and it is free. The exam is worth taking when a door it opens is one you want to walk through, and not otherwise. The queue will not notice either way.

My second opinion is that the certificate is most dangerous when it is mistaken for the work. A team that has three certified people and no known-error list has studied the framework and not adopted it, which is the usual order and the wrong one. If you have the days, run the thirty-day plan first and take the exam second. The exam is easier after you have done the thing it describes, and the interview is easier still.

The certificate on the wall is still on the wall. The queue is still forty-one on Tuesday. Both of those are fine, provided you knew which one you were buying. The framed one was never going to shorten the other, and the people who say it will are, as a rule, selling the frame.

Frequently Asked Questions