Value stream mapping diagrams

Value stream maps that outlive the workshop

Most value stream maps are drawn on brown paper during a two-day workshop, photographed, and forgotten. The current state was right for one afternoon; by the time the future state is due, nobody can find the photo, and the numbers on the sticky notes have drifted. A value stream map on a hosted canvas keeps the map alive: process steps sit left to right in the order work actually moves, every hand-off carries its wait time on the edge, and the totals for lead time and process time stay where everyone can read them. When the process changes, the same canvas changes, and nobody redraws it from a photo.

Start with the customer on the right and the trigger on the left, then walk the process backwards the way a gemba walk does: what happens just before shipping, and what happens before that? Draw each step as a Process node inside a frame for the team or cell that owns it, and put the queue between two steps on the connecting edge so the wait is visible as a gap, not a footnote. Information flow (planning, orders, schedules) goes above the material flow with Data and Document shapes, so the two never blur. Keep the first version honest and small; a map with ten steps people agree on beats a map with forty nobody trusts.

From current state to future state

The value of the map is the conversation it starts. Mark the bottlenecks with notes, add Stat cards for total lead time and process time, and save a revision snapshot of the current state before anyone moves a box. Then duplicate the frame for the future state on the same canvas, so the before and after sit side by side during the review. Share a branded public link with the people who were not in the room, and export SVG or PNG for the improvement plan; Pro adds embed for the team wiki plus watermark-free PDF and JPEG.

Archboard does not ship a dedicated value stream symbol set yet. Kaizen bursts, push arrows, and the timeline ladder are drawn today with Flowchart, BPMN, Infographic, and Core nodes. That keeps the map readable for people who never learned the notation, and it means the same canvas can hold the software delivery pipeline when the value stream crosses into IT. Sign in with Google or GitHub, start from the closest template, and draw the stream you are improving this quarter.

Open a published example

• CI/CD + ObservabilityA left-to-right delivery pipeline with feedback loops. Relabel the stages as process steps.
• API Gateway InfographicThe Infographic stats, steps, and sections used for lead-time and process-time totals.
• Now / Next / Later RoadmapQuarter columns and dependencies for planning the future-state improvements.

Questions