methodatlas
Method guideDelivery

Value Stream Mapping

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityMedium
Time1-3 h
Participants4-10
FormatWorkshop
MaturityCanonical
Prepare plan
01

Prerequisite

What needs to be finished first

Complete firstClear scope

One product family and clear start/end points, with access to actual work and participants.

Without a boundary, data, perspectives, or flows become mixed.
Complete firstAccess to evidence

Relevant people and sources can be included.

Gaps remain visible; missing evidence must not be invented.
02

Preparation

What needs to be ready before start

Materials

Shared workspace, accessible sources, and a decision log.

People / roles

Process participants · facilitator · data owner

Pre-read

Clarify the question, timeframe, data access, roles, and known uncertainties in advance.

Time needed

2–4 hours for a prepared value stream; arrange observation and measurement in advance.

Setup

Create a shared version. Label facts, assumptions, and decisions separately.

03

Core question

The one question this method answers

How does one concrete work item move from request to delivery today?

04

Flow

Phases with goal, actions, output and pitfall

Value Stream Mapping makes the actual information and work flow for a product family visible, including waits and lead times. The representation supports a justified next improvement step.

Current flow with lead and processing time

Fictional worked example

Make the actual information and work flow for a product family visible, including waits and lead times.

Product family

Define product family, start, end, and demand.

Software change from confirmed need to production.

Current flow

Map observed steps, information flow, and inventory.

Triage waits 96 h; implementation 1.5 h; review waits 72 h; testing 2 h; deployment waits 24 h.

Measures

Record processing time, wait, and units per step.

Lead time: 195.5 h. Processing time: 3.5 h. Sample of 12 changes.

Next test

Connect bottleneck to future state, experiment, and owner.

Fictional hypothesis: scheduled review windows reduce review wait; inspect weekly.

Fictional software change: request waits 96 h before triage, implementation takes 1.5 h, review waits 72 h, testing takes 2 h, deployment waits 24 h. Observed lead time: 195.5 h; processing time: 3.5 h. Values come from event records and a sample.

Understanding the Fundamentals of Value-Stream Mapping · Lean Enterprise Institute

  1. 1

    Scope

    Choose product family and scope

    Goal

    Are all participants looking at the same flow?

    Inputs for this step

    • Product family, customer value, and flow boundary

    Actions

    • Bound the stream by customer value, demand, and the end of the flow.
    • Are all participants looking at the same flow?

    Output

    Bounded product family and flow limits

    Bounded product family and flow limits

    Quality check

    Are all participants looking at the same flow?

    Pitfall

    Workshop map replaces observation Follow actual work and verify timestamps and queues in the process.

    Timing: Part of the agreed work block; research may be separate.

  2. 2

    Current flow

    Observe current state at the work

    Goal

    Are values observed rather than planned?

    Inputs for this step

    • Work items, handoffs, and direct observation

    Actions

    • Follow items; map steps, handoffs, queues, and information signals.
    • Are values observed rather than planned?

    Output

    Observed current flow with handoffs and queues

    Observed current flow with handoffs and queues

    Quality check

    Are values observed rather than planned?

    Pitfall

    Lead time confused with processing time Report wait and processing separately using the same system boundary.

    Timing: Part of the agreed work block; research may be separate.

  3. 3

    Measures

    Measure time and inventory

    Goal

    Are lead time and cycle time distinguished?

    Inputs for this step

    • Timestamps, inventory, wait, and processing times

    Actions

    • Record processing time, wait, inventory, and lead time with defined units.
    • Are lead time and cycle time distinguished?

    Output

    Time data separating processing and wait

    Time data separating processing and wait

    Quality check

    Are lead time and cycle time distinguished?

    Pitfall

    Improvements collected before current state Complete an evidence-based current flow before future-state ideas.

    Timing: Part of the agreed work block; research may be separate.

  4. 4

    Future state

    Choose future state and next test

    Goal

    Does the future state follow from current-state evidence?

    Inputs for this step

    • Evidence-based bottlenecks and improvement question

    Actions

    • Mark bottlenecks, design a testable future state, and assign the first improvement.
    • Does the future state follow from current-state evidence?

    Output

    Derived future state and first improvement test

    Derived future state and first improvement test

    Quality check

    Does the future state follow from current-state evidence?

    Pitfall

    Product family scope too broad Narrow to similar flow and demand; mark exceptions.

    Timing: Part of the agreed work block; research may be separate.

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

Value Stream Mapping · Current StateEnd-to-End-Arbeit mit Prozesszeit, Wartezeit, Informationsfluss und Engpass sichtbar machen
Value Stream MappingDas Visual zeigt Kundenbedarf, Prozessschritte, Wartezeiten, Informationsfluss und Kaizen Burst.Wertfluss, Wartezeit und Engpass trennenCurrent State zeigt, wo Arbeit wertschöpfend läuft und wo sie zwischen Schritten wartet.Steuerung / PrioritätPlanung, Pull-Signal, Expedite-RegelnFlowQueueHandoffWertEngpassKundenbedarfRequestKundenwertgeliefertAnalysePT 2 hBuildPT 6 hReviewPT 1 hWartezeit 2 dWartezeit 5 dWartezeit 3 dKaizen BurstBuild-Wartezeit begrenzen
Form

Versioned result with question, evidence, open issues, next action, ownership, and review date.

Versioning / ownership

Record date, scope, sources, and changes. Preserve earlier observations.

Tool alternatives
  • Whiteboard or paper
  • Shared spreadsheet
  • Versioned project space

value-stream-mapping-working-template.md

Prepare Value Stream Mapping with a clear question, roles, and sources.

Value Stream Mapping: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Plan the full method Time: Set according to scope and available evidence

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

  • Materials: Shared workspace, accessible sources, and a decision log.
  • Roles: Process participants · facilitator · data owner
  • Advance information: Clarify the question, timeframe, data access, roles, and known uncertainties in advance.
  • Overall time needed: 2–4 hours for a prepared value stream; arrange observation and measurement in advance.
  • Setup: Create a shared version. Label facts, assumptions, and decisions separately.

Prepare for the work steps

Scope: Choose product family and scope

  • Product family, customer value, and flow boundary

Current flow: Observe current state at the work

  • Work items, handoffs, and direct observation

Measures: Measure time and inventory

  • Timestamps, inventory, wait, and processing times

Future state: Choose future state and next test

  • Evidence-based bottlenecks and improvement question

Current flow with lead and processing time

Product family

Define product family, start, end, and demand.

...

Current flow

Map observed steps, information flow, and inventory.

...

Measures

Record processing time, wait, and units per step.

...

Next test

Connect bottleneck to future state, experiment, and owner.

...

Blank worksheet: start with a bounded question. Enter observed facts only, mark assumptions, and record open questions and sources.

Understanding the Fundamentals of Value-Stream Mapping · Lean Enterprise Institute

Scope: Choose product family and scope

Expected artifact: Bounded product family and flow limits

Bounded product family and flow limits

Entry:

...

  • Are all participants looking at the same flow?

Current flow: Observe current state at the work

Expected artifact: Observed current flow with handoffs and queues

Observed current flow with handoffs and queues

Entry:

...

  • Are values observed rather than planned?

Measures: Measure time and inventory

Expected artifact: Time data separating processing and wait

Time data separating processing and wait

Entry:

...

  • Are lead time and cycle time distinguished?

Future state: Choose future state and next test

Expected artifact: Derived future state and first improvement test

Derived future state and first improvement test

Entry:

...

  • Does the future state follow from current-state evidence?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/value-stream-mapping/run-sheet

06

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

value-stream-mapping-beispiel.md

Concrete filled scenario, fictional example

Fictional worked example

Fictional software change: request waits 96 h before triage, implementation takes 1.5 h, review waits 72 h, testing takes 2 h, deployment waits 24 h. Observed lead time: 195.5 h; processing time: 3.5 h. Values come from event records and a sample.

All data is invented. Lead time includes wait and processing; the two time types stay separate.

07

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

  1. Choose product family and scopeWorkshop map replaces observationView in phase
  2. Observe current state at the workLead time confused with processing timeView in phase
  3. Measure time and inventoryImprovements collected before current stateView in phase
  4. Choose future state and next testProduct family scope too broadView in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

The question or boundary remains ambiguous: narrow it first.
Key data or participants are missing: label the gap and arrange access.
The group mixes observation and explanation: revisit the evidence.
An immediate safety or operational risk appears: stop and use the responsible procedures.

Where to go next?

A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving

Carries a flagged bottleneck into structured problem solving.

Visual Management workspace showing the question, observations, and next decision.
Operations
Visual Management

Makes the agreed target state visible and checkable day to day.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profileMore methods