What Is Six Sigma?
Six Sigma is a data-driven methodology for eliminating defects and reducing variation in any process. Developed at Motorola in 1986 and popularized by General Electric under Jack Welch, it uses statistical tools to measure performance, identify root causes, and implement lasting solutions.
The name comes from statistics: a process operating at "six sigma" produces only 3.4 defects per million opportunities. Most companies operate between 3 and 4 sigma.
💡 Key Insight
Six Sigma isn't just about quality — it's about using data to make better decisions. If you can measure it, you can improve it.
The Sigma Levels
The sigma level tells you how capable your process is. Higher sigma = fewer defects = happier customers.
| Sigma Level | Defects / Million | Yield | What It Feels Like |
|---|---|---|---|
| 2σ | 308,537 | 69.15% | Nearly 1 in 3 items has a defect |
| 3σ | 66,807 | 93.32% | Typical unmanaged process |
| 4σ | 6,210 | 99.38% | Pretty good — but still ~6K defects/million |
| 5σ | 233 | 99.977% | World-class operations |
| 6σ | 3.4 | 99.99966% | Near-perfect quality |
At 99% quality (3.8σ): 20,000 lost mail articles per hour. 5,000 botched surgeries per week. 2 short or long landings at major airports daily.
At 99.99966% quality (6σ): 7 lost mail articles per hour. 1.7 botched surgeries per week. 1 bad landing every 5 years.
The difference between "good" and "excellent" quality can be life-changing — literally.
DMAIC: The Five Phases
DMAIC (Define, Measure, Analyze, Improve, Control) is the structured problem-solving framework at the heart of Six Sigma.
Define
What's the problem? Who's the customer? What does "good" look like? Create a clear problem statement, define scope, and identify the customer's critical-to-quality (CTQ) requirements. A good problem statement is specific and measurable: "Order accuracy dropped from 99.2% to 97.1% in Q3."
Measure
Collect baseline data. How bad is the problem right now? Establish your measurement system and validate it's accurate. Map the current process, measure cycle times, defect rates, and variation. You can't improve what you don't measure.
Analyze
Find the root cause — not symptoms. Use Pareto charts, fishbone diagrams, regression analysis, and hypothesis testing to identify the vital few factors driving your defects. SymplProcess's Pareto Analysis tool automates this.
Improve
Design and test solutions. Use pilot runs to validate improvements before full-scale rollout. Focus on solutions that address root causes, not workarounds for symptoms.
Control
Lock in the gains. Create control charts, standard operating procedures, and monitoring dashboards so improvements stick. Without control, processes drift back to their old state within weeks.
Common Pitfalls
✅ Signs You're Doing It Right
- Decisions backed by data, not opinions
- Root causes validated before solutions tried
- Control plans in place before project closes
- Team members from the process are involved
❌ Common Mistakes
- Jumping to solutions in the Define phase
- Analysis paralysis — 6 months of data collection
- No control phase = improvements evaporate
- Using Six Sigma for simple problems that just need a fix
Interactive Demo
Explore how sigma level and process mean shift affect defect rates. Adjust the sliders to see the normal distribution change in real time.
Stop reading, start modeling
Model your process flow, run simulations, optimize staffing with TOC math, and test your knowledge with 107 interactive checks — all in one platform.