VSM workshops cost a week, ship one map
Five days of cross-functional time produces one current-state map. By the time the future-state is debated, the current state has moved.
Live VSMs generated from event data — material flow, information flow, lead time, cycle time, value-add ratio, and waste classification — continuously updated as the process changes.
Five days of cross-functional time produces one current-state map. By the time the future-state is debated, the current state has moved.
The whiteboard is the map; the kaizen backlog is the spreadsheet; the actual savings live in a deck somewhere. None of them update each other.
Mapping a manufacturing line is concrete. Mapping a loan origination, a clinical pathway, or an onboarding flow is mostly post-its and arguing.
Will reducing the inspection step by 30% really cut lead time by 20%? In a traditional VSM, you find out after you ship the change.
Pulls event data from the systems that touch the work, infers the actual sequence of steps, and renders a live VSM with all the standard Lean iconography.
Tags non-value-add work, necessary non-value-add, and value-add at every step using the eight-waste DOWNTIME framework.
Models proposed interventions against the historical event log: 'if we collapsed steps 4 and 5, lead time drops from 14 days to 9.' Confidence intervals included.
Re-runs the VSM on a schedule or on data change. When the actual process diverges from the documented future state, the agent flags it.
The canonical Lean metrics, computed continuously from the same event data the map is drawn from.
Total elapsed time from start to finish of the value stream
Time the work is actually being processed at each step
Process time as a percentage of lead time — the canonical Lean metric
Required production pace to meet customer demand
Percentage of work completed without rework at each step
Cumulative yield across the full value stream
Work waiting between steps — the visual signal of where flow is breaking
How decisions and instructions move alongside the work
It changes what they're for. The current-state mapping — which used to consume most of the workshop — is generated by the agent in advance and shows up in the room as a starting point. Workshops become focused on judgment, prioritization, and change management, which is what they should have been about in the first place.
That's actually where agents do best. Multi-system value streams — order management to billing to fulfillment to support — are exactly the ones where humans struggle to draw the map manually because the data lives in five different tools. Agents stitch the case across systems using shared keys, time correlation, or causal inference when keys are missing.
Yes — most of our VSM engagements are in service operations. Loan origination, claims processing, hiring pipelines, customer onboarding, and clinical pathways all map cleanly. The agent uses time-in-step instead of inventory boxes, but the core logic — lead time, value-add ratio, waste classification — translates directly.
Useful, with bounds clearly stated. The simulator models the historical event log forward under the proposed intervention. It captures first-order effects (removing a step) and second-order effects (reducing a wait) but cannot predict third-order effects like behavior change or capacity rebalancing. Output always includes a confidence interval and a list of assumptions for the human to challenge.
Standard VSM iconography — process boxes, inventory triangles, push/pull arrows, supplier/customer endpoints, data boxes, timeline at the bottom — rendered from current data. Hovering a step shows the cycle time distribution; clicking opens the variant analysis. Exportable to PNG/SVG for the kaizen room wall when needed.
VSM is the Lean half. Pair it with the Six Sigma DMAIC discipline for end-to-end coverage.
The technique underneath VSM generation. Mining produces the variants; VSM produces the picture.
The parent service: PipeIQ's full process-improvement agent platform.
Pick a stream where lead time is the headline problem. We'll generate the current-state map, classify the waste, and run two future-state simulations in under three weeks.