9 Tips for Moving from One PDSA Cycle to the Next
Congratulations—You’ve finished your first PDSA cycle, which means you have taken an essential step towards driving change. Give yourself a pat on the back and get ready to dive into the next phase of continuous improvement: your second, third and fourth PDSA cycle, or, as many cycles as needed to reach the final adoption stage.
Think about the first time you baked a cake. Did it turn out perfectly? Or did you need to try several attempts, learning and improving each time? A stand-alone PDSA cycle can rarely, if ever, result in an adoptable change idea. Instead, we rely on sequential tests that build on changes that show promise, widen the scale of testing and are performed under multiple settings and conditions.
Moving to that next cycle can be daunting, regardless of whether your first cycle went as planned. Before moving forward, remember to double check your predictions against these nine rules:
Make realistic predictions: Use the data from your first PDSA cycle to adjust your predictions for your second. Making more informed, data-driven predictions will help you better measure and understand the success or failure rates of your next cycle.
Stay on goal: Modifying an individual test of change—the original PDSA cycle—does not mean your overall project goals should change. Remember to review your answers to the three fundamental questions and make sure your change modification still supports those goals.
Update your learning questions: A new PDSA cycle means creating a new question that your test answers. Specifically, design a new question that addresses the problem noted in the previous PDSA cycle.
Identify who needs to be notified: A change to the initial test will likely impact multiple groups of people. Meeting with all key stakeholders helps ensure that the adaption will go smoothly during the Do phase of your next PDSA cycle.
Differentiate between the method and the administrator: Let’s say you have identified one element of your initial change test that needs to be adapted. For example, a new protocol did not capture as much data as expected. When considering how to adapt the protocol for your next PDSA cycle, be careful not to confuse the person (or people) who collected the data with the method of collection. Adapting the method, rather than blaming those who implement it, will lead to better outcomes.
Don’t abandon too soon: Before abandoning a change idea, reflect on your execution. Did you follow through on all steps outlined in the Plan stage? Don’t make the mistake of discarding a promising idea because of poor execution.
But, don’t adopt too soon either: When we see improvement that is greater than predicted, we can be tempted to adopt it as standard. Remember if there is still room for improvement, keep adapting and start another PDSA cycle. Stuck on next steps? Consider testing under an unlikely circumstance or increase the test’s reach.
Don’t repeat the cycle: While this may seem like a given, it can be tempting to re-test the same change if you think the results from the first cycle were a fluke. Maybe staff who had never called in sick caught a bug; maybe there was a power outage and multiple back-up generators failed. Even if an anomaly occurs, adapt the model based on the cycle’s results. In the next cycle come up with a plan for these exceptions so that you are prepared to deal with them when they occur again in the future.
Develop a robust implementation plan: Your work does not stop once you’ve identified a change idea to adopt. Provide clear instructions that include a plan for training, methods for securing resources and needed equipment, directions for revisions to policies and procedures and updated job descriptions
Interested in seeing these methods in action? Our free 30-minute online course, Quality Improvement 102, applies these rules to a series of PDSA cycles seeking to reduce infant mortality through smoking cessation. Take the course and continue you learning.
Still new to PDSA cycles? Try Quality Improvement 101 to build a foundation for driving change.
Keeping Families Together Improves Children’s Health Outcomes, from Borders to Communities
Thousands of children were recently separated from their families on the Texas border. Too many children have undergone the trauma of preventable family separation, which cannot be undone. NICHQ's new Chief Health Officer, Elizabeth Coté, MD, MPA, has witnessed the devastating effects of caregiver-child separation in communities across the country and across the world. In this article, she speaks up about the harm of that separation and urges us to remain vigilant about keeping families together.
Case Study: Engagement of Title V, Healthy Start and Families to Increase New Mother Wellness in NJ
A new issue brief, co-authored by AMCHP and NICHQ, explores how New Jersey engaged mothers in its efforts to improve postpartum visit rates as a strategy to increase new mother wellness.
Building Resiliency in Teen Moms Can Improve Breastfeeding and Save Babies
Less than one in five adolescent mothers exclusively breastfeeds their babies for the recommended six months. This means that, with the right supports, over 80 percent more teen moms and their babies can gain proven health benefits, including a reduced risk of sudden infant death syndrome. Here, Lori Feldman-Winter, MD, MPH, highlights strategies that uniquely empower teen mothers to breastfeed their babies.
Empowering Parents to Improve Early Childhood Systems
We know first-hand that parent partners can make a big difference in improving children's health outcomes. Here, we’re highlighting one parent partner's story and providing strategies for states interested in putting parent support and parent-partnerships at the forefront of their early childhood improvement efforts.
Recruiting Physician Champions for Improvement Projects
Having a physician champion on board can be an important benefit for clinically-based improvement teams. The physician champion plays a crucial role when it comes time to make the case for other physicians to support an improvement idea. Here are three tips for successful recruitment.
Use Evaluation to Guide PDSAs Rather Than Derail Them
Evaluation is a critical tool for any improvement project. Yet, teams sometimes find themselves mistaking evaluation tasks for tests of change, which stalls their PDSAs. Here, we help you differentiate between tests and tasks so that you can use evaluation as the powerful tool it should be: one that informs and launches your test of change.