Set direction for service value creation and prioritisation.
Element 3
Build end-to-end service flow from demand to value.
The Service Value Chain is the operating model of ITIL 4. It defines six interlinked activities that transform demand into value through the creation, delivery and continual support of products and services.
It helps organisations see services as cross-functional systems rather than disconnected teams or handovers, making bottlenecks, ownership gaps and delays visible.
Use feedback and performance data to close the loop.
Shape expectations, relationships and service demand.
Coordinate testing, change, release and handover.
Connect procurement, engineering and platform delivery.
Handle incidents, requests, monitoring and day-to-day support with visible service outcomes.
Implementation guidance
- Identify demand-to-value scenarios such as customer onboarding or critical service restoration.
- Map those scenarios to value chain activities and expose delays, approvals and handovers.
- Align supporting practices, ownership and tooling to each activity.
- Design dashboards, feedback loops and improvement triggers around the live flow.
Evidence
Show how value actually flows.
- Documented value stream maps and linked value chain activities.
- Role accountability and approval gates by value chain step.
- Metrics by activity, such as changes transitioned on time.
- Practice maturity reviews mapped to value chain stages.
- Feedback loops and improvement plans linked to specific bottlenecks.
Visualise flow and friction.
ServiceNow or Jira Service Management for flow visibility, Miro or Lucidchart for stream mapping, and Power BI or Grafana for throughput, blockage and value dashboards.
Measure time, handoffs and automation.
Track time from demand to value, time spent per activity, handover frequency, automation coverage and backlog items tied to value stream blockers.
Fragmented delivery, unclear ownership and weak feedback loops.
Map full end-to-end streams, define activity leads, reduce unnecessary handoffs and use Improve to close the loop with real operating data.
Launch with a phased operating model approach.
Weeks 1–2 identify services and streams, Weeks 3–4 align practices and roles, Weeks 5–6 define KPIs and dashboards, then run retrospectives and performance reviews as a standing rhythm.