Lean Six Sigma · Beginner · 12 min read
What Is Lean Six Sigma?
Lean Six SigmaLean Six Sigma is a practical method for making work faster and more consistent: Lean removes the waste that slows work down, and Six Sigma removes the variation that makes results unpredictable. Together they give teams a shared, evidence-based way to fix the problems that keep coming back.
Why this matters at work: every workplace has processes that are slower, messier, or less reliable than anyone wants — and most fixes don’t stick because they treat symptoms. Lean Six Sigma is the most widely used improvement framework in industry, and its vocabulary (DMAIC, the eight wastes, belts, sigma levels) shows up in job postings, project charters, and the ASQ certification exams.
By the end, you should be able to
- Explain what Lean targets (waste), what Six Sigma targets (variation), and why they work best together.
- Name the eight wastes and spot them in an office or factory process.
- Walk through the five DMAIC phases and say what each one produces.
- Describe what a sigma level means and what the belt levels are for.
Lean and Six Sigma: two halves of one idea
Lean — the war on waste
Born on the Toyota production line, Lean asks one question of every step in a process: does the customer actually value this? Anything else — waiting, rework, extra motion, piles of half-finished work — is waste, and waste is what makes work slow. Lean’s goal is flow: value moving to the customer with as few interruptions as possible.
Six Sigma — the war on variation
Developed at Motorola and made famous at GE, Six Sigma attacks a different enemy: inconsistency. A process that averages fine but swings wildly still produces defects, missed deadlines, and unhappy customers. Six Sigma uses data and statistics to find why results vary, then removes those causes so the process becomes predictable.
Put together: Lean makes the process fast, Six Sigma makes it reliable. A process that is quick but erratic frustrates customers; one that is consistent but slow loses them. Lean Six Sigma pursues both at once, using a shared project roadmap (DMAIC) and a shared rule: decisions follow data, not opinions.
Terminology
| Term | Meaning | Plain-language version |
|---|---|---|
| CTQ | Critical to quality | The few things the customer truly cares about |
| Defect | Any outcome outside customer requirements | A result the customer would reject |
| DPMO | Defects per million opportunities | The defect rate, scaled up so small rates are visible |
| Sigma level | How many σ fit between the process mean and the nearest limit | A single score for process quality (higher is better) |
| DMAIC | Define, Measure, Analyze, Improve, Control | The five-phase project roadmap |
| Gemba | “The real place” (Japanese) | Go watch the actual work, don’t improve from a desk |
| Kaizen | Continuous improvement | Many small fixes beat one giant one |
| Belt | Yellow / Green / Black / Master Black | Levels of training and project responsibility |
Interactive: the eight wastes
Lean names eight wastes, remembered by the acronym DOWNTIME. Click each one to see what it means and what it looks like in both an office and a factory.
Pick a waste above
Each card explains the waste and shows one office example and one factory example.
Interactive: what “sigma level” means
The “Six Sigma” name is a quality target: fit six standard deviations between the process average and the nearest customer limit. Slide the level and watch the defect rate collapse — the scale is why companies chase higher sigma. (The numbers use the industry-standard 1.5σ long-term shift convention.)
At 3 sigma, roughly 66,807 of every million deliveries go wrong — about 1 in 15. Most struggling processes live here.
DMAIC: the improvement roadmap
Every Lean Six Sigma project follows the same five phases. The discipline of the sequence is the point — it stops teams from jumping to solutions before they understand the problem.
- Define — agree on the problem, the customer impact, the goal, and the scope. Output: a one-page project charter.
- Measure — collect data on how the process performs today. Output: a trustworthy baseline (and often a surprise).
- Analyze — use the data to find the root causes of waste and variation, not the symptoms. Output: verified causes.
- Improve — design, pilot, and prove solutions that attack those root causes. Output: a demonstrated improvement.
- Control — lock the gains in with standards, training, and monitoring (control charts live here). Output: an improvement that lasts.
Worked example: the invoice-error project
A finance team reworks about 18% of invoices because of errors, delaying payments and irritating suppliers.
- Define: “Reduce invoice rework from 18% to under 5% in 90 days.” The CTQ is right first time.
- Measure: two weeks of tallies show the error rate is really 21% — and 70% of errors are wrong purchase-order numbers.
- Analyze: going to the gemba reveals the ordering system shows PO numbers in a different format than the invoice template expects — a process problem, not a people problem.
- Improve: the template now auto-fills the PO number from the system. A four-week pilot cuts rework to 4%.
- Control: the fix becomes the standard template, new-starter training is updated, and a monthly chart watches the error rate so drift is caught early.
Notice what made it work: the team measured before analyzing (the real rate and the biggest cause were both surprises), found a root cause by watching the actual work, and finished with a control so the gain would stick.
Belts: who does what
| Belt | Typical role | Time on improvement work |
|---|---|---|
| Yellow Belt | Team member: understands the basics, supports projects, spots waste locally | A few hours per project |
| Green Belt | Leads smaller projects in their own area while doing their day job | Part-time |
| Black Belt (ASQ CSSBB) | Leads major cross-functional projects; coaches Green Belts; deep statistical toolkit | Often full-time |
| Master Black Belt | Trains Belts, selects projects, connects the programme to business strategy | Full-time |
Common misconceptions
Where the statistics comes in
Measure, Analyze, and Control are powered by statistics, and this library covers the core tools: start with the normal distribution, then see how a process compares to its specification with process capability (Cp & Cpk), and how the Control phase watches a process over time with control charts.
Try it yourself
Name that waste. Match each scenario to the waste it best illustrates, then check your answers.
Check your understanding
Five questions. Pick an answer for each, then press Check my answers.
Final summary
- Lean removes waste so value flows quickly; Six Sigma removes variation so results are consistent.
- The eight wastes (DOWNTIME) give you a checklist for spotting non-value work in any process.
- DMAIC — Define, Measure, Analyze, Improve, Control — is the roadmap, and its sequence is the discipline.
- Sigma level turns a defect rate into one score; 6σ corresponds to about 3.4 DPMO.
- Belts describe training and project responsibility, from Yellow (team member) to Master Black Belt (programme leader).
- The method works anywhere work flows through steps — offices, hospitals, and software as much as factories.
References & further reading
- ASQ Quality Resources — What Is Six Sigma?: asq.org/quality-resources/six-sigma
- ASQ Quality Resources — What Is Lean?: asq.org/quality-resources/lean
- Womack, J. P. & Jones, D. T., Lean Thinking — the classic introduction to Lean principles.
- George, M. L., Lean Six Sigma — the standard text on combining the two methods.