Key takeaways
Short answer: A process map documents the detailed steps, decisions and handoffs inside a single process — it zooms in. A value stream map shows the entire flow from order to delivery, including the information flow and, crucially, the time and inventory sitting between steps — it zooms out. Process mapping helps you improve how a task is done; value stream mapping helps you see where lead time and waste actually hide. See also value added vs non value added.
A process map is a detailed, step-level picture of one process. It captures each task, decision point, handoff and rework loop, usually as a flowchart or swimlane diagram. Its strength is depth: it makes the logic of a single process explicit so you can find redundant steps, unclear handoffs and decision points that cause variation.
A value stream map takes a whole product family from order to delivery and draws both the material flow and the information flow that triggers it. Critically, it records the time and inventory between steps — the waiting that usually dwarfs the processing. Its strength is breadth: it exposes where lead time accumulates across the whole system, not within one step.
A plant has a slow order-to-ship lead time of nine days. A process map of the machining step shows it is tight — twelve clean steps, little rework — so the team concludes machining is fine and looks elsewhere. A value stream map then reveals the truth: machining takes 40 minutes, but the part waits two days in a queue before it and three days after, and a separate information delay holds the order for a day before it even starts. The processing was never the problem; the waiting between steps was. The process map validated the step; the VSM found the nine days.
Process mapping answers "is this step well designed?" Value stream mapping answers "where does our lead time actually go?" A beautifully optimised step inside a value stream full of queues changes nothing for the customer. Conversely, a VSM that flags a problem step often needs a process map to redesign it. They are complementary tools at different altitudes.
The single most valuable line on a value stream map is the timeline at the bottom, which separates value-added processing time from the waiting between steps. In most plants the ratio is shocking — minutes of value-added work inside days of lead time. That ratio, manufacturing cycle effectiveness, is what a VSM exists to expose and a process map cannot show.
1. Process-mapping when the problem is flow. You perfect a step while lead time stays unchanged.
2. Value-stream-mapping without the information flow. Half the delay is often in how the order is triggered, not the material.
3. Mapping the current state and stopping. The point is to draw a future state and close the gap.
4. Confusing the two and producing a hybrid that does neither well. Pick the altitude that matches the question.
Process and flow problems both surface in OEE and lead time, but from different angles. A VSM that exposes waiting between machines points at starving and blocking — OEE Performance and Availability losses — while a process map of a single asset helps remove the micro-stops and quality loops inside it. Together they connect flow waste to the machine-level losses OEE measures.
See how Fabrico captures this automatically on your lines — explore OEE for manufacturing or book a demo.
No — a VSM adds the information flow and the time and inventory between steps, and spans the whole flow rather than one process.
Usually the value stream map, to find where lead time hides, then a process map to redesign the problem step.
The waiting and inventory between steps — usually the bulk of lead time.
Often yes — VSM to locate the problem, process map to fix the step inside it.
The timeline separating value-added time from waiting — it exposes how little of lead time is actual work.
Login
Blog
