Key concepts of service management

Key concepts of service management is the vocabulary objective: what a service actually is, who the parties to it are, and the handful of paired terms — utility and warranty, output and outcome, cost and risk — that the rest of the syllabus is built out of. Objective 1 of ITIL 4 Foundation, worth 12.5% of the exam.

Share of the exam
12.5%
Questions in a real sitting
roughly 5 of 40
Questions in this bank
15
Signed for by a person
0
Machine-checked only
15

Partly checked. None of the 15 questions here has been read against the cited source by a person. 15 questions have been checked against their cited clause by an automated pass — which is not the same thing, and is not a signature.

Only questions a person has signed for are used in mock exams here. That is the whole difference between the two kinds of checking above.

How these questions are written — where each question comes from, what the verification ledger records, and what happens when one is found wrong.

What this objective covers

The 15 questions written for this objective cite 1 ITIL 4 syllabus clause (1).

They break down as 15 single-answer questions.

What this objective is really about

This is the objective that defines the words. Almost every other part of ITIL 4 assumes you already know what a service is, what value means, and who the customer is as distinct from the user and the sponsor. Candidates who skim this section tend to lose marks much later, on questions that look like they are about incident management or the service value chain but actually turn on one of these definitions.

The central idea is that a service is a way of helping someone achieve an outcome they want, while taking on some of the cost and risk they would otherwise carry themselves. Notice how much work the word "some" does there. A service does not remove every cost and every risk — it typically introduces new ones, starting with the price and the dependence on the provider — and the exam tests whether you can hold both halves of that in mind at once.

The paired terms, and why they are paired

Utility and warranty are the pair candidates confuse most. Utility is what a service does: the functionality, the capability, whether it fits the purpose you have. Warranty is how dependably it does it: availability, capacity, security, continuity, whether it is fit to actually use. Both are required. A service with the right features that falls over twice a week does not deliver value, and neither does a rock-solid service that does the wrong thing.

Output and outcome are the second pair. An output is something the provider hands over — a file, a report, a working laptop. An outcome is what changes for the person receiving it. Outputs can be delivered perfectly while the outcome fails completely, which is why ITIL insists on measuring the second rather than the first.

Cost and risk are the third, and they are the ones with a direction. Each runs both ways: a service removes some costs and risks from the consumer, and imposes others. Judging value means weighing both directions, not just counting what was removed.

Roles, and why there are three of them

On the consuming side, ITIL separates the customer, the user and the sponsor. The customer defines what is needed and owns the outcome. The user is whoever actually uses the service day to day. The sponsor authorises the money. One person can hold all three roles, and in a small organisation often does — but they are separated because in a large one they are usually different people who want different things.

The exam likes scenarios where a role is described by its behaviour rather than named. Someone who signs off the budget but never logs in is a sponsor. Someone who reports a fault every week but has no say in what the service should do is a user. Read for what the person is accountable for, not for their job title.

Where candidates lose marks

Three traps recur. The first is treating value as something the provider delivers to the consumer; in ITIL 4 it is co-created, which means the consumer has to contribute for value to arise at all. The second is reading value as objective and financial; it is defined in terms of perception, so different stakeholders can legitimately value the same service differently. The third is confusing a product with a service offering — a product is the configuration of resources the provider assembles, and one product can support several offerings aimed at different groups.

Lessons in this objective

The objective cut into the pieces the blueprint declares. Each one has the material written out and the questions that test it.

Drill this objective

The trainer can run a short practice set drawn from this objective alone, which is what the weight column above is for: revise the heavy objectives first.

Practise Key concepts of service management

Questions on this objective

Practise Key concepts of service management

The other objectives in ITIL 4 Foundation