ITIL v5 Compass
Digital Transformation & AI
Value Streams & Mapping

Value Streams and Value Stream Mapping

Why Value Streams

Organizations operate in diverse contexts with different roles in service relationships and varying digital product architectures. The ITIL Product and Service Lifecycle Model activities occur in unique workflows that deviate from predetermined models to adapt to current circumstances.

"Management practices contribute to lifecycle activities in varying combinations." Real-world workflows are never standardized; they form through many lower-level actions and responses.

To manage actual work (not just designed processes) and ensure value creation, organizations must identify, map, analyze, and continually improve their value streams.

Definition

A value stream represents "a series of steps an organization undertakes to enable value for consumers through management of products and services."

Key characteristics include:

  • The actual sequence performed, not a predetermined blueprint
  • Flow of information and artifacts created and transferred
  • End-to-end coverage across one or several organizations
  • Focus on enabling value for stakeholders

Value Stream Mapping and Management Goals

  • Focus on customer value and optimize end-to-end flows
  • Visualize value creation from initiation through delivery
  • Identify and eliminate waste to maximize value
  • Identify and implement workflow improvements

What Mapping Achieves

  • Shared understanding of organizational value creation
  • Clarity on how value is produced
  • Optimization of work and information flow with improved output quality

Core vs. Enabling Value Streams

Core value streams enable consumer value as intended by the operating model.

Enabling value streams support internal customers and sustain core streams (examples: procurement, supplier onboarding).

Value Stream Mapping Steps

Value stream identification

Start with consumer-oriented outputs and customer-facing catalogues. Use live walks through actual workflows or reverse mapping from recent outputs, combining both approaches for accuracy.

Mapping the as-is state

Document activities, timing, and relevant information. Calculate:

  • Cycle time: Duration of individual steps
  • Wait time: Delays between steps
  • Lead time: Total initiation-to-delivery duration
  • Flow efficiency: Ratio of value-added time to lead time

Classify activities as value-adding, supporting, coordinating, or non-value-adding.

Analyzing the stream

Identify bottlenecks, dependencies, and improvement opportunities through time metrics and end-to-end examination. Balance flow efficiency with output quality -- optimization cannot sacrifice service standards.

Mapping to-be improvements

Two approaches:

  • Ideal maps: Perfect flow with zero waits (inspirational)
  • Feasible maps: Realistic improvements targeting three-to-six month horizons

Planning and implementing changes

Address internal changes across all four dimensions (organization, competencies, processes, automation) and external dependencies (suppliers, contracts, inter-organizational cooperation).

Value Stream Management

One-time mapping exercises rarely sustain improvements. Organizations adopt ongoing value stream management -- continuous focus on actual work, analysis, and improvement understanding of the entire stream network.

⚠️

Value streams display high variability and require indirect management through improving underlying management practices and products/services. Individual practice improvements can affect multiple streams simultaneously.