Enterprise-wide Deployment and Lean Six Sigma Fundamentals
What this domain tests
You must show that you understand Lean Six Sigma as a management system, not just a toolbox. Know the difference between Lean (flow, waste, speed, the seven wastes: overproduction, waiting, transport, overprocessing, inventory, motion, defects) and Six Sigma (variation reduction, DMAIC, statistics). Questions often ask which tool fits which problem: waste → value stream map, 5S, kanban; variation → control charts, capability studies, DOE.
Deployment structures
Understand roles: Executive sponsor/Champion (removes barriers, funds projects), Master Black Belt (deploys, mentors, trains), Black Belt (leads complex projects full time), Green Belt (leads projects part time), Yellow/White Belt (awareness, local support). Know belt selection criteria, project selection and prioritization (cost of poor quality, customer impact, feasibility), and the project funnel/pipeline.
Traps candidates fall for
- Confusing Lean speed tools with Six Sigma statistical tools, or claiming one replaces the other.
- Assuming belts must be full-time; Green Belts usually are not.
- Treating DMAIC as the only path - DMADV/DFSS is for designing new processes where none exists.
- Ignoring change management and leadership engagement; deployment fails without them.
- Confusing cost of poor quality (internal/external failure, appraisal) with prevention costs.
Rule of thumb
Match the method to the situation: fix an existing, measurable process → DMAIC; design something new → DMADV; eliminate obvious waste and improve flow → Lean events (kaizen). A project with no baseline data and no defined customer requirement is not ready - go back to project selection.
Worked example
A plant has long lead times and excess WIP but stable defect rates. The right first move is a value stream map and kaizen to cut waste - not a DOE. If defects were high and variable, a capability study and control chart would come first.