PDSA & Quality Improvement
PDSA for FQHC Quality Improvement: A Practical Guide
How to run Plan-Do-Study-Act cycles in a health center so the work is small enough to finish and documented enough to defend.
By Jessica R. Smith, BSN · Updated · 10 min read
Why PDSA stalls in health centers
PDSA rarely fails because the model is wrong. It fails because cycles are scoped too large, ownership is diffuse, and the record of what happened lives in a slide deck that is never updated after the meeting.
The fix is unglamorous: a smaller aim, a named owner, a date, and a written decision at the end of each cycle.
Scoping an aim you can actually finish
A good aim names the population, the measure, the direction of change, and the period. It should be small enough that one person can describe the test in two sentences.
- Name the measure the cycle is meant to move
- Name one owner, not a committee
- Set a period short enough to learn something within a quarter
- Decide in advance what result would cause you to adopt, adapt, or abandon
Studying results without overclaiming
Two data points are not a trend. Looking at performance across enough periods to distinguish normal variation from a real shift keeps a team from celebrating noise or abandoning a change too early.
Write the decision down
The decision is the artifact that makes the cycle defensible later. Adopt, adapt, or abandon, with a sentence of reasoning and a date.
Connecting cycles to reporting
Cycles that reference a measure roll up cleanly into a quarterly assessment. Cycles that do not reference anything become orphan documents.
See the PDSA Cycle Manager
MeasureWise keeps each cycle's aim, owner, results, and decision together and exportable at any stage.
See the PDSA Cycle Manager