Avoiding Common PDSA Pitfalls: A Guide for Effective QI

Why This Topic Matters

Effective Quality Improvement is not about making perfect changes on the first attempt; it's about disciplined learning and adaptation. PDSA cycles embody this principle, allowing teams to test hypotheses, gather data, and make informed decisions about whether to adopt, adapt, or abandon a change idea. Without a robust understanding and application of PDSA, QI projects can stall, deliver sub-optimal results, or even inadvertently introduce new problems.

For junior doctors, trainees, and QI leads, mastering the PDSA cycle is fundamental. It equips you with the skills to systematically improve patient care, streamline processes, and contribute to a culture of continuous learning within your department or organisation. Avoiding common mistakes ensures that your efforts are efficient and genuinely contribute to positive outcomes.

Practical Explanation: The Stages of PDSA and Common Pitfalls

The PDSA cycle is iterative and cyclical, moving through four interconnected stages:

1. Plan (P) – The Foundation of Your Test

This stage involves defining the objective of your test, making predictions about the outcome, and outlining the specific steps for implementing the change and collecting data.

Common Pitfalls:

• Vague Objectives: A poorly defined aim or objective makes it hard to know what you're testing or what success looks like. Without clarity, the 'Study' phase becomes difficult.
• Lack of Specificity in the Plan: Not detailing who will do what, where, and when. This leads to inconsistent implementation and difficulty replicating the test.
• Poor Prediction: Skipping the prediction step. Predicting helps articulate your hypothesis and forces you to consider the 'why' behind the change. It also creates a benchmark for the 'Study' phase.
• Inadequate Measurement Plan: Not deciding beforehand what data to collect, how to collect it, or who is responsible. This can result in missing crucial information needed to understand the impact of the change.
• Too Large a Scale: Attempting to test a change on too many patients, staff, or settings at once. The essence of PDSA is small-scale testing.

2. Do (D) – Implementing the Change

This stage involves carrying out the planned change, collecting the data, and observing the process and outcomes.

Common Pitfalls:

• Deviation from the Plan: Implementing the change differently from how it was planned, without documenting the deviation. This makes it impossible to link observed outcomes back to the intended intervention.
• Not Collecting Data as Planned: Forgetting to collect some data points, collecting insufficient data, or collecting it inconsistently. This compromises the 'Study' phase.
• Lack of Documentation: Not noting down problems encountered, unexpected observations, or even just the date/time of the test. These details are vital for learning.

3. Study (S) – Analysing and Interpreting Results

This stage involves analysing the collected data, comparing it against predictions, and summarising what was learned.

Common Pitfalls:

• Skipping Data Analysis: Moving straight from 'Do' to 'Act' without properly reviewing the data. This means missing valuable insights and potential unintended consequences.
• Ignoring Predictions: Failing to compare actual results against initial predictions. This comparison is key to understanding your hypothesis and refining your theory of change.
• Misinterpreting Results: Drawing conclusions that are not supported by the data, or attributing changes to the wrong causes.
• Not Documenting Learning: Failing to clearly articulate what was learned – what worked, what didn't, and why.

4. Act (A) – Refining and Moving Forward

Based on the learning from the 'Study' phase, this stage involves deciding what to do next: adopt, adapt, or abandon the change, and then planning the next PDSA cycle.

Common Pitfalls:

• Jumping to Scale-Up: Immediately adopting a change widely after a single small-scale test, without further refinement or testing in varied conditions. This can lead to unexpected failures.
• Abandoning Too Early: Giving up on a change idea after one unsuccessful cycle, without understanding why it failed or considering adaptations.
• Not Planning the Next Cycle: Failing to use the learning to inform the next steps, whether that's refining the existing change, testing a new one, or spreading successful changes.
• Lack of Standardisation: If a change is successful and ready for wider adoption, not developing a clear plan for standardisation and embedding it into routine practice.

Step-by-Step Approach to Better PDSA Cycles

To mitigate these pitfalls, adopt a disciplined and thoughtful approach to each stage:

1. Start Small, Think Big: For your first cycle, identify the smallest possible test of your change. This could be one patient, one shift, or one clinician. The aim is rapid learning, not immediate perfection.
2. Define Your Purpose Clearly: Before 'Plan', articulate the specific question your PDSA cycle aims to answer. What change are you testing? What do you expect to happen? What data will tell you if it worked?
3. Use a PDSA Worksheet: Standardising your approach with a dedicated worksheet or template ensures all key elements are considered and documented. This includes objective, predictions, specific steps, data collection plan, and a section for study and action.
4. Embrace Iteration: Understand that QI is rarely a linear process. Expect to conduct multiple PDSA cycles, each building on the last. Each cycle should refine your understanding and the change itself.
5. Engage Frontline Staff: Involve those who will be doing the work in the planning and execution. Their insights are invaluable for identifying practical challenges and solutions.
6. Schedule Dedicated 'Study' Time: Protect time to review your data and discuss findings as a team. This isn't an afterthought; it's the core of the learning process.
7. Document Your Learning: Keep a clear log of what was learned in each cycle, including both successes and failures. This builds an organisational memory and prevents repeating mistakes.

Example in Clinical Practice: Improving VTE Prophylaxis Documentation

Scenario: A surgical ward team identifies inconsistent documentation of Venous Thromboembolism (VTE) prophylaxis in patient notes, leading to potential safety risks.

Initial Aim: To improve VTE prophylaxis documentation completeness from 70% to 95% within 3 months.

Common Pitfall (and correction):

• Mistake: Team immediately tries to roll out a new, more complex documentation form for all new admissions across the entire ward.
• Correction (Small-Scale PDSA):
  • P (Plan): Objective: Test if a simple, pre-printed sticker for VTE prophylaxis documentation (with tick boxes for assessment and prescription) improves compliance. Prediction: Documentation will improve for selected patients. Specifics: Test on 3 patients admitted during morning rounds on a single day. Nurse in charge will use the sticker; junior doctor will review it. Data: check 3 patients' notes for sticker use and completeness. Baseline: 70%.
  • D (Do): Nurse uses sticker for 3 patients. Junior doctor reviews notes. One patient's sticker isn't fully completed. Note: junior doctor found sticker easy to use, but forgot to complete one section.
  • S (Study): Data shows 2/3 stickers completed correctly (66%). Not an improvement from baseline. Observation: junior doctor forgot to tick 'patient educated'. Learning: The sticker is easy to use, but a prompt or quick reminder is needed for the education aspect.
  • A (Act): Decision: Adapt the sticker. Add a prominent 'Educated?' box with a signature line. Plan next PDSA cycle: Test the revised sticker on 5 patients, this time with a brief verbal reminder during handover. Then plan further cycles to test with different staff, on more patients, and eventually on different shifts.

This iterative approach, starting small and learning from each cycle, prevents a large-scale failure and builds a more robust solution.

How Lazomis Can Help

Lazomis offers tools that can streamline and enhance your PDSA cycle management:

• QI Project Setup: Structure your project from the outset, clearly defining aims, measures, and initial change ideas, ensuring you begin with a robust 'Plan'.
• PDSA Cycle Templates: Access standardised, editable templates to guide your planning, execution, study, and action phases, helping you avoid missing critical steps and ensuring consistent documentation across your team.
• Data Collection & Visualisation: Easily track and visualise your chosen metrics before, during, and after your tests. This supports the 'Do' and 'Study' phases by providing clear, real-time feedback on the impact of your changes, allowing for rapid interpretation of results.
• Documentation and Learning Log: Centralise your PDSA cycle documentation, observations, and learning. This creates a shared knowledge base, making it easier to see the progression of your improvements and inform future 'Act' decisions.

This resource supports, but does not replace, clinical judgement. Local policy, formulary and specialist advice should be followed.

Key Takeaways