2.1.7. Utility, Warranty, User Experience, Sustainability
💡 First Principle: These four are the dimensions along which value is judged — utility asks does it do the job?, warranty asks does it do the job well enough?, experience asks how did it feel?, and sustainability asks can we keep doing this responsibly?
Utility is the functionality offered by a product or service to meet a particular need — "fitness for purpose," or what it does. Warranty is the assurance that a product or service will meet agreed requirements — "fitness for use," covering availability, capacity, security, and continuity, or how well it performs. A service needs both: a feature-rich app (utility) that's always crashing (no warranty) creates no value, and a rock-solid app that does nothing useful is equally worthless.
User experience (UX) is the sum of a user's interactions with a product or service and how they feel about it. Sustainability is the ability to maintain value over the long term, balancing economic, social, and environmental considerations — a concept given new prominence in Version 5.
| Term | Question it answers | One-word anchor |
|---|---|---|
| Utility | Does it do what's needed? | Purpose |
| Warranty | Does it perform reliably enough? | Use |
| User Experience | How did using it feel? | Feeling |
| Sustainability | Can we keep doing this responsibly? | Longevity |
⚠️ Exam Trap: Utility and warranty are the most-confused pair in this set. Memorize the anchor: utility = fitness for purpose (both have "p"-sounds: purpose), warranty = fitness for use. You need both for value — a question offering only one as "sufficient for value" is wrong.
Reflection Question: A service has excellent utility but poor warranty. Why does ITIL say no value is created, rather than "partial value"?
