Value Stream Mapping (VSM)

Value Stream Mapping is one of the most powerful and widely used tools in the Lean practitioner's toolkit. It provides a visual representation of how value flows through a process — from the initial trigger (a customer order, a purchase requisition, an incoming request) to the final delivery of the product or service. Crucially, it makes visible not just the value-adding steps, but the waiting, rework, overprocessing and excess inventory that consume time and resources without adding value for the customer.

Originally developed as part of the Toyota Production System and popularized by the 1998 book Learning to See (Rother and Shook), VSM has since been applied across manufacturing, healthcare, finance, logistics and service industries.

The Core Concept: Value vs. Waste

VSM is built on a fundamental Lean distinction: not all activity is value. From the customer's perspective, value is created only when a product is actually being transformed or a service is genuinely being delivered. Everything else — waiting, transporting, correcting errors, doing work twice — is waste that adds cost and time without adding value.

A value stream map makes this distinction visible for an entire process. It typically shows that in most administrative and logistics processes, the ratio of value-adding time to total lead time is dramatically low — often below 10%. The rest of the time, work is waiting in queues, being reworked, sitting in inventory or being processed unnecessarily.

The VSM Process: Current State to Future State

A VSM exercise follows a structured sequence:

1. Select the value stream

Choose a specific product family or service line as the scope. VSM works best at the level of a single end-to-end value stream — Order-to-Cash for a specific product category, for example — rather than attempting to map the entire organization at once.

2. Map the current state

Walk the process — physically or through direct observation — from end to end. Document each step, the time it takes (cycle time), the wait time between steps, the number of items in queue (inventory) and how information flows. The result is a current state map that shows the process as it actually runs, not as it is documented.

The summary timeline at the bottom of the map contrasts value-adding time (time when the product or service is actually being worked on) with total lead time (elapsed time from start to delivery). This ratio — often revealing — is one of the most powerful outputs of a VSM exercise.

3. Identify improvement opportunities

With the current state visible, the team identifies the most significant sources of waste: long waits between steps, large work-in-progress queues, rework loops, sequential handoffs that could be parallelized. Kaizen bursts (improvement action markers) are added to the map to indicate where improvement focus is needed.

4. Design the future state

The future state map redesigns the value stream with the identified improvements applied. It should reflect a realistic near-term target — typically achievable within 6-12 months — rather than a theoretical ideal. The future state map becomes the implementation blueprint.

5. Implement and measure

The improvement plan derived from the future state map is implemented in prioritized phases. Progress is measured against the baseline metrics established during current state mapping — lead time, value-adding ratio, defect rate, queue depths.

VSM for Office and Administrative Processes

Applying VSM to administrative processes — invoice processing, order management, approval workflows, HR onboarding — follows the same principles as manufacturing VSM, but the "materials" are information rather than physical goods:

• The flow unit is a transaction, a document or a request rather than a physical item
• Inventory corresponds to work queues — documents waiting for review, approvals pending, open tasks in a backlog
• Cycle time is the active processing time for each step; wait time is the time between steps
• Information flows include the systems, emails and handoffs through which the work progresses

VSM and Process Mining: Complementary Approaches

Traditional VSM relies on direct observation and team workshops. This means the current state map reflects what participants believe the process looks like — which may differ significantly from what actually happens, particularly for complex, high-volume processes with many variants.

Process mining constructs the process map from event log data — showing the actual flows, frequencies and timings extracted from the ERP or other source systems. For organizations running Business Central, process mining can produce a data-accurate current state picture significantly faster than manual VSM observation. The event data already exists in the ERP; the question is whether it can be analyzed systematically to reveal value stream metrics.

The two approaches are complementary: process mining provides the evidence base for the current state map, while VSM provides the collaborative framework and lean thinking that identifies the most valuable improvements to pursue.

Related Concepts

• Lean
• Process Mapping
• Bottleneck Analysis
• Process Mining
• Cycle Time
• Process Improvement
• Operational Excellence