A spaghetti diagram is a lean tool that traces the physical path an operator, part, or document travels through a process, drawn as a continuous line on a scale floor plan. The tangled result makes wasted motion and transport visible, so a workspace can be re-laid-out to shorten the path.
The name is the finding. When you draw every trip a worker makes across a shift on top of a floor plan, the line loops back on itself so many times it looks like a plate of spaghetti. That mess is not a drawing problem; it is the process telling you how much of the day is spent walking, fetching, and carrying instead of adding value. A spaghetti diagram turns motion and transport, two of the classic wastes in lean manufacturing from something people vaguely complain about into a line you can measure and cut.
What Is a Spaghetti Diagram?
A spaghetti diagram is a scale sketch of a physical area, a cell, a line, a lab, a warehouse aisle, with the travel path of one person or one part drawn on top as a single unbroken line. You follow the subject through a real cycle or a real shift and draw where they go: to the machine, back to the bench, over to the supply rack, across to the printer, back again. Every trip adds a segment. By the end the line records the true geography of the work, not the tidy sequence a process document implies.
It is a member of the same family as the walk-path portion of a standard work chart, but it is used differently. Standard work draws the intended, optimized path; a spaghetti diagram draws the actual, messy one, usually to justify changing the layout in the first place. Both sit on a floor plan; one is the diagnosis and the other is the prescription.
What Does a Spaghetti Diagram Reveal?
It reveals motion and transport waste, the two wastes that hide best because they feel like work. Motion is people moving, walking to a rack, reaching, searching for a tool. Transport is material moving, a part carried from one machine to a bench and back. Neither changes the product, and both are usually invisible in a process document that only lists value-adding steps. The spaghetti line drags them into the open. A path that crosses itself a dozen times is telling you the stations are in the wrong places, the supplies are too far from the point of use, or the work is bouncing between areas that should be adjacent.
The tool is also quantitative when you want it to be. Measure the length of the drawn path against the floor plan's scale and you get total travel distance; time the trips and you get travel time you can compare against value-adding time. "The operator walks about a quarter mile a shift to fetch stock" lands harder in a layout review than "the rack feels far away." That number is what justifies moving a machine, and it is the baseline you measure the re-layout against.
How Do You Create a Spaghetti Diagram?
You draw a spaghetti diagram by observation, on the floor, in real time. It is a gemba exercise, not a desk one, the whole value comes from following the real path, not the imagined one.
- Get a scale floor plan of the area. A rough but proportional sketch of the space with machines, benches, racks, and doorways in their real positions. Scale matters because you will measure distance off it later.
- Pick one subject and one time window. Follow a single operator, part, or document through one full cycle or one shift. Trying to track everything at once produces an unreadable tangle that measures nothing.
- Walk with them and draw every trip. Start the pen where they start and never lift it: each move to a new location adds a segment. Do not tidy the path or skip the "quick" trips, the small ones are where the waste accumulates.
- Mark the reason for key trips. Note why the longer or repeated journeys happen: fetching stock, chasing a tool, getting a signature, carrying a part to inspection. The reasons tell you what to fix.
- Measure the total distance and count the trips. Use the plan's scale to convert the drawn line into feet or meters, and tally how many times the subject crossed the space. This is your baseline number.
- Redesign the layout to shorten the path. Move stations closer to their point of use, bring supplies to the line, and sequence machines in process order. Then draw the proposed path on a fresh plan and compare distances.
- Verify the new path on the floor. Re-run the observation after the change. A re-layout that looks shorter on paper but adds a new bottleneck has to be caught by watching it run, not by admiring the drawing.
How Is a Spaghetti Diagram Different From Value Stream Mapping?
They answer different questions and work at different scales. A spaghetti diagram is about physical geography, how far things and people move inside one area. A value stream map is about flow and time, how material and information move through the whole process, from order to shipment, with data on cycle times, inventory, and lead time. You would use a spaghetti diagram to fix a poorly arranged cell; you would use a value stream map to see that the cell sits behind a three-day pile of inventory that dwarfs any walking you could save.
| Dimension | Spaghetti diagram | Value stream map |
|---|---|---|
| What it shows | Physical travel path on a floor plan | Material and information flow across the whole process |
| Scale | One area, cell, or room | Door to door, often multiple processes |
| Waste targeted | Motion and transport | All eight wastes, especially inventory and waiting |
| Key output | Travel distance and a re-layout | Lead time, value-added ratio, a future-state plan |
The two are complementary. Teams often run a value stream map first to find which process is the real constraint, then draw a spaghetti diagram inside that process to fix the physical layout, then re-cut cycle time and re-measure. Using a spaghetti diagram on a cell that is not the constraint is real work that produces no throughput gain, the map keeps you honest about where to point it.
What Makes a Spaghetti Diagram Fail?
The tool is simple, which is exactly why it gets misused. The most common failure is drawing it from memory at a desk instead of on the floor, which produces the neat path people imagine rather than the tangled one that actually happens, and the tangle was the entire value. A close second is tracking too many subjects at once, so the page becomes an unreadable knot that measures nothing. Teams also skip the scale, drawing a proportion-free doodle they cannot convert into real distance, which strips out the number that would have justified the change. And some stop at the drawing: a beautiful before-and-after that never becomes a moved machine is a diagram, not an improvement. The fix for all four is discipline, one subject, real observation, a scaled plan, and a committed re-layout with a re-measured result.
By the Numbers
Motion and transport are two of the seven wastes (muda) Taiichi Ohno identified in the Toyota Production System, later commonly extended to eight (Lean Enterprise Institute, Muda; Toyota Motor Corporation, Toyota Production System). Both are pure waste, they consume time, labor, and floor space while changing nothing about the product a customer will pay for. That is what makes them worth hunting: unlike processing steps you can only speed up, travel can often be designed out entirely by moving a machine or a rack. A spaghetti diagram is the cheapest instrument for finding it, a floor plan, a pen, and one shift of watching. For the broader picture of where travel waste sits, see the eight wastes of lean and for compact layouts that prevent it, cellular manufacturing.
What Do You Do After You Draw the Diagram?
Drawing the tangle is the easy part; acting on it is where the gain lives. The path points to specific fixes: relocate stations so they sit in process order, bring point-of-use supplies to the line so operators stop walking to a central rack, and pair the re-layout with 5S so the newly placed tools stay where they belong. A cleaner path often reveals that one operator can now tend two machines that used to be too far apart, which turns saved motion into freed capacity. Then you re-standardize the walk path in standard work so the improvement holds instead of drifting back as people revert to old habits.
Where this connects to running a plant: a spaghetti diagram is a snapshot of one shift someone happened to watch, and floors change every day as jobs, mixes, and staffing shift. Harmony captures what actually happens at each station over time, so instead of one hand-drawn observation you can see patterns of movement and handoffs continuously, where parts pile up, where a step waits. That turns a one-time drawing into an ongoing view, the same way a SIPOC only helps if it reflects the real process. See it on a running line in the CLS case study or the platform overview.