Key ITIL terms and definitions

One sentence organizes this whole domain: a service provider and a service consumer co-create value within a service relationship. Nearly every term you meet is a piece of it, so when a definition looks unfamiliar, place it on that sentence and it settles into who is involved, what they exchange, or why. The recurring Foundation trap is that the terms arrive in closely related pairs that are easy to confuse: product and service, output and outcome, utility and warranty, service quality and service level, service provider and digital product vendor. Because this is a Foundation exam, a question tests whether you can recognize a definition and separate it from its near neighbour, not whether you can apply it, so the real skill is precision on the boundary between two similar terms. At 30% this is the second-largest domain behind the ITIL Value System (40%), and together the two make up most of the exam, so the vocabulary defined here is the language the rest of the syllabus is written in.

The five subtopics build the vocabulary from the inside out. It starts with the base concepts in Product and Service Management: digital product and service management as a set of capabilities, the product-versus-service and good-versus-access distinctions, and the four value characteristics (utility, warranty, user experience, and sustainability). Experience, Strategy and Transformation then adds three families of context terms: how people feel about a service, where the organization is heading, and how it changes to get there. Service Offerings names what a provider actually packages for a consumer group, built from goods, access to resources, and service actions. Value Co-creation is the point of it all: value judged by the consumer, reached by weighing desired outcomes against the costs and risks that come with them. Service Relationships closes the loop with who is involved and how performance is measured: the provider, consumer, and digital product vendor roles, the sponsor, customer, and user roles, the basic, cooperative, and collaborative relationship types, and the service quality, service level, and Service Level Agreement (SLA) that track how well the service performs. Reach for whichever page owns the term you are unsure of; the map below points each one to its home.

The instinct the exam rewards is boundary-precision, so when two options both sound right, pick the one that respects the exact line ITIL draws. Ownership transfers for a good but not for access to resources, which the provider keeps. An outcome is the result the consumer wants, while an output is only the deliverable that enables it. A service enables value co-creation, while a product is merely a configuration of resources made available to consumers through services. A digital product vendor supplies the product itself, while a service provider runs the ongoing, value-co-creating relationship around it. Default to the reading that keeps value co-creation between provider and consumer at the centre, and to the precise ITIL term over the looser everyday sense of the same word.