2.4.3. Output and Outcome
💡 First Principle: An output is what gets produced; an outcome is what changes for the stakeholder as a result. Confusing them is the single most common way organizations fool themselves into thinking they've created value when they haven't.
An output is a tangible or intangible deliverable produced by an activity — a report, a deployed feature, a resolved ticket. An outcome is a result for a stakeholder, enabled by one or more outputs — the decision the report informed, the job the feature made easier, the work the user resumed after the ticket closed.
Understanding the difference: you can pile up outputs and produce no outcome. A dashboard nobody acts on is an output without an outcome. ITIL relentlessly redirects attention from outputs (which providers love to count) to outcomes (which consumers actually care about).
⚠️ Exam Trap: This is a guaranteed exam favourite. Test yourself: "feature deployed" = output; "users complete checkout faster" = outcome. If an option calls a deliverable an outcome, check whether it names a result for a stakeholder or just a thing produced.
Reflection Question: A team proudly reports "we closed 500 tickets this month." Why might that be an output boast that says nothing about outcomes?
