Module
Lean Six Sigma for Quality
DMAIC and lean tools applied to reduce variation and waste on prioritised quality problems.
Module details
Outcome: DMAIC and lean tools applied to reduce variation and waste on prioritised quality problems.
Roles
- Black Belt
- Green Belt
- Quality Engineer
Workflow
- 1.Define problem with measurable Y and baseline
- 2.Measure with validated data and MSA
- 3.Analyse causes with data before hypothesis
- 4.Improve and control with owner and cadence
Evidence
Common failures
- Tool applied without data validation
- Improve phase skipped straight to control
Escalation
Projects stalled beyond 30 days at any phase gate escalate to sponsor for scope reset.
KPIs
- Sigma level shift
- Financial impact per project
Official sources
- ISO 9001 — Quality management systems (ISO 9001:2015)
International requirements for a quality management system covering leadership, planning, support, operation, performance evaluation and improvement.
International Organization for Standardization · Authority: ISO
Related on Sanjeewa.life
Learning
Technology
- Analytics Platforms
DMAIC phases
- 1.Define— Frame the problem, customer, scope and measurable goal.Key activities: Draft project charter with problem and goal statement; Identify customer and CTQ; Map high-level process (SIPOC)Exit criteria: Signed charter; Approved scope and Y metric
- 2.Measure— Establish a validated baseline of the process performance.Key activities: Operationally define Y and Xs; Run measurement system analysis; Collect representative baseline dataExit criteria: Validated measurement system; Baseline capability documented
- 3.Analyse— Identify and confirm root causes driving variation in Y.Key activities: Stratify data and generate hypotheses; Run graphical and statistical analysis; Confirm root causes with evidenceExit criteria: Verified root causes; Prioritised improvement targets
- 4.Improve— Design, pilot and implement counter-measures.Key activities: Generate and evaluate solutions; Pilot with defined success criteria; Deploy validated solutionExit criteria: Piloted solution with measured impact; Post-improvement capability
- 5.Control— Sustain the gain and hand back to the process owner.Key activities: Publish control plan and standard work; Set monitoring, response plan and audit cadence; Transfer ownership and close projectExit criteria: Active control plan; Sustained performance for defined horizon
Six Sigma tools
- SIPOCPhase: define
High-level view of Suppliers, Inputs, Process, Outputs and Customers.
Prerequisites: Agreed project scope
Output: SIPOC diagram anchoring scope boundaries
Misuse warning: Not a substitute for a detailed process map in Analyse.
- Critical-to-Quality TreePhase: define
Translate customer needs into measurable requirements.
Prerequisites: Voice of the customer captured
Output: CTQ tree with metrics and targets
Misuse warning: Author-driven CTQs without customer input mislead the project.
- Measurement System Analysis / Gauge R&RPhase: measure
Confirm the measurement system is capable of detecting real variation.
Prerequisites: Operationally defined metric; Trained operators
Output: MSA report with repeatability and reproducibility indices
Misuse warning: Never draw improvement conclusions before the measurement system is proven capable.
- Process Capability (Cp, Cpk, Pp, Ppk)Phase: measure
Quantify how a process performs against specification limits.
Prerequisites: Stable process (for Cp/Cpk); Validated measurement system
Output: Capability indices with the assumptions recorded
Misuse warning: Reporting Cp/Cpk on an unstable process, or comparing indices across different sampling plans, misleads decisions.
- Statistical Process ControlPhase: control
Detect special-cause variation using control charts.
Prerequisites: Stable data collection; Correct chart type for data
Output: Live control chart with response rules
Misuse warning: Reacting to every point ignores the purpose of control limits.
- Pareto AnalysisPhase: analyse
Prioritise the vital few causes contributing most to the effect.
Prerequisites: Categorised defect or cause data
Output: Ranked bar chart with cumulative line
Misuse warning: Categories chosen for convenience hide the true drivers.
- Cause-and-Effect (Fishbone) DiagramPhase: analyse
Structure brainstorming of possible causes across categories.
Prerequisites: Clearly stated problem
Output: Populated fishbone ready for data-based verification
Misuse warning: Brainstormed causes are hypotheses, not confirmed root causes.
- 5 WhysPhase: analyse
Drill from symptom toward systemic cause by asking why.
Prerequisites: Access to people who do the work; Verified problem statement
Output: Chain of causes ending at a systemic cause
Misuse warning: Stopping at a convenient blame level misses the real cause.
- Failure Mode and Effects AnalysisPhase: analyse
Rank failure modes by severity, occurrence and detection.
Prerequisites: Process or design map; Cross-functional team
Output: Ranked risks with mitigation actions
Misuse warning: RPN scoring without action ownership converts risk analysis into paperwork.
- Hypothesis TestingPhase: analyse
Test whether an observed effect is statistically significant.
Prerequisites: Defined hypotheses; Adequate sample size
Output: Test result with p-value and practical interpretation
Misuse warning: Statistical significance without practical significance drives the wrong decision.
- Cost of Poor QualityPhase: define
Quantify the financial impact of failure, appraisal and prevention.
Prerequisites: Access to financial and quality data
Output: COPQ estimate with categories
Misuse warning: Ignoring hidden costs understates the case for action.
- Standard WorkPhase: control
Codify the current best-known method for a task.
Prerequisites: Stable process; Trained operators
Output: Standard work documents with cycle and takt data
Misuse warning: Freezing standard work prevents the improvement it should enable.
- Mistake-Proofing (Poka-Yoke)Phase: improve
Design the process so errors are prevented or made obvious.
Prerequisites: Understood failure mode
Output: Poka-yoke device or design change
Misuse warning: Adding checks without changing the design is inspection, not prevention.
- Control PlansPhase: control
Define what is monitored, by whom, with what response when out of control.
Prerequisites: Confirmed improvement; Trained owners
Output: Signed control plan with response actions
Misuse warning: Control plans without response actions leave gains unprotected.