15.3 Six Sigma, Kaizen, and Root Cause Tools

15.3 Six Sigma, Kaizen, and Root Cause Tools

Quick Answer: Six Sigma uses DMAIC to reduce variation and defects with data. Kaizen delivers rapid, focused improvements—often in week-long events. 5 Whys and fishbone diagrams help teams find root causes. Planners pick the tool based on problem chronicity, scope, and whether the need is fast waste removal or deep statistical analysis.

Domain IX pairs quality methods with continuous improvement because planning performance collapses when defects, rework, and unexplained variation consume capacity. You do not need to be a black belt for CPIM, but you must know what each method is for and when a planner should sponsor or join the work.

Six Sigma and the DMAIC Roadmap

Six Sigma is a disciplined approach to reducing process variation so outputs stay within customer specifications. The name refers to a statistical capability goal (very low defect rates), but exam questions focus more on the project method than on calculating sigma levels.

The standard project roadmap is DMAIC:

How DMAIC differs from casual PDCA

PDCA and DMAIC are compatible; DMAIC is a heavier, more analytical form of improvement for chronic, high-impact problems. Use DMAIC when:

• The problem has persisted despite informal fixes.
• Variation or defect data must prove cause before spending capital or changing certified processes.
• Multiple stakeholders disagree about “the real cause.”
• The Control phase must feed formal quality systems and planning master data.

A planner’s role in DMAIC often includes providing demand/supply history, quantifying schedule impact, protecting service during Improve pilots, and ensuring Control updates MRP lead times, scrap factors, or safety-stock logic once capability is proven.

Kaizen and Kaizen Events

Kaizen means continuous, incremental improvement involving the people who do the work. Day-to-day kaizen is small ideas implemented quickly. A kaizen event (kaizen blitz) concentrates a cross-functional team on one process for a short, intense period—commonly three to five days—with authority to implement changes before the event ends.

Typical kaizen event pattern

1. Prepare — select a bounded scope, gather baseline data, arrange materials and decision-makers.
2. Map and observe — walk the process — a gemba walk, observing the actual work where it happens, time elements, identify TIMWOOD wastes.
3. Ideate and test — try layout, standard-work, or flow changes immediately.
4. Implement — install visual controls, new standard work, relocated materials.
5. Report and follow up — present results; assign a 30-day list for items that could not finish on-site.

Kaizen events excel when the process is visible, the scope is narrow (one cell, one warehouse zone, one transaction flow), and leadership will authorize real-time changes. They are weaker for enterprise IT cutovers or problems that need months of designed experiments.

Kaizen versus Six Sigma project

Planners often sponsor kaizen when schedule adherence is hurt by material presentation, staging chaos, or unclear pull rules—and sponsor DMAIC when yield variation destroys ATP promises despite “everyone knowing” different causes.

Root Cause Tool: 5 Whys

The 5 Whys technique asks “why?” repeatedly until the team reaches a root cause that can be acted on—not merely another symptom. Five is a guideline; stop when a controllable cause appears, or continue if the fifth answer is still a symptom.

Example (planning context):

1. Why were orders late? — Components were missing at release.
2. Why missing? — Receipts were delayed in inspection.
3. Why delayed? — A high percentage failed dimensional checks.
4. Why failing? — A supplier process drifted after a tooling change.
5. Why undetected? — No incoming key-characteristic control or supplier change notification.

Countermeasures then target supplier change control and verification—not merely more expedites.

When planners should use 5 Whys

• Problems are relatively linear and experts know the process.
• You need a fast structured discussion in a daily tier meeting or after an incident.
• You want to avoid stopping at the first convenient blame (“warehouse screwed up”).

Limits

5 Whys can anchor on a wrong path if the first answers are guesses. For multi-factor or highly political problems, pair it with data (Measure/Analyze) or a fishbone so alternative cause families are not ignored.

Root Cause Tool: Fishbone (Ishikawa) Diagram

A fishbone diagram organizes potential causes into categories branching from the effect (the “head”). Common manufacturing categories are the 6Ms:

Teams brainstorm causes under each bone, then use data, Pareto analysis, or tests to confirm which causes matter. Fishbone is a structuring tool—it prevents tunnel vision—not automatic proof of the root cause.

When Planners Use Each Approach

Use this decision frame on exam scenarios:

Integrating tools with planning control

Root-cause quality work that never updates the planning system creates a recurring illusion of progress. If Analyze shows average yield is 92% not 98%, MRP must reflect 92% (or the process must be Improved to 98%)—otherwise planned quantities remain fantasy. If a kaizen cuts move time into a supermarket, kanban quantities may need resizing. If DMAIC Control charts show a new stable lead time, the planning lead-time file should change after a deliberate freeze period.

Common Exam Traps

• Treating kaizen events and DMAIC as identical—duration, rigor, and problem fit differ.
• Stopping 5 Whys at a person to blame instead of a process cause.
• Using a fishbone as proof without Measure/Analyze confirmation.
• Improving a process but leaving MRP parameters, scrap factors, and safety stocks unchanged.
• Launching Six Sigma on a simple 5S housekeeping gap that a one-day kaizen could fix.

Choose the lightest tool that matches the problem’s complexity, verify causes, implement, and control the gain in both the physical process and the planning data that represent it.