Kaizen Study Guide

📖 Core Concepts Kaizen – “continuous improvement”; involves all employees and functions, using existing resources (zero‑investment). PDCA Cycle – Deming’s loop: Plan → Do → Check → Act; the engine of Kaizen experiments. Muda (Waste) – The seven loss categories: Transport, Inventory, Motion, Waiting, Overproduction, Overprocessing, Defects. 5S – Workplace‑organizing method: Sort, Set‑in‑order, Shine, Standardize, Sustain. Genchi Genbutsu – “Go to the source”; see the real work before deciding. Five Whys – Ask “Why?” repeatedly (≈5 times) to reach the root cause. Fishbone Diagram – Visual “cause‑and‑effect” chart that maps multiple potential causes to a single problem. Kaizen Types – Point, System, Line, Cube – differing in scope and planning depth. Kaizen Blitz – Short, intensive (≈1‑week) event targeting a specific area. --- 📌 Must Remember Kaizen = incremental, employee‑driven improvement; Kaikaku = radical change. PDCA is iterative: each cycle produces a tighter, more reliable process. The 7 wastes are the primary targets for any Kaizen activity. 5S creates the visual, organized foundation needed for continuous improvement. Genchi Genbutsu ≠ “report reading”; it’s on‑site observation. Five Whys stops when the answer is a process issue, not a person‑level fault. Kaizen Blitz limits scope → faster results, but may create trade‑offs with other areas. --- 🔄 Key Processes PDCA Implementation Plan: Identify problem, set objective, choose tool (5S, 5 Whys, etc.). Do: Execute the small‑scale change (often a Point Kaizen). Check: Measure results vs. baseline (use visual control or OEE). Act: Standardize successful change, or repeat the cycle for refinement. Five Whys Root‑Cause Analysis Start with the problem statement. Ask “Why did this happen?” → answer becomes the next problem. Continue ≈5 times until the cause is a process factor, not a person. 5S Roll‑out Sort: Remove unnecessary items. Set in order: Arrange needed items for easy access. Shine: Clean and inspect work area. Standardize: Document the new layout & procedures. Sustain: Audits & daily discipline to maintain gains. Kaizen Blitz Workflow Define a narrow problem → assemble cross‑functional team → apply PDCA → capture lessons → spread to other lines (Line/Cube Kaizen). --- 🔍 Key Comparisons Point Kaizen vs. System Kaizen Point: Quick fix, little planning, isolated impact. System: Short‑term strategic plan, addresses system‑level issues. Kaizen vs. Kaikaku Kaizen: Incremental, continuous, employee‑driven. Kaikaku: Breakthrough, top‑down, large‑scale redesign. JIT vs. JIS JIT: Deliver materials when needed. JIS: Deliver in the exact sequence required by downstream processes. Fishbone Diagram vs. Five Whys Fishbone: Visual map of many possible causes. Five Whys: Linear questioning to drill down to a single root cause. --- ⚠️ Common Misunderstandings “Kaizen is only for manufacturing.” – It applies to services, logistics, admin, and any repeatable process. “If a Kaizen works, no further improvement is needed.” – Kaizen is continuous; each success becomes a new baseline for the next PDCA cycle. “Five Whys always need exactly five questions.” – Use enough “Why?”s to reach a process‑level cause; sometimes fewer or more are appropriate. “5S is a one‑time cleanup.” – Sustainability (the “S” at the end) requires ongoing audits and discipline. --- 🧠 Mental Models / Intuition Small‑Batch, Fast‑Feedback Loop – Treat each Kaizen as a rapid experiment: tiny change → immediate measurement → quick learning. Visual Management – If you can’t see a problem, you can’t fix it. Use 5S, visual control, and boards to make status obvious. Chain Reaction – A point improvement can ripple through the supply chain (Cube Kaizen) – think of a domino effect, not an isolated island. --- 🚩 Exceptions & Edge Cases Point Kaizen trade‑off – Fixing a bottleneck on one line may overload downstream work; always check system impact. Kaizen Blitz scope – Over‑broad scopes dilute focus; keep the target narrow (e.g., one workstation, one part). 5S in highly variable environments – Excessive sorting may hinder flexibility; balance standardization with needed variability. --- 📍 When to Use Which Use Point Kaizen when the issue is obvious, localized, and low risk (e.g., a broken tool). Use System Kaizen for recurring problems that cross multiple stations or departments. Deploy 5S as the foundation before any other Kaizen activity to ensure a clean, organized workspace. Apply Five Whys when you have a specific defect and need a quick root cause. Choose Fishbone when many potential causes are suspected and you need a visual brainstorm. Select Kaizen Blitz for a time‑boxed, high‑visibility improvement drive (e.g., new product launch). --- 👀 Patterns to Recognize Recurring waste type (e.g., excess motion) → signals a 5S opportunity. Repeated defects on a single workstation → likely a Point Kaizen or Five Whys case. Downstream delays after upstream speed‑up → indicates a System Kaizen need to balance flow. Visible clutter or disorganized tools → classic sign of 5S neglect. --- 🗂️ Exam Traps Confusing Kaizen with Kaikaku – Remember: incremental vs. radical. Choosing Fishbone when only one root cause exists – Five Whys is more efficient. Assuming JIT eliminates all inventory – JIT reduces excess inventory but still requires some safety stock. Believing a successful Kaizen eliminates the need for further PDCA – Each improvement creates a new baseline that must be re‑checked. Selecting Kaizen Blitz for a complex, cross‑functional problem – The scope may be too large; a System Kaizen is safer. ---