Key definitions that carry the exam

About a third of the Version 5 Foundation exam, roughly twelve questions, tests key terms and definitions, and definitions appear inside many questions in other areas too. A candidate who knows the definitions precisely has a large head start; a candidate who knows them only roughly will keep falling for distractors that use a neighbouring term. This lesson gathers the definitions most worth memorizing, shows how to tell similar terms apart and gives practice in the Foundation style.

ITIL-110 explained these concepts in depth with examples. Here the goal is narrower: to fix each definition in memory with its signature words, the two or three words that identify it in a missing word question or distinguish it from a near neighbour. The definitions below are paraphrased study versions. Your exam materials give the official wording, and it is worth comparing the two and learning the official version for the terms you find hardest.

Service management, value and co-creation

Service management is a set of specialized organizational capabilities for enabling value for customers in the form of services. The signature words are 'specialized organizational capabilities' and 'value for customers in the form of services'. Capabilities here means more than processes: it includes people, knowledge, information, technology, partners and ways of working.

Value is the perceived benefits, usefulness and importance of something. The word 'perceived' matters. Value is decided by the stakeholder who receives it, not by the provider, and two customers can value the same service differently. ITIL stresses that value is co-created: providers and consumers create it together through their relationship. A freight booking service creates value only when the customer actually uses it to move goods on time.

A service is a means of enabling value co-creation by facilitating outcomes that customers want to achieve, without the customer having to manage specific costs and risks. Three signature phrases appear here: 'enabling value co-creation', 'facilitating outcomes' and 'without having to manage specific costs and risks'. When a question asks what distinguishes a service, look for the option about outcomes and costs and risks the customer no longer manages.

Products, offerings and relationships

A product is a configuration of an organization's resources designed to offer value for a consumer. The signature words are 'configuration of resources'. Products are what the provider builds; customers do not usually see them whole. A service offering is a formal description of one or more services, designed to address the needs of a target consumer group. An offering may include goods, access to resources and service actions.

A service relationship is a cooperation between a service provider and a service consumer, and it includes service provision, service consumption and service relationship management. Service provision is what the provider does to deliver services. Service consumption is what the consumer does to use them. Service relationship management is the joint work of both to ensure continual value co-creation. A frequent missing word question puts these three side by side.

Organizations, consumers and roles

An organization is a person or a group of people that has its own functions with responsibilities, authorities and relationships to achieve its objectives. Organizations act as service providers and service consumers, often both at once. Larchmont Technology Services provides services to Larchmont's business units and consumes cloud services from its suppliers.

ITIL names three consumer roles. The customer defines the requirements for a service and takes responsibility for the outcomes of service consumption. The user uses services. The sponsor authorizes the budget for service consumption. One person can hold all three roles, or they can be three different people. At a Larchmont client, the logistics manager who chose the service is the customer, the shipping clerks who book loads are users, and the finance director who signed the contract is the sponsor.

Outputs, outcomes, costs and risks

An output is a tangible or intangible deliverable of an activity. An outcome is a result for a stakeholder enabled by one or more outputs. The difference is worth a mark or two on most exams. Larchmont's booking confirmation email is an output; the customer's goods arriving on time, with the customer free to plan around it, is the outcome. Questions often describe something and ask whether it is an output or an outcome; ask yourself whether it is a deliverable or a result for a person.

Cost is the amount of money spent on a specific activity or resource. From the consumer's point of view, a service removes some costs (such as owning trucks) and imposes others (such as the service fee and the time spent learning the portal). Risk is a possible event that could cause harm or loss, or make it more difficult to achieve objectives; it can also be defined as uncertainty of outcome. Services likewise remove some risks (vehicle breakdown) and impose others (dependence on the provider). Questions about removed and imposed costs and risks reward candidates who remember that services do both.

Utility and warranty

Utility is the functionality offered by a product or service to meet a particular need; it is often summarized as 'what the service does' and described as fit for purpose. Warranty is the assurance that a product or service will meet agreed requirements; it is summarized as 'how the service performs' and described as fit for use. Warranty usually covers availability, capacity, security and continuity, the areas often written into service level agreements.

A classic question describes a feature, such as 'the portal can print customs documents', and asks whether it is utility or warranty. Another describes a guarantee, such as 'the portal is available 99.9 % of the time during business hours', and asks the same. Features and functions are utility; performance, availability and security are warranty. Both are needed for value: a service that does the right thing unreliably, or the wrong thing reliably, does not create value.

Definitions from the rest of the syllabus

Many other definitions appear across the syllabus, and the exam can test them anywhere. The table collects those that most often turn up in Foundation-style questions, with their signature words. Several are covered in more depth in later lessons; here the point is to recognize them.

Look at how many pairs sit close together: incident and problem, problem and known error, configuration item and IT asset, change and event. Distractors exploit these pairs. If a question describes 'a problem that has been analysed but has no permanent fix', the answer is known error, and 'problem' will be a distractor. If it describes 'any component that needs to be managed to deliver a service', the answer is configuration item, and 'IT asset' will be a distractor because it adds financial value.

Learning definitions efficiently

Definitions are best learned by retrieval, not rereading. Research on learning consistently finds that testing yourself, by trying to recall an answer before checking it, produces better long-term memory than reading the same material again. Flashcards work well: the term on one side and the definition on the other, practised in both directions. Spacing the practice over days rather than cramming it into one evening further improves recall.

Kofi and Lena built a shared deck of 60 cards from this lesson and the practice lessons. They review it on their phones for ten minutes a day, and the app shows cards they miss more often. Lena added a third field to each card, 'nearest neighbour', naming the term most likely to be confused with it, because those confusions were costing her marks.

# Self-test on look-alike terms: which signature words point to which term?
cards = {
    "incident": ["unplanned", "interruption", "reduction in quality"],
    "problem": ["cause", "potential cause"],
    "known error": ["root cause found", "not resolved"],
    "configuration item": ["component", "needs to be managed"],
    "IT asset": ["financially valuable"],
    "change": ["addition", "modification", "removal"],
    "event": ["change of state", "significance"],
}
clues = [
    "a component that needs to be managed to deliver a service",
    "a problem whose root cause was found but not resolved",
    "an unplanned interruption to a service",
    "any financially valuable component",
    "a change of state with significance for managing a service",
]
for clue in clues:
    scores = {term: sum(w in clue for w in words) for term, words in cards.items()}
    best = max(scores, key=scores.get)
    print(f"{clue:<62} -> {best}")

a component that needs to be managed to deliver a service      -> configuration item
a problem whose root cause was found but not resolved          -> problem
an unplanned interruption to a service                         -> incident
any financially valuable component                             -> configuration item
a change of state with significance for managing a service     -> event

The matcher works by counting signature words, which is a fair model of how a well-prepared candidate reads a missing word question: spot the defining phrase and map it to the term. Look at the second clue: it contains the word 'problem', yet the matcher still chooses known error, because 'root cause found' and 'not resolved' are the defining words. In the real definition the defining words are 'analysed' and 'not resolved'.

Practising definition questions

Below are five definition questions in the Foundation style, followed by the reasoning. Try each before reading the answer.