pdca-improvement

Solid

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.

AI & Automation 36 stars 16 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%
52
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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...

Details

Author
RBraga01
Repository
RBraga01/Quality-Engineering-Skills
Created
3 months ago
Last Updated
yesterday
Language
JavaScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

pdca-cycle

Use when executing iterative tasks, continuous improvement, quality assurance, process optimization, or when user asks to 'apply PDCA', 'iterate and improve', 'continuous improvement cycle', 'plan-do-check-act'.

5 Updated 2 months ago
konglong87
AI & Automation Solid

dmaic

DMAIC (Define-Measure-Analyze-Improve-Control) — Six Sigma structured problem-solving for chronic, data-driven quality improvement projects. Use when a problem recurs despite corrective actions, when a process needs systematic capability improvement, or when a customer requests a Six Sigma approach. Use 8D for reactive single-incident problems; use DMAIC for recurring systemic issues requiring statistical analysis. Covers IATF 16949 §10.1 and ISO 9001 §10.3.

36 Updated yesterday
RBraga01
Code & Development Listed

pdca-process-review

用 PDCA(Plan-Do-Check-Act,戴明循環)系統性檢視���優化任何反覆執行的流程或工作方式。當使用者要求「用 PDCA 檢視/分析/優化某個流程」「這個流程哪裡卡住、怎麼改善」「幫我做一次流程復盤」「持續改善」,或提到 PDCA、戴明循環、Deming cycle、Plan-Do-Check-Act 等詞彙時,務必觸發。也要主動用於這種情境:使用者描述一個自己反覆在做、但成效不如預期或執行起來很亂的流程(不論是研究方法執行、教學/評審工作、行政作業、專案管理、還是個人習慣),想要找出問題根源並規劃下一步調整——即使對方沒有講出「PDCA」這個詞。不限定領域,適用任何重複性流程的檢視與優化。

0 Updated 2 months ago
goingli0324