Session Summary
Session Host: Dr. Shelley Howk
Presenters & Panelists: Dr. Janet Craig & Dr. Elaine Bland
Session Objectives: At the end of this webinar, you will be able to:
- Describe how quality improvement does not need to be complex or time-consuming.
- Incorporate a framework that guides healthcare teams in deciding what to improve for greatest impact.
- Explain how to involve team members and patients in meaningful quality improvement.
Recommended Resources:
- Session Recording
- Listen-Sort-Empower Cycle – Mayo Clinic
- IHI Framework for Improving Joy in Work
- ACTT PPIP Support Webinars – Quality Improvement Basics
- Physician Leadership Network Previous Recording- ‘STAC’-ing up for Quality Improvement
- New! AMA Access Training for Primary Care
- Coming Soon! AMA Access Training for Specialists & Team Members with a Caseload
- Upcoming AMA Primary Care Strategic Forum May 1-3
Session Highlights & Themes:
Quality Improvement can be simple and effective
Quality improvement doesn't need to be complex or time-consuming. By focusing on the core issues (or "pebbles in your shoes"), healthcare teams can find simple, practical solutions that improve both the team’s efficiency and patient care.
The Listen, Sort, Empower Cycle
This tool, used by the Mayo Clinic, helps healthcare teams identify and prioritize areas for improvement. Teams begin by listening to team members and patients to identify key areas of concern. Teams then sort this feedback into categories of what they can control, influence, or have no control over. Tools such as the Impact Feasibility Grid can help teams sort what they’ve heard and focus in on changes that are both easy to implement and have the greatest impact. Teams are more likely to make lasting improvements when they are empowered to solve problems and make decisions together. When staff members actively participate in identifying and addressing issues, it increases morale, reduces burnout, and improves outcomes.
Moving toward a solution, vs. Rushing to Solutions
In QI work, it's important to avoid rushing to solutions. Instead, teams should first take the time to listen and sort the issues, gather data, and then use small iterative tests, such as Plan-Do-Study-Act cycles (PDSA cycles) to explore potential solutions. Through these cycles teams can refine their processes based on real-time feedback.
