Study guide

2.5 Outcomes, Costs, Risks, Utility and Warranty

ITIL 4 Foundation Certification Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 ITIL 4 Foundation Exam Facts 1.2 What ITIL 4 Is and Why It Matters 1.3 How to Study and Pass

2 Key Concepts of Service Management

2.1 Value and Value Co-Creation 2.2 Organizations, Service Providers, Consumers and Stakeholders 2.3 Products, Services and Service Offerings 2.4 Service Relationships 2.5 Outcomes, Costs, Risks, Utility and Warranty

3 The Seven Guiding Principles

3.1 Focus on Value and Start Where You Are 3.2 Progress Iteratively with Feedback and Collaborate and Promote Visibility 3.3 Think and Work Holistically, Keep It Simple and Practical, and Optimize and Automate 3.4 Applying and Balancing the Guiding Principles

4 The Four Dimensions of Service Management

4.1 Organizations and People 4.2 Information and Technology 4.3 Partners and Suppliers 4.4 Value Streams and Processes, and the PESTLE Factors

5 The Service Value System and Value Chain

5.1 The Service Value System: Purpose and Components 5.2 The Service Value Chain and Its Six Activities 5.3 Value Streams: How the Chain Creates Value 5.4 The Continual Improvement Model

6 Core ITIL Practices I

6.1 ITIL Management Practices Overview 6.2 Incident Management 6.3 Problem Management 6.4 Change Enablement

7 Core ITIL Practices II

7.1 Service Request Management and the Service Desk 7.2 Service Level Management 7.3 Continual Improvement (Practice) 7.4 Other Key Practices: Purpose and Key Terms

2.5 Outcomes, Costs, Risks, Utility and Warranty

Key Takeaways Explain This Topic AI

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

Services affect costs two ways: removing costs from the consumer and imposing costs on the consumer

Services affect risks two ways: removing risks from the consumer and imposing risks on the consumer

Utility is fitness for purpose — what the service does; warranty is fitness for use — how the service performs

  • Both utility AND warranty are required to create value; one without the other is insufficient
  • Last updated: June 2026

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.

Output Outcome

Definition A tangible or intangible deliverable of an activity A result for a stakeholder enabled by one or more outputs

  • Focus What is produced What the stakeholder wants to achieve
  • Owner Typically the provider produces it The consumer realizes it
  • Example A photo album; a monthly report Treasured memories; a confident business decision

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 : A vailability, C apacity, S ecurity, and C ontinuity.

Utility Warranty

Question it answers What does the service do? How well does the service perform?

  • Test it provides Fit for purpose Fit for use
  • Achieved by Supporting performance or removing constraints Availability, capacity, security, 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.