What Is Lean Six Sigma?

Lean Six Sigma isn’t a third methodology sitting alongside Lean and Six Sigma. Instead, it’s what you get when you run the two together as one practice. The site already covers each half on its own: Lean on its own terms, what Six Sigma is on its own terms, and how the two differ. This page is the missing piece. It shows what the two look like combined into one discipline. It also explains why most organizations today don’t run one without the other.

What Is Lean Six Sigma?

Lean Six Sigma is a combined management methodology. It pairs Lean’s focus on removing waste and improving flow with Six Sigma’s focus on removing variation and defects. In addition, both run through the same project framework, DMAIC (Define, Measure, Analyze, Improve, Control). A Lean Six Sigma practitioner doesn’t choose one lens. For them, waste and variation are both problems worth solving, often on the same project.

That combination isn’t cosmetic. A process can be fast and still badly inconsistent, or consistent and still badly wasteful. Most real processes have some of both problems. As a result, fixing only one leaves money and customer frustration on the table.

Where Lean Six Sigma Came From

Lean and Six Sigma started out as two completely separate traditions, built decades apart, for different reasons.

Lean’s roots go back to the 1950s, to the Toyota Production System, developed largely by Taiichi Ohno. Toyota’s problem wasn’t statistical. Post-war Japan had far less capital and raw material than American manufacturers. So Toyota built a system obsessed with removing anything that didn’t serve the customer: excess inventory, unnecessary motion, waiting, overproduction. The term “Lean” was popularized decades later. However, the practice itself dates to that era.

Six Sigma’s roots go back to 1986 at Motorola. There, engineer Bill Smith and quality leader Mikel Harry developed a data-driven approach to cutting defects to near zero. The “six sigma” in the name refers to a specific statistical defect rate. Motorola’s problem wasn’t flow. Inconsistent quality was costing them warranty claims and reputation. Therefore, they wanted a rigorous, provable way to find and remove the root causes.

The two traditions were formally combined around 2001, when Chuck Mills, Barbara Wheat, and Mike Carnell published Leaning into Six Sigma: The Path to Integration of Lean Enterprise and Six Sigma. The book argued that manufacturers running Six Sigma projects were leaving Lean-sized gains on the table. In fact, the reverse was true too. Over the next decade, “Lean Six Sigma” became the default. Most organizations and certification bodies (ASQ, IASSC, Villanova, and others) now teach it as one program, not a choice between two.

The Core Idea: Speed and Precision, Together

The simplest way to hold the combination in your head: Lean makes a process faster and leaner; Six Sigma makes it more precise and consistent. Neither one guarantees the other.

• A process can run Lean, with minimal waste and fast cycle times, and still produce output that varies wildly from unit to unit.
• A process can run in excellent statistical control, with every unit landing where it should. Yet it can still take three times longer than needed because of waste nobody removed.
• The goal is a process that’s both fast and consistent. Getting there usually takes both toolkits, not a double dose of one.

In practice, most Lean Six Sigma projects tackle waste first. Removing waste is usually cheaper and faster, and it needs no statistical proof. In fact, a team can often see it and fix it directly. Once the obvious waste is gone, the remaining variation is a cleaner signal. As a result, it is easier to isolate and test with Six Sigma’s tools. Lean first to clear the noise, then Six Sigma to solve what’s left. That sequence is the practical heart of the combination. See the full breakdown of which Lean Six Sigma tools belong to which toolkit, and when to reach for each.

DMAIC, Run with a Lean Lens

A Lean Six Sigma project still follows DMAIC, Six Sigma’s five-phase framework. But Lean thinking shows up in every phase. It isn’t bolted on as an afterthought:

• Define: the team scopes the project around customer quality requirements (a Six Sigma habit). It also scopes around the value the customer will pay for (a Lean habit). That avoids optimizing something the customer never cared about.
• Measure: alongside the usual Six Sigma baseline data, the team builds a Value Stream Map. As a result, it shows where time and material are wasted, not just where defects occur.
• Analyze: root causes get sorted into two groups. Waste-driven causes are fixable with Lean tools. By contrast, variation-driven causes need statistical confirmation.
• Improve: solutions draw from both toolkits. A Kaizen event might redesign a wasteful layout. Meanwhile, a Designed Experiment might prove which setting reduces variation.
• Control: the control plan locks in both kinds of gains. Standard Work keeps the Lean improvements from eroding. Statistical Process Control keeps the variation gains from drifting back.

Lean Six Sigma Belts

Certification follows the same belt structure as standalone Six Sigma: Yellow, Green, and Black. But a Lean Six Sigma curriculum teaches both toolkits at every level. Lean is not optional extra credit. Depth differs by belt. A Yellow Belt learns to recognize both toolkits and support a project team. A Green Belt runs both toolkits independently on a project of moderate complexity. A Black Belt leads full projects and mentors Green Belts in both disciplines. That includes advanced methods, like multi-factor Designed Experiments, that a Green Belt usually only assists with.

Why Most Organizations Run Them Combined Today

Today it’s rare to find a pure Six Sigma program with no Lean influence. Similarly, a pure Lean program with no statistical rigor is just as rare. A few reasons the combination won over running either alone:

• Most real business problems are mixed problems. Slow and wasteful doesn’t exclude inconsistent and defect-prone. In fact, look with both lenses and you’ll often find both on the same process.
• Lean wins build momentum for the harder Six Sigma work. A team that gets a quick, visible win from removing waste is more willing to invest in the slower work. That means weeks of proper statistical root-cause investigation.
• Six Sigma’s rigor protects Lean’s gains from backsliding. A Lean improvement without a control plan can quietly drift back to the old way. Control Charts and a documented Control Plan make a Lean win stick.
• Certification bodies standardized on it. ASQ, IASSC, and most university programs now teach a combined curriculum by default. That makes the combination the industry norm, not a niche choice.

A Real-World Example: Lean Six Sigma in a Hospital

A hospital’s emergency department is struggling on two fronts. First, patients wait an average of 95 minutes before being seen. Second, time to a correct diagnosis varies enormously: 20 minutes for some patients, over 4 hours for others with a comparable condition. Leadership brings in a Lean Six Sigma team instead of choosing one methodology. After all, both problems are real, and neither toolkit alone would catch both.

The Lean side of the project maps the patient’s full journey from arrival to triage to a treatment bay. The map exposes several pure waste problems. Patients wait at three check-in points that collect overlapping information. Lab samples sit in a pickup bin for up to 40 minutes. Finally, triage nurses walk an average of 1,200 feet per shift to fetch supplies. None of this needs statistics. The team merges check-in into one step, adds a courier pickup schedule, and moves supply carts closer to triage. The average wait drops from 95 minutes to 61 without a single hypothesis test.

The Six Sigma side of the project tackles the diagnosis-time variation separately. A Control Chart of diagnosis time confirms the process is out of control. In other words, the variation is not just natural differences between conditions. The team stratifies the data by shift, physician experience, and time of day. Diagnosis time balloons during shift changes, when a case is handed from one physician to another. A Fishbone session and a short Designed Experiment compare two handoff formats: verbal-only versus a written checklist. As a result, the checklist cuts handoff diagnosis delay by over 60%. The Lean map alone would never have surfaced this, because a shift-change handoff doesn’t look like physical waste.

The Control phase locks in each gain differently. Standard Work now governs the new check-in and supply-cart layout, a Lean-style control. The handoff checklist becomes an audited Control Plan item, with monthly compliance tracked on a Control Chart, a Six Sigma-style control. Neither gain would have held without a control built for its own type of problem.

Lean vs. Six Sigma vs. Lean Six Sigma: Which Do You Actually Need?

Despite how often they’re bundled together, there are legitimate reasons to run one without the other:

• Choose Lean alone when the process is already statistically well-behaved, with low variation and few defects. The only real complaint is speed, cost, or excess inventory. A well-functioning accounting close process that just takes too many days is a Lean problem, not a variation problem.
• Choose Six Sigma alone when the process is already lean, with minimal waste and efficient flow. The only real complaint is inconsistency or defects. A fast, efficient manufacturing line that occasionally produces an out-of-spec part is a Six Sigma problem, not a waste problem.
• Choose Lean Six Sigma when you don’t know yet which problem you have. That describes most processes that haven’t been through a structured improvement effort. The combined approach costs little extra up front, since Define and Measure are largely shared. And it avoids solving only half the problem.

Common Myths About Lean Six Sigma

• “Lean Six Sigma is only for factories.” Both halves started in manufacturing. Today the combined method is standard in healthcare, banking, insurance, software, and government. A hospital or call center has as many waste and variation problems as a factory floor. However, they just look different.
• “You need heavy statistics software to do Lean Six Sigma.” Many of the biggest fixes on a real project are pure Lean, like removing a redundant step or moving a supply cart. Therefore, they need no statistics at all. The statistical tools matter, but they’re not the whole methodology.
• “Lean Six Sigma is just a certification, not a real skill set.” The certification formalizes a skill set that predates it by decades. The belts signal that someone can run DMAIC and apply both toolkits competently.
• “Six Sigma and Lean compete with each other.” They fix different things: waste versus variation. So there’s no real tension in running both on the same project. It’s not like choosing between two software platforms that do the same job.

Frequently Asked Questions

Is Lean Six Sigma just Six Sigma with extra steps?

No. Six Sigma alone can leave real waste untouched. For example, a process can be well controlled and still inefficient. Lean Six Sigma adds the waste lens on top of the variation lens. So a project doesn’t stop at “consistent” if the process is still slow or resource-heavy.

Can I learn Lean without Six Sigma, or vice versa?

Yes, both exist as standalone disciplines, and some roles only need one. A pure flow role might only need Lean. A pure data-analysis role might only need Six Sigma’s statistics. But most Green and Black Belt certifications teach them together by default. Most improvement roles eventually run into both kinds of problems.

Does Lean Six Sigma only apply to manufacturing?

No, though both traditions started there. Lean Six Sigma is now used widely in healthcare, financial services, IT, government, and call centers. It fits anywhere a process can be slow, inconsistent, or both. The tools translate directly. You can value-stream-map a hospital discharge process exactly like a factory floor. You can analyze call-center handle-time variation exactly like a defect rate.