Continuous Improvement Methods Cheatsheet (Lean, PDCA, 5S, RCA, Six Sigma)

At a glance

Use this cheatsheet to match common continuous improvement (CI) methods to the problem you face, follow a short template to get started, and avoid common misapplications that waste time or create resistance.

Method snapshots

• PDCA (Plan–Do–Check–Act) — Fast iterative learning cycles for testing changes. Best for process experiments, small improvements, and team learning. Typical cadence: days–weeks. Team: 1–6 people.
• 5S — Workplace organization to reduce waste and visualize problems (Sort, Set in order, Shine, Standardize, Sustain). Best for shop floor, offices, labs—any physical workspace. Cadence: one-off event + regular daily/weekly checks. Team: cross-functional or local shift team.
• Root Cause Analysis (RCA) — Structured problem solving to find causes (5 Whys, Fishbone/Ishikawa). Best for recurring defects, incidents, or service failures where causes are unclear. Cadence: hours–days. Team: small cross-functional group.
• Six Sigma (DMAIC) — Data-driven approach for reducing variation and defects at scale (Define–Measure–Analyze–Improve–Control). Best for complex, high-impact quality problems where measurement and statistics matter. Cadence: weeks–months. Team: trained practitioners (Green/Black Belts) with data support.
• Kaizen / Continuous Improvement Events — Focused workshops (half-day to a few days) to remove specific wastes and rapidly implement countermeasures. Best for flow problems and visible bottlenecks. Team: 5–12 people including process owners.

Quick selection guide

Match problem scale to method:

• If the problem is a visible flow bottleneck or workspace disorder and you want fast visible wins → 5S or Kaizen.
• If you want to test a small change quickly and learn → PDCA trial (timebox the experiment).
• If a problem recurs or caused a safety/quality incident and root causes are unclear → RCA (5 Whys + Fishbone).
• If defect rates, costs, or variation are high and you can measure the process → Six Sigma (DMAIC) with statistical analysis.

Mini-templates

Common pitfalls & how to avoid them

• Applying heavy methods to small problems: Don’t start Six Sigma when a PDCA or Kaizen would resolve it faster. Use data intensity proportional to problem scale.
• Quick fixes for systemic issues: Avoid temporary workarounds that ignore root causes. Pair RCA with countermeasures and controls.
• No owner or measure: Every experiment or project needs a visible owner, a clear metric, and a timeline.
• Skipping the people layer: Improvements fail when affected teams aren’t involved. Use cross-functional teams and gemba (go see).

Practical tips for adoption

• Timebox small experiments (PDCA cycles) and celebrate quick wins to build momentum.
• Use visual controls from 5S and simple dashboards for transparency.
• Keep Six Sigma for high-variation, high-cost problems where data can guide decisions; train or partner with statisticians when needed.
• Document RCA outputs and assign specific countermeasure owners with dates.

Next steps — a 30-minute plan

1. Pick one visible problem (waste, delay, defect).
2. Select a method from this cheatsheet that matches problem scale.
3. Run one PDCA cycle or a short Kaizen workshop; use the mini-templates above.
4. Record the results, assign follow-up, and plan the next cycle.

Want this as a team worksheet or a saved checklist your group can run and record outcomes for? Consider converting this cheatsheet into an interactive checklist and RCA template to capture and track experiments.