Study guide
15.3 Six Sigma, Kaizen, and Root Cause Tools
APICS CPIM Certified in Planning and Inventory Management Exam
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts 1.2 ECM 9.0 Domains and Weights 1.3 How to Study for CPIM
2 Supply Chain Strategy Foundations
2.1 Supply Chains, the Environment, and Strategy 2.2 Environment Analysis and Strategic Scope 2.3 Developing and Managing Organizational Strategy 2.4 Competitive Analysis: Five Forces, Benchmarking, and Value Chain
3 Strategy Performance and Operations Choices
3.1 Performance Monitoring and KPIs 3.2 Functional and Operational Strategies 3.3 Environments, Types, and Layouts 3.4 Service Process Design and Product-Process Trade-offs
4 Sales and Operations Planning
4.1 S&OP Purpose and Process 4.2 Aggregate Demand and Supply Plans 4.3 Reconciling S&OP Plans 4.4 Portfolio, New Product Introduction, and Life-Cycle Planning in S&OP 4.5 Strategic Buffers, Bottlenecks, and Capacity-Constrained Resources
5 Plan and Manage Demand
5.1 Demand Management 5.2 Sources of Demand and Forecasting 5.3 Forecast Performance 5.4 Marketing, Promotions, and Product Management 5.5 Qualitative, Associative, and AI-Driven Forecasting
6 Master Scheduling
6.1 Creating the Master Schedule 6.2 Rough-Cut Capacity Planning and MPS Validation 6.3 Using and Maintaining the Master Schedule 6.4 Planning Bills and Two-Level Master Scheduling 6.5 NPI, DFMA, Prototype, and End-of-Life Schedules
7 MRP, CRP, and Supply Disruptions
7.1 Material Requirements Planning 7.2 CRP, Order Promising, and Final Assembly Scheduling 7.3 Changes and Supply Disruptions 7.4 Product Costing and Variance Analysis for Planners
8 External Supply Sources
8.1 Suppliers and Procurement 8.2 Purchasing and Maintenance 8.3 Supply Chain Risk Management 8.4 Sourcing Footprint and Supplier Relationship Types 8.5 Supplier Release Mechanics and Inbound Logistics
9 Sustainability and Reverse Logistics
9.1 Sustainability Strategies 9.2 Waste Hierarchy and Reverse Logistics 9.3 Sustainability Standards, Reporting, and Life-Cycle Assessment
10 Inventory Planning and Costs
10.1 Inventory Planning 10.2 Inventory Costs, Accounting, Costing, and Metrics 10.3 EOQ, Reorder Point, and Safety Stock
11 Inventory Management and Control
11.1 Inventory Management Policies 11.2 Inventory Control 11.3 Service Levels and Inventory Tradeoffs 11.4 MRO Inventory and Maintenance Planning Inputs 11.5 Traceability Standards and Off-Site Inventory
12 Detailed Schedules and PAC
12.1 Planning Detailed Schedules 12.2 Scheduling and PAC Methods 12.3 Creating Production and Service Schedules 12.4 Managing Detailed Schedules and Scheduling Materials 12.5 Sequencing Rules, Lot Splitting, and Overlapped Scheduling 12.6 Capacity Types, Safety Capacity, and Labor Scheduling 12.7 Process Batches, Transfer Batches, and Backflushing
13 Plan and Manage Distribution
13.1 Planning Distribution 13.2 Replenishment and DRP 13.3 Order Management, Trace/Track, and KPIs
14 Quality and Business Investments
14.1 Quality Systems and Tools 14.2 Capital Equipment and Facilities 14.3 Technology in Planning and Inventory 14.4 The Seven Basic and Seven New Quality Tools 14.5 SPC Charts and Variation Types 14.6 Systems Requirements, Master Data, and Emerging Technologies
15 Continuous Improvement
15.1 Continuous Improvement Overview 15.2 Lean, JIT, and the Seven Wastes 15.3 Six Sigma, Kaizen, and Root Cause Tools 15.4 TPM, SMED, Standardized Work, and Visual Management
16 Integration and Exam Readiness
16.1 Planning Hierarchy Integration 16.2 High-Yield Calculations Drill 16.3 Exam Day, Scoring, and Credential Maintenance
15.3 Six Sigma, Kaizen, and Root Cause Tools
Key Takeaways Explain This Topic AI
DMAIC (Define, Measure, Analyze, Improve, Control) structures Six Sigma projects that attack chronic variation and defect problems with data.
Kaizen events are short, focused bursts of improvement—often a week—aimed at a bounded process with immediate implementation.
5 Whys drills from symptom to root cause by repeatedly asking why; it fits relatively linear problems with engaged process experts.
Fishbone (Ishikawa) diagrams organize potential causes across categories such as methods, machines, materials, manpower, measurement, and environment.
Planners choose tools by problem type: kaizen for rapid bounded waste removal, DMAIC for stubborn variation, 5 Whys/fishbone for structured cause analysis feeding either approach.
Last updated: July 2026
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 :
Phase Purpose Planner-relevant outputs
Define Clarify the problem, customer CTQs, scope, and goals Problem statement tied to OTIF, scrap cost, or schedule loss; project charter
Measure Quantify current performance and data quality Baseline defect rate, lead-time distribution, or forecast-error stats; measurement system check
- Analyze Find root causes with data, not opinions Vital few drivers (Pareto); validated cause hypotheses
- Improve Design and pilot countermeasures Process change, poka-yoke, parameter update; pilot results
Control Lock gains and monitor Control plan, updated SOPs, planning-parameter changes, response rules if metrics drift
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
Prepare — select a bounded scope, gather baseline data, arrange materials and decision-makers.
Map and observe — walk the process — a gemba walk , observing the actual work where it happens, time elements, identify TIMWOOD wastes.
Ideate and test — try layout, standard-work, or flow changes immediately.
Implement — install visual controls, new standard work, relocated materials.
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
- Dimension Kaizen event Six Sigma DMAIC project
- Duration Days Weeks to months
- Emphasis Speed, waste, flow, engagement Data, variation, statistical rigor
- Best fit Obvious wastes, layout, standard work Chronic defects, complex multi-factor variation
- Risk if misused Superficial fixes that bounce back Analysis paralysis while the floor waits
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):
Why were orders late? — Components were missing at release.
Why missing? — Receipts were delayed in inspection.
Why delayed? — A high percentage failed dimensional checks.
Why failing? — A supplier process drifted after a tooling change.
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 :
- Category Examples relevant to planning
- Methods Unclear release rules, tribal scheduling practices
- Machines Unreliable equipment causing variable lead times
- Materials Wrong revision, poor supplier quality, inaccurate BOMs
- Manpower (People) Training gaps, tribal knowledge, absenteeism on bottleneck skills
- Measurement Bad inventory accuracy, wrong scrap factors in MRP
- Mother Nature (Environment) Humidity affecting materials; seasonal capacity loss
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:
- Situation Prefer
- Visible waste, bounded cell, leadership wants results this week Kaizen event
- Chronic defect/variation problem with disputed causes and large $ impact DMAIC Six Sigma project
- Incident review or fast drill-down in a stand-up 5 Whys
- Team needs to surface many possible cause families before prioritizing Fishbone , then verify with data
Any improvement that must stick in the planning system End with Control/Act : update standards and planning parameters
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.