Value Co-creation

A payroll team runs its monthly pay cycle on a provider's cloud platform. The provider keeps the platform available and secure; the team supplies correct employee data and follows the process. Neither side produces the result alone, and that is the whole idea of value co-creation: value is created jointly through the active collaboration of a service provider and a service consumer within a service relationship.

Start with the word value itself. In ITIL, value is the perceived benefits, usefulness, and importance of something. The load-bearing word is perceived: value is subjective and is judged by the stakeholder who receives it, above all the service consumer, not by the provider's cost of delivery or the effort it put in. Two consumers can receive the same output and perceive very different value from it.

Because value is the shared goal, it is what directs the collaboration. The provider applies its resources and capabilities; the consumer provides requirements and uses the service correctly; and every activity on both sides is meant to contribute to the value being pursued. The figure below shows the two sides meeting: the provider's resources and capabilities and the consumer's requirements and correct use both feeding the single value they co-create. ITIL (Version 5) puts value co-creation between providers, consumers, partners, and technology at the centre of service delivery^[1], which is why the exam treats these as core Key ITIL terms and definitions^[2].

A service creates value only when the desired outcomes (the results the consumer wants, defined in full under Outputs versus outcomes below) are reached while the associated costs and risks are optimized together. That one sentence carries three defined terms, so take them one at a time.

Cost is the amount of money spent on a specific activity or resource. Risk is a possible event that could cause harm or loss, or make it more difficult to achieve objectives; it can also be read as uncertainty of outcome, and it can be positive as well as negative. Neither is something to eliminate. The provider takes on some costs and risks precisely so the consumer can reach its outcomes more effectively than it could alone, and the aim is to optimize costs and risks, not to drive them to zero. Equally, outcomes are not to be maximized regardless of the costs and risks that chasing them would create. Value is the balance across all three.

The part candidates most often miss is that costs and risks each move in two directions. A service removes costs from the consumer (costs the provider now bears) and removes risks from the consumer (risks the provider now carries). But consuming a service also imposes new costs, the price of consumption, and new risks: depending on a provider is itself a risk, and a security breach at the provider can reach the consumer. The figure below sets the two directions side by side: the costs and risks a service lifts off the consumer against the new costs and risks consuming it imposes. So when you weigh a service, weigh the net of what it lifts against what it adds, in both money and risk. ITIL (Version 5) frames value as co-created while weighing outcomes, costs, risks, experience, and sustainability^[1].

An output is what a service produces; an outcome is what the consumer achieves because of it. Keeping these apart is the single most tested distinction in this topic, so define both precisely before comparing them.

An output is a tangible or intangible deliverable produced by an activity: the thing that is created, such as a report or a provisioned server. An outcome is a result for a stakeholder, enabled by one or more outputs: what the consumer actually wants to achieve with the support of the service. The relationship runs one way. Outputs enable outcomes, a single outcome may draw on several outputs, and the consumer ultimately cares about the outcome.

Here is the trap the word hides. Because a service can point to the outputs it delivered, it is easy to read a delivered output as proof the job is done, and it is not. A service can deliver every output it promised and still fail to produce the desired outcome. A monthly usage report (an output) is worthless if it never leads to the better-informed decisions the consumer wanted (the outcome). The figure below draws both the intended path, an activity producing an output that enables the outcome, and the failure case, every output delivered yet the outcome still not reached. So co-creation is judged by the outcomes reached, not by the outputs handed over, which is why ITIL ties value to shared ownership of the outcomes^[1] rather than to delivery alone.

Utility and warranty tell you whether a service works; user experience and sustainability decide much of how it is valued. All four are value characteristics, and each contributes to the value that gets co-created.

• Utility is fitness for purpose: what the service does, the functionality that lets the consumer reach an outcome it could not before.
• Warranty is fitness for use: the assurance that the service will perform when needed, covering availability, capacity, security, and continuity.
• User experience (UX) is how a person actually feels using the service. Two services with identical utility and warranty can be perceived very differently because one is pleasant to use and the other is not.
• Sustainability is the assurance of ongoing environmental, social, and economic responsibility in how the service is provided.

The exam point is that all four contribute, so utility and warranty alone are not sufficient; user experience and sustainability also shape perceived value. ITIL (Version 5) weighs experience and sustainability alongside outcomes, costs, and risks^[1] when judging co-created value.

Feedback is what keeps all of this on course over time. Feedback gives the provider and consumer information about how well outcomes are being achieved, so products and services can be adjusted and continually improved to keep co-creating value. Without it, a service that has quietly stopped delivering the outcome sends neither party a signal to act.

Foundation questions on value co-creation are recall and recognition (Bloom levels 1 to 2), so they reward clean definitions and the ability to tell four close terms apart under a scenario. A handful of stem shapes recur, and knowing the discriminator for each is most of the battle.

'What is value, and who judges it?'

The answer defines value as the perceived benefits, usefulness, and importance of something, judged by the consumer. The tempting distractor frames value as the provider's cost of delivery or effort. It is not: value is the consumer's perception, not the provider's input.

'Which is an output, and which is an outcome?'

The stem describes a deliverable and a result and asks you to label them. The output is the thing produced (a report, a server); the outcome is what the consumer achieves with it (a decision made, an order fulfilled). The classic trap offers a delivered output as if it were the outcome. Hold on to the one-way link: outputs enable outcomes, and delivering the output does not guarantee the outcome.

'How do costs and risks contribute to value?'

The correct option has them optimized and weighed against outcomes, and it often notes that a service both removes them from and imposes them on the consumer. Two distractors recur: one says the goal is to drive costs and risks to zero (it is not, they are optimized); another treats a service as only ever reducing consumer risk (consumption adds new risks too).

'Which contribute to co-created value?'

When the stem lists value characteristics, the complete answer is all four: utility, warranty, user experience, and sustainability. The trap offers only utility and warranty, which are necessary but not sufficient.

These terms sit at the core of the exam's Key ITIL terms and definitions^[2] category, and the paper is 40 multiple-choice questions in 60 minutes, closed book, with a 65% pass mark^[2], so precise recall of these boundaries converts directly into marks.