Six Sigma DMAIC vs Lean, and PDSA
Three ways to improve a process in a hospital: Six Sigma to reduce variation and defects, Lean to remove waste and speed the flow, PDSA for small, fast tests of change, with the tools each one uses.
What is Six Sigma?
Six Sigma, developed at Motorola in the 1980s, aims to make a process so consistent that defects become very rare: at the "six sigma" level, about 3.4 defects per million opportunities (a figure that allows for the conventional 1.5-sigma long-term shift). In health care a defect is anything that falls outside what the patient or the process needs: a wrong-dose error, a lost specimen, a result that arrives too late. The method relies on measurement and statistics, and on trained project leaders (often called green belts and black belts).
What are the five DMAIC phases?
- Define: the problem, the goal, the scope, who the customers are and what matters to them; usually written in a project charter. "Lab results for the emergency department take too long."
- Measure: how the process performs today, with reliable data: the baseline. "Median turnaround is 85 minutes; 30% take more than two hours."
- Analyze: find and confirm the root causes, with tools such as a fishbone diagram, the 5 whys, a Pareto chart and statistical tests. "Most delays happen between collection and arrival at the lab."
- Improve: design, test and put in place solutions that remove the causes, often with a pilot first.
- Control: keep the gains: standard procedures, training, and monitoring with control charts, so the process does not drift back.
For a process that does not exist yet, or one so broken it must be redesigned, a variant called DMADV is used: Define, Measure, Analyze, Design, Verify.
What is Lean?
Lean comes from the Toyota Production System. It looks at the process from the patient's point of view and removes waste: everything that uses time or resources without adding value. Its main tools are the value stream map (a map of every step, its time and its waiting), standard work, 5S (sort, set in order, shine, standardise, sustain) and continuous small improvements (kaizen).
Eight kinds of waste are commonly listed: the seven wastes of the Toyota Production System plus unused talent.
- Defects: errors and rework.
- Overproduction: doing more than needed, such as duplicate tests.
- Waiting: patients, staff or results waiting.
- Non-used talent: skills and ideas of staff left unused.
- Transportation: moving patients, specimens or supplies more than needed.
- Inventory: excess stock, or patients queuing.
- Motion: unnecessary movement of staff, such as walking to a distant printer.
- Extra processing: steps that add nothing, such as entering the same data twice.
What is PDSA?
PDSA (Plan, Do, Study, Act) comes from the work of Shewhart and Deming, and is at the centre of the Institute for Healthcare Improvement's Model for Improvement. Plan a small change and predict what will happen; do it, often with one clinician or for one day; study the results against the prediction; act: adopt, adapt or abandon the change, then run the next cycle. The Model for Improvement starts with three questions: what are we trying to accomplish, how will we know that a change is an improvement, and what change can we make that will result in improvement?
Six Sigma, Lean and PDSA side by side
| Six Sigma | Lean | PDSA | |
|---|---|---|---|
| Main aim | Less variation, fewer defects | Less waste, faster flow | Learn quickly whether a change works |
| Structure | DMAIC (or DMADV) | Value stream map, then remove waste | Repeated small cycles |
| Typical tools | Statistics, control charts, root cause analysis | Value stream map, 5S, standard work, kaizen | Run charts, small tests |
| Pace | Projects of weeks to months | Events of days, and continuous improvement | Cycles of hours to weeks |
Which quality tools go with them?
- Fishbone (Ishikawa) diagram: groups possible causes by category, such as people, methods, equipment, environment.
- 5 whys: asking "why?" repeatedly until the root cause appears.
- Pareto chart: causes sorted by how often they occur, because a few causes usually explain most of the problem (the 80/20 rule).
- Run chart and control chart: a measure over time. A control chart adds limits that separate common cause variation (the normal noise of the process) from special cause variation (a signal that something changed).
- Flowchart and value stream map: the steps as they really happen.
Information systems feed all of them: timestamps in the EHR and the lab system are the raw data of turnaround, waiting and flow measures.
What do candidates get wrong?
- Getting the DMAIC order wrong. After Define and Measure comes Analyze (finding root causes), before Improve.
- Jumping to solutions. Improving before analysing fixes symptoms, not causes.
- Swapping Lean and Six Sigma. Lean targets waste and flow; Six Sigma targets variation and defects.
- Forgetting Control. Without it, the process slides back to where it was.
- Reacting to every point on a control chart. Common cause variation is normal; only special causes call for a search for what changed.
- Swapping DMAIC and DMADV. DMAIC improves an existing process; DMADV designs a new one.
Summary for revision
- Six Sigma: variation and defects; DMAIC = Define, Measure, Analyze, Improve, Control.
- DMADV: for a new process: Define, Measure, Analyze, Design, Verify.
- Lean: waste and flow; value stream map, 5S, kaizen; eight wastes.
- PDSA: plan, do, study, act, in small repeated cycles.
- Tools: fishbone, 5 whys, Pareto (80/20), run and control charts (common vs special cause).
Sources
- American Society for Quality (ASQ): Six Sigma (DMAIC, DMADV), Lean, and the basic quality tools.
- Institute for Healthcare Improvement (IHI): the Model for Improvement and the PDSA cycle.
Related free practice questions
The site files this concept under the domain Healthcare Information and Systems Management.
Try exam-style questions
A 20-question trial exam with an explanation for every option and a score per domain, drawn from 40 free questions. No payment method needed.
Start the trial examQuestions about the exam: CPHIMS guide · What is CPHIMS? · Exam cost · Eligibility · Passing score · Renewal · Exam day · How long to study · Is it worth it? · What is CAHIMS?
Concepts explained: HL7 v2 vs FHIR · Capitation vs fee-for-service · Safe Harbor vs Expert Determination · Incident vs problem vs change · Backup types, RTO and RPO · Privacy Rule vs Security Rule · CDS five rights · Lewin vs Kotter · SDLC and go-live strategies · Testing types · Earned value (SPI, CPI) · Structure, process, outcome · HIE models · Levels of interoperability · Bandwidth vs latency · EMTALA · Risk responses · RACI matrix · Build vs buy · Sunk vs opportunity cost · Data governance
The four domains: Healthcare and Technology Environments · Clinical Informatics · Healthcare Information and Systems Management · Management and Leadership
Written by Adel Moustafa, About us
Written and checked against the sources above on 22 October 2026. An independent site, not affiliated with or endorsed by HIMSS. CPHIMS® is a registered trademark of HIMSS.