Skip to content
LeanSuite - Lean Manufacturing Software

Book summary · Flow and value stream mapping · Intermediate

Value Stream Mapping: summary and review

How to Visualize Work and Align Leadership for Organizational Transformation

By Karen Martin and Mike Osterling. First published 2013.

The short answer

This book treats a value stream map as a leadership alignment exercise, not a drawing exercise. Martin and Osterling take a team through five steps: prepare with a charter, map the current state with time and quality data, design the future state with leaders who can approve it, write a dated plan, then execute. Its examples lean toward office, service and knowledge work. It suits a manager or engineer chartering a stream that crosses departments. For a first map of a stamping or assembly line, start with Learning to See.

Read it if

  • You are chartering a stream that crosses departments, such as order to cash, and need directors in the room.
  • Your last map ended up on a wall.
  • Your lead time sits in queues of information, not piles of parts.

Skip it if

  • You want the plant floor notation and kanban loop design. Learning to See covers that.
  • You need to model variability.
  • You have no leadership sponsor. The method depends on senior people.

When it pays off: Before you charter a value stream map, and again before the future-state session when you decide who must attend. It pays off most after a map that led to no change.

The core ideas, in plain language

  1. 1

    Charter before you draw

    The team agrees in writing on where the stream starts and ends, the problem, targets, timeframe and how much change the organization can absorb. Martin calls the charter a communication, consensus and planning tool.

  2. 2

    Map the whole stream at low resolution

    An end-to-end stream has roughly 5 to 15 process blocks. A map with hundreds of blocks is a process map, which Martin says is what she mostly sees labeled as a value stream map.

  3. 3

    Three metrics for work you cannot touch

    Process time is the work time if uninterrupted. Lead time is elapsed time from available to passed on. Percent complete and accurate is how often the next person can work without correcting, adding or clarifying. Martin reports that a step scoring near zero is not rare.

  4. 4

    Walk the stream twice

    The first walk finds the processes and their sequence. The second collects metrics and barriers. Even when the work is data and email, go where it happens and ask the people doing it.

  5. 5

    Leaders design the future state

    Frontline staff supply current-state facts. Martin says the future state needs directors and above, since only they can merge departments. Otherwise the design must be sold upward and gets diluted.

  6. 6

    Three days in a row, ending with a plan

    Current state on day one, finish it and design the future on day two, then a plan with owners and dates on day three. Splitting the sessions adds rework. The plan guards against what Martin calls map wallpaper.

How to use it on Monday morning

  1. 1

    Draft the charter on one page

    Write the trigger that starts the stream, the event that ends it, the one number to move and the sponsor who can approve changes. Take 45 minutes, then show the sponsor.

  2. 2

    Do walk one with the people who do the work

    Spend two hours with sticky notes. List the process blocks in order, 5 to 15, describing the usual case, not the exception. Do not solve problems yet.

  3. 3

    Do walk two with three questions per block

    Ask how long the work takes uninterrupted, how long it sits before starting, and how often what arrives needs correcting. Check against recent real items, not memory.

  4. 4

    Put the dates on the plan now

    Book directors for the future-state session before the current state is finished, and agree that day three ends with a dated list with named owners.

What to be careful about

  • Pitched at office and service work

    The publisher pitches it at service and office settings, and Tim McMahon's 2014 review says the same. Expect less on material flow design than in Learning to See, which LEI describes as manufacturing-focused.

  • It depends on senior time

    Three consecutive days with directors and above is the hardest part to get in most plants. Run the method with a lower-level team and you reproduce the failure Martin warns about: a design nobody with authority owns.

  • A map is a snapshot

    Araibi, Shaiful and Shadhar (2023) note that a standard map records fixed values and cannot show variability. Use the map to pick where to look, then measure variation at that step.

  • Outcome evidence is thin

    The support found is a Shingo publication award (announced February 2015) and endorsements. No independent study of results turned up, so treat the claims as the authors' consulting experience.

Value Stream Mapping compared with Learning to See

Pick Learning to See (Rother and Shook) to map material and information flow on a plant floor with the standard notation and a worked stamping case. Pick Martin and Osterling when the stream crosses offices or the problem is getting leaders to act. Order to ship needs both.

Read the summary of Learning to See.

Book details

Bibliographic details of Value Stream Mapping
TitleValue Stream Mapping: How to Visualize Work and Align Leadership for Organizational Transformation
AuthorKaren Martin and Mike Osterling
First published2013. A paperback reissue by TKMG Press, the authors' own firm, was listed in November 2025 (not cited here, because its publisher page could not be retrieved).
Edition shownFirst edition, hardcover, McGraw-Hill Education, 2013
ISBN-13978-0071828918

Details checked against public records on 7 October 2026. Other editions have other ISBNs. We carry no affiliate links.

FAQ

Questions about Value Stream Mapping

Rather see it on your own problem?

Bring the problem you are stuck on, and we will show you on a call how LeanSuite handles it.

Pass it on

We want LeanSuite to be the best place on the internet for lean help. If this was useful, send it to someone on your team or in your network who needs it.