Value Stream Mapping
A lean technique for visualizing and analyzing the complete flow of materials and information needed to deliver a product or service.
Also known as: VSM, Value Stream Analysis, Material and Information Flow Mapping
Category: Techniques
Tags: lean, processes, improvement, visualization, management
Explanation
Value Stream Mapping (VSM) is a lean management tool used to visualize, analyze, and improve the flow of materials and information required to bring a product or service to the customer. It maps the entire process from beginning to end, distinguishing value-adding steps from waste.
## What it maps
A value stream map captures:
- **Process steps** - Each activity in the flow
- **Information flow** - How decisions and data move
- **Material flow** - How physical or digital items move
- **Time data** - Processing time vs. wait time at each step
- **Inventory/queues** - Where work piles up between steps
- **Metrics** - Cycle time, lead time, defect rates
## How to create one
1. **Select the value stream** - Choose a specific product family or service
2. **Walk the process** - Follow the work from start to finish (gemba)
3. **Map the current state** - Document what actually happens, not what should happen
4. **Identify waste** - Mark non-value-adding steps (muda)
5. **Design the future state** - Envision the improved process
6. **Create an action plan** - Define steps to move from current to future state
## Key metrics
- **Lead time** - Total time from request to delivery
- **Processing time** - Time spent actually working on the item
- **Process cycle efficiency** = Processing time / Lead time
- **Takt time** - The rate at which you need to complete items to meet demand
A typical finding: processing time is only 5-10% of total lead time. The rest is waiting, handoffs, and queues.
## In software development
VSM has been adapted for software delivery:
- **Stages**: Idea, requirements, design, development, testing, deployment, monitoring
- **Wait times**: Approval queues, code review backlogs, staging environment availability
- **Handoffs**: Between teams (design to dev, dev to QA, QA to ops)
- **Waste**: Unnecessary documentation, unused features, rework from unclear requirements
## Benefits
- Makes invisible waste visible
- Provides a shared understanding of the whole process
- Highlights bottlenecks and queues objectively
- Focuses improvement efforts on the highest-impact areas
- Connects tactical improvements to end-to-end flow
## Common discoveries
- Most of lead time is waiting, not working
- Handoffs between teams create significant delays
- Batch processing creates artificial bottlenecks
- Information gaps cause rework and delays
Related Concepts
← Back to all concepts