Skip to content
LeanSuite - Lean Manufacturing Software

Book summary · Flow and value stream mapping · Beginner

Learning to See: summary and review

Value-Stream Mapping to Add Value and Eliminate Muda

By Mike Rother and John Shook. First published 1999.

The short answer

Learning to See is a workbook that teaches value stream mapping: draw one product family's material and information flow from supplier to customer, then redesign it with eight future-state questions about takt time, finished goods, continuous flow, pull, a single scheduling point and mix. Rother and Shook adapted the method from Toyota's own flow maps and teach it through a fictional stamping plant. It suits repetitive manufacturing and teams mapping their first stream. It fits job shops, high-mix work and offices much less well.

Read it if

  • You are about to map your first value stream and want the standard method, with symbols and a worked example.
  • You are a supervisor or engineer who will sit in a mapping workshop and need to know what the map is supposed to produce.
  • You run repetitive, high-volume production and need a way to decide where flow, supermarkets and a single scheduling point belong.

Skip it if

  • Your work is high-mix job shop, project or office work. The method assumes a relatively stable flow through one product family.
  • You want an improvement routine. The book designs a target state but does not teach the daily practice of closing the gap.

When it pays off: After you have chosen a first product family and before you hold a mapping workshop. It is also worth rereading when your maps keep being drawn and then shelved.

The core ideas, in plain language

  1. 1

    Map one product family at a time

    A map covers a single family of products that share processing steps, from receiving to shipping. Mapping the whole plant at once produces a diagram nobody can act on. Choosing the family is the first decision and comes from a matrix of products against process steps.

  2. 2

    Walk the flow yourself

    The current-state map is built by walking the path from the customer end back to the supplier, with data recorded at each process: cycle time, changeover, uptime and shifts, plus the inventory between steps. The authors want the mapper to see the actual flow, not copy a planning system.

  3. 3

    Material and information flow together

    The tool draws both the material flow and the information flow that schedules it. The authors say the method is based on Toyota's material and information flow maps and leaves out the third Toyota flow, people and process.

  4. 4

    Eight questions design the future state

    The future state comes from answering eight questions in order: takt time, whether to build to a finished goods supermarket or straight to shipping, where continuous flow is possible, where supermarket pull is needed, the single pacemaker process that gets the schedule, how to level the mix, what increment of work to release there, and which improvements make it work. Improvements the design needs are marked as kaizen bursts and then grouped into loops with owners and dates.

  5. 5

    Pitch ties the schedule to the floor

    The increment released at the pacemaker is set from takt time and pack size. If takt is 30 seconds and a container holds 20 pieces, the pitch is 10 minutes, so the floor gets a steady beat that shows within minutes whether the plan is being met.

  6. 6

    It sits inside the Lean Thinking plan

    Womack and Jones wrote in the foreword that mapping the full value stream is the step of their action plan that many readers skipped, jumping to waste-removal blitzes that left the rest of the stream unchanged. The workbook exists to repair that.

How to use it on Monday morning

  1. 1

    Pick one family and bring the right three people

    Pick a product family that is on every shift's mind and bring a production planner, a supervisor and an operator who runs the longest step. Plan one hour. Their different views of where product waits are what makes the map worth drawing.

  2. 2

    Do a scan walk, no stopping

    Rother's advice is to walk the whole stream dock to dock at high altitude first. One hour is enough for a rough sketch. Add detail on later passes.

  3. 3

    Ask why the inventory is there

    Count what sits between steps, then ask for each pile what causes this much to be held here. Write the reason next to each pile, not only the count, because the reason is what you will have to remove.

  4. 4

    Work out takt before you draw a future state

    Divide available seconds per shift (paid time less breaks) by customer demand per shift. A shift of 27,600 available seconds with demand of 460 gives 60 seconds. Write it on the map before anything else, since every later decision depends on it.

  5. 5

    Set one target condition for one process

    Choose one process, usually the assembly step, and a target a few weeks to 12 months away. Run rapid trial cycles asking what blocks the target and what the next step is.

What to be careful about

  • A map is not an improvement

    In a 2004 article Rother wrote that some readers appeared to think mapping all value streams is the goal. He says improvement comes from moving toward a target condition and that mapping is only a tool. Graban also said maps do not make a plant lean; people do.

  • It assumes a simple flow

    Irani (2021) argues that the classic map assumes an assembly line making a limited range of similar products to stock, focuses on one product family, treats data box values as constant and is one snapshot in time. Taleghani and colleagues (2013) make the same case about variability and non-linear flow.

  • It is the authors' adaptation, not Toyota's method

    The introduction says Shook saw the mapping at Toyota as an afterthought and a simple means of communication, and that Toyota did not use it to train people. Rother and Shook formalized it as a teaching method. Do not assume it is how Toyota develops improvers.

  • Maps get overworked

    Rother warns against too much detail on a first pass, tallying inventory for its own sake and reaching too far into the future. Treat the symbols and eight questions as a way to start the conversation, not a form to fill in.

Learning to See compared with Value Stream Mapping: How to Visualize Work and Align Leadership for Organizational Transformation

Pick Learning to See for repetitive manufacturing, where takt, pull and a pacemaker process apply. Pick Karen Martin and Mike Osterling's 2013 book for office, service or other non-repetitive work, since its publisher describes it as covering leadership alignment, team building and charter development. Manufacturers who want both can read this one first.

Read the summary of Value Stream Mapping.

Tools and templates on LeanSuite that go with it

Book details

Bibliographic details of Learning to See
TitleLearning to See: Value-Stream Mapping to Add Value and Eliminate Muda
AuthorMike Rother and John Shook
First published1999. Lean Enterprise Institute workbook. The introduction is dated May 1998 and Rother says he and Shook wrote it in 1997; booksellers list the first edition as 1999, the year it won a Shingo Research Prize. Foreword by James Womack and Daniel Jones.
Edition shownWorkbook, current printing as listed by the publisher, Lean Enterprise Institute, 2018
ISBN-13978-0966784305
Pages148

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

Key terms

Lean glossary

FAQ

Questions about Learning to See

More lean books

Back to the lean books hub for reading paths and filters.

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.

Schedule Demo

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.