Continuous Improvement Fundamentals — Kaizen, PDCA, and Root Cause Analysis

Domain VII of the PMI-ACP exam content outline is Continuous Improvement — continuously improving the quality, effectiveness, and value of the product, the process, and the team itself. It's the smallest domain by weight, but it pulls together a cluster of named tools PMI expects you to recognize individually, not just as "the team got better at something."

Kaizen — a lean manufacturing concept that improves quality, productivity, safety, and workplace culture. The word is Japanese: kai means change, zen means good — "change for good." Kaizen is activities that continuously improve every function and involve people at every level, not just management handing down improvements from above — it's explicitly a bottom-up approach. Its basic elements are teamwork, ownership, discipline, engagement, and motivation, and it stresses small, incremental, regular improvement steps rather than one big redesign.

Plan-Do-Check-Act (PDCA / Deming cycle) — the mechanism Kaizen is actually achieved through. Plan: plan the improvement. Do: implement the plan and measure its performance. Check: measure the improvement actually obtained against the plan. Act: based on the check, take the actions needed to improve further. PDCA applies to both process improvements and product improvements, and it places business processes into a continuous feedback loop rather than a one-time fix. Agile's own Plan-Develop-Evaluate-Learn cycle is the same underlying loop, just relabeled for iterative software delivery.

Fishbone (Ishikawa) diagram — a decision-making tool used to identify the root cause of a problem or an area for improvement, organized into category "bones" (commonly hardware, environment, method, user) that branch toward the effect being investigated. Once the root cause is visible, the team can devise a process to fix or avoid it going forward.

5-Why analysis — another root-cause tool: repeatedly ask "why" (commonly five times) until the questioning reaches the actual underlying cause instead of stopping at the first symptom. Both Fishbone and 5-Why are commonly run inside a retrospective, but they're distinct named techniques in their own right — don't confuse the tool with the meeting it's typically used in.

Study focus: PMI likes to test the PDCA step names directly — "Check" means measuring the improvement obtained against the plan, not analyzing what to improve (that's Plan) and not taking corrective action (that's Act). When a question describes a recurring issue and asks which tool determines the real reason it keeps happening, Fishbone or 5-Why is the expected answer — not a retrospective by itself, which is the container the analysis happens inside.