1.2. Value as the Organizing Idea

💡 First Principle: Everything in ITIL points back to value — and value is never something a provider simply hands over; it's something the provider and the consumer create together, which is why "co-creation" is the load-bearing word in the entire framework.

Here's the intuition. A gym doesn't make you fit. It provides equipment, space, and guidance — but the value (being fitter) only materializes when you show up and use it. The gym co-creates the outcome with you; neither side produces it alone. Software services work the same way: a provider can deliver a flawless platform, but if it doesn't fit how the consumer actually works, no value appears.

This reframes the provider's job. The goal isn't to produce outputs (a working server, a delivered feature) — it's to enable outcomes (the customer accomplishes something they care about). An organization can hit every delivery target and still fail to create value, because outputs are what you make and outcomes are what the other party actually wanted.

Value is shaped by more than just the desired outcome. It's a balance of outcomes the consumer wants, the costs they take on or avoid, and the risks they accept or hand off. A service that delivers a great outcome but at ruinous cost or unacceptable risk hasn't created much value. Keeping these three in tension is the heart of ITIL thinking, and you'll see this triad — outcomes, costs, risks — return again and again.

💡 Key Point: When in doubt on any ITIL question, ask "does this help value get co-created for the consumer?" Most correct answers point toward co-created value; most distractors point toward provider-side activity for its own sake.