Output vs Outcome in ITIL 4
An IT department deploys a new CRM system. The project team delivers the software on time and within budget. However, sales staff find the system cumbersome and continue using spreadsheets. Which ITIL 4 concept best describes this situation?
Quick Answer
The answer is that the output was achieved but the outcome was not. In ITIL 4, an output is a tangible deliverable—like the deployed CRM software—while an outcome is the actual business result, such as improved sales efficiency. Here, the project delivered the software on time and within budget (output), but because the sales staff found it cumbersome and continued using spreadsheets, the desired improvement in performance never materialized (outcome). This scenario is a classic ITIL 4 Foundation exam trap: it tests your ability to distinguish between delivering a product and achieving value. Many candidates mistakenly focus on the successful deployment, overlooking the critical adoption and behavior change required for a true outcome. A helpful memory tip is to think of output as “what you produce” and outcome as “what you achieve”—if nobody uses the output, the outcome fails.
⚠ Common exam trap
Many candidates confuse 'output' with 'outcome' or incorrectly attribute the failure to warranty issues, when in fact the system was delivered as promised (output) but did not deliver the intended business result (outcome).
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The output was achieved but the outcome was not
The project team achieved the output (delivering the CRM system on time and within budget) but failed to achieve the desired outcome (sales staff actually using the system to improve their work). In ITIL 4, an output is a tangible deliverable, while an outcome is the result for stakeholders—here, the outcome of improved sales efficiency was not realized, as staff reverted to spreadsheets.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Value co-creation failed due to poor warranty
Why it's wrong here
Value co-creation failed due to poor adoption, not warranty.
- ✗
The service has warranty but lacks utility
Why it's wrong here
Warranty may be fine, but the functionality (utility) may not meet user needs, but the core issue is outcome vs output.
- ✓
The output was achieved but the outcome was not
Why this is correct
The output (system) was delivered, but the outcome (improved efficiency) was not realized.
- ✗
The service has utility but lacks warranty
Why it's wrong here
The issue is not about warranty (availability, capacity); it's about achieving the intended outcome.
Go deeper
Related to this question
About these practice questions
Courseiva writes every ITIL4F question from scratch — 531 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
5 more ways this is tested on ITIL4F
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A software development team delivers a new feature to the marketing department. The feature is working but the marketing team reports no increase in campaign effectiveness. Which ITIL 4 distinction does this illustrate?
medium- ✓ A.Output vs Outcome
- B.Incident vs Problem
- C.Service Request vs Change
- D.Utility vs Warranty
Why A: ITIL 4 distinguishes between 'output' (a tangible deliverable, such as a working software feature) and 'outcome' (the actual business result, such as increased campaign effectiveness). In this scenario, the team delivered the output (the feature works), but the desired outcome (improved marketing performance) was not achieved, illustrating the critical gap between delivering a product and realizing business value.
Variation 2. A software development team delivers a new feature (output) but users find it difficult to use, resulting in low adoption. Which statement BEST describes this situation?
medium- A.An outcome was delivered, but the output was not produced
- B.The service has warranty but not utility
- ✓ C.An output was delivered, but the desired outcome was not achieved
- D.The service has utility but not warranty
Why C: The team successfully produced the new feature (the output), but users found it difficult to use, leading to low adoption. In ITIL 4, an output is a tangible or intangible deliverable, while an outcome is the actual result or value achieved for stakeholders. Here, the output was delivered, but the desired outcome—user adoption and value realization—was not achieved.
Variation 3. An organisation implements a new human resources (HR) system. The project team delivers the system on time and within budget. However, HR staff find the system difficult to use and employee satisfaction with HR services does not improve. According to ITIL 4, which statement describes this situation?
hard- A.The output and outcome are the same in this context
- B.The outcome (employee satisfaction) was achieved, but the output (delivery) failed
- ✓ C.The output (system delivery) was successful, but the outcome (improved satisfaction) was not achieved
- D.The output and outcome were both achieved
Why C: In ITIL 4, an output is a tangible deliverable (e.g., the HR system delivered on time and within budget), while an outcome is the result for stakeholders (e.g., improved employee satisfaction). The scenario shows the output was successful, but the outcome was not achieved because the system was difficult to use and satisfaction did not improve. Option C correctly identifies this mismatch.
Variation 4. A hospital IT department implements a new patient record system that requires doctors to double-enter data. Although the system works correctly, doctors complain it increases their workload. According to ITIL 4, this is an example of:
medium- A.A positive outcome due to utility
- ✓ B.An output without a positive outcome
- C.A warranty failure
- D.A successful service relationship
Why B: The new patient record system produces an output (the record is created and stored correctly), but doctors must double-enter data, which increases their workload and reduces efficiency. In ITIL 4, a positive outcome requires that the service not only meets functional requirements (utility) but also supports the user's goals without negative side effects. Here, the system fails to deliver a positive outcome because it degrades the user experience and adds unnecessary effort, even though the output is technically correct.
Variation 5. An IT team develops a new mobile app for employees to submit expense reports. The app processes reports and sends them to the finance system. Which of the following is an OUTPUT of the app?
hard- ✓ A.A processed expense report is sent to the finance system
- B.Employee satisfaction improves
- C.Finance team spends less time on data entry
- D.Employees receive reimbursement faster
Why A: The app's output is the direct, tangible result of its processing function: a processed expense report sent to the finance system. In ITIL 4, an output is a specific deliverable created by an activity, not the broader outcome or benefit that follows. Here, the app's core technology—processing expense data and transmitting it via an API or file transfer—produces this report as its immediate, measurable result.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This ITIL4F practice question is part of Courseiva's free PeopleCert certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the ITIL4F exam.