Model For Improvement Clip 1

The Model for Improvement was developed by Associates in Process Improvement (www.apiweb.org)
Model For Improvement Clip 1
Robert Lloyd, PhD
From the IHI Open School's online course:
QI102 Lesson 1 courses.ihi.org

[@jakejarvis1148]

He writes over the black marker with the blue marker... He just ruined that blue marker. It will now leave a black streak for the rest of its existence.

[@cuwonline]

Captions: 1 00:00:00,000 --> 00:00:11,730 Every time you start out on a journey, whether it be by land or sea, you need 2 00:00:11,730 --> 00:00:14,700 to have some way to guide your journey 3 00:00:14,700 --> 00:00:19,560 some roadmap, a compass, if you will, that gives you direction and gives you some 4 00:00:19,560 --> 00:00:22,650 sort of sense of where you're going. 5 00:00:24,330 --> 00:00:27,959 Well, we have that at the IHI. It's called the model for improvement. 6 00:00:28,949 --> 00:00:34,170 The model for improvement gives us the foundation and the framework for doing 7 00:00:34,170 --> 00:00:35,550 improvement work. 8 00:00:35,550 --> 00:00:42,89 It is really structured around several key components: basically two major 9 00:00:42,90 --> 00:00:44,309 sections of the model for improvement. 10 00:00:44,309 --> 00:00:48,539 First of all, "What is your aim?" "How will you know that a change is an improvement?" 11 00:00:48,539 --> 00:00:53,70 is the second question, which gets to measurement. 12 00:00:58,130 --> 00:01:05,300 The third question deals with "What changes can you actually put in place to 13 00:01:05,300 --> 00:01:07,280 achieve the aim?" 14 00:01:07,280 --> 00:01:11,90 So these three things continually loop together and we always check ourselves 15 00:01:11,90 --> 00:01:12,920 against our aim. 16 00:01:12,920 --> 00:01:18,110 "How good? By when?" is typically one of the things we ask in the aim statement. 17 00:01:18,650 --> 00:01:28,880 How good do you want to be, and then by when. It's not good enough just to say 18 00:01:28,880 --> 00:01:32,869 that we want to be in the top decile, the top quartile, but by when? 19 00:01:32,869 --> 00:01:37,460 Let's give a date. The measures: are you going to look at process and outcome 20 00:01:37,460 --> 00:01:41,839 measures? And then what changes are you are actually going to put into place 21 00:01:41,840 --> 00:01:46,160 that you can track with data and then match back up against your aim? 22 00:01:46,160 --> 00:01:52,460 This then gets carried out in daily work with a team through something called the 23 00:01:52,460 --> 00:02:05,330 P-D-S-A cycle or Plan, Do, Study, and Act. The three questions give us the 24 00:02:05,330 --> 00:02:08,329 framework that we always go back to. What are we trying to accomplish, 25 00:02:08,960 --> 00:02:14,270 how will we know change is an improvement, what changes can we actually make. PDSA cycles 26 00:02:14,270 --> 00:02:19,310 is where we do our testing on a day-to-day basis. We go out and we take 27 00:02:19,310 --> 00:02:23,270 the ideas, we put them into a PDSA cycle, we plan it, 28 00:02:23,270 --> 00:02:28,69 we do it, we study it, (that is, we get the data, we come back up and look at this 29 00:02:28,69 --> 00:02:32,720 question), and then we act (that is, we're going to change our plan based on the 30 00:02:32,720 --> 00:02:36,859 feedback we obtained, and then we're going to go through another cycle). This 31 00:02:36,860 --> 00:02:40,910 then becomes our model and a framework for how we're going to actually carry 32 00:02:40,910 --> 00:02:44,240 out improvement strategies. It gives us our guide and our roadmap.

[@IHIOpenSchool]

Check out part 2 here - kzbin.info/www/bejne/bH6shqSaqtGBrbM

[@timbuckle4947]

hi