Planning Effective PDSA Cycles for Quality Improvement

Why This Topic Matters

In healthcare, delivering safe, effective, and patient-centred care requires continuous improvement. PDSA cycles, originating from the work of W. Edwards Deming, provide a powerful, iterative framework for testing proposed changes on a small scale, learning from the results, and refining the approach before wider implementation. This 'small tests of change' philosophy minimises risk, maximises learning, and fosters a culture of innovation.

Without careful planning, PDSA cycles can become ad-hoc exercises, leading to missed learning opportunities, wasted effort, and an inability to reliably determine the impact of a change. Effective planning ensures clarity of purpose, appropriate data collection, and a structured approach to analysis, all of which are vital for successful QI projects within the complex NHS environment.

NHS England's drive for continuous improvement across all services underscores the importance of a robust understanding and application of QI methodologies, with PDSA cycles at its core. GIRFT (Getting It Right First Time) programmes, for example, often involve testing changes in practice before wider roll-out, aligning with the PDSA philosophy.

Practical Explanation: What is a PDSA Cycle?

At its heart, a PDSA cycle is a scientific method for learning and improvement. It involves four interconnected stages:

• Plan: Define the objective of the test, predict the outcome, and plan exactly how the test will be carried out (who, what, where, when) and what data will be collected.
• Do: Carry out the test as planned, observe what happens, and collect the data.
• Study: Analyse the data collected, compare it to your predictions, summarise what was learned, and identify unexpected issues or opportunities.
• Act: Based on what was learned, decide what to do next: adopt the change, adapt it, or abandon it. This often leads to the next PDSA cycle.

The iterative nature of PDSA means that one cycle often informs the next. Small-scale tests allow teams to rapidly learn, refine, and adapt changes based on real-world conditions, gradually scaling up successful interventions.

Common Pitfalls in PDSA Planning

Even experienced teams can encounter challenges when planning PDSA cycles. Awareness of these common pitfalls can help in designing more robust tests:

• Lack of a Clear Aim: Without a well-defined aim statement for the overall QI project, individual PDSA cycles can lack direction and purpose.
• Vague Predictions: Not clearly articulating what is expected to happen, and why, makes the 'Study' phase less impactful.
• Overly Ambitious Tests: Attempting to test too much at once, or on too large a scale, can lead to overwhelming data, difficulties in attributing effects, and increased risk.
• Insufficient Data Planning: Not deciding in advance what data to collect, who will collect it, and how it will be analysed can lead to gaps in learning.
• Skipping the 'Study' Phase: Moving directly from 'Do' to 'Act' without a formal review and analysis of the results misses the crucial learning opportunity.
• Lack of Psychological Safety: Team members may be hesitant to share failures or unexpected results if the environment isn't supportive, hindering genuine learning.
• Poor Communication: Not engaging key stakeholders or communicating the purpose and results of the cycle effectively can lead to resistance or lack of buy-in.

Step-by-Step Approach to Planning a PDSA Cycle

Effective planning transforms a theoretical concept into a practical tool for improvement. Use this framework to structure your PDSA planning:

1. Define Your Overall QI Aim and Specific Change Idea

Before planning a PDSA, ensure your overarching QI project has a clear, measurable Aim Statement (e.g., 'Reduce unnecessary inpatient bed days for elective surgery patients by 15% within 6 months'). Identify the specific Change Idea you want to test that is hypothesised to help achieve this aim (e.g., 'Introduce a pre-operative patient education pathway').

2. Formulate the PDSA Objective and Prediction

Each PDSA cycle should have a specific objective directly related to the change idea. Ask: What do we want to learn or prove with this specific test?

• Objective: State clearly what you intend to achieve with this PDSA. (e.g., 'To determine if the new patient education leaflet is understood by 3 out of 5 patients in clinic A').
• Prediction: Based on your knowledge and hypotheses, what do you expect to happen, and why? This helps frame your learning. (e.g., 'We predict that 3 out of 5 patients will correctly recall the key discharge messages after reading the leaflet, because the language has been simplified and reviewed by our patient group.').

3. Plan the 'Do' Phase: How will the Test be Carried Out?

This is where you detail the logistics of your test. Be specific:

• Who: Who will be involved in carrying out the test? (e.g., Clinical Nurse Specialist, 2 junior doctors).
• What: Exactly what steps will be taken? (e.g., 'CNS will give leaflet to first 5 patients in clinic on Monday, then ask 3 specific questions later that day.'). What resources are needed?
• Where: Where will the test take place? (e.g., 'Outpatient Clinic A').
• When: When will the test happen? Set clear start and end dates/times. (e.g., 'Monday 9am-12pm, 15th October').
• Duration: How long will this specific test run? Keep it short initially.

4. Plan the 'Study' Phase: Data Collection and Analysis

Crucial for learning, this step outlines what information you need to gather and how you'll make sense of it.

• What data to collect: What objective measures will tell you if your prediction was accurate and if the change had the intended effect? (e.g., 'Number of patients correctly answering questions', 'Time taken to deliver leaflet', 'Patient feedback on clarity').
• How will data be collected: Specify the method. (e.g., 'Tally sheet', 'Short questionnaire', 'Observation checklist').
• Who will collect the data: Assign responsibility.
• When and how will data be analysed: Plan a meeting or dedicated time for the team to review the data together. Visual tools like run charts can be helpful.

5. Plan the 'Act' Phase: Next Steps

Anticipate the potential outcomes and subsequent actions. This demonstrates foresight and continuous improvement thinking.

• If successful: How will you scale up the change, or what's the next small test? (e.g., 'Test with 10 patients across two clinics').
• If partially successful/unexpected results: How will you adapt the change? (e.g., 'Revise leaflet based on feedback, re-test with different patient group').
• If unsuccessful: What did you learn? What will you abandon, or what new idea will you test? (e.g., 'Abandon leaflet, explore digital information delivery').

6. Document Your Plan

Use a simple PDSA worksheet or template to capture all the above information. This serves as a clear record for your team and for future cycles.

Example in Clinical Practice

Overall QI Aim: To reduce the average waiting time for patients to see a doctor in the Medical Assessment Unit (MAU) by 20% within 3 months.

Change Idea: Introducing a 'red flag' nurse triage system at MAU reception to prioritise patients with acutely deteriorating conditions.

PDSA Cycle 1: Testing the Triage Tool Clarity

• Objective: To determine if the newly designed 'red flag' triage tool (based on NEWS2 criteria) can be consistently understood and applied by two MAU reception nurses during a pilot shift.

• Prediction: We predict that the two nurses will correctly identify 8 out of 10 'red flag' patients using the tool, as the criteria are clear and they have received a 30-minute briefing. There may be some initial hesitation in decision-making.

• Plan (Do Phase):

  • Who: Nurse A, Nurse B (MAU reception nurses), QI Lead (observing).
  • What: Nurses A and B will use the new triage tool for the first 10 consecutive patients presenting to MAU reception during their morning shift (8am-12pm).
  • Where: MAU reception desk.
  • When: Tuesday, 24th October, 8am-12pm.
  • Instructions: Nurses will mark each patient as 'red flag' or 'not red flag' on a tally sheet and note any difficulties or questions.

• Plan (Study Phase):

  • Data to Collect: Number of 'red flag' patients identified, number of times nurses referred to QI lead for clarification, qualitative notes on ease of use, time taken for initial assessment.
  • How: Tally sheet, observation log by QI Lead, brief post-shift verbal feedback session with nurses.
  • Who: QI Lead will compile data.
  • When/How to Analyse: Team meeting at 1pm on Tuesday, 24th October, to review tally sheet and discuss feedback.

• Plan (Act Phase):

  • If prediction met/exceeded: Proceed to PDSA Cycle 2: Test the tool with all nurses over one day and measure actual patient waiting times for 'red flag' patients.
  • If prediction not met/significant issues: Review the tool's design and nurse training. Revise the tool or training, then conduct PDSA Cycle 1 again.

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

How Lazomis Can Help

Lazomis provides structured tools and templates that streamline the planning and documentation of your PDSA cycles. Our dedicated QI project management features allow teams to:

• Create and manage PDSA cycles: Define objectives, predictions, and detailed plans directly within your project.
• Track data collection: Integrate data points relevant to your PDSA tests, making it easier to move from 'Do' to 'Study'.
• Document learning and actions: Record what was learned, compare actual results to predictions, and plan subsequent 'Act' steps, ensuring a clear audit trail for your improvement journey.
• Facilitate team collaboration: Share PDSA plans and results with your team and stakeholders, fostering transparent communication and collective learning.

By centralising your PDSA planning and execution, Lazomis helps ensure your tests of change are systematic, well-documented, and contribute effectively to your overall quality improvement aims.

Key Takeaways