Value Stream Mapping: How to See and Eliminate Waste in Any Process

Value stream mapping is the lean practitioner’s most powerful diagnostic tool. A good value stream map shows, on a single page, every step a product or service goes through from customer order to delivery, the time each step takes, the inventory and information that flows between them, and the gap between value-adding and non-value-adding activity. Once you can see the value stream clearly, the waste becomes impossible to ignore.

This article explains what a value stream map is, how to build one, and how it fits inside both pure Lean deployments and the Lean Six Sigma DMAIC framework taught by the International Lean Six Sigma Institute.

Origins and Why Value Stream Mapping Works

Value stream mapping has its roots in Toyota’s ‘material and information flow diagrams’, which were used internally for decades before being introduced to a wider audience by Mike Rother and John Shook in the 1999 Lean Enterprise Institute workbook Learning to See. The reason the technique spread so quickly outside Toyota is that it makes waste visible in a way no spreadsheet ever does.

The map combines three layers of information that are usually scattered across different systems: the physical flow of material (or work, in a service setting), the flow of information that triggers the work, and the time the work takes at each step. Putting all three on one page produces a shared reference that operators, supervisors, and senior leaders can all read.

The Lean Enterprise Institute maintains an excellent reference on value stream mapping fundamentals, written by the people who introduced the practice to the world outside Toyota.

The Anatomy of a Value Stream Map

A standard value stream map has four sections.

• The customer block, top right, showing demand: how many units per day, how many distinct part numbers, what the takt time is.
• The information flow, top section, showing forecasts, orders, schedules, and the production control system that coordinates everything.
• The process boxes, middle section, showing each step in sequence with a data box underneath recording cycle time, changeover time, uptime, number of operators, and any other relevant metrics.
• The timeline, bottom, showing process times against waiting times, and culminating in a total lead time and a total value-adding time.

That final timeline is where the diagnosis happens. In a typical first map, the team discovers that total lead time is days or weeks while total value-adding time is minutes. The ratio (process cycle efficiency) is often below 5 percent. Once that gap is visible, the question ‘where should we improve?’ becomes obvious.

Current State, Future State, Action Plan

Value stream mapping is a three-step exercise. The current state map captures the process as it actually is, not as the documentation says it is. The future state map, drawn after analysis of the current state, shows the target configuration after improvements. The action plan lists the projects required to move from current to future state, with owners and deadlines.

The current state map is built by walking the process, not by sitting in a conference room with the org chart. The team starts at the customer end and works upstream, recording what they see and timing operations directly. Operators are interviewed, but the map reflects observation, not memory or assumption.

The future state map is built around specific lean concepts: pulling work from downstream rather than pushing it from upstream, levelling production to match takt time, creating continuous flow where possible, and using supermarkets only where flow is impossible. The future state is not a wish list; it is a target that the team intends to reach in three to twelve months.

Where Value Stream Maps Fit Inside DMAIC

Value stream mapping has become a standard tool in the Define and Measure phases of DMAIC projects, even though it originated outside Six Sigma. It does several things no other tool does at once.

In Define, the map establishes the scope of the project visually. A team that says ‘we are improving the customer onboarding process’ often discovers, during mapping, that the process they thought they were improving has six handoffs they did not know existed and three approval gates that take days each.

In Measure, the timeline at the bottom of the map produces baseline metrics for lead time, process time, and process cycle efficiency. These complement the cause-specific data collected in the same phase.

In Improve, the future state map becomes the structured target for the redesign, ensuring that local improvements add up to a globally improved value stream rather than just shifting bottlenecks.

For practitioners working towards certification, value stream mapping is covered in both the ILSSI Yellow Belt and Green Belt programmes.

The Seven (or Eight) Wastes

Lean identifies seven categories of waste, traditionally enumerated as transportation, inventory, motion, waiting, overproduction, over-processing, and defects. The acronym TIMWOOD makes them easier to remember. Many modern practitioners add an eighth, the under-utilisation of human talent, giving TIMWOODS.

A value stream map makes each type of waste visible. Inventory waste shows up as triangles between process boxes. Waiting waste shows up in the timeline at the bottom. Overproduction shows up in the gap between customer demand and actual production rates. Defects show up in the rework loops back upstream. Once the team has the vocabulary and the map, the conversation moves from ‘we are too slow’ to ‘we have a 14-day waiting waste between order entry and credit check, and we should attack that first’.

Service and Office Value Streams

Value stream mapping was developed in manufacturing but has been applied successfully in office processes, healthcare, software development, and many service industries. The mechanics are the same: walk the process, time each step, record the information flow, draw it on one page. The vocabulary adapts: ‘inventory’ becomes ‘work-in-progress’, ‘changeover’ becomes ‘setup time’, ‘machine’ becomes ‘system’ or ‘person’.

In healthcare, value stream maps of patient journeys routinely reveal multi-day waits between five-minute clinical interactions. In software development, value stream maps reveal weeks of waiting between hours of actual coding. The improvements that flow from these maps are often substantial, because the inefficiencies are systemic and have never been visible in a single view before.

Common Mistakes

• Drawing the map in a conference room from memory. The map must be built by walking the process.
• Skipping the timeline at the bottom. The total lead time vs total value-adding time comparison is the central insight; without it the map is just a flowchart.
• Trying to map the entire enterprise in one go. Pick a product family or service stream, not the entire business.
• Building a beautiful future state map and never converting it into a project list with owners and deadlines.
• Treating the map as a deliverable rather than a tool. The map exists to drive action, not to hang on a wall.

Practical Tips From Real Deployments

Use paper or a whiteboard for the first map, not software. The point of the exercise is collective seeing, and software tends to push the conversation towards layout and aesthetics rather than process understanding. Software comes into its own for the final published version, after the thinking is done.

Time every step yourself with a stopwatch. Asked times are almost always wrong, usually because operators report the time when things go well rather than the time across the full distribution of conditions.

Include the information flow at the top of the map. Many improvements come from simplifying the information flow rather than the material flow. The number of scheduling systems that touch a typical process often exceeds the number of process steps.

Set the future state map to a horizon of three to twelve months. Maps drawn against a five-year horizon are aspirational; maps drawn against a six-week horizon are too short to allow systemic change. The middle is where action plans actually deliver.

Final Thoughts

Value stream mapping survives every fashion in lean and continuous improvement because it answers a question every organisation needs to answer: where is the time going? Once the answer is visible on a single page, the rest of the lean toolkit (kaizen, 5S, kanban, standard work) has something specific to work on. A team that learns to map well has acquired one of the most durable skills in operational excellence.

To begin your value stream mapping training within an accredited Lean Six Sigma framework, explore the ILSSI training and certification options.