← ClaudeAtlas

pdca-improvementlisted

Run a PDCA cycle, Plan Do Check Act improvement cycle, or structured improvement project. Guides through problem analysis, piloting, verification, and standardisation. Distinguished from 8D: PDCA is for proactive improvement initiatives, 8D is for reactive defect response. Use for process optimisation, lessons learned implementation, and quality objectives.
RBraga01/Quality-Engineering-Skills · ★ 3 · AI & Automation · score 79
Install: claude install-skill RBraga01/Quality-Engineering-Skills
# PDCA Improvement Cycle ## When to use Use PDCA for: - Continuous improvement initiatives (not problem reactions — use 8D for that) - Implementing a process optimisation with uncertain outcome - Piloting a change before full deployment - Structured improvement from lessons learned or audit findings - Meeting a quality objective that requires a new approach **Key distinction from 8D:** PDCA is proactive or slow-burn improvement. 8D is reactive to a specific defect or failure. Both use root cause analysis, but PDCA has a broader scope and a pilot step before full deployment. **When PDCA is used for corrective action** (e.g., responding to an audit finding or recurring NC): a [Corrective Action Request (CAR)](../../documentation/car-corrective-action/) must also be opened to document root cause, actions, and VOE per ISO 9001 §10.2. PDCA is the improvement methodology; the CAR is the governance record. ## Prerequisites - Improvement goal defined (with target metric) - Baseline data available (current performance) - Owner and resources assigned --- ## Workflow ### PLAN — Analyse and define the approach 1. **Define the current situation** - What is the problem or improvement opportunity? - What is the current measured performance? (baseline) - What is the target? (SMART: Specific, Measurable, Achievable, Relevant, Time-bound) 2. **Analyse root cause** - Use [Fishbone](../fishbone-analysis/) and [5-Why](../5why-root-cause/) to understand why current performan