2.4 Outcomes, Outputs, Costs and Risks

The Four Building Blocks of Value

ITIL builds its concept of value from four terms that constantly appear as answer options: outputs, outcomes, costs, and risks. Foundation questions frequently give you a short scenario and ask which of these a described item is. Learn the definitions verbatim and practise telling the deliverable from the result, and the money from the possible harm.

Output versus outcome

An output is a tangible or intangible deliverable produced by carrying out an activity. A generated report, a closed ticket, a provisioned laptop, and a deployed release are all outputs. They are things an activity produces.

An outcome is a result for a stakeholder enabled by one or more outputs. The report is an output; the better renewal decision the customer makes because of the report is the outcome. The closed ticket is an output; the user getting back to productive work is the outcome. Outputs are easy to count, which is precisely the trap: teams that optimise for outputs (more tickets closed, more reports produced) can look busy while creating little value, because stakeholders care about outcomes, not deliverables.

Whenever a question contrasts a produced thing with the benefit someone experiences, the produced thing is the output and the experienced benefit is the outcome.

Costs: Removed and Imposed

Cost is the amount of money spent on a specific activity or resource. In value terms, ITIL looks at cost from the consumer's perspective and splits it in two:

• Costs removed from the consumer by the service. These are costs the consumer no longer has to bear because the provider takes them on, for example the cost of buying and running servers, hiring specialists, or maintaining infrastructure. Removing these costs is part of the value the service creates.
• Costs imposed on the consumer by the service. These are the costs of consuming the service, such as subscription fees, the price of the network needed to reach it, and the staff time to adopt and use it. These are costs the consumer takes on because of the service.

A service is attractive when the costs it removes clearly outweigh the costs it imposes.

Risks: Removed and Imposed

Risk is a possible event that could cause harm or loss, or make it more difficult to achieve objectives. It can also be described as uncertainty of outcome. Like costs, risks come in two directions from the consumer's view:

• Risks removed from the consumer by the service. For example, a managed backup service removes the risk that the consumer loses data through its own poor backup practices.
• Risks imposed on the consumer by the service. For example, relying on that same provider imposes a new risk that the provider could suffer an outage or a security breach the consumer cannot directly control.

Good providers reduce the risks they remove and manage the risks they impose, so the net risk picture favours the consumer.

How They Combine into Value

Here is the relationship the exam wants you to hold: value is a function of the outcomes a consumer achieves, weighed against the costs and risks involved in achieving them. Outcomes pull value up; costs and risks pull it down. A scheduling app that reduces missed appointments (a desirable outcome) only creates value if its subscription cost and its data-privacy risk are acceptable to the consumer. Change the price or the risk enough and the same outcome is no longer perceived as valuable.

This is why value is co-created and consumer-judged: the provider influences outcomes, costs, and risks, but the consumer weighs them and decides whether value resulted.

Common exam traps

• Output mistaken for outcome. A dashboard is an output; the faster decisions it enables are the outcome. If the option describes a deliverable, it is an output.
• Forgetting risks and costs have two directions. Services both remove and impose costs and risks. A question about 'the cost of consuming the service' points to imposed cost, while 'costs the consumer no longer bears' points to removed cost.
• Treating outputs as valuable in themselves. Outputs enable outcomes but have no value on their own; stakeholders value outcomes.

A combined worked example

A retailer buys a fraud-detection service. The outputs are the flagged-transaction alerts the system produces each day. The outcome is fewer fraudulent chargebacks and higher customer trust, the result the retailer actually cares about. The service removes the cost of building an in-house fraud team and removes the risk of undetected fraud, but it imposes a monthly fee and a new risk that a false positive blocks a legitimate sale. The retailer's finance lead weighs the reduced chargebacks against the fee and the false-positive risk.

If the alerts are accurate and the fee is modest, perceived value is high; if false positives spike, the same outputs suddenly enable a worse outcome and value falls, even though the number of alerts is unchanged. This is exactly why ITIL treats outputs as merely counted, while outcomes, costs, and risks are what actually determine value.