22.1 PDSA, Lean & Six Sigma

PDSA, Lean & Six Sigma

Quick Answer: Healthcare executives improve performance with disciplined methods: PDSA tests changes iteratively; Lean removes waste and improves flow; Six Sigma reduces harmful variation and defects. FACHE leaders must know when each method fits, how to resource teams, and how to hardwire gains into operations—not merely sponsor a poster campaign.

Quality and Performance Improvement on the Board of Governors exam treats performance improvement (PI) as a management system. Scenarios test whether a COO launches an enterprise redesign without a pilot, whether “Lean” is misused as headcount cuts alone, or whether Six Sigma projects ignore clinical ownership. Master the tools, their logic, and executive responsibilities.

Why Method Matters for Executives

Healthcare is complex: multiple professions, handoffs, regulatory constraints, and life-critical processes. Gut-feel change often fails or creates new risks. Structured methods give leaders a shared language for:

• Framing a measurable aim
• Understanding current process and root causes
• Designing and testing interventions
• Distinguishing improvement from noise
• Spreading and standardizing what works

Boards expect a quality program that produces reliable results over time—lower harm, better outcomes, smoother throughput, and better experience—while respecting workforce capacity. PI methods are how strategy becomes operations.

PDSA: The Learning Cycle

PDSA (Plan–Do–Study–Act), also called the Deming or Shewhart cycle, is the foundational test-and-learn method used in continuous quality improvement (CQI) and the Model for Improvement (IHI).

Key managerial points:

1. Small tests of change — pilot on one unit, one shift, or a limited patient cohort before system-wide policy.
2. Multiple rapid cycles beat one large “big bang” rollouts when uncertainty is high.
3. Study is not optional PR; without measurement, teams cannot know whether the change worked.
4. Act includes updating standard work, training, EHR prompts, and accountability—not only declaring success.

PDSA pairs with three Model for Improvement questions: What are we trying to accomplish? How will we know a change is an improvement? What change can we make that will result in improvement? FACHE candidates should recognize that aim + measures + change ideas + PDSA is the classic package.

Lean: Value, Flow, and Waste

Lean (Toyota Production System adapted to healthcare) optimizes value from the patient’s perspective and removes waste (muda) that does not contribute to that value. Lean is not primarily a cost-cutting brand name; cost and capacity often improve as by-products of better flow and fewer defects.

Classic waste categories leaders should recognize:

• Overproduction — unnecessary tests, duplicate documentation
• Waiting — patients or staff idle for beds, results, or decisions
• Transport — unnecessary movement of patients, specimens, or materials
• Overprocessing — steps that do not change outcomes (redundant forms)
• Inventory — excess supplies or “batching” that hides problems
• Motion — inefficient workplace layout
• Defects — errors, rework, infections, returns to OR
• Unused talent — front-line knowledge ignored

Core Lean tools and concepts:

• Value-stream mapping — visualize end-to-end process, delays, and handoffs
• 5S — sort, set in order, shine, standardize, sustain (workplace readiness)
• Standard work — best-known method documented and trained, not personal improvisation
• Pull / just-in-time — trigger work based on demand (e.g., bed management signals)
• Visual management — boards and cues that make abnormal conditions obvious
• Kaizen — continuous small improvements and rapid improvement events
• Respect for people — engage staff in problem-solving; avoid pure top-down edicts

Executive Lean pitfalls: using Lean only to cut FTEs without redesigning work; holding “kaizen events” without follow-through; mapping processes once and never updating standard work; and celebrating activity (number of events) instead of outcomes (throughput, harm, experience).

Six Sigma: Variation and Defects

Six Sigma targets process variation and defects. The statistical aspiration is extremely low defect rates (classically near 3.4 defects per million opportunities at six sigma quality), but healthcare leaders use the discipline—define problems clearly, measure rigorously, analyze causes, improve, control—more than a pure industrial DPMO score.

DMAIC is the project framework:

Related tools: process maps, SIPOC, failure modes and effects analysis (FMEA), control charts (statistical process control), Pareto analysis, and regression or other analytics where volume supports them. Belt structures (Green/Black Belt) and champions can help, but clinical and operational ownership matter more than titles. Six Sigma fits high-volume, measurable processes (lab turnaround, medication errors, claim denials, OR first-case starts). It is weaker when aims are purely experiential or data systems cannot support valid measurement—then simpler PDSA may be the right start.

Choosing and Combining Methods

Mature organizations integrate tools rather than fighting over brands:

• Use Lean to see waste and redesign flow
• Use Six Sigma when variation and defects dominate and data are strong
• Use PDSA as the universal engine for testing and learning inside either approach
• Use control charts and run charts to separate common-cause from special-cause variation so leaders do not overreact to noise

A practical portfolio:

Governance, Resources, and Culture

Executives make PI real by:

1. Aligning projects to strategy and safety priorities — not random pet projects
2. Protecting time for front-line participation and data support
3. Building capability — training, coaching, internal facilitators
4. Reviewing results at operations and board quality committees with measures, not anecdotes alone
5. Removing barriers — policy, IT, supply, and incentive conflicts that block standard work
6. Psychological safety — encourage reporting and experimentation without punitive response to honest learning

Linking PI to Daily Management

Projects fail when they end with a celebration and no hardwiring. Leaders should expect:

• Documented standard work and role clarity
• Process owners and escalation paths
• Embedded measures on unit boards and leadership huddles
• Audit of reliability (not only outcomes)
• Spread plan with adaptation for local context

Exam Angle

Expect questions that ask which method fits a scenario, what PDSA phase is missing, whether a leader scaled too early, or whether “Lean” was reduced to layoffs. Correct answers emphasize aim clarity, measurement, small tests, waste vs. value, variation reduction, and sustained standard work—with executive accountability for system design, not blame of single workers for system failures.