SkarpChapter 6 of 13
The Service Value Chain: From Demand to Value
Follow the path work takes through the Service Value Chain activities, seeing how plan, engage, design & transition, obtain/build, deliver & support, and improve combine into real value streams.
Big Picture: From Demand to Value
Service Value Chain in Context
In ITIL 4, the Service Value Chain (SVC) is the core operating model of the Service Value System (SVS). It shows how demand and opportunities are turned into value through connected activities.
Six Core Activities
The SVC has six activities: 1) Plan, 2) Engage, 3) Design & transition, 4) Obtain/build, 5) Deliver & support, and 6) Improve (which runs across everything).
Inputs, Practices, Outputs
Each activity takes inputs (requirements, information, components), uses practices (like incident management or change enablement), and produces outputs (products, services, knowledge, changes, or improvements).
What Is a Value Stream?
A value stream is a specific path through these activities for a purpose, such as resolving an incident, releasing a new feature, or onboarding a new customer.
No Single Fixed Flow
ITIL 4 does not define a single mandatory process flow. Organizations design their own value streams by combining the six activities in different sequences to fit their context.
The Six Service Value Chain Activities
Plan
Plan ensures a shared understanding of the vision, current status, and improvement direction for all products and services. Think strategies, roadmaps, portfolio decisions, and policies.
Engage
Engage provides a good understanding of stakeholder needs, transparency, and ongoing engagement. Think interacting with customers, users, and suppliers; capturing requirements and feedback.
Design & Transition
Design & transition ensures products and services meet stakeholder expectations for quality, costs, and time-to-market. Think designing services, preparing releases, testing, and change enablement.
Obtain/Build
Obtain/build ensures service components are available when and where needed, and meet agreed specifications. Think developing code, configuring infrastructure, and procuring technology.
Deliver & Support
Deliver & support ensures services are delivered and supported effectively and efficiently, in line with agreed specifications. Think service desk, incident handling, and daily operations.
Improve
Improve ensures products, services, and practices are continually improved across all value chain activities. Think spotting issues, analyzing data, and implementing measurable improvements.
A Simple Value Stream: Fixing a Critical Incident
Scenario Overview
Imagine a university’s learning platform goes down during online exams. We trace the value stream from the first complaint to restored service and later improvements.
Engage in an Incident
Students call the service desk; monitoring raises alerts. The service desk logs the incident, communicates, and updates stakeholders. This is about communication and understanding needs and impact.
Deliver & Support in Action
The incident team investigates and restores service: triage, diagnosis, workaround, and fix in production. This is operational work to run and support the service.
Obtain/Build for Deeper Fixes
If needed, developers create a code or configuration fix. Operations prepare infrastructure or scripts. This is creating or modifying components for the solution.
Design & Transition the Change
The fix is tested, approved, and deployed into production following change enablement. This is preparing and moving the change into live use.
Improve and Plan
A post-incident review identifies improvements (Improve). Management later uses incident trends to adjust strategy and roadmaps for the platform (Plan).
Value Streams: How Activities Combine
What Is a Value Stream?
A value stream is the end-to-end sequence of activities that creates value for a specific customer or stakeholder. It uses some or all of the six Service Value Chain activities.
Map vs Route
Think of the Service Value Chain as a map (six activities). A value stream is a route on that map, chosen for a specific scenario like a service request or a new product.
Typical Patterns
Examples: Service request: Engage → Deliver & support → Improve. New service: Plan → Engage → Design & transition → Obtain/build → Deliver & support → Improve.
Exam Technique
Underline verbs in scenarios: designing = Design & transition; building/buying = Obtain/build; running/operating = Deliver & support; gathering needs = Engage; setting direction = Plan; improving = Improve.
Identify the Activity: Quick Matching Exercise
Match each mini-scenario to the most relevant Service Value Chain activity. Think it through before checking your reasoning.
- A product owner and architecture team create a 3-year roadmap for the company’s digital services.
- Which activity is primary?
- Hint: It is about direction and shared understanding.
- The service desk gathers user feedback on a new feature and passes it to the development team.
- Which activity is primary?
- Hint: It is about understanding stakeholder needs.
- A team is testing a release candidate before it goes live.
- Which activity is primary?
- Hint: It is about preparing and moving changes into production.
- Developers are coding a new module for an existing application.
- Which activity is primary?
- Hint: It is about creating service components.
- The operations team monitors systems and resolves alerts to keep services running.
- Which activity is primary?
- Hint: It is about operating and supporting live services.
- A continuous improvement team analyzes incident trends and implements a new automation script to reduce incidents.
- Which activity is primary?
- Hint: It is about systematic improvement.
Pause and write your answers (1–6) on paper or in a note. Then compare with the key below.
Suggested answers (no peeking until you try):
- Plan
- Engage
- Design & transition
- Obtain/build
- Deliver & support
- Improve
Three Common Value Streams Side by Side
Service Request Value Stream
Scenario: a student requests access to a new tool. Flow: Engage (request and confirmation) → Deliver & support (grant access) → Improve (analyze data and refine or automate the request).
New Service Development Stream
Scenario: a new AI tutoring app. Flow: Plan → Engage → Design & transition → Obtain/build → Deliver & support → Improve.
Problem Resolution Stream
Scenario: Wi‑Fi drops nightly. Flow: Engage (reports) → Deliver & support (workaround) → Obtain/build (better solution) → Design & transition (deploy) → Deliver & support → Improve.
Flexibility of Value Streams
The same six activities appear in different orders and with different emphasis, depending on the scenario. That flexibility is a key feature of ITIL 4’s value stream approach.
Check Understanding: Activity Purposes
Choose the best answer for each question about Service Value Chain activities.
Which Service Value Chain activity is MOST responsible for ensuring that products and services meet stakeholder expectations for quality, costs, and time-to-market?
- Engage
- Design & transition
- Obtain/build
- Deliver & support
Show Answer
Answer: B) Design & transition
**Design & transition** is correct because its purpose is to ensure that products and services meet stakeholder expectations for quality, costs, and time-to-market. Engage focuses on stakeholder interaction, Obtain/build on creating components, and Deliver & support on operating and supporting live services.
Check Understanding: Value Streams
Another quick question to reinforce value stream flows.
A company is building a new analytics feature. Developers are writing code, and infrastructure engineers are setting up a new database cluster. Which Service Value Chain activity is MOST central to this work?
- Plan
- Engage
- Obtain/build
- Improve
Show Answer
Answer: C) Obtain/build
**Obtain/build** is correct because this activity ensures service components are available when and where needed and meet agreed specifications. Writing code and setting up infrastructure are classic Obtain/build work.
Key Terms Review: Service Value Chain Activities
Use these flashcards to quickly review the six Service Value Chain activities and the idea of value streams.
- Service Value Chain (SVC)
- The central operating model of the ITIL 4 Service Value System. It is a set of interconnected activities that convert demand and opportunities into value.
- Value stream
- An end-to-end series of steps (a route through the Service Value Chain) that an organization uses to create and deliver value to a specific customer or stakeholder.
- Plan (SVC activity)
- Ensures a shared understanding of the vision, current status, and improvement direction for all products and services.
- Engage (SVC activity)
- Provides a good understanding of stakeholder needs, transparency, and ongoing engagement with all stakeholders.
- Design & transition (SVC activity)
- Ensures that products and services meet stakeholder expectations for quality, costs, and time-to-market.
- Obtain/build (SVC activity)
- Ensures that service components are available when and where needed and meet agreed specifications.
- Deliver & support (SVC activity)
- Ensures that services are delivered and supported effectively and efficiently in line with agreed specifications.
- Improve (SVC activity)
- Ensures continual improvement of products, services, and practices across all value chain activities.
Apply It: Build a Mini Value Stream
Design a simple value stream for this scenario and label each step with a Service Value Chain activity.
Scenario:
Your university wants to introduce a new mobile app that lets students book study rooms in real time.
Task:
- Write down 4–6 steps that would realistically happen from idea to students using the app.
- Next to each step, assign the most relevant SVC activity.
Example structure (fill in your own details):
- → Plan or Engage?
- → Engage or Design & transition?
- → Obtain/build?
- → Design & transition?
- → Deliver & support?
- → Improve?
When you are done, compare with this sample answer:
- University leadership defines the goal and budget → Plan
- IT interviews students and librarians about needs → Engage
- Team designs the app workflow and prepares release plan → Design & transition
- Developers build the app and set up backend services → Obtain/build
- IT launches the app, supports users, and monitors usage → Deliver & support
- Team reviews usage data and feedback to refine features → Improve
Your exact steps can differ. What matters is that you can justify which activity each step belongs to based on its purpose.
Key Terms
- Plan
- Service Value Chain activity that ensures a shared understanding of the vision, current status, and improvement direction for all products and services.
- Engage
- Service Value Chain activity that provides a good understanding of stakeholder needs, transparency, and ongoing engagement with all stakeholders.
- Improve
- Service Value Chain activity that ensures continual improvement of products, services, and practices across all value chain activities.
- Obtain/build
- Service Value Chain activity that ensures service components are available when and where needed and meet agreed specifications.
- Value stream
- An end-to-end series of steps an organization uses to create and deliver value to a specific customer or stakeholder, implemented by combining Service Value Chain activities.
- Deliver & support
- Service Value Chain activity that ensures services are delivered and supported effectively and efficiently in line with agreed specifications.
- Design & transition
- Service Value Chain activity that ensures products and services meet stakeholder expectations for quality, costs, and time-to-market.
- Service Value Chain (SVC)
- The central operating model of the ITIL 4 Service Value System, consisting of six interconnected activities that convert demand and opportunities into value.
- Service Value System (SVS)
- The ITIL 4 model that describes how all components and activities of an organization work together as a system to enable value creation.