Product or Service? ITIL v5's Key Concepts, Through Microsoft 365
ITIL v5's building blocks made practical: products vs services, what's in a service offering, and how value, costs and risks work, with M365 examples.
Last week I followed one automation through ITIL® v5's lifecycle. This week I'm going back to basics: the key concepts the whole framework is built on. They sound simple, but v5 sharpens them in ways that matter, especially if you work in Microsoft 365.
Product vs service
In ITIL v5, a product is a configuration of an organization's resources designed to offer value to a consumer. A service is a way of enabling value co-creation: it helps customers get the outcomes they want, without them having to manage specific costs and risks.
The digital versions are what most of us deal with every day:
- A digital product is a product based on digital technology.
- A digital service is a service that fully or largely relies on digital products.
The key point is that they aren't one-to-one. One product can enable many services, and one service can depend on several products. Entra ID is a good example. As a product, it enables single sign-on, conditional access, self-service password reset and automated onboarding: several services from one product. And a service like "remote working" depends on Entra ID, Intune, Teams and Exchange Online together.
ITIL also puts it neatly: products provide capabilities; service offerings describe potential value.
What's actually in a service offering
A service offering is a formal description of one or more services for a target group of consumers. It can contain three things:
| Part | What it means | Microsoft 365 example |
|---|---|---|
| Transfer of goods | Ownership passes to the consumer | Shipping a new starter a laptop |
| Access to resources | You use something the provider still owns | Using the M365 tenant, Teams, Exchange Online |
| Service actions | Things the provider does for you, or with you | A password reset, onboarding training, a consultation |
For digital services, access to resources is the main form of value. Transferring goods is rare, and providers try to minimize it. Service actions are common, but digital providers try to reduce or automate them. That's why self-service password reset beats a ticket to the service desk.
Value: outputs, outcomes, costs and risks
Value is the perceived benefits, usefulness and importance of something. In ITIL it's co-created: provider and consumer create it together, by combining resources and actions.
Two distinctions make this practical:
- Output vs outcome. An output is a deliverable; an outcome is a result for a stakeholder that the output enables. Assigning a Teams licence is an output. A remote team that can actually collaborate is the outcome.
- Costs and risks come in two types. A service removes some, which is the value proposition, and imposes others, which is the price of consuming it.
Moving email to Exchange Online shows both types. It removes the cost of running mail servers and the risk of a hardware failure. But it imposes a subscription cost and a new dependency on Microsoft and your internet connection.
The rule ITIL gives is simple: a service is only seen as valuable when its positive effects outweigh its negative ones. Every M365 business case I've worked on comes down to that balance.
What I'm taking into the exam
- Product = resources configured to offer value. Service = enabling outcomes without the customer managing specific costs and risks.
- Digital service = relies fully or largely on digital products.
- One product, many services, and the other way round.
- A service offering is made of goods, access to resources and service actions. In digital services, access dominates and goods are rare.
- Output (deliverable) vs outcome (result).
- Costs and risks are either removed or imposed.
On Friday: who's who in a service relationship.
ITIL® is a registered trademark of PeopleCert group. This post contains my personal study notes and interpretation, not official ITIL guidance.