What Is Lean?

Lean is a management philosophy and operational methodology derived from the Toyota Production System (TPS), codified for Western audiences by Womack, Jones, and Roos in The Machine That Changed the World (1990) and further developed in Lean Thinking (1996). Its central premise is that any activity consuming resources — time, labour, materials, capital, space — without creating value in the eyes of the customer is waste (muda) and should be systematically eliminated.

The Five Lean Principles (Womack & Jones)

  1. Specify Value: Define value precisely from the customer's perspective — only what the customer is willing to pay for counts as value
  2. Map the Value Stream: Identify every step in the process end-to-end; classify each as value-adding, necessary non-value-adding, or waste
  3. Create Flow: Eliminate interruptions, batching delays, and waiting so that value-creating steps flow continuously without queues or stoppages
  4. Establish Pull: Let customer demand pull products through the system rather than pushing forecast-based production that creates overproduction and inventory
  5. Pursue Perfection: Continuous improvement (kaizen) — relentlessly reduce waste, compress lead times, and raise quality as a never-ending pursuit

The 8 Forms of Waste (TIMWOODS)

Waste Description Supply Chain / Operational Example
TransportationUnnecessary movement of materials or productsParts routed through multiple warehouses before reaching production
InventoryExcess stock beyond immediate needsSafety stock far above statistically justified levels; end-of-season overstock
MotionUnnecessary movement of people or equipmentWarehouse operators walking excessive distances due to poor slotting
WaitingIdle time waiting for next stepProduction line stopped waiting for parts; purchase orders waiting for approval
OverproductionProducing more than currently neededManufacturing to forecast rather than orders; producing large batches "while the machine is set up"
OverprocessingMore processing than the customer requiresInspecting every unit of a low-risk product; multiple approval layers for routine POs
DefectsErrors requiring rework, scrapping, or warrantyWrong items shipped; production rejects; supplier quality failures returned from customers
Skills underutilisationNot leveraging people's knowledge and creativityExperienced operators not consulted on kaizen; improvement ideas not captured or acted on

Lean's primary metric: Lead Time and Flow Efficiency

Lean measures success primarily through time — cycle time, lead time, and the ratio of value-adding time to total elapsed time (flow efficiency). A manufacturing process with 3 days of value-adding work taking 30 days total elapsed time has a flow efficiency of just 10%. Lean relentlessly attacks the 27 days of non-value-adding time — the waiting, transport, batching, and administrative delays — to compress lead time and free working capital tied up in WIP.

What Is Six Sigma?

Six Sigma is a data-driven improvement methodology developed at Motorola in the late 1980s by Bill Smith and Mikel Harry, and subsequently popularised by Jack Welch at General Electric in the 1990s. Its objective is to reduce process variation to the point where defects are statistically negligible — specifically, fewer than 3.4 Defects Per Million Opportunities (DPMO).

The name derives from the statistical concept of the standard deviation (σ, sigma). A process operating at Six Sigma quality has its specification limits set at six standard deviations from the process mean — meaning the probability of a value falling outside specification is 3.4 per million, accounting for the 1.5-sigma mean shift that Motorola observed in long-run industrial processes.

The sigma scale

Sigma Level DPMO Yield Typical Context
308,537 69.1% Unmanaged processes; batch manufacturing with poor SPC
66,807 93.3% Low-capability processes; typical "average" industrial process without active quality management
6,210 99.4% Improved process with SPC; many manufacturing processes post-lean implementation
233 99.977% High-capability processes; well-managed discrete manufacturing
3.4 99.99966% Six Sigma target; aerospace, medical device, semiconductor, financial transaction processing

The DMAIC Framework

Six Sigma projects are executed through the DMAIC problem-solving cycle:

  1. Define: Scope the problem precisely. Identify the customer(s), CTQ (Critical to Quality) requirements, project boundaries, and business case. Output: Project Charter.
  2. Measure: Baseline current process performance. Validate the measurement system (MSA — Measurement System Analysis). Collect baseline DPMO, Cp/Cpk, and key input data. Output: Validated baseline metrics.
  3. Analyse: Identify root causes of defects and variation. Tools: fishbone diagrams (Ishikawa), hypothesis testing, regression analysis, ANOVA, FMEA. Output: Quantified, validated root causes.
  4. Improve: Design and verify the solution. Tools: Design of Experiments (DOE), piloting, simulation. Output: Validated improvement solution with demonstrated capability gain.
  5. Control: Implement sustained controls to prevent regression. Tools: control charts (SPC), control plans, standard operating procedures, mistake-proofing (poka-yoke). Output: Control plan and handover to process owner.

Six Sigma's primary metric: DPMO and Process Capability

Six Sigma measures success through defect rates and statistical process capability. Key metrics:

Lean vs Six Sigma: Full Comparison

Dimension Lean Six Sigma
Origin Toyota Production System (Japan, 1950s–70s); codified by Womack & Jones (1990s) Motorola (1980s); popularised by GE under Jack Welch (1990s)
Primary target Waste (non-value-adding activities) Variation and defects (process inconsistency)
Core question Where is value not being created? What can be eliminated? Why does this process produce defects? What causes variation?
Problem-solving cycle PDCA (Plan-Do-Check-Act) / Kaizen events DMAIC (Define-Measure-Analyse-Improve-Control)
Analytical approach Process observation, waste mapping, flow analysis (often visual) Statistical analysis: hypothesis testing, regression, DoE, SPC, MSA
Primary metrics Lead time, cycle time, flow efficiency, inventory turns, OEE DPMO, sigma level, Cp/Cpk, defect rate, process yield
Project duration Kaizen events: 3–5 days; VSM + implementation: weeks to months DMAIC projects: typically 3–6 months (rigorous data collection required)
Statistical depth Low–moderate (Lean tools are largely operational, not statistical) High (hypothesis testing, regression, DoE, SPC are core tools)
Change model Incremental, continuous (kaizen); team-based, on the shop floor Project-based, structured; led by trained Green/Black Belt specialists
Best problems to solve Long lead times, excess inventory, process bottlenecks, unnecessary steps, poor flow High defect rates, unexplained process variation, quality escapes, inconsistent output
Limitation Does not address root-cause analysis of defects and variation rigorously Does not systematically address waste that is not a defect; can be slow for simple improvements
Cultural model Everyone participates in continuous improvement; flat, team-driven Specialist hierarchy (Yellow / Green / Black / Master Black Belt); project-led

DMAIC vs PDCA

The two most widely used structured improvement cycles are DMAIC (Six Sigma) and PDCA (Lean / Deming). Understanding their differences helps choose the right approach for a specific improvement problem.

PDCA (Lean) DMAIC (Six Sigma)
Plan: Identify the problem; hypothesize a solution; plan the test Define: Scope the project; identify CTQs; build the charter; establish the business case
Do: Implement the solution on a small scale / pilot Measure: Baseline current performance; validate measurement system; collect data
Check: Evaluate results vs the hypothesis; measure improvement Analyse: Identify and validate root causes statistically
Act: Standardise if successful; adjust and repeat if not Improve: Design, test, and implement the solution
Control: Implement control charts, SOPs, and monitoring to sustain gains

Key differences in use

Core Tools Comparison

Category Lean Tools Six Sigma Tools
Problem identification Value Stream Mapping (VSM); Gemba walk; waste walk; spaghetti diagram SIPOC; CTQ tree; Voice of Customer (VOC); project charter; Pareto chart
Root cause analysis 5 Whys; fishbone (Ishikawa); process observation Fishbone; hypothesis testing (t-test, ANOVA, chi-square); regression analysis; FMEA
Process measurement Takt time; cycle time; OEE (Overall Equipment Effectiveness); lead time measurement Measurement System Analysis (MSA / Gauge R&R); process capability (Cp/Cpk); run charts; control charts (SPC)
Flow and layout Cellular manufacturing; one-piece flow; kanban; SMED; line balancing Process mapping; flow analysis (often within the Analyse phase); simulation
Workplace organisation 5S (Sort, Set, Shine, Standardise, Sustain); visual management; andon systems Standardised work documents; SOPs for the Control phase; mistake-proofing (poka-yoke)
Improvement design Future state VSM; kaizen event; standard work Design of Experiments (DOE); solution prioritisation matrix; piloting and validation
Sustaining improvements Standardised work; visual management; daily management systems Statistical Process Control (SPC) charts; control plans; reaction plans; process owner handover
Scheduling / production Heijunka (production levelling); pull scheduling; drum-buffer-rope; supermarkets Not primarily a scheduling methodology (scheduling is a Lean/operations domain)

Lean Six Sigma: The Integrated Approach

Lean Six Sigma (LSS) combines the waste elimination philosophy and operational toolkit of Lean with the statistical problem-solving rigour of Six Sigma. The integration was driven by the practical observation that:

How Lean and Six Sigma complement each other

Lean asks: "Are we doing the right steps? Are there steps we should eliminate?"
Six Sigma asks: "Are we doing the remaining steps correctly, consistently?"
Lean Six Sigma asks both simultaneously.

The LSS DMAIC with Lean tools embedded

In practice, Lean Six Sigma projects use the DMAIC structure but integrate Lean tools at each phase:

When LSS is the right choice

Lean Six Sigma is appropriate when improvement problems have both a waste dimension (process is slow, has unnecessary steps) and a quality dimension (output variability or defect rate is unacceptable). In supply chain, most significant improvement opportunities fall into this category: a procurement process that is slow (Lean) and produces purchasing errors (Six Sigma); a warehouse operation with excessive travel time (Lean) and high mispick rates (Six Sigma); a planning process with unnecessary manual steps (Lean) and poor forecast accuracy (Six Sigma).

When to Use Each Methodology

Problem Type Recommended Approach Rationale
Warehouse with excessive operator travel time and high inventory inaccuracy Lean (slotting, VSM) Travel time is a waste problem; inaccuracy from missing scan discipline is a waste/standard work problem — both are Lean-addressable without statistical depth
Production line with high scrap rate — root cause unknown and debated Six Sigma (DMAIC) Unknown root cause in a complex process requires statistical investigation: hypothesis testing, process capability analysis, DoE
Order-to-delivery lead time 18 days vs competitor's 5 days Lean (VSM, flow redesign) Long lead time is a classic flow and waste problem — VSM will identify batching delays, approvals, waiting, and handoffs to eliminate
Customer complaints about product weight variation in packaged food Six Sigma Weight variation is a direct statistical process control (SPC) problem — Cp/Cpk analysis and DoE on fill machine parameters are appropriate
Procurement process slow (15-day average PO cycle) AND high error rate on POs Lean Six Sigma Both flow (Lean) and accuracy (Six Sigma) dimensions — LSS addresses both simultaneously
Supplier delivering on-time only 65% of the time Six Sigma (DMAIC with supplier) On-time delivery variation requires root cause analysis of what causes late deliveries — data-driven supplier DMAIC project
5S implementation in a distribution centre Lean (Kaizen / PDCA) Straightforward waste and visual management improvement — statistics not needed; kaizen event appropriate
Transaction error rate in invoice processing — financial and regulatory impact Six Sigma Defect reduction with financial stakes and compliance requirements — requires rigorous DMAIC with Pareto analysis of error types and root causes
End-to-end supply chain transformation Lean Six Sigma programme Systemic transformation benefits from both waste elimination (Lean) and variation reduction (Six Sigma) applied simultaneously across all process layers

Certification Levels

Both Lean and Six Sigma have established certification levels that signal the depth of practitioner knowledge and project leadership capability. The most widely recognised body for Lean Six Sigma certification is ASQ (American Society for Quality), though many corporations operate internal belt programmes.

Level Scope Typical Role Project Complexity
White Belt Basic awareness of Lean Six Sigma concepts Team member; supports improvement projects No project leadership required
Yellow Belt Foundational tools and DMAIC overview Participates in projects; may lead small kaizen events Simple, local scope improvements
Green Belt Full DMAIC capability; intermediate statistical tools Part-time project leader; supports Black Belt projects Moderate complexity; single function or process
Black Belt Advanced statistical tools (DoE, multivariate analysis, FMEA); full project leadership Full-time improvement specialist; leads complex DMAIC projects; coaches Green Belts Cross-functional, significant financial impact
Master Black Belt Expert-level statistics; programme design; change management Programme leader; trains and mentors Black Belts; drives improvement culture at enterprise level Strategic, enterprise-wide improvement programmes

Industry Examples

Toyota — Lean in Manufacturing

Toyota's success with Lean is rooted in two core principles: jidoka (stop the line when a defect occurs — never pass a defect forward) and just-in-time (produce only what is needed, when it is needed, in the quantity needed). These principles, supported by kanban, standardised work, and heijunka, reduced Toyota's inventory levels dramatically compared to American car manufacturers while simultaneously improving quality — disproving the assumed trade-off between low cost and high quality that defined Western manufacturing thinking through the 1970s and 80s.

Motorola and GE — Six Sigma in Quality

Motorola achieved a 10-fold improvement in product quality over 5 years following Six Sigma adoption in 1987, saving approximately $16 billion by 1994. When Jack Welch mandated Six Sigma across GE in 1995, the programme generated an estimated $12 billion in savings in its first five years. GE's application extended beyond manufacturing to financial services (GE Capital), healthcare (GE Medical Systems), and back-office operations — demonstrating Six Sigma's applicability beyond the production floor.

Amazon — Lean in Fulfilment

Amazon's fulfilment network applies Lean principles intensively: continuous flow in fulfilment centres, takt-time-driven pick processes, real-time andon cord equivalents for system failures, kaizen events for process optimisation, and an obsessive focus on eliminating the 8 wastes from the order pick-pack-ship process. Amazon's robotics integration (through Kiva Systems / Amazon Robotics) is an extension of the Lean principle of eliminating operator motion waste — rather than having operators walk to shelves, shelves are brought to stationary operators.

Healthcare — Lean Six Sigma in Clinical Operations

Hospitals have increasingly adopted Lean Six Sigma to address patient flow (Lean) and clinical error reduction (Six Sigma) simultaneously. Virginia Mason Medical Center's adoption of the Toyota Production System ("Virginia Mason Production System") reduced waiting times, eliminated high-risk inventory, and cut costs significantly. Lean addressed flow and waste in patient pathways; Six Sigma addressed variation in clinical outcomes and medication errors — a textbook LSS combination.

Frequently Asked Questions

What is the difference between Lean and Six Sigma?

Lean targets waste — any activity consuming time, labour, inventory, or capital without creating customer value. Its origin is the Toyota Production System; its tools are operational (VSM, kanban, 5S, SMED, heijunka) and its primary metric is lead time and flow efficiency. Six Sigma targets variation and defects — statistically reducing process inconsistency to fewer than 3.4 defects per million opportunities. Its origin is Motorola's quality programme; its tools are statistical (DMAIC, hypothesis testing, DoE, SPC, Cp/Cpk) and its primary metric is DPMO and process capability. Both are essential; neither is complete without the other for most real improvement challenges.

What is DMAIC in Six Sigma?

DMAIC is Six Sigma's five-phase project framework: Define (scope the problem, identify customers and CTQ requirements), Measure (baseline current performance, validate the measurement system), Analyse (identify and statistically validate root causes of defects and variation), Improve (design, test, and implement the solution), and Control (install SPC charts, control plans, and SOPs to sustain the gains). DMAIC ensures that solutions are evidence-based — changes are not implemented until root causes are statistically confirmed and improvements validated through piloting, preventing the common error of solving the perceived problem rather than the actual one.

What is Lean Six Sigma?

Lean Six Sigma integrates the waste elimination focus and operational tools of Lean with the statistical rigour and DMAIC framework of Six Sigma. In practice, LSS projects use DMAIC as the project structure but incorporate Lean tools (VSM, flow analysis, 5S, kanban) alongside Six Sigma tools (SPC, DoE, hypothesis testing) to tackle improvement problems that have both a waste dimension and a quality/variation dimension simultaneously. LSS is now the dominant continuous improvement framework across manufacturing, healthcare, financial services, and logistics.

What does Six Sigma level mean statistically?

A Six Sigma process produces no more than 3.4 defects per million opportunities (DPMO). Statistically, this requires that the specification limits be 6 standard deviations from the process mean — meaning the probability of any individual output falling outside the acceptable range is 3.4 per million (accounting for the 1.5-sigma long-run mean shift that Motorola empirically observed in industrial processes). Practically: 99.99966% of outputs are within specification. A 3-sigma process, by contrast, produces 66,807 DPMO — a defect rate that seems low but represents significant material waste and customer risk at scale.

Should a supply chain professional learn Lean or Six Sigma first?

For supply chain professionals, Lean is typically the more immediately applicable starting point. The 8 wastes, value stream mapping, and flow analysis directly address the most visible supply chain problems: long lead times, excess inventory, unnecessary steps, and poor flow. Six Sigma statistical tools become critical when you encounter repeating quality failures (supplier defects, order errors, forecast inaccuracy) whose root causes are not surface-obvious. Lean Six Sigma Green Belt certification provides a practical foundation in both — and is the most marketable continuous improvement credential for supply chain and operations roles.