Product and Service Management

One shift defines ITIL (Version 5): an organization stops managing services on their own and starts managing digital products and services together, across their whole life. Digital product and service management^[1] is ITIL's name for the specialized organizational capabilities that do exactly this, so an organization can enable value for its customers and other stakeholders through digital products and services. The concepts below are the ones the rest of ITIL is built on, and Foundation tests one thing about them: whether you can tell them apart and name the one a question is describing.

Read digital product and service management as the evolution of what earlier ITIL simply called service management. The lens widens from services alone to products and services treated as two sides of the same digitally-enabled technology solution^[1] and managed together instead of in separate silos. Each term that follows names one moving part of that wider picture.

Continual improvement is singled out as a key concept of digital product and service management in its own right. It is a recurring activity, performed at all levels of the organization, that keeps products, services, and practices meeting stakeholders' expectations as needs and conditions change, which is what stops a once-valuable service from quietly drifting out of date.

The rest of the page is that vocabulary, and the figure below groups it. First come the things you manage: product, service, their digital forms (digital product and digital service), and the good. Then the four characteristics that give a service its quality: utility, warranty, user experience, and sustainability. Then the whole-life model, the ITIL Product and Service Lifecycle, kept current by continual improvement. And finally the audiences ITIL serves: enterprises, managed service providers, digital product vendors, and the professionals who practise this discipline.

The two concepts every other term leans on are product and service, and the useful thing to fix in your head is not their definitions in isolation but how they relate. A product is a configuration of an organization's resources, while a service is how the value in those resources actually reaches a consumer: it enables value co-creation (value that the provider and consumer create together) by facilitating the outcomes the consumer wants, without that consumer having to manage the specific costs and risks involved. So the two are not rivals. A product is usually not consumed directly; instead, parts of it are made available to consumers as services, the integrated product-and-service view^[2] at the heart of Version 5. The figure below traces that path, from the organization's resources through to the consumer.

Digital products and digital services

The word "digital" adds a channel, not a new category. A digital product is a product made available or delivered through digital technology, and a digital service is a service enabled by information technology and delivered through digital channels, the digital form of each concept. ITIL (Version 5) puts digital experience at the centre^[3] because most modern products and services now reach the consumer this way, but the underlying definitions do not change when you prefix them with "digital".

A good is not access to resources

A good is a separate key concept, and its defining test is ownership. A good is a tangible item that has value and whose ownership can be transferred to a consumer, who then becomes responsible for its future use, such as a laptop or a mobile phone. The trap to defuse right away is that a good is not the same as access to resources: with a good, ownership passes to the consumer, whereas access to resources lets the consumer use something the provider keeps and continues to own. If ownership transfers, it is a good; if it does not, it is access to resources, which is covered under service offerings.

A service's quality is not one thing but four, and Foundation leans on your keeping them straight. ITIL (Version 5) describes a service's quality through four value characteristics, and the PeopleCert Foundation syllabus^[4] expects all four: utility, warranty, user experience, and sustainability.

Utility versus warranty

Utility and warranty are the classic pair, and the fastest way to hold them apart is two short questions. Utility answers "what does the service do?" — it is the functionality offered to meet a need, or fitness for purpose, and a service has utility when it supports the consumer's performance or removes a constraint on them. Warranty answers "how well does it perform?" — it is the assurance the service will meet agreed requirements, or fitness for use, delivered through availability, capacity, security, and continuity. A service can be fit for purpose yet fail on warranty, doing the right thing but doing it unreliably, which is exactly why an answer needs both.

User experience and sustainability

User experience and sustainability are the characteristics Version 5 adds to the classic pair, and naming only utility and warranty is the classic exam trap. User experience is the whole experience a user has interacting with a product or service and its provider, including its usability and how the user feels. Sustainability is the assurance that a product or service continually meets requirements for environmental responsibility, as well as social progress and economic growth. These two sit alongside utility and warranty, not beneath them: the Foundation guidance^[5] weighs experience and sustainability as part of value, not as optional extras. The figure below groups all four, the classic pair beside the two Version 5 adds. Together, the four are what define a service's quality.

Two more key concepts describe not a thing but a span of time: the whole life of a product or service. The ITIL Product and Service Lifecycle is a key concept of digital product and service management, an overarching, end-to-end model of how one common set of activities applies across a product or service's whole life, from the first sign of an opportunity through to retirement.

Those activities are eight in number, discover, design, acquire, build, transition, operate, deliver, and support^[6], and the single most important thing to know about them at this level is that they are not a sequence. The model is neither prescriptive nor rigid^[6]: work can move backwards or forwards between any of the activities, they are used iteratively, and different versions of the same product or service can sit in several activities at once, so one version can be live and operating while a newer one is still being designed. ITIL calls this an ecosystem approach rather than a linear, siloed one. The purpose and scope of each activity is a topic in its own right, covered under the Product and Service Lifecycle domain; here you only need to recognize the lifecycle as a whole-life key concept, and not confuse it with two neighbours it is often mixed up with: the value chain (the operating model that arranges the same activities into value streams) and a single value stream (one specific series of steps for one product or service).

Continual improvement is the companion concept that keeps that whole-life view honest. Because a lifecycle runs from opportunity to retirement, something has to keep the product, the service, and the practices around them meeting expectations the whole way, and that recurring activity, run at all levels of the organization, is continual improvement.

Picture four readers arriving at ITIL from different places: a large enterprise trying to get IT and the business pulling the same way, a provider running the same services for many client organizations, a company that builds and sells software, and an individual mapping out a career. ITIL pays each of them back differently, and Foundation expects you to match the benefit to the audience.

Audience	What ITIL gives them
Enterprises	A shared framework and language to co-create value, improve the quality and consistency of digital products and services, align IT with business objectives, and manage cost and risk
Managed service providers	Proven best practice and a shared vocabulary to deliver consistent, high-quality services across many clients and to strengthen service relationships
Digital product vendors	A way to integrate service management with product development, so products deliver value and improve the customer's experience
Digital product and service management professionals	A globally recognized qualification, a common vocabulary, and practical, career-building guidance

The common thread, which the ITIL Foundation programme^[5] frames as a shared language and structured thinking^[4], is that ITIL gives very different audiences one vocabulary for value. Enterprises get alignment and better decisions, providers get consistency across clients, vendors get product and service management joined up, and professionals get a recognized credential and a way to grow.

Most Foundation questions on these terms do the same two things: they hand you a one-line description and ask which concept it names, or they dangle a tempting near-miss as a wrong answer. The reliable move is to read the stem for its signal phrase and map it to the one concept that phrase defines, the lookup the figure below captures.

• "A configuration of resources designed to offer value" names a product; the moment a stem says value is enabled "without the consumer managing costs and risks", it has switched to a service.
• "Ownership transfers to the consumer" names a good; if ownership stays with the provider and the consumer only gets to use the resource, it is access to resources, not a good.
• "What the service does" is utility; "how well it performs", through availability, capacity, security, and continuity, is warranty.
• "Delivered through digital technology or channels" marks a digital product or digital service, without changing the base definition.

The distractors are just as patterned. A question about a service's quality that offers only utility and warranty is testing whether you remember that user experience and sustainability belong in the set too. A question about the lifecycle that offers a six-activity service value chain is offering ITIL 4 framing that Version 5 has replaced with eight activities^[6]. And a stem that treats a product and a service as interchangeable is ignoring the one rule that ties them together: a product is a configuration of resources, while a service is how the value from those resources reaches the consumer.