1 / 35

Model for Improvement

Model for Improvement. Karen O ’ Keeffe. From Charles Darwin:. “ It is not the strongest of the species that survive, nor the most intelligent, but the one most responsive to change. ”. Three Fundamental Questions for Improvement. What are we trying to accomplish?

Download Presentation

Model for Improvement

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Model for Improvement Karen O’Keeffe

  2. From Charles Darwin: “It is not the strongest of the species that survive, nor the most intelligent, but the one most responsive to change.”

  3. Three Fundamental Questions for Improvement • What are we trying to accomplish? • How will we know that a change is an improvement? • What changes can we make that will result in improvement?

  4. G. Langley, et al The Improvement Guide. Jossey-Bass Publishers, San Francisco, 1996: xxi.

  5. Aim: What are we trying to accomplish? What are we trying to improve, in what time frame ?

  6. Value of an Aim Statement? • Answers and clarifies “What are we trying to accomplish? • Creates a common language to communicate about the improvement project • Provides opportunity to engage others in conversations and understanding of the improvement work

  7. Aim Statements include: • What is expected to happen • The system to be improved or the population of patients • Specific numerical goals • Time frame • Guidance for activities, such as strategies for the effort, or limitations

  8. Aim Statements – • We aim to reduce harm and improve patient safety for all of our internal and external customers. • By June 2013 management requires us to reduce the incidence of pressure injuries in A & R by 50% • Our most recent data shows we only complete med rec on 35% of disharged patients. We intend to increase this average to 50% by 5/1/13.

  9. 2nd Question How will we know that a changes is an improvement • Develop measures that reflect the improvement efforts. • Use Measure over time – run charts • Make measurement intervals as short as possible – weekly instead of monthly – (learn quicker)

  10. Measurement:How Do We Know a Change is an Improvement? Improvement is about making changes to systems; it is about changing an organization’s approach to improving the health of patients. It is not solely about measurement.

  11. 3rd QuestionWhat changes can we make that will result in improvement ? • "All improvement will require change, but not all change will result in improvement!” • G. Langley, et al The Improvement Guide. Jossey-Bass Publishers, San Francisco, 1996: xxi.

  12. Change Ideas:What changes can we make that will lead to improvement? • Key Changes for improved care based on: • The best available evidence • Knowledge of front line workers • Experiences of experts • Creative thinking

  13. The PDSA Cycle for Learning and Improvement • Questions and predictions (why) • Plan to carry out the cycle (who, what, where, when) • Plan for data collection • What changes • are to be made? • Next cycle? Act Plan Do Study • Complete the analysis of the data • Compare data to predictions • Summarize what was learned • Carry out the plan • Document problems and unexpected observations • Begin analysis of • the data G. Langley, et al The Improvement Guide. Jossey-Bass Publishers, San Francisco, 1996: xxi.

  14. Use the PDSA Cycle for: • Developing a change • Testing or adapting a change idea • Learning how a change will work in different environments or systems • Creating belief that changes be effective • Learning more about the system

  15. Why test ? • Increase belief for team that change will work • Learn how to adopt changes in your environment. • Document effect change making to overall aim. • Develop broader knowledge of your system and effects of changes.

  16. PDSA: Break it Down/Simplify… Plan - Figure out the questions you want to answer, plan a way to answer the questions, and predict results Do - “Just do it” (i.e. do the plan); collect the data Study - What did you learn? Act - What will you do with the knowledge you learned? What do you want to do next?

  17. Revise and Re evaluate • Remember that the first changes tried do not always work. (this is a great source of learning) • Use another PDSA cycle until it works as expected / predicted.

  18. Tips for Testing Changes • Identify changes that will assist the team to reach goals • Harvest good ideas and adapt them to your setting • Solicit team members ideas • Start with changes that are easy to test • Collect and study useful data during each test • Learn from “failed” tests • Eventually test over a wide range of conditions

  19. Failure is just succeeding at learning what doesn't’t work!

  20. Objectives of Cycles for Testing • Decide if change will work in actual environment • Decide on combination of changes for desired effect • Evaluate cost, social impact, side effects • Evaluate how much improvement we can expect • Increase degree of belief

  21. Successful Cycles to Test and Adapt • Scale down size of test (# of patients, location) • Conduct the test over a short time period • Test with volunteers • Do not try to get buy-in or consensus for the test • Collect useful data during each test • Think a couple of cycles ahead • Plan multiple cycles to test and adapt change In later cycles, test over a wide range of conditions

  22. Initially use Smaller Scale Tests: The power of “one” Conduct the initial test with… • one facility • one office • one doc • one patient / resident 1

  23. Move Quickly to Testing Changes • Year • Quarter • Month • Week • Day • Hour “What tests can we complete by next Tuesday?”

  24. On-line Model for Improvement • To review the Model for Improvement or share with colleagues, visit the IHI’s website • http://www.ihi.org/IHI/Topics/Improvement/ImprovementMethods/HowToImprove/

  25. Thank you! Madlen Caplow, Neil Heffron, Brandon Bennett, Lloyd Provost, NICHQ, the IHI and others from whom I ‘shamelessly’ stole some of these slides.

  26. References “A Primer on Leading the Improvement of Systems,” Don M. Berwick, BMJ, 312: pp 619-622, 1996. “Accelerating the Pace of Improvement - An Interview with Thomas Nolan,” Journal of Quality Improvement, Volume 23, No. 4, The Joint Commission, April, 1997. “Building Measurement and Data Collection into Medical Practice”, Eugene Nelson, Mark Splaine, Paul Batalden, Stephen Plume. Annals of Internal Medicine Vol 128; no16, March 15, 1998. “How to Take Multiple Measures to Get a Complete Picture of Organizational Performance.” Provost, Lloyd and Leddick, Susan National Productivity Review. Autumn 1993. pp. 477-490. Quality Improvement Through Planned Experimentation. 2nd edition R. Moen, T. Nolan, L. Provost, McGraw-Hill, NY, 1998. The Improvement Guide: A Practical Approach to Enhancing Organizational Performance. G. Langley, K. Nolan, T. Nolan, C. Norman, L. Provost. Jossey-Bass Publishers., San Francisco, 1996. “The Three Faces of Performance Measurement: Improvement, Accountability and Research.” Solberg, Leif I., Mosser, Gordon and McDonald, Susan Journal on Quality Improvement. March 1997, Vol.23, No. 3. “Understanding Variation”, Quality Progress, Vol. 13, No. 5, T. W. Nolan and L. P. Provost, May, 1990. A Primer on Leading the Improvement of Systems,” Don M. Berwick, BMJ, 312: pp 619-622, 1996.

More Related