Quality Improvement in Social Care: The PDSA Method Explained

"Quality improvement" gets used loosely in social care — sometimes meaning whatever a service does to prepare for an inspection, sometimes meaning nothing more specific than "getting better." It's actually a defined methodology with a long track record in healthcare, and understanding it properly is different from understanding what a regulator assesses. Our guide to CQC's Single Assessment Framework covers what CQC looks for; this piece covers the separate discipline of how a service actually gets better at delivering it.

The Model for Improvement and the PDSA cycle

The most widely used quality improvement framework in health and social care is the Model for Improvement, built around small, structured tests of change called Plan-Do-Study-Act (PDSA) cycles. The method asks three questions before any change is tested: what are we trying to accomplish, how will we know a change is an improvement, and what change can we make that will result in an improvement. Only after those questions are answered does a team run a PDSA cycle — plan a small test, do it on a limited scale, study what actually happened against what was predicted, and act on what was learned, either adopting the change, adapting it, or abandoning it before trying something else.

The deliberate smallness of each cycle is the point. Rather than rolling out a new medication-administration process across an entire care home at once, a PDSA approach tests it with one shift, one unit, or one week first — making it far easier to spot problems, adjust, and build staff confidence before wider rollout. Multiple short cycles run in sequence, each building on what the last one learned, rather than one large change implemented and hoped for.

Why this is a different discipline from inspection readiness

A common confusion in care settings is treating quality improvement as synonymous with meeting CQC's quality statements or preparing evidence for an inspection. They're related but distinct: CQC's Single Assessment Framework describes what "good" looks like and how it's assessed from the outside; quality improvement methodology is the internal discipline of testing and refining how a service actually gets there. A service can have excellent policies on paper and still lack a functioning improvement process — and inspectors increasingly look for evidence of the latter specifically, not just compliant documentation.

Measurement: the part most services underinvest in

PDSA only works if "how will we know a change is an improvement" has a real answer, not a vague one. That means picking a small number of measures before testing a change, not after — falls per resident per month, medication errors per week, time from referral to first contact — and tracking them over time with a simple run chart rather than comparing two single snapshots. A single before-and-after comparison is vulnerable to normal week-to-week variation; a run chart across several weeks or months makes it possible to distinguish a genuine improvement from ordinary noise in the data. This is the piece most services skip, often because it feels like extra administrative burden on top of already-stretched staff time — but without it, "quality improvement" activity has no way of actually confirming whether anything improved.

Building improvement into a service's culture, not just its projects

Quality improvement works best as an ongoing habit distributed across frontline staff, not a project owned solely by a manager or quality lead. Services that sustain genuine improvement tend to share a few practical habits: frontline staff are involved in choosing what to test, because they see problems and workarounds a manager often doesn't; small tests are framed explicitly as safe to fail, so staff aren't discouraged from trying something that doesn't work; and successful changes are actively spread to other units or shifts rather than left to fade once the original project ends. None of this requires large resource — the PDSA method is specifically designed to work at small scale with existing staff time, which is part of why it's remained the dominant approach in resource-constrained care settings for decades.

FAQ

Is quality improvement the same thing as meeting CQC's quality statements?
No. CQC's quality statements describe the standard being assessed; quality improvement methodology is the internal process a service uses to actually get better at meeting it. Good quality improvement practice makes strong inspection evidence, but the two aren't interchangeable.

What's a PDSA cycle in simple terms?
A small, structured test of a change: Plan what you'll test and predict what will happen, Do it on a small scale, Study whether the result matched the prediction, and Act by adopting, adapting or abandoning the change before deciding what to test next.

Why test a change on one unit or shift first, rather than rolling it out everywhere?
Small-scale testing makes problems visible and cheap to fix before they affect the whole service, and it tends to build more staff buy-in than a change imposed all at once without any opportunity for early feedback.

What's the most common mistake services make with quality improvement?
Skipping proper measurement — testing a change without tracking a clear measure over time to confirm whether it actually made things better, which makes it impossible to distinguish a genuine improvement from normal variation.

Quality improvement is a learnable discipline, not an innate quality some services have and others don't, and it complements rather than replaces regulatory compliance work. Learnsignal's guide to CQC's Single Assessment Framework and our wider UK healthcare compliance training guide cover the regulatory side of the same picture. Get in touch to talk through building quality improvement capability into your team's training.