Lean / Value-Stream Mapping & Six Sigma (DMAIC)

Overview

Lean is derived from the Toyota Production System developed by Taiichi Ohno at Toyota (see also Root-Cause Tools). The term "Lean" was coined by John Krafcik in a 1988 MIT Sloan Management Review article and popularized by James Womack, Daniel Jones, and Daniel Roos in The Machine That Changed the World (1990, Rawson Associates), a landmark study of automotive manufacturing. Womack and Jones elaborated the principles in Lean Thinking (1996, Simon & Schuster). The Lean philosophy centers on maximizing customer value while systematically eliminating all waste — any activity that consumes resources without creating value the customer would pay for.

The eight types of waste in Lean (often remembered as DOWNTIME):

• Defects — work that requires rework or correction
• Overproduction — making more than is needed, sooner than needed
• Waiting — idle time while waiting for the next step
• Non-utilized talent — underusing people's skills and knowledge
• Transportation — unnecessary movement of materials or information
• Inventory — excess materials or work-in-progress beyond what's needed now
• Motion — unnecessary movement by people
• Extra-processing — doing more work or using more complex processes than required

Value Stream Mapping (VSM) is a Lean tool for visualizing the complete flow of materials and information required to deliver a product or service to a customer. Developed at Toyota; brought to Western audiences by Mike Rother and John Shook in Learning to See (1998, Lean Enterprise Institute) — arguably the most influential Lean workbook published. A VSM maps both the current state (how things actually work today) and the future state (how they should work after improvement), making waste and inefficiency visible so it can be targeted.

Six Sigma was developed at Motorola in 1986, credited principally to Bill Smith (an engineer who identified the link between field failure rates and factory defect rates) and championed by CEO Bob Galvin. Mikel Harry at Motorola codified the statistical methodology. Jack Welch made Six Sigma globally famous by deploying it as a central management discipline at GE in the 1990s, saving an estimated $12 billion in its first five years.

DMAIC is Six Sigma's five-phase problem-solving cycle:

• Define — the problem, the project scope, the customer requirements, and the team
• Measure — current process performance with data; quantify the size of the problem
• Analyze — identify root causes using statistical and analytical tools
• Improve — implement and verify solutions that address root causes
• Control — sustain improvements with monitoring, documentation, and control plans so the process doesn't revert

Lean Six Sigma combines the waste-elimination focus of Lean (speed and flow) with the statistical rigor of Six Sigma (defect and variation reduction). The combination is now widely deployed in manufacturing, healthcare, financial services, and supply chain operations.

When to Use It

When the client's problem is operational: process bottlenecks, quality failures, cycle time, cost per transaction, or error rates. Lean / VSM is most powerful for diagnosing and redesigning processes that have accumulated waste over time. DMAIC is most powerful when the problem is a measurable defect or variation that can be quantified and root-caused statistically. Both are strongest when the improvement work will be sustained internally — they're methodologies for building internal capability, not one-time consulting deliverables.

How It Works

Value Stream Mapping

1. Define the product family — what specific product, service, or customer journey is being mapped?
2. Draw the current-state map — walk the process from customer demand back to supply. Document each step: cycle time, wait time, inventory levels, error rates. Include information flows as well as physical/operational flows.
3. Identify waste — on the current-state map, mark the waste: where is inventory building up? Where is waiting time longest? Where are defects or rework concentrated?
4. Design the future-state map — what does the process look like when waste is removed and flow is continuous? Where can steps be combined, eliminated, or automated?
5. Build the improvement plan — close the gap between current and future state through a series of targeted kaizen (improvement) events.

DMAIC

1. Define: write a problem statement, define the scope, identify the customer and their requirements (CTQs — Critical to Quality), charter the team.
2. Measure: select the key metrics, collect baseline data, establish the current process capability (sigma level, defect rate, cycle time).
3. Analyze: use tools (root cause analysis, regression, hypothesis testing, fishbone diagrams) to identify the sources of variation and defects.
4. Improve: develop potential solutions, pilot the best option, verify the improvement with data.
5. Control: implement a control plan — statistical process control charts, standard work documentation, monitoring dashboards — to sustain the improvement.

Common Pitfalls

• Lean as headcount reduction — the goal is to redeploy capacity to value-creating work, not to eliminate jobs; framing it as cost-cutting destroys the employee engagement that makes Lean sustainable
• Six Sigma without Lean — reducing defects without addressing flow creates highly efficient processes that still move too slowly; the combination is more powerful than either alone
• DMAIC for every problem — DMAIC is designed for recurring, measurable quality problems; for one-time strategic decisions or problems that don't have a stable process to measure, it's the wrong tool
• Skipping Control — the most commonly abbreviated phase; without a control plan, improved processes revert within months; the Control phase is what makes improvement permanent
• Top-down deployment without frontline buy-in — the people closest to the work usually know where the waste is; Lean works best when they own the improvement effort, not when it's done to them

Recommended Books

• Lean Thinking — Womack & Jones
• Learning to See — Rother & Shook
• The Lean Startup — Eric Ries