Search for “Lean Six Sigma tools” and most lists just merge two separate toolkits under one banner without explaining why. That’s backwards. The real question a practitioner needs answered isn’t “what are all the tools,” it’s “which toolkit do I reach for right now?” This page answers that question directly: which tools belong to Lean, which belong to Six Sigma, which ones genuinely overlap, and how to tell which kind of problem you’re actually looking at before you pick up any tool at all.

If you want the full tool-by-tool reference organized by DMAIC phase, see the complete Six Sigma Tools list. This page instead focuses on the Lean side of the toolkit and on how the two toolkits fit together in a combined Lean Six Sigma project.

Two Different Lenses on the Same Process

Lean and Six Sigma were built to answer two different questions, and that difference matters far more than most “Lean Six Sigma tools” lists let on:

• Lean asks: is this step adding value to the customer, or is it waste? Lean tools are built to spot and remove the eight classic wastes, excess motion, waiting, overproduction, and the rest, usually without needing a single statistical calculation.
• Six Sigma asks: why does this output vary, and how do I control it? Six Sigma tools are built to find and eliminate the root causes of variation and defects, almost always using data and statistics to prove the cause before acting on it.

A process can be perfectly Lean (zero wasted motion, zero wasted time) and still produce wildly inconsistent output. It can also be statistically rock-solid and still be full of waste, fast, consistent, and still doing three unnecessary steps every single time. That’s why a real Lean Six Sigma project needs both toolkits, not just one relabeled as the other.

	Lean	Six Sigma
Primary target	Waste (non-value-added activity)	Variation and defects
Origin	Toyota Production System, 1950s	Motorola, 1986
Core question	Does this step add value to the customer?	Why does this output vary?
Typical evidence	Observation (time, motion, inventory)	Statistical data and hypothesis tests
Fastest wins	Removing obvious waste, often cheap and quick	Fixing a proven root cause of variation, often slower to prove but more durable
Needs statistics?	Rarely	Almost always

Lean-Only Tools

These tools exist specifically to find and remove waste and improve flow. None of them require statistics, and most of them were developed inside the Toyota Production System decades before anyone combined them with Six Sigma.

• Classic Wastes (TIMWOODS): the standard checklist of 8 waste categories, the starting vocabulary for spotting waste anywhere in a process.
• Value Stream Mapping: maps the full flow of material and information end to end, specifically to separate value-added steps from waste.
• 5S: a workplace-organization method (Sort, Set in Order, Shine, Standardize, Sustain) that removes clutter and wasted motion from the physical or digital workspace.
• SMED (Quick Changeovers): reduces the time it takes to switch a process or machine from one product to another.
• Poka-Yoke (Error-Proofing): designs a process so a specific mistake becomes physically impossible, or gets caught immediately.
• Kanban: a visual signaling system that pulls work through a process based on actual downstream demand instead of a forecast.
• Takt Time: the pace a process needs to run at to match customer demand exactly, neither overproducing nor falling behind.
• Push-Pull System: compares scheduling work based on a forecast (push) against releasing work only when the next step actually signals demand for it (pull).
• Cellular Systems: arranges equipment and people in the order a product actually flows through, instead of grouping by machine type, to cut travel and waiting time.
• Spaghetti Diagram: traces the physical path a person, part, or document takes through a workspace, which usually exposes a surprising amount of unnecessary travel.
• Kaizen: a focused, rapid-improvement event (or a broader continuous-improvement philosophy) aimed at eliminating a specific source of waste quickly.

Six Sigma-Only Tools

These tools exist specifically to prove, statistically, what’s actually driving variation or defects, rather than relying on a team’s best guess. A full, linked reference for all of these lives on the Six Sigma Tools page; here’s the short list that has no real Lean equivalent:

• Hypothesis Testing: determines whether an observed difference is statistically real or could be explained by chance alone.
• Regression Analysis: quantifies how strongly an input actually drives an output, and by how much.
• Design of Experiments (DOE): tests multiple factors at once to find which ones, and which combinations, actually move the outcome.
• Measurement Systems Analysis (MSA) and Gage R&R: verify that your measurement system itself is accurate and consistent enough to trust.
• Process Capability (Cp & Cpk): quantifies whether a process can consistently meet customer specification limits.
• Failure Mode Effects Analysis (FMEA): scores potential failure modes by severity, occurrence, and detection, to prioritize which risks need action first.

Tools Both Toolkits Actually Share

A handful of tools genuinely belong to both traditions, either because they predate the Lean/Six Sigma split entirely, or because they’re equally useful for a waste problem and a variation problem.

• Process Mapping: every Lean Six Sigma project, Lean-flavored or Six-Sigma-flavored, starts by mapping how the process actually works today.
• Cause and Effect (Fishbone) Diagram: works equally well to brainstorm sources of waste or sources of variation.
• 5 Whys: a root-cause technique with no statistical or Lean-specific assumptions baked in, it works on any kind of problem.
• Control Charts: originally a Six Sigma/SPC tool, but just as useful for monitoring a Lean flow metric (cycle time, WIP) as a quality metric.
• Standard Work: a Lean concept at its core (document the current best way to do a task), but it’s also exactly how a Six Sigma Control Plan gets followed day to day.

Which Lens Do I Actually Need?

Before reaching for any tool, ask what kind of problem is actually in front of you:

• “This takes too long” or “there’s too much sitting around waiting” is almost always a Lean (flow/waste) problem. Start with Value Stream Mapping or a Spaghetti Diagram.
• “This is inconsistent” or “we don’t know why some units come out wrong” is almost always a Six Sigma (variation) problem. Start with a Control Chart or a Fishbone Diagram, then confirm causes with Hypothesis Testing.
• “This is both slow and inconsistent”, the most common real-world case, needs both: a Lean pass to strip out obvious waste first (it’s cheaper and faster to fix), followed by a Six Sigma pass on whatever variation remains once the waste is gone.

That last point is worth repeating because it’s the actual logic behind combining the two methodologies in the first place: removing waste first is usually faster and cheaper than removing variation, and it often makes the variation problem easier to see and measure once the noise of obvious waste is gone. For the full history of how these two originally separate disciplines came together into one practiced methodology, see What Is Lean Six Sigma?

A Worked Example: Both Toolkits on One Process

Say an insurance company’s claims process takes an average of 14 days to close, and customers are complaining both that it’s slow and that similar claims seem to take wildly different amounts of time, some close in 3 days, others drag on for 30. That’s a textbook “both” problem, and it shows exactly why you need both toolkits rather than picking one.

The Lean pass comes first. A Value Stream Map of the current process reveals that a claim sits untouched in a shared inbox for an average of 4 days before anyone even opens it, pure waiting, no one disputes it’s waste. A Spaghetti Diagram of how a physical claims folder moves between departments shows it crossing the building six times for approvals that could happen in one sitting. Fixing just these two issues (a dedicated intake queue, co-locating the approval step) cuts the average close time from 14 days to 9, without touching a single statistic.

But the inconsistency problem is still there, some claims still close in 3 days, others in 20. That’s where the Six Sigma pass takes over. A Control Chart of closure time confirms the process is statistically out of control, not just naturally variable. A Fishbone Diagram session with the claims team generates a list of suspected causes: claim complexity, adjuster experience level, and whether a third party needs to be contacted. Hypothesis Testing on the data confirms that adjuster experience is the real driver (newer adjusters take significantly longer) while claim complexity, the team’s favorite guess, turns out not to be statistically significant at all. The fix, pairing new adjusters with a mentor for their first 90 days, is a Six Sigma-driven solution that the Lean pass alone would never have surfaced, because Lean tools don’t test whether a suspected cause is statistically real.

Notice the order: Lean first, to clear out the obvious, easy-to-fix waste cheaply, then Six Sigma, to solve the harder, statistically-hidden problem that was left over once the noise was gone. Running it in the opposite order (chasing adjuster-level statistics while claims are still sitting in an inbox for 4 days) would have buried the real signal under a much bigger, much simpler problem.

How This Splits Across Belt Levels

Certification bodies don’t expect every belt to go equally deep on both toolkits:

• Yellow Belt is typically expected to recognize the major tools in both toolkits and understand the Lean/Six Sigma distinction conceptually, without running statistical analysis independently.
• Green Belt is expected to run the Lean tools independently and to execute the core Six Sigma statistical tools (basic hypothesis testing, control charts, process capability) with some support on the more advanced ones.
• Black Belt is expected to run the full statistical toolkit independently, including multi-factor DOE and more advanced hypothesis tests, while also leading a team through the Lean side of a project and coaching Green Belts on both.

Common Exam Mistakes with Lean Six Sigma Tools

A few specific mix-ups show up often enough on practice exams that they’re worth calling out directly:

• Treating Kaizen as a purely Lean term. It originated in Lean/Toyota practice, but many Six Sigma bodies now teach “Kaizen events” as a general rapid-improvement format that can target either waste or variation, don’t assume a question about Kaizen is automatically testing Lean content specifically.
• Assuming Control Charts are Six-Sigma-only. They’re taught in the Measure and Control phases of DMAIC, but they’re just as legitimately used to monitor a pure Lean flow metric like cycle time or work-in-process, with no defect or specification limit involved at all.
• Confusing a Process Map with a Value Stream Map. A question that mentions inventory levels, wait times, or information flow between steps is pointing at a Value Stream Map, not a basic Process Map, even if the word “map” is all you catch on a quick read.
• Picking a statistical tool for a question that’s actually describing waste. If a stem describes a process taking too long, having excess inventory, or involving unnecessary movement, with no mention of defects, specification limits, or inconsistency, the answer is almost always a Lean tool, not a statistical one, even on a Six Sigma-branded exam.

Frequently Asked Questions

Do I need to learn both toolkits to use Lean Six Sigma?

Yes, at least at a working level. A combined Lean Six Sigma belt curriculum (Yellow, Green, or Black Belt on most certification bodies) teaches both toolkits together precisely because real processes almost always have both a flow problem and a variation problem hiding in them somewhere.

Which Lean Six Sigma tools get confused with each other most often?

Process Mapping and Value Stream Mapping are the most commonly confused pair. A basic process map shows the steps; a value stream map adds timing, inventory, and information flow specifically so you can see where waste is hiding between the steps, not just what the steps are.

Can Lean tools fix a variation problem on their own?

Not reliably. Lean tools are excellent at removing waste, which often reduces variation as a side effect (less handling, fewer handoffs, fewer opportunities to introduce error), but they were never built to statistically prove what’s causing variation in the first place. If a process is still inconsistent after a thorough Lean pass, that’s the signal to bring in the Six Sigma statistical toolkit rather than keep looking for more waste that may not exist.

Do ASQ, IASSC, and Villanova teach the same Lean Six Sigma tools?

The core toolkit is largely shared across certification bodies, Fishbone diagrams, FMEA, control charts, and value stream mapping all show up everywhere, but emphasis and depth differ. IASSC’s curriculum tends to weight the Lean side more heavily at the Green Belt level than ASQ’s, while ASQ’s Body of Knowledge adds some tools (like certain advanced DOE designs) that IASSC leaves out entirely. If you’re preparing for a specific exam, always check that body’s own BOK rather than assuming every certification tests an identical tool list.