Key takeaways
Short answer: A spaghetti diagram traces the actual physical path a person, part or product takes across a floor plan, exposing wasted motion, backtracking and transport. A value stream map traces the process flow and the time accumulating between steps, exposing waiting and lead time. They reveal different wastes — physical movement versus elapsed time — and the strongest improvement work uses both. See also value stream mapping vs process mapping.
A spaghetti diagram is drawn directly on a scaled floor plan: you follow a person or a part and trace every move they make as a line. The result usually looks like a tangle of spaghetti — which is the point. It makes wasted motion, backtracking, crossing paths and long transport instantly visible in a way no table of numbers can.
A value stream map abstracts away the physical layout and instead draws the sequence of process steps, the information flow that triggers them, and the time and inventory between them. It exposes where lead time accumulates — the days of waiting that dwarf the minutes of processing — which a spaghetti diagram, focused on space rather than time, cannot show.
A cell has a nine-day lead time and operators who seem constantly busy. A value stream map shows the nine days are mostly queues between steps — a time problem. A spaghetti diagram of the same cell shows something different: an operator walks 400 metres per shift fetching tools and materials from across the building, crossing the same aisle eleven times — a movement problem. The two maps found two distinct wastes. The VSM said "fix the queues"; the spaghetti diagram said "relocate the tools and materials." Neither alone would have seen both.
A spaghetti diagram lives in space; a value stream map lives in time. Wasted motion can be invisible on a VSM (the step still takes the same recorded time) while waiting can be invisible on a spaghetti diagram (a stationary part draws no line). Because the seven wastes include both transport/motion and waiting, you need both lenses to see them all.
A spaghetti diagram drives layout change — relocating tools, resequencing stations, creating a cell so the path collapses from a tangle into a tight loop. A value stream map drives flow change — cutting batch sizes, removing queues, levelling the schedule. They lead to different countermeasures, which is exactly why running only one leaves half the improvement on the table.
1. Using a VSM to fix a movement problem. It does not show the walking; the layout stays bad.
2. Using a spaghetti diagram to fix a lead-time problem. It does not show the queues.
3. Drawing either as a one-off wall decoration. The map is the start; the countermeasure is the point.
4. Estimating the path instead of walking it. The real path is always messier than the imagined one.
Movement waste eats into changeover and response times, while waiting between machines shows up as starving and blocking. Both ultimately appear in OEE — the spaghetti diagram attacks the motion that slows changeovers (Availability), the VSM attacks the flow losses (Performance). Together they connect layout and flow 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 — they are separate tools; one maps physical movement, the other maps process flow and time.
Usually a VSM to find the slow part of the flow, then a spaghetti diagram on the problem cell.
Motion, transport and backtracking — wasted physical movement.
Waiting and lead time accumulating between steps.
Yes — they reveal different wastes that the other lens cannot see.
Programați o întâlnire individuală cu experții noștri sau înscrieți-vă direct în planul nostru gratuit.
Nu este nevoie de card de credit!
Login
Blog
