PDSA Cycle Toolkit: A Practical Guide for UK Healthcare Improvement

Why this topic matters

Effective quality improvement is crucial for delivering high-quality, safe, and efficient patient care. The NHS faces ongoing challenges, from patient flow and workforce pressures to ensuring equitable access and outcomes. PDSA cycles provide a practical, iterative method to address these challenges locally, allowing teams to learn rapidly from small-scale tests before broader implementation.

For clinicians, trainees, and QI leads, mastering the PDSA cycle is essential. It enables a structured approach to problem-solving, moving beyond simply identifying issues to systematically testing potential solutions. This iterative learning prevents the pitfalls of large-scale, untested implementations that can disrupt services or even cause harm.

Practical explanation: What is a PDSA Cycle?

At its core, a PDSA cycle is a scientific method for testing a change. It involves four interconnected stages:

1. Plan: Set the stage for your test

This is the critical thinking phase. Before you do anything, you need a clear plan. It requires a deep understanding of your problem and a hypothesis about how a specific change will lead to an improvement.

• Define the objective: What specific improvement are you trying to achieve with this test? Be precise. (e.g., 'Reduce the average waiting time for phlebotomy by 5 minutes').
• Make predictions: What do you expect to happen when you implement this change? Why? This helps you to articulate your underlying theory.
• Outline the change: What exactly are you going to do? Be detailed. (e.g., 'Introduce a new triage system for phlebotomy patients at reception').
• Identify resources and responsibilities: Who needs to be involved, what equipment is needed, and what are their roles? (e.g., 'Receptionist A will use the new system, Dr. B will observe').
• Determine data collection: What data will you collect to assess if your prediction was correct? How will you collect it, who will collect it, and when? (e.g., 'Record entry and exit times for 10 patients using the new system on Tuesday morning').
• Plan for potential risks: What could go wrong, and how will you mitigate it?

2. Do: Carry out the test

This is where you execute your plan, ideally on a small scale, in a controlled environment.

• Implement the change as planned: Stick to your detailed plan. Avoid making ad-hoc changes during this stage.
• Collect data: Gather the data identified in your 'Plan' phase. Be meticulous.
• Observe and document: Note any unexpected issues, challenges, or observations that arise during the test, even if they seem minor.

3. Study: Analyse the results and learn

This stage is about reflecting on what happened, comparing it to your predictions, and making sense of the data.

• Analyse the data: Compare the collected data against your objective and predictions. Did the change lead to the expected outcome?
• Summarise and interpret: What did the data show? What did you learn? Were your predictions correct? If not, why not?
• Identify unintended consequences: Did anything unexpected happen, positive or negative?
• Reflect as a team: Involve all relevant team members in discussing the findings.

4. Act: Decide the next steps

Based on your learnings, you decide what to do next. This closes the loop and often leads to the start of a new PDSA cycle.

• Adopt: If the test was successful and sustainable, integrate the change into routine practice. This might mean standardising a new process, updating a policy, or rolling it out to a larger population.
• Adapt: If the test showed promise but needs refinement, modify the change based on your learning and run another PDSA cycle. This is the most common outcome.
• Abandon: If the test clearly didn't work or had negative consequences, discard the change and consider trying a different intervention or re-evaluating the problem.
• Iterate: The 'Act' phase often leads back to 'Plan' for the next cycle, either refining the current change or testing a new one. This iterative nature is key to continuous improvement.

Common pitfalls

Successfully running PDSA cycles requires discipline and careful attention. Avoid these common traps:

• Skipping the 'Plan' phase: Rushing into action without clear objectives, predictions, or data collection plans often leads to ambiguous results and wasted effort.
• Too large a 'Do' phase: Testing a change on too big a scale from the outset increases risk and makes it harder to learn. Start small and safe.
• Failing to 'Study': Neglecting to properly analyse data and reflect on observations. A test without learning is just an activity, not improvement.
• Ignoring the 'Act' phase: Not making a clear decision on the next steps (adopt, adapt, abandon) means the learning isn't fully utilised.
• Lack of clear predictions: Without a prediction, it's hard to know if you were right or wrong, making learning less effective.
• Poor data collection: Inadequate or inconsistent data collection makes it impossible to 'Study' effectively.
• One-off activity: Viewing PDSA as a single event rather than an iterative, continuous process.

Step-by-step approach: Implementing a PDSA cycle

Here’s a structured approach to guide your team:

1. Define your Aim: What specific, measurable, achievable, relevant, and time-bound improvement are you targeting (your ‘SMART’ aim statement)?
2. Identify a Change Idea: Based on your understanding of the problem, what specific intervention might lead to your aim?
3. Complete the 'Plan' section of your PDSA template:
   • Objective: What are you testing?
   • Prediction: What do you anticipate will happen?
   • Detailed steps: How will you run the test?
   • Who, what, when, where?
   • Data collection: What data, by whom, how, and when?
4. Execute the 'Do' phase: Carry out the test exactly as planned, collecting all necessary data and noting observations.
5. Critically 'Study' the results: Convene your team, review the data and observations. Compare to your predictions. What did you learn?
6. Decide to 'Act': Based on your learning, formally decide to Adopt, Adapt (and run a new PDSA), or Abandon. Document your rationale.
7. Document and Communicate: Keep clear records of each cycle and communicate your findings to relevant stakeholders. This supports transparency and shared learning.

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

[Downloadable PDSA Cycle Template (PDF/Editable Word Doc - optional add)]

Example in clinical practice: Reducing ward round delays

Aim: To reduce the average start delay of the morning ward round on Ward X from 20 minutes to 10 minutes by end of next month.

Change idea: Introduce a pre-ward round 'huddle' at 08:30 for 5 minutes to confirm patient priorities and allocate tasks before the 09:00 ward round start.

PDSA Cycle 1: Testing the huddle with a small group

• Plan:
  • Objective: To see if a 5-minute pre-ward round huddle can reduce the ward round start delay for one consultant team.
  • Prediction: The ward round will start closer to 09:00, possibly within 5-10 minutes of the planned start, due to better preparation.
  • Details: Consultant A, Registrar B, Ward Sister C and 2 junior doctors will meet in the ward office at 08:30 for 5 minutes on Monday, Wednesday, and Friday next week. Agenda: confirm sickest patients, discharge planning, prioritised tasks. Nurse in charge will continue their handover during this time.
  • Data: Ward sister will record actual ward round start time (when all core members are present at the first patient's bedside) for these 3 days.
• Do: The team conducts the huddles as planned. Sister C records start times. Observations: Day 1 – forgot one junior doctor; Day 2 – huddle ran for 8 minutes; Day 3 – worked well, good clarity.
• Study: Average start delay was 8 minutes on huddle days vs. 15 minutes on control days (from previous data). Prediction partially correct, improvement seen. Huddle length needs discipline. Engagement was good.
• Act: Adapt. Refine huddle agenda to be stricter on time. Remind team about timings. Run another PDSA cycle, expanding to a second consultant team for a week.

This iterative process of small-scale testing and learning is how teams make sustained progress.

How Lazomis can help

Lazomis provides a structured environment to support your PDSA cycles, from initial project setup through to data collection and reporting. Our QI module guides you through defining your aim, selecting measures, and documenting each stage of your PDSA cycles.

• Project Setup: Clearly define your aims and change ideas within a dedicated QI project.
• PDSA Templates: Utilise digital templates to document each 'Plan', 'Do', 'Study', 'Act' phase, ensuring no critical steps are missed.
• Integrated Data Collection: Link your PDSA cycles to data collection tools, allowing you to track measures directly and streamline your 'Study' phase analysis.
• Visualisation and Reporting: Generate run charts or control charts automatically from your aggregated data to visualise the impact of your changes, helping you easily interpret and communicate your 'Study' findings.
• Collaboration: Share your PDSA cycles and project progress with team members and stakeholders, fostering transparency and collective learning.

Key takeaways