2.5 Outcomes, Costs, Risks, Utility and Warranty

Outputs vs Outcomes

This distinction is one of the most heavily tested in the whole exam, and the two words are easy to confuse. Memorize both definitions:

• An output is "a tangible or intangible deliverable of an activity."
• An outcome is "a result for a stakeholder enabled by one or more outputs."

An output is what the activity produces; an outcome is the result the stakeholder actually wanted. The classic ITIL illustration is wedding photography: the output is the photo album (a tangible deliverable), but the outcome is the happy memories evoked when looking at it. The photographer produces the output; the consumer realizes the outcome.

Exam tip: If something is a deliverable you can point at — a report, a server, an album — it's an output. If it's the result or benefit the stakeholder is chasing, it's an outcome. Services exist to facilitate outcomes, not merely to produce outputs.

Costs and Risks: Each Cuts Two Ways

A cost is the amount of money spent on a specific activity or resource. ITIL 4 stresses that, from the consumer's viewpoint, a service affects costs in two directions:

• Costs removed from the consumer — costs the consumer no longer bears because the provider absorbs them (e.g. the cost of buying and maintaining servers when you move to a cloud service). This is part of the value proposition.
• Costs imposed on the consumer — new costs the service introduces for the consumer (e.g. the subscription fee, plus staff time and training to use it). These are costs of consuming the service.

A risk is a possible event that could cause harm or loss, or make it more difficult to achieve objectives. Risk also cuts two ways for the consumer:

• Risks removed from the consumer — risks the provider now carries (e.g. the risk of hardware failure or under-capacity, which the cloud provider manages).
• Risks imposed on the consumer — new risks the relationship creates (e.g. the provider going out of business, or a security breach on the provider's side).

Exam tip: The pattern is symmetrical and tested directly: services both remove and impose costs, and both remove and impose risks. A consumer weighs the costs and risks taken away against the new ones introduced when judging whether the service is worth it.

Utility and Warranty: Both Required for Value

Value from a service comes from two attributes that ITIL 4 always tests together: utility and warranty.

Utility is "the functionality offered by a product or service to meet a particular need." In plain terms, utility is what the service does, and it determines whether the service is fit for purpose. To have utility, a service must either support the performance of the consumer or remove constraints from the consumer (or both).

Warranty is "the assurance that a product or service will meet agreed requirements." Warranty is how the service performs, and it determines whether the service is fit for use. Warranty is typically addressed across four conditions, easily remembered as ACSC: Availability, Capacity, Security, and Continuity.

Both are necessary — neither is sufficient

The single most important point: value requires BOTH utility AND warranty. A service that does the right thing (utility) but is constantly down (no warranty) creates no value — and neither does a perfectly reliable service that does the wrong thing. A pay-by-card system that accepts payments only 50% of the time has the right utility but inadequate warranty, so it fails to deliver value. On the exam, if an option says value comes from utility or warranty alone, it is wrong: you need them together.

How These Five Concepts Connect

The five ideas in this section fit together into one picture of how a consumer judges value:

• A service produces outputs, which enable the outcomes the consumer actually wants.
• In pursuing those outcomes, the service removes some costs and risks from the consumer while imposing new ones.
• Whether the outcomes are worthwhile depends on the service having both the right utility (fitness for purpose) and adequate warranty (fitness for use).

Value, then, is the consumer's overall judgement: do the desired outcomes — with good utility and warranty, and removed costs and risks — outweigh the new costs and risks introduced? If yes, value is co-created.

Worked Example: A Cloud Backup Service

Walk through a small business adopting a cloud backup service:

• Output: nightly encrypted backup files stored off-site.
• Outcome: the business can keep operating after a laptop is lost or ransomware strikes — the result it truly wants.
• Costs removed: no need to buy tape drives or a fireproof safe. Costs imposed: a monthly subscription and some staff time to configure folders.
• Risks removed: the risk of losing data when local hardware fails. Risks imposed: the risk that the provider suffers an outage or breach.
• Utility: it backs up the right files automatically — fit for purpose.
• Warranty: it is available 99.9% of the time, scales as data grows (capacity), encrypts data (security), and can restore after a disaster (continuity) — fit for use.

Only because both utility and warranty hold, and the removed costs and risks outweigh the imposed ones, does the consumer judge the service valuable. Drop the warranty — backups that silently fail half the time — and the identical utility no longer creates any value at all.