Lean value stream mapping highlights seven core wastes—overproduction, waiting, transport, extra processing, inventory, motion, and defects. Grasping these helps teams spot inefficiencies, streamline workflows, and boost value delivery. Some frameworks add an eighth, but the classic model centers on seven.

Multiple Choice

How many types of wastes are identified in Lean value stream mapping?

In Lean value stream mapping, seven types of waste are identified. This concept is pivotal in Lean methodology, which aims to streamline processes and enhance efficiency by eliminating waste. The seven wastes consist of overproduction, waiting, transport, extra processing, inventory, motion, and defects. Each of these categories highlights different areas where resources are not utilized effectively—leading to inefficiencies. The identification of these wastes allows organizations to pinpoint specific areas of improvement within their processes. Understanding and mitigating these wastes are critical for organizations striving for operational excellence and higher quality outputs. By focusing on the reduction of these seven wastes, businesses can achieve better value delivery to customers while maintaining efficient use of resources. While there are variations that include additional types of waste in specific frameworks—such as the eighth waste of unused creativity— in the context of traditional Lean value stream mapping, the recognized standard is the seven wastes.

Lean value stream mapping is like a flashlight in a dim workshop, helping teams spot where time and energy slip away. When you map out a process from start to finish, you’re not just drawing boxes and arrows—you’re highlighting the places where resources get stuck, misused, or wasted. And the classic guidepost for that effort? The seven wastes. They’re the stubborn culprits that keep value from flowing smoothly to the customer. Let me walk you through them, with real–world flavor and a few practical angles you can actually put to work.

Seven wastes you’ll see in most Lean value maps

  • Overproduction

  • Waiting

  • Transport

  • Extra processing (or over-processing)

  • Inventory

  • Motion

  • Defects

Each category helps you notice a different kind of inefficiency, and together they cover the broad spectrum of everyday friction in a process. Here’s how they break down and why they matter.

Overproduction: making more than you need, when you don’t yet know what “enough” looks like

Overproduction is the mirror opposite of just-in-time thinking. It happens when steps in the process generate outputs before they’re truly needed. Maybe a team creates more components than the next step can absorb, or a report is prepared well before it’s actually used. The result? Stuff sits idle, clutter piles up, and the next person pays the price in excess handling and storage costs. In value stream mapping, spotting overproduction often looks like a box that’s full before the downstream process even asks for it. The remedy is to synchronize demand with flow—pull signals, smaller batch sizes, and tighter feedback loops so production aligns with actual need.

Waiting: time when value sits on the sidelines

Waiting isn’t just “taking a break.” In many value streams, it’s a sign that downstream steps aren’t ready, a handoff is delayed, or information isn’t flowing smoothly. You’ve got people idling while systems catch up, or machinery standing idle because the next instruction hasn’t arrived. Waiting compounds cycle times and erodes momentum. In a map, it’s the staggered gaps between steps where the clock is ticking but value isn’t moving. Reducing waiting often means leveling workloads, improving scheduling, and ensuring that the information path keeps pace with the physical path. It’s amazing how much smoother work becomes when teams stop waiting on handoffs and start coordinating more tightly.

Transport: unnecessary movement that adds risk and delay

Transport is more than a short trip from A to B. It includes any movement of materials or information that doesn’t add direct value. Each hop carries risk—loss, damage, misplacement—and a little extra time. In a value map, you’ll notice long routes, multiple transfers, or handoffs that force people to re-enter data or re-check details. The antidote is to reduce distance, simplify routing, and keep related steps close together—think horizontal flow, colocated cells, or digital substitutes that cut physical motion without losing fidelity.

Extra processing: doing more than what the customer needs

Extra processing is the “nice-to-have” that isn’t strictly necessary for the outcome the customer requires. It could be a signature step in a review that adds little value, or a high-precision check that doesn’t improve quality from the customer’s view. The more you map, the more you’ll spot steps that feel like they’re there for comfort rather than consequence. The fix is to remove nonessential steps, simplify workflows, and ensure every activity clearly contributes to value. It’s a subtle art—keep the good stuff, trim the fluff.

Inventory: the stock that ties up capital and hides problems

Inventory isn’t just piles of stuff in a warehouse. It’s every item sitting between process steps, every part that’s waiting to be used, every unfinished piece that blocks downstream progress. Large inventories mask bottlenecks and let defects linger longer because problems aren’t surfaced promptly. A well–designed map shows where items accumulate, and the cure is to pull smaller lots, implement just-in-time triggers, and expose problems earlier so they can be addressed rather than concealed.

Motion: wasted energy in human movement

Motion covers the physical effort people expend to do their jobs—walking, searching, reaching, bending—without adding value. It’s not simply a matter of comfort; excessive motion can shave minutes off a shift and erode concentration. On a value map, it shows up as sprawling layouts or dispersed resources. The fix is thoughtful workplace design: layout optimization, standardized tools, ergonomic setups, and the kind of thinking that makes work feel almost effortless because everything you need is in reach.

Defects: quality gaps that require rework

Defects are the cracks in the system where something doesn’t meet the standard and has to be corrected, reworked, or discarded. They ripple through the process, causing rework, delays, and wasteful use of resources. In mapping, defects are a loud signal that a step isn’t robust enough, that feedback loops aren’t catching issues early, or that standards aren’t clear. The cure is to build quality in—faster detection, better specifications, and a culture that learns from mistakes without blame. When defects drop, you’re not just saving time; you’re raising trust—inside the team and with customers.

What you gain by mapping these wastes—and why it matters beyond the bottom line

Lean value stream mapping isn’t just a classroom exercise. It’s a practical lens for everyday work. When you identify and address these seven wastes, you:

  • Shorten cycle times, so value reaches customers faster

  • Reduce costs by cutting unnecessary steps and materials

  • Improve quality by catching errors earlier and more consistently

  • Elevate employee engagement by removing frustrating bottlenecks

  • Create a more predictable workflow, which helps teams plan and collaborate better

The flipside is worth noting: while seven wastes form the backbone of “classic” Lean mapping, some frameworks point to an eighth waste—unused creativity. That one nudges you to consider ideas that aren’t acted on, the spark of innovation that never makes it into the process. It’s a nod to human potential, a gentle reminder that a process map can and should evolve to include fresh ways of delivering value. Still, in the standard palette of Lean value stream maps, seven wins out as the core set.

From theory to practice: a few pointers to bring the map to life

  • Start small, then scale up. Pick a single value stream with a clearly defined start and finish. Map it, learn, adjust, and expand to related streams. You’ll avoid the “kitchen sink” syndrome where the map becomes unreadable.

  • Use a current-state map first. Don’t worry about perfection on day one. The goal is to see it with fresh eyes and identify obvious wastes, then iterate toward a future state.

  • Involve the people closest to the work. They know the bottlenecks, the handoffs, the small annoyances. Their insights are gold, and their buy-in makes improvements stick.

  • Keep the map readable. Simple symbols, clear arrows, and a logical sequence help everyone grasp the flow at a glance. A cluttered map is a signal that the process itself is cluttered in reality.

  • Tie improvements to metrics. It’s not about clever diagrams; it’s about real gains: shorter lead times, fewer defects, lower inventory. Track the before-and-after to show impact.

A few practical scenarios to illustrate the seven wastes

  • In a product–intensive team, overproduction might look like building extra components that sit in a bin until a downstream step is ready. The fix could be swapping to smaller batch runs and a pull-based approach so production matches demand more closely.

  • In a services context, waiting could show up as delays between receiving a customer request and starting work. A tighter process—streamlined intake, faster triage, and clear ownership—helps speed things up without sacrificing accuracy.

  • For a logistics operation, transport waste becomes visible as long, zigzag routes between suppliers, warehouses, and customers. Reorganizing the layout or using cross-docking can dramatically cut motion and time.

  • In a software development setup, extra processing and defects might reveal themselves as over-complicated approval steps or repetitive reviews. Simplifying reviews and automating checks can reduce rework and accelerate delivery.

The subtle art of balancing rigor with real-world nuance

Here’s the thing: Lean value stream mapping isn’t about chasing a perfect diagram. It’s about understanding how work actually flows and where energy leaks out. It’s as much about people and culture as it is about boxes and arrows. A map should feel alive—updated as teams learn, tested in day-to-day work, and used as a conversation starter rather than a ceremonial artifact.

If you’re new to this, you might worry that it sounds a bit theoretical. But the beauty of the seven wastes lies in their everyday relevance. They show up in the little choices you make every day—how you organize your desk, how you schedule shifts, how you handle information. Addressing them isn’t about heroic sacrifices; it’s about small, consistent improvements that compound over time.

A final thought to carry forward

Lean value stream mapping gives you a practical language for talking about flow. It helps teams stop pretending that everything is fine when, in reality, friction is quietly piling up. By identifying the seven wastes—overproduction, waiting, transport, extra processing, inventory, motion, and defects—you gain a compass for prioritizing what to fix first, where to pilot changes, and how to measure progress.

And if you ever hear someone whisper about an eighth waste—unused creativity—smile. It’s a friendly reminder that good processes should be adaptable, open to better ideas, and never afraid to revisit assumptions. The map isn’t a cage; it’s a guide, helping you navigate toward smoother, smarter, more human systems that deliver real value with less waste, every day.

If you’re curious to see how this plays out in a specific field—be it manufacturing, healthcare, or software services—feel free to share a snapshot of a process you’re exploring. We can talk through where each waste tends to hide and sketch out a practical path to a cleaner, faster flow.