SkarpChapter 17 of 20
Managing and Improving Value Streams in Practice
Move beyond static diagrams to see how organizations govern, measure, and continually improve their value streams over time.
From Static Maps to Managed Value Streams
From Map to Management
You already know how to map value streams. Now we move from static diagrams to managing and improving value streams over time.
Value Streams in the SVS
A value stream is the series of steps an organization uses to create and deliver products and services, inside the service value system.
Continual Improvement Link
Real organizations must govern, measure, and improve value streams using continual improvement at all levels.
Guiding Principles Backbone
All of this is guided by the seven principles: focus on value, start where you are, progress iteratively with feedback, collaborate and promote visibility, think and work holistically, keep it simple and practical, optimize and automate.
Who Owns and Governs a Value Stream?
Value Stream Owner
A value stream needs a clear owner who is accountable for its performance from demand to outcomes.
Key Responsibilities
The owner defines purpose and scope, aligns with strategy, agrees on utility and warranty, clarifies roles, and sponsors improvements.
Governance Structure
Governance usually includes a cross-functional team, regular data-driven reviews, and links to higher-level governance bodies.
Holistic View
Picture a horizontal stream with the owner above it and teams along it, all aligned to one shared outcome across the six value chain activities.
Value Stream Metrics: What Do We Measure?
Why Metrics?
Metrics show whether a value stream is actually enabling value co-creation between provider and consumer.
Flow Metrics
Flow metrics include lead time, cycle time, work in progress, and throughput, showing how smoothly work moves.
Quality & Experience
Quality metrics track defects, incidents, and reliability; experience metrics capture satisfaction, NPS, and user feedback.
Cost & Outcomes
Cost and productivity metrics help judge efficiency, but always link them back to outcomes, not just raw output.
Feedback Loops: Keeping the Stream Alive
Why Feedback Loops?
Feedback loops turn static metrics into decisions and actions that keep the value stream healthy and evolving.
Operational & Tactical Loops
Short-cycle loops include daily huddles and dashboards; medium-cycle loops include sprint and service reviews.
Strategic Loops
Longer-cycle loops review the overall health and strategic fit of the value stream with senior stakeholders.
Link to Continual Improvement
These loops support the continual improvement model steps from "Where are we now?" to "Did we get there?" across the value stream.
Worked Example: Managing an Incident Resolution Value Stream
Incident Stream Overview
Demand starts when a user reports a disruption; the outcome is restored service. Engage, deliver and support, and improve are key activities.
Governance Setup
A Head of Service Operations owns the stream, with a cross-functional team and a monthly review using a simple dashboard.
Key Metrics
They track response and resolution times, backlog, reopen rates, change-related incidents, and user satisfaction after closure.
Feedback in Action
Daily huddles manage today’s flow; monthly and quarterly reviews drive improvements like better categorization or self-service.
Linking Value Streams to Management Practices and the Operating Model
Streams and Practices
Value streams connect ITIL practices into end-to-end flows; they do not replace practices.
Example: New Feature
A new feature stream uses change enablement, release and deployment, design, availability, incident, problem, and service desk.
Operating Model Link
The operating model explains how people, tech, suppliers, and value streams fit together across the four dimensions.
Exam Reminder
Avoid optimizing one practice in isolation; improvements should consider the whole stream and the service value chain.
AI and Automation in Value Streams (with Responsible Use)
AI in the Value Stream
AI and automation now appear across engage, design and transition, obtain/build, deliver and support, and improve activities.
Common Uses
Examples include chatbots, automated testing and deployment, code assistants, remediation scripts, and analytics.
Responsible Use
Modern regulations demand transparency, data protection, human oversight, and checks for bias and fairness in AI.
Exam Focus
Prefer answers that automate low-risk, repetitive work while keeping humans in charge of complex or high-impact decisions.
Thought Exercise: Where Would You Improve?
Work through this scenario and decide where you would target improvements in the value stream.
Scenario (read carefully):
- A SaaS company delivers an online learning platform.
- Teachers (users) submit requests for new features via a portal.
- Product managers review requests monthly and select a few for development.
- Development and testing usually take 2–3 weeks.
- Deployment is automated and takes minutes.
- However, teachers often wait 4–5 months before seeing their requested features, and many say they "never hear back" after submitting a request.
Questions to reflect on:
- Sketch the value stream in your head from demand to value. Where does demand enter? When is value realized?
- Which service value chain activities are clearly involved? (Hint: engage, plan, design and transition, obtain/build, deliver and support, improve.)
- Based on the data, where is the likely bottleneck? Is it development speed, deployment, or something else?
- Which metrics would you want to see to confirm your hypothesis (e.g. lead time per step, number of items waiting for review)?
- Suggest one low-cost improvement that follows "start where you are" and "progress iteratively with feedback".
Pause and jot down your answers before moving on. On the exam, similar scenarios appear as multiple-choice questions, but the thinking process is the same: trace the value stream, identify the constraint, then choose the option that improves flow and value, not just local activity.
Quick Check: Metrics and Feedback
Test your understanding of value stream metrics and feedback loops.
A team wants to improve its incident resolution value stream. They currently track only the number of tickets closed per day. Which additional metric and feedback mechanism combination best supports value stream management in line with ITIL guiding principles?
- Add a weekly report on how many tickets each agent closes; use it to rank agents from best to worst.
- Measure average resolution time and percentage of reopened incidents; review these in a daily 15-minute huddle to identify and remove blockers.
- Measure how many knowledge articles are written; review this monthly with senior management.
- Track total hours spent on incidents; send a quarterly email summary to all staff.
Show Answer
Answer: B) Measure average resolution time and percentage of reopened incidents; review these in a daily 15-minute huddle to identify and remove blockers.
Option 2 adds **flow** (average resolution time) and **quality** (reopen rate) metrics, plus a short feedback loop (daily huddle) that allows the team to act quickly. This aligns with "focus on value" and "progress iteratively with feedback". The other options focus on individual ranking, activity counts, or slow feedback that is less helpful for managing the value stream.
Quick Check: AI and Automation in Value Streams
Check how well you can apply AI and automation concepts to value streams.
In a request fulfillment value stream, which proposed use of AI and automation is MOST consistent with ITIL guidance and responsible practices?
- Use an AI system to automatically approve all access requests without human review, to speed up flow.
- Introduce a virtual agent that answers common "how do I" questions and routes more complex requests to human agents, while logging all interactions for analysis under the organization’s data protection rules.
- Replace the service desk with an AI chatbot that refuses to transfer users to humans, to reduce staffing costs.
- Use AI to secretly monitor employees’ personal messages to predict service issues before they are reported.
Show Answer
Answer: B) Introduce a virtual agent that answers common "how do I" questions and routes more complex requests to human agents, while logging all interactions for analysis under the organization’s data protection rules.
Option 2 automates low-risk, repetitive work (common questions and routing), keeps humans involved for complex cases, and explicitly follows data protection rules. This matches "optimize and automate" plus responsible AI practices. The other options remove human oversight or misuse data, which conflicts with ITIL’s emphasis on value, trust, and governance.
Flashcards: Core Terms and Lists
Use these flashcards to reinforce key ITIL terms and lists related to managing value streams.
- service
- A means of enabling value co-creation by facilitating outcomes that customers want to achieve, without the customer having to manage specific costs and risks.
- service value system (SVS)
- A model representing how all the components and activities of an organization work together as a system to enable value creation.
- service value chain
- A set of interconnected activities that an organization performs to deliver a valuable product or service to its consumers and to facilitate value realization.
- continual improvement
- A recurring activity performed at all levels to ensure that an organization’s performance continually meets stakeholders’ expectations.
- Seven guiding principles (list in order)
- 1) focus on value, 2) start where you are, 3) progress iteratively with feedback, 4) collaborate and promote visibility, 5) think and work holistically, 6) keep it simple and practical, 7) optimize and automate
- Six service value chain activities (in order)
- plan, improve, engage, design and transition, obtain/build, deliver and support
- utility
- The functionality offered by a product or service to meet a particular need.
- warranty
- Assurance that a product or service will meet agreed requirements.
- value co-creation
- The joint activities performed by a service provider and a service consumer to create value.
- ITIL Foundation (Version 5) exam domains (in order)
- 1) Key ITIL terms and definitions, 2) The four dimensions of product and service management, 3) The ITIL product and service lifecycle, 4) The ITIL Service Value System, 5) Value stream identification, mapping, and management, 6) ITIL and AI, 7) ITIL and other frameworks
Putting It All Together and Next Steps in Your Skarp Path
What You Learned
You moved from static value stream maps to understanding ownership, metrics, feedback loops, and improvement in practice.
Connections
Value streams run through the service value chain and rely on multiple practices working together, often supported by AI and automation.
Skarp Next Steps
Use the diagnostic, mock exams, and spaced review to strengthen scenario skills about where and how to improve value streams.
Keep Practicing
Look at real services around you and ask: who owns this stream, what do they measure, and where would I improve it?
Key Terms
- user
- A person who uses services.
- service
- A means of enabling value co-creation by facilitating outcomes that customers want to achieve, without the customer having to manage specific costs and risks.
- sponsor
- A person who authorizes budget for service consumption.
- utility
- The functionality offered by a product or service to meet a particular need.
- customer
- A person who defines the requirements for a service and takes responsibility for the outcomes of service consumption.
- warranty
- Assurance that a product or service will meet agreed requirements.
- flow metrics
- Measures that describe how work moves through a value stream, such as lead time, cycle time, work in progress, and throughput.
- value stream
- The series of steps an organization uses to create and deliver products and services to consumers, from demand to value realization.
- feedback loop
- A structured mechanism that takes information from activities or outcomes and feeds it back into decisions and actions to adjust or improve performance.
- service offering
- A description of one or more services, designed to address the needs of a target consumer group.
- value co-creation
- The joint activities performed by a service provider and a service consumer to create value.
- service management
- A set of specialized organizational capabilities for enabling value for customers in the form of services.
- value stream owner
- The role accountable for the performance and improvement of a specific value stream end to end.
- service value chain
- A set of interconnected activities that an organization performs to deliver a valuable product or service to its consumers and to facilitate value realization.
- service value system
- A model representing how all the components and activities of an organization work together as a system to enable value creation.
- continual improvement
- A recurring activity performed at all levels to ensure that an organization’s performance continually meets stakeholders’ expectations.