Value Stream Map Maker

What does a value stream map add to a process map?

A value stream map examines how work and information move from an initial request or input to a delivered result. Timing and queue information help distinguish active processing from waiting across the stream.

Use it when elapsed time matters

A value stream map is useful for investigating long delivery times and repeated queues. Start with an observed current state before sketching improvements so proposed benefits have a clear baseline.

Use measured and consistently defined data

1. Choose one stream. Keep the scope focused on a defined product, service, or request type.
2. Define time measures. State what cycle time, processing time, and lead time mean in your data.
3. Separate work and waiting. A short task can sit in a long queue before the next step.
4. Include information flow. Approvals, schedules, and instructions can determine when work moves.
5. Keep proposed gains separate. Future-state estimates must not look like observed current performance.

A measured process draft

MyMap lays out the stream and measurements you describe, then revises the diagram on request. The fixed example is a purchase-order approval swimlane across Requester, Manager, and Finance; it shows handoffs but has no cycle-time or wait-time data, so it is not a complete measured VSM.