Services, outcomes, service roles and utility

What a service is, and the word the definition turns on

A service is a way of helping somebody reach a result they want, where the provider takes on some of the cost and risk of getting there. The exam wording of this leans hard on one qualifier: SPECIFIC costs and risks. A service does not abolish cost and risk, and pretending otherwise is the trap in half the questions on this objective. It moves a particular set of them off the consumer — buying the hardware, hiring the specialists, carrying the failure — and hands back a different set, starting with the price and with dependence on somebody else.

The second load-bearing idea is that value is co-created rather than delivered. The provider cannot produce the result on its own; the consumer has to bring something — its own people, its own data, its own decisions — or nothing useful happens. An answer that describes value flowing one way, from provider to consumer, is describing the model ITIL 4 deliberately moved away from.

Outputs are handed over. Outcomes are what change

An output is a deliverable: a file, a report, a configured laptop, a payment instruction. An outcome is the difference that deliverable makes to somebody — staff actually get paid, the report actually changes a decision. The two are easy to state and easy to confuse under time pressure, because a scenario question will describe several tangible things and one consequence and ask which is which.

The test that survives the exam room: outputs are what the provider can point at and say "we produced this"; outcomes are what the consumer can point at and say "this is now different for us". A provider can deliver every output perfectly and the outcome can still fail, which is precisely why ITIL insists on measuring the second. Note also that the ACTIVITY is neither — a monthly processing run is the work, not its output.

Three roles, and why they are separated at all

The customer defines what is needed and carries responsibility for the result. The user is whoever actually works with the service. The sponsor authorises the money. In a small organisation one person holds all three, and the separation still matters, because in a large one they are three people who want different things and a question will describe exactly that friction.

Questions here almost never use the role name. They describe behaviour and expect you to read it: somebody who signs off the annual budget and has never logged in is a sponsor; somebody who raises a ticket every week and has no say over what the service should do is a user; somebody who states the requirement and answers for whether it was met is the customer. Read for accountability, not for seniority.

Utility: the half that answers "what does it do"

Utility is the functionality — what the service is capable of, whether it fits the purpose you have for it. Hosting a meeting of two hundred people and recording it is utility. It is the half of the fitness pair that this lesson introduces; the other half, warranty, is the next lesson, and the exam most often tests them by describing a service in a single paragraph and asking you to sort the sentence into one or the other.

The sorting rule is short. If the sentence says what the service CAN DO, it is utility. If it says how reliably, how securely or how available it does it, it is warranty. Numbers with percentage signs are almost always warranty; feature lists are almost always utility.