Two Good Things, One Bad Result: The Hidden Conflict Between Lean and Six Sigma
By Marc Bradburry II “The Big Bearded Ginger”
Introduction: The Great Mix-Up
It is one of the most common misconceptions in business improvement, the idea that Lean and Six Sigma are interchangeable. You will hear teams say they are “doing Lean” to reduce defects or “using Six Sigma” to improve speed. Both have value, both drive improvement, but they serve different purposes, and when leaders mix them without understanding that difference, they end up chasing progress in circles.
You can do good things and still get bad results if those things work against each other. Many leadership teams never notice it happening, KPIs fluctuate, projects stall, morale dips, and everyone blames “resistance to change.” In reality, the system is fighting itself.
Lean: The Pursuit of Flow
Lean is about eliminating waste, anything that does not add value for the customer. Built on the Toyota Production System, its goal is not perfection but flow. Lean removes clutter, shortens cycle times, and smooths bottlenecks. It focuses on time, motion, and clarity of process.
Lean asks, “How can we do this faster, cleaner, and with less?”
Applied well, Lean builds structure and speed. It simplifies the day, makes problems visible, and helps teams see exactly where value is created and where it is lost. But Lean is not a defect reduction program, that is Six Sigma’s lane. Using Lean tools to fix precision problems is solving the wrong equation. You might make the process faster, but not necessarily more consistent.
Six Sigma: The Pursuit of Precision
Six Sigma’s goal is consistency, producing the same high-quality result every time. It is built on data, measurement, and statistical validation, not visual management or layout changes.
Six Sigma uses the DMAIC framework—Define, Measure, Analyze, Improve, Control—to identify variation and eliminate it at the source.
It asks, “Why is output inconsistent, and what variables are driving defects?”
The work is statistical: control charts, capability studies, regression, and process mapping. Done well, Six Sigma delivers stable results, down to 3.4 defects per million opportunities. But those measurements depend entirely on process stability. The moment the baseline moves, the math breaks.
The Hidden Conflict: When Good Changes Collide
Your defect study depends on a stable process. If you rearrange workflow mid-analysis, your baseline resets, your control limits no longer mean what they did, and you have to start over.
Teams often do two good things—a Lean change and a Six Sigma analysis—at the same time. The result is noise, not progress.
Cycle of Conflict: How It Shows Up
Scenario 1: You launch a DMAIC project and begin collecting data. Then, halfway through, you change the layout to cut walking, and your variation picture no longer matches reality.
Scenario 2: You streamline steps to hit takt, but the defects remain. The cause is not motion, it is variation in the material itself, and Lean alone cannot fix that.
The Right Sequence: Lean First; Six Sigma Second
Clear the clutter, then tune the machine.
Step one: use Lean to stabilize flow, remove bottlenecks, and create repeatable standard work.
Step two: apply Six Sigma to lock in precision, control variation, and confirm process capability.
That order matters. Lean clears the noise; Six Sigma tunes the signal. Reverse them, and you will spend more time chasing why the numbers changed than fixing why the process did. Lean gives your data a stable stage, and Six Sigma makes the performance repeatable.
Quick Reference: What to Use When
Use Lean when…
- Queues grow or movement is heavy.
- Changeovers drag, or WIP hides problems.
- Visual control is weak; or takt time is missed because of motion.
Use Six Sigma when…
- Outputs swing or defects show repeating patterns.
- Measurement error is likely, or root causes look probabilistic.
- The process is stable but not consistent in results.
Why This Matters to Leaders and CI Teams
Mid and upper management often sit between “do more with less” and “deliver perfect quality.” They push Lean for speed while demanding Six Sigma precision. Without a shared roadmap, improvement efforts compete instead of compound. Understanding this distinction protects your investment and keeps teams from burnout.
For CI professionals, it changes how you stage projects. Lock the process before measuring it. Collaborate with operations before pulling data. Explain to leadership that stability is a prerequisite for measurement, not a byproduct of it.
Final Thought
Lean makes you fast. Six Sigma makes you accurate. When you mix them blindly, speed and accuracy fight… and neither wins.
Before you start a project, decide which hat you are wearing. Are you clearing waste or controlling variation? Both matter, but each requires a different mindset and a different moment. The best leaders know when to separate them… and when to bring them together.
Discover more from Marc Bradburry | Transforming Industries with Innovation & Leadership
Subscribe to get the latest posts sent to your email.
