Value Stream Mapping (VSM)

See the whole flow of value, and where it stalls. Value stream mapping charts material and information flow end to end, separates value-added from non-value-added time, and turns a current-state map into a leaner future state.

Create Value Stream Map →

What is Value Stream Mapping?

Value stream mapping (VSM) is a Lean method for visualizing the complete flow of material and information required to deliver a product or service, from customer request to delivery. Unlike a simple process flowchart, it captures both the flow of work and the flow of information that triggers it, along with the time and inventory at each step.

The central analysis separates value-added time (steps the customer would pay for) from non-value-added time (waiting, transport, rework and other waste). The striking finding in most value streams is that value-added time is a tiny fraction of total lead time, so the biggest gains come from removing the waiting and queues between steps, not from speeding up the value-adding steps themselves.

VSM is done in two stages. A current-state map documents how the value stream works today, exposing where time and inventory accumulate. A future-state map then designs an improved flow, and the gap between them drives the improvement plan.

In plain terms: Value stream mapping draws your whole process end to end, including all the waiting between steps and the information that tells work to move. It almost always reveals a shocking truth: the actual work takes minutes, but the thing sits around for days. That waiting is where the real improvement is.

How VSM Works

Current-State Map

Document today's flow of material and information, with process times, wait times and inventory at each stage.

Value vs Non-Value Time

Separate value-added time from non-value-added time. The ratio (process cycle efficiency) usually reveals huge waiting waste.

Future-State Map

Design an improved flow that removes waiting and waste, then plan the changes to close the gap.

Key Formulas

Total lead time = Σ(process times + wait times)
Value-added time = Σ time customer would pay for
Process cycle efficiency = value-added time / total lead time
Takt time = available time / customer demand

Reading the Map

Process cycle efficiency, value-added time divided by total lead time, is usually a single-digit percentage. That gap is the opportunity: it shows that most lead time is waiting, so improvement should target the queues and handoffs between steps.

Takt time, the pace of customer demand, anchors the future state. Designing flow to takt, and removing the accumulations of inventory and waiting that the current-state map exposes, is how VSM converts a picture into a plan.

Assumptions & Validation

Single Product Family

The map covers one product or service family with a similar flow.

If violated: Group products into families first; mixing dissimilar flows muddies the map.

Real Observed Data

Times and inventory come from observing the actual value stream.

If violated: Walk the process and measure; do not rely on assumed times.

Whole-Stream Scope

The map spans the full door-to-door flow, not one department.

If violated: Extend the scope to include upstream and downstream steps where waste hides.

⚠️ Check assumptions first

The purpose of value stream mapping is to expose the waiting between steps, not to optimize individual steps in isolation. Mapping only one department, or focusing on speeding up value-adding steps that are already a small fraction of lead time, misses where the waste actually lives. Map the whole door-to-door flow with real observed times, and target the queues and handoffs the map reveals.

When NOT to Use Value Stream Map (VSM)

Detailed Step Logic

To document the decision logic within a single complex step, a standard process flowchart is more suitable.

Statistical Variation

To characterize variation in a step's cycle time numerically, control charts and capability analysis fit better.

Highly Variable Custom Work

For one-of-a-kind work with no repeatable flow, a standardized value stream may not exist to map.

Industry Applications

Lead-Time Reduction

Expose and remove the waiting that dominates total lead time in manufacturing or service flows.

Lean Transformation

Provide the current-state baseline and future-state target that anchor a Lean improvement roadmap.

Office & Service Processes

Map information-heavy processes such as order-to-cash or claims to find delays and handoff waste.

Kaizen Scoping

Use the future-state gaps to scope focused Kaizen events on the highest-impact segments.

Frequently Asked Questions

What is the difference between value stream mapping and a process flowchart?

A process flowchart shows the sequence of steps and decision logic within a process. A value stream map shows the broader flow of both material and information needed to deliver a product or service, along with the time and inventory at each stage, and it explicitly separates value-added from non-value-added time. VSM takes a whole-system, time-based view aimed at exposing waiting waste, whereas a flowchart focuses on step logic.

What is value-added versus non-value-added time?

Value-added time is time spent on activities the customer would willingly pay for, those that transform the product or service toward what the customer wants. Non-value-added time is everything else: waiting, transport, inspection, rework and storage. In most value streams, value-added time is only a small fraction of total lead time, which is why removing the non-value-added waiting yields the largest improvements.

What is process cycle efficiency?

Process cycle efficiency is value-added time divided by total lead time, expressed as a percentage. It quantifies how much of the total elapsed time actually advances the product toward the customer. Because most lead time in a typical value stream is waiting, this efficiency is often surprisingly low, single digits in many cases, which reveals the scale of the improvement opportunity.

What is takt time and how does it relate to VSM?

Takt time is the pace at which products must be completed to meet customer demand, calculated as available working time divided by demand over the same period. In value stream mapping, takt time anchors the future-state design: the flow is arranged so that work moves at the rhythm of demand, which helps balance the process and reveals where capacity is mismatched to need.

What is the difference between a current-state and a future-state map?

A current-state map documents how the value stream operates today, exposing where time, inventory and waste accumulate. A future-state map designs an improved flow that removes those wastes and moves closer to one-piece flow at takt. The difference between the two maps defines the improvement gap, and closing that gap becomes the basis for the Lean implementation plan.

Why should a value stream map cover the whole flow rather than one department?

Waste in a value stream lives mostly in the handoffs, queues and waiting between departments, not within them. Mapping only one department optimizes a local step while missing the larger delays that dominate lead time. A door-to-door map spanning the full flow, from customer request to delivery, is what exposes the systemic waiting that offers the greatest improvement potential.

See Where the Time Really Goes

Map the whole flow, expose waiting waste, and design a leaner future state. Free during Beta.

Create Value Stream Map →