2.1 Value and Value Co-Creation
Key Takeaways
- ITIL 4 defines value as the perceived benefits, usefulness, and importance of something — value is inherently subjective and defined by the recipient
- Value is co-created through an active collaboration between the service provider and the service consumer, not delivered one-way from provider to consumer
- Service consumption and service provision both contribute activities that are essential to realizing value
- The same service can hold very different value for different consumers, which is why a provider cannot define value unilaterally
- The shift from 'the provider delivers value' to 'value is co-created' is a foundational change introduced in ITIL 4
What ITIL 4 Means by 'Value'
Value is the single most important concept in the entire ITIL 4 framework — every other idea ultimately exists to support it. The official definition is precise and worth memorizing word for word: value is "the perceived benefits, usefulness, and importance of something."
Notice the three components in that definition — perceived benefits, usefulness, and importance. Two of them, perceived and importance, signal something the exam tests heavily: value is subjective. It is defined by the recipient, not by the person providing the service. The provider cannot simply declare that something is valuable; only the consumer who experiences it can decide whether it actually is.
Consider a corporate email service. To a sales team that lives in their inbox, the service is enormously valuable. To a factory-floor worker who never logs in, the very same service has almost no value. Identical service, identical cost to run — radically different perceived value. That is why value must always be understood from the consumer's perspective, and why providers must constantly check their assumptions against what consumers actually experience.
Value Co-Creation: The Big Shift
Earlier service management thinking (including ITIL v3) described value as something a provider delivers to a consumer — a one-directional hand-off, like a package being shipped. ITIL 4 deliberately rejects that model. Instead, it states that value is co-created through an active collaboration between the service provider and the service consumer.
The key word is co-create. Both parties must contribute activities for value to emerge. A provider can stand up a flawless online banking platform, but no value exists until customers log in, enter accurate details, and complete transactions. If the consumer supplies the wrong account number or never uses the app, the provider's perfect output produces zero value. Value lives in the interaction, not in the deliverable.
Exam tip: If an answer option says a provider "delivers value to" the consumer, treat it with suspicion. ITIL 4 language is almost always "co-creates value" or "enables value co-creation." The deliberate move away from one-way delivery is one of the most commonly tested distinctions in this section.
Why the shift matters
Recognizing co-creation changes how providers behave. Instead of optimizing only their own internal outputs, they must understand the consumer's context, gather feedback, and adjust continually. Value becomes a relationship to be managed, not a product to be shipped once and forgotten.
Service Provision and Service Consumption
Because value is co-created, both sides perform real, distinct activities. ITIL 4 names these two contributing sets of activities service provision and service consumption.
| Term | Who performs it | Typical activities |
|---|---|---|
| Service provision | The service provider | Managing resources, providing access to those resources, fulfilling service actions, managing the service level, continual improvement |
| Service consumption | The service consumer | Using the provider's resources, performing the consumer's own activities (e.g. defining requirements, paying), and ultimately realizing outcomes |
Both columns are necessary. Provision without consumption creates nothing; consumption is impossible without provision. The collaboration across these two roles is exactly what "co-creation" describes in practice.
Pulling it together
- Value = perceived benefits, usefulness, and importance — and it is subjective, defined by the recipient.
- Value co-creation = value emerges from active collaboration, never a one-way delivery.
- Service provision and service consumption are the two complementary sets of activities that make co-creation real.
Hold onto this trio. Every later concept — products, services, outcomes, utility, and warranty — is built on the premise that the goal of service management is to enable value to be co-created.
Value Flows in Both Directions
A point candidates often miss is that value is not created only for the consumer. In a healthy service relationship, both the provider and the consumer realize value, and each must contribute to the other receiving it. The consumer receives value in the form of the outcomes it wants. The provider receives value too — typically revenue, but also brand reputation, market data, capability development, or fulfilment of a public-sector mandate. Because both sides are seeking value, both have a genuine stake in cooperating, which is precisely what makes co-creation sustainable rather than a slogan.
This is also why ITIL 4 frames service management around enabling value rather than producing deliverables. The official definition of service management is "a set of specialized organizational capabilities for enabling value for customers in the form of services." Read that carefully: the capabilities are specialized — they take experience, knowledge, and skill to develop — and their purpose is enabling value, not merely running technology. A team can keep every server online and still fail at service management if no value is co-created.
A Worked Example
Imagine a ride-hailing app. The provider configures drivers, vehicles, mapping data, and a payment platform. But no value exists until a consumer opens the app, requests a ride, and travels to a destination. The consumer supplies essential activities: choosing a pickup point, confirming the route, and paying. If the consumer enters the wrong address, even a flawless app produces a poor outcome.
Value — getting safely from A to B — is genuinely co-created from both parties' actions, and both walk away better off: the rider reaches the destination, and the provider earns a fare and trip data. Strip out either side's contribution and the value collapses, which is the whole point ITIL 4 is making.
According to ITIL 4, what is the official definition of 'value'?
Which statement best reflects ITIL 4's view of how value is created?
A corporate email platform is extremely valuable to the sales team but nearly worthless to a factory worker who never logs in. This best illustrates that value is: