Lean Six Sigma Tools: Essential Methods to Use

Lean Six Sigma gives you a toolkit for fixing broken processes, but the list of tools can feel endless and it is rarely clear which one to reach for or when. The simplest way to make sense of the essential Lean Six Sigma tools is to map them to the phase of the project where you actually use them: Define, Measure, Analyze, Improve, Control (DMAIC). Learn them in that order and each tool has an obvious job.

This guide walks through the core tools by DMAIC phase, with what each is best for and when to reach for it, which ones to start with, the one teams get wrong most often, and a real Sleep Number example where the toolkit took product quality issues down by 80%.

What are Lean Six Sigma tools?

Lean Six Sigma tools are the practical methods a team uses to understand a process, find why it is failing, fix it, and keep it fixed. You will often see them split into “Lean tools” and “Six Sigma tools,” but in practice the core tools are used for both. What changes is not the toolbox but the problem you are solving: Lean Six Sigma uses Lean when the process is too slow and Six Sigma when the output has too many errors and defects, and the same tools support both. So rather than memorizing two lists, it is far more useful to know which tool fits which phase of a DMAIC project.

The essential Lean Six Sigma tools, by DMAIC phase

Here are the tools that do the heavy lifting on almost every project, grouped by the phase where you use them.

Define: scope the problem

• Voice of the Customer (VOC). Collects customer feedback on your performance. Reach for it at the start of a Lean Six Sigma journey as the source of improvement ideas.
• Pareto. Ranks the drivers of customer complaints in order of importance so you focus on the most impactful ones. Use it at the start to prioritize the problems with the biggest impact and turn them into projects. A useful rule: one Pareto bar at a time, where one Pareto bar becomes one project.
• Problem statement. A description of the problem, preferably with data, that the project is aiming to fix. Write it once the project is selected.
• SIPOC. A high-level snapshot of the process you are improving, setting the clear start and stop boundaries and the scope. Also done once the project is selected. See the SIPOC model for the detail.

Measure: size the problem with data

• Data collection. Collects data about the problem and proves with data how big it really is. Comes right after the Define phase.
• Baseline performance. Turns that data into a graphical statement of the problem, so the audience sees the magnitude, which drives urgency and buy-in to fix it. Also after Define.
• Goal statement. A numerical statement of how much you will improve the baseline, which sets the vision of the future state and the business case. Comes after baseline performance.

Analyze: find the root cause

• Fishbone. Determines the root causes that solutions need to fix in order to permanently solve the problem. Reach for it after the Measure phase, working with the subject-matter experts as well as the data.

Improve: fix the cause

• Solutions. The changes that fix the root causes of the problem, developed after the Analyze phase. The point is to fix the cause, not the symptom, so the fix holds.

Control: hold the gain

• Controls. Control mechanisms, such as a control chart, that make sure the solutions are sustainable and the process does not drift back.

Which tools are Lean and which are Six Sigma?

This is the question everyone asks, and the honest answer is that the core tools above are used for both Lean and Six Sigma. VOC, Pareto, SIPOC, fishbone, control charts and the rest are not owned by one side. What tells you whether you are doing Lean or Six Sigma is the problem in front of you: if customers are complaining about delays, you are leaning on Lean to remove waste and speed the process up; if they are complaining about errors and defects, you are leaning on Six Sigma to reduce variation. The toolkit is shared; the target is what differs.

The three tools to start with

If a team is just starting out, three tools give the most value for the least effort: Voice of the Customer, Pareto, and the problem statement. Together they give a team direction, focus, and a narrow scope, which is exactly what sets a first project up to succeed. Get those three right and the rest of the toolkit has something solid to work on.

The tool teams get wrong most often

The most misused tool is the problem statement. People are impatient and want to jump to solutions right away, so they either skip the problem statement or replace it with a goal statement describing the future they want. Because they never pinned down the actual problem they are trying to solve, they end up with solutions that do not work and do not fix anything. Writing a clear, data-backed problem statement first is the unglamorous step that makes everything after it land.

The tools in action: a $10M example at Sleep Number

Sleep Number, a leading US wellness company, faced serious product quality issues that were driving a high volume of customer complaints, warranty costs, and reputation risk. Here is how the toolkit was applied in sequence. Voice of the Customer collected the complaints coming into the call center. Pareto ranked those complaints in order of importance so the team could focus on the biggest drivers, and each driver, each Pareto bar, became its own project.

For each project the team wrote a problem statement and confirmed the magnitude of the problem with baseline performance data. Root causes were identified with fishbone analysis and fixed with the right solutions, and control charts made sure the improvements held. After many projects, product quality issues were down by 80%, saving roughly $10M annually in warranty costs, and customer experience improved 500%. None of that came from a single clever fix. It came from using the right tool, in the right phase, over and over. It is the same discipline behind the Six Sigma principles.

Putting the tools to work

The essential Lean Six Sigma tools are easier to master once you stop sorting them into Lean versus Six Sigma and start using them by DMAIC phase: VOC, Pareto, problem statement and SIPOC to define, data and baselines to measure, fishbone to analyze, solutions to improve, and controls to hold the gain. The organizations that get results build this fluency into their own people through a structured process improvement program, rather than relying on outside help for every project.

The Lean Six Sigma Company runs in-company group training and full deployment support across the United States. If you want your team to use these Lean Six Sigma tools well and act on what they find, those are the right starting points.

Frequently Asked Questions