Value stream map template, with a worked example
A value stream map (VSM) is a process map that also shows time. For each step, it records how long people work on the item and how long the item waits. The map shows where the delay is, so a team can remove it.
Wavelength is a voice to diagram tool that turns a spoken process or a call transcript into an editable flowchart. Each step in a Wavelength flow can hold active time, wait time, and cost. Wavelength adds them up and shows the slow steps as a heat map. This page gives you a template, a worked example, and the steps to build your own map.
What a value stream map shows
A normal flowchart answers the question "what happens, and in what order?" A value stream map answers a second question: "where does the time go?" Most teams are surprised by the answer. The work itself is often fast. The item spends most of its life in a queue, in an inbox, or waiting for an approval.
Lean teams first used value stream maps in manufacturing. Today, office teams use them for any process that has handoffs: onboarding a customer, closing the books, paying an invoice, or shipping a code change. The method is the same. You map the current state, you measure it, and then you draw a future state with less waiting.
The value stream map template
Copy this table. Make one row for each step. Keep the steps in the order the work happens.
| Step | Owner | Active time | Wait time before the next step | Cost per run | Notes |
|---|---|---|---|---|---|
| 1. (first step) | (role or team) | (minutes) | (minutes) | ($) | (rework, errors, tools) |
| 2. | |||||
| 3. | |||||
| Total | (handoffs: count the owner changes) | (sum) | (sum) | (sum) | Cycle time = active + wait |
Use minutes for every time column, also when a wait lasts days. One unit makes the totals easy to compare. A day of waiting is 1,440 minutes. A working day is about 480 minutes.
The five numbers that matter
- Active time. The time a person or system works on the item. Some teams call this process time or touch time.
- Wait time. The time the item sits between steps. This is usually the biggest number on the map.
- Cycle time. Active time plus wait time, from the first step to the last step. This is what the customer feels.
- Handoffs. The number of times the work moves from one owner to another. Each handoff adds a queue and a chance for an error.
- Cost per run. What one pass through the process costs, in labor and tools.
Many lean teams also track the share of active time in the cycle time. If the active time is 90 minutes and the cycle time is 3 days, the item is in work for about 2 percent of its life. That number makes the case for change better than any slide.
A worked example: vendor invoice approval
A finance team pays vendor invoices. Here is the current state, measured over one week.
| Step | Owner | Active (min) | Wait (min) | Cost ($) |
|---|---|---|---|---|
| Receive invoice in shared inbox | AP clerk | 5 | 480 | 3 |
| Match invoice to purchase order | AP clerk | 15 | 60 | 9 |
| Purchase order matches? | AP clerk | 2 | 0 | 1 |
| Send to budget owner for approval | Budget owner | 10 | 2,880 | 12 |
| Enter in ERP and schedule payment | AP clerk | 10 | 1,440 | 6 |
| Pay vendor | ERP | 1 | 0 | 1 |
| Total | 3 handoffs | 43 | 4,860 | 32 |
The active time is 43 minutes. The cycle time is 4,903 minutes, which is about 3.4 days. The approval step alone holds the invoice for two days. So the fix is not a faster clerk. The fix is a faster approval: an approval limit, so small invoices skip the budget owner, or a reminder after four hours.
In the future state, invoices under the limit go straight to the ERP. The team draws that future state as a second map and compares the totals. Wait time drops for most invoices, and the handoff count goes down by one.
How to build a value stream map in Wavelength
- Talk through the process. Hold the mic and describe the steps as you would to a new hire. You can also paste a meeting transcript or upload a recording. Wavelength draws the flow.
- Add the numbers. Select a step. In the inspector, type the active time, the wait time, and the cost per run.
- Read the totals. The metrics bar shows active time, wait time, cost, cycle time, and handoffs for the whole flow. Wavelength counts a handoff each time the owner changes.
- Find the slow steps. Turn on the metrics heat map. The steps with the most time get the strongest color.
- Draw the future state. Create a future state copy of the flow and change it by voice: "skip the budget owner when the invoice is under 500 dollars." Then compare the two flows side by side, with the change in active and wait time.
To share the numbers, download the steps and metrics as a .csv file and open it in Excel or Google Sheets. You can also export the map as PNG, PDF, PowerPoint, draw.io, or BPMN 2.0.
Tips for a useful value stream map
- Map one item. Follow a single invoice, ticket, or order from start to finish. Do not map "how invoices usually go."
- Measure, do not guess. Ask people for timestamps from the inbox, the ticket system, or the ERP. Guesses about wait time are almost always too low.
- Walk the process with the people who do it. The owner of a step knows about the rework that nobody else sees.
- Keep the first map rough. A map with eight steps and real numbers is better than a perfect map with forty steps and no numbers.
- Fix the biggest wait first. One long queue usually holds most of the cycle time.
Value stream map, process map, and SIPOC
| Tool | What it shows | Use it to |
|---|---|---|
| SIPOC diagram | Suppliers, inputs, process, outputs, customers | Agree on the scope before you map |
| Process map | Steps, decisions, and owners | Show who does what, in what order |
| Value stream map | Steps with active time, wait time, and cost | Find the delay and remove it |
| BPMN diagram | A standard notation for process models | Hand the process to an automation or BPM tool |
What Wavelength does not do
Wavelength does not draw the classic manufacturing VSM icons, such as the factory, the truck, the push arrow, or the inventory triangle. It shows the timeline as numbers on each step, totals for the whole flow, and a heat map. If your plant team needs the full lean icon set on one sheet, use a general drawing tool such as Visio or Lucidchart for that view. Wavelength also does not pull timestamps from your systems by itself. You type the numbers on each step.
Related
- SIPOC diagram: template and worked example
- Process map template: a free template you can open and edit
- BPMN diagram examples: worked examples with BPMN export
- AI diagram generator from text: paste a description, get a flowchart
- Flow diagram examples: worked examples you can open and edit
- Resources: all guides and templates
Common questions
What is a value stream map?
A value stream map is a process map that also shows time. For each step it records the active time and the wait time, so a team can see where the delay is and remove it.
What is the difference between cycle time and active time?
Active time is the time someone works on the item. Cycle time is the active time plus all the wait time, from the first step to the last step.
Is there a free value stream map template?
Yes. Copy the table on this page. In Wavelength, the free plan lets you add active time, wait time, and cost to each step, and it adds up the totals for you.
Can I export the value stream map numbers?
Yes. Wavelength exports the steps and metrics as a .csv file that opens in Excel or Google Sheets. The map itself exports as PNG, PDF, PowerPoint, draw.io, or BPMN.
How do I show a future state value stream map?
In Wavelength, create a future state copy of the flow, change it by voice or by hand, and compare the two flows. The compare view shows the change in active time, wait time, and handoffs.
Every new account starts with 7 days of Pro. No card needed.