What a value stream map is
A value stream map records each process step with its cycle time, changeover time, uptime and the inventory waiting after it. Comparing total lead time against value-adding time usually reveals that most elapsed time is queueing, not working.
When to use one
- A Lean improvement programme needs a quantified current state
- Lead time is unacceptable but nobody agrees where it is being spent
- Building the business case for reducing batch sizes or buffers
The data format
One step per line: Step, CycleTime(s), Changeover(s), Uptime%, InventoryAfter(units).
Paste rows like this — copy the example straight into the builder to see it render:
Order entry, 30, 5, 95, 120 Procurement, 90, 0, 90, 480 Machining, 240, 60, 85, 360 Assembly, 180, 20, 92, 240 Shipping, 60, 0, 98, 90
How to make one
- Paste your data into the Studio, or upload a CSV or XLSX file.
- Set your colours — by hand, from pasted brand hex codes, or extracted from your logo.
- Generate and export as PNG or SVG for your deck or report.
One thing people get wrong. The inventory between steps is the real finding. Teams optimise the slowest step and are surprised nothing improves, because the time was sitting in the queues.
Why it runs in your browser
Charts are parsed and drawn entirely on your own device. No rows, files or logos are uploaded, so a value stream map built from confidential project or process data never touches a server. You can verify it: open your browser's network tab while you generate one.