The ITIL Service Value Chain: Six Activities and Value Streams Explained
The service value chain is the operating model at the heart of the ITIL service value system. It describes six activities that an organisation combines in different sequences to create products and services and to turn demand into value. Understanding it helps you see where each practice fits and why “it depends” is so often the honest answer in service management.
The Six Activities
| Activity | Purpose | Typical examples |
|---|---|---|
| Plan | Shared understanding of vision, current status and direction across the organisation | Strategy, portfolio decisions, roadmaps, policies |
| Improve | Continually improve products, services and practices | Improvement initiatives, retrospectives, reviews |
| Engage | Good understanding of stakeholder needs, transparency and relationships | Customer meetings, service desk, feedback surveys |
| Design and transition | Products and services that meet expectations for quality, cost and time to market | Service design, testing, release planning |
| Obtain/build | Service components available when and where needed, and meeting specifications | Procurement, development, configuration |
| Deliver and support | Services delivered and supported to agreed specifications and stakeholder expectations | Incident handling, requests, operations |
Inputs and Outputs
Each activity receives inputs and produces outputs. Demand from outside enters through plan and engage; products and services leave through deliver and support; and improve touches everything. Activities also feed each other: engage passes requirements to design and transition; design and transition passes specifications to obtain/build; obtain/build passes components back; and deliver and support collects feedback that returns to improve. These flows are what the value chain diagram shows.
Value Streams
A value stream is a specific series of steps an organisation follows to create and deliver a product or service. Different value streams combine the six activities in different ways. The value chain is the general model; a value stream is one concrete route through it.
Worked Example 1: Resolving an Incident
| Step | Value chain activity |
|---|---|
| User reports slow email | Engage |
| Agent diagnoses and applies a fix | Deliver and support |
| Fix needs a configuration change | Obtain/build, then deliver and support |
| Repeat cause is raised as a problem and improvement | Improve |
Worked Example 2: Onboarding a New Employee
HR submits a joiner request (engage). The service desk checks the standard bundle (deliver and support). A laptop is ordered from the supplier (obtain/build) and configured. On the first day, IT delivers the equipment and confirms access (deliver and support). After a few weeks of feedback about slow delivery, the team streamlines the stream (improve), and the quarterly roadmap includes automated provisioning (plan).
Value Streams vs Processes
A process is a set of activities that transforms inputs into outputs, usually inside a practice. A value stream is wider: it may cross several practices, teams and suppliers. Mapping value streams reveals delays between teams that process documents never show, such as a ticket waiting three days in an approval queue.
Common Mistakes
- Reading the six activities as a fixed sequence.
- Forgetting improve and plan because they feel less urgent than delivery.
- Mapping processes inside one team while ignoring the delays between teams.
- The six activities are plan, improve, engage, design and transition, obtain/build, and deliver and support.
- Organisations combine them in different sequences to form value streams.
- A value stream is a concrete route through the chain and often crosses several teams.
- Mapping value streams exposes the delays that single-team process maps miss.