{"id":3237,"date":"2013-09-08T17:59:00","date_gmt":"2013-09-08T17:59:00","guid":{"rendered":"http:\/\/www.saasoft.com\/blog\/?p=3237"},"modified":"2013-09-08T17:59:00","modified_gmt":"2013-09-08T17:59:00","slug":"drat","status":"publish","type":"post","link":"https:\/\/hcse.blog\/?p=3237","title":{"rendered":"DRAT!"},"content":{"rendered":"

[Bing Bong]<\/strong>\u00a0 The sound bite heralded Leslie joining the regular Improvement Science mentoring session with Bob.\u00a0 They were now using web-technology to run virtual meetings because it allows a richer conversation and saves a lot of time. It is a big improvement.<\/p>\n

<Bob><\/em> Hi Lesley, how are you today?<\/p>\n

<Leslie><\/em> OK thank you Bob.\u00a0 I have a thorny issue to ask you about today. It has been niggling me even since we started to share the experience we are gaining from our current improvement-by-design project.<\/p>\n

<Bob><\/em> OK. That sounds interesting. Can you paint the picture for me?<\/p>\n

<Leslie><\/em> Better than that – I can show you the picture, I will share my screen with you.<\/p>\n

\"DRAT_01\"<\/a> <Bob><\/em> OK. I can see that RAG table. Can you give me a bit more context?<\/p>\n

<Leslie><\/em> Yes. This is how our performance management team have been asked to produce their 4-weekly reports for the monthly performance committee meetings.<\/p>\n

<Bob><\/em> OK. I assume the “Period” means sequential four week periods … so what is Count, Fail and Fail%?<\/p>\n

<Leslie><\/em> Count is the number of discharges in that 4 week period, Fail is the number whose length of stay is longer than the target, and Fail% is the ratio of Fail\/Count for each 4 week period.<\/p>\n

<Bob><\/em> It looks odd that the counts are all 28.\u00a0 Is there some form of admission slot carve-out policy?<\/p>\n

<Leslie><\/em> Yes. There is one admission slot per day for this particular stream – that has been worked out from the average historical activity.<\/p>\n

<Bob><\/em> Ah! And the Red, Amber, Green indicates what?<\/p>\n

<Leslie><\/em> That is depends where the Fail% falls in a set of predefined target ranges; less than 5% is green, 5-10% is Amber and more than 10% is red.<\/p>\n

<Bob><\/em> OK. So what is the niggle?<\/p>\n

<Leslie><\/em>Each month when we are in the green we get no feedback – a deafening silence. Each month we are in amber we get a warning email.\u00a0 Each month we are in the red we have to “go and explain ourselves” and provide a “back-on-track” plan.<\/p>\n

<Bob><\/em> Let me guess – this feedback design is not helping much.<\/p>\n

<Leslie><\/em> It is worse than that – it creates a perpetual sense of fear. The risk of breaching the target is distorting people’s priorities and their behaviour.<\/p>\n

<Bob><\/em> Do you have any evidence of that?<\/p>\n

<Leslie><\/em> Yes – but it is anecdotal.\u00a0 There is a daily operational meeting and the highest priority topic is “Which patients are closest to the target length of stay and therefore need to have their\u00a0 discharge expedited?<\/em>“.<\/p>\n

<Bob><\/em> Ah yes.\u00a0 The “target tail wagging the quality dog” problem. So what is your question?<\/p>\n

<Leslie><\/em> How do we focus on the cause of the problem rather than the symptoms?\u00a0 We want to be rid of the “fear of the stick”.<\/p>\n

<Bob><\/em> OK. What you have hear is a very common system design flaw. It is called a DRAT.<\/p>\n

<Leslie><\/em> DRAT?<\/p>\n

<Bob><\/em> “Delusional Ratio and Arbitrary Target”.<\/p>\n

<Leslie><\/em> Ha! That sounds spot on!\u00a0 “DRAT” is what we say every time we miss the target!<\/p>\n

<Bob><\/em> Indeed.\u00a0 So first plot this yield data as a time series chart.<\/p>\n

<Leslie><\/em> Here we go.<\/p>\n

\"DRAT_02\"<\/a><Bob><\/em>Good. I see you have added the cut-off thresholds for the RAG chart. These 5% and 10% thresholds are arbitrary<\/strong> and the data shows your current system is unable to meet them. Your design looks incapable<\/strong>.<\/p>\n

<Leslie><\/em>Yes – and it also shows that the % expressed to one decimal place is meaningless because there are limited possibilities for the value.<\/p>\n

<Bob><\/em> Yes. These are two reasons that this is a Delusional Ratio; there are quite a few more.<\/p>\n

\n

\"DRAT_03\"<\/a><Leslie><\/em> OK\u00a0 and if I plot this as an Individuals charts I can see that this variation is not exceptional.<\/p>\n

<Bob><\/em> Careful Leslie. It can be dangerous to do this: an Individuals chart of aggregate yield becomes quite insensitive with aggregated counts of relatively rare events, a small number of levels that go down to zero, and a limited number of points.\u00a0 The SPC zealots are compounding the problem and plotting this data as a C-chart or a P-chart makes no difference.<\/p>\n

This is all the effect of the common practice of applying\u00a0 an arbitrary performance target then counting the failures and using that as means of control.<\/p>\n

It is poor feedback loop design – but a depressingly common one.<\/p>\n

<Leslie><\/em> So what do we do? What is a better design?<\/p>\n

<Bob><\/em> First ask what the purpose of the feedback is?<\/p>\n

<Leslie><\/em> To reduce the number of beds and save money by forcing down the length of stay so that the bed-day load is reduced and so we can do the same activity with fewer beds and at the same time avoid cancellations.<\/p>\n

<Bob><\/em> OK. That sounds reasonable from the perspective of a tax-payer and a patient. It would also be a more productive design.<\/p>\n

<Leslie><\/em> I agree but it seems to be having the opposite effect.\u00a0 We are focusing on avoiding breaches so much that other patients get delayed who could have gone home sooner and we end up with more patients to expedite. It is like a vicious circle.\u00a0 And every time we fail we get whacked with the RAG stick again. It is very demoralizing and it generates a lot of resentment and conflict. That is not good for anyone – least of all the patients.<\/p>\n

<Bob><\/em>Yes.\u00a0 That is the usual effect of a DRAT design. Remember that senior managers have not been trained in process improvement-by-design either so blaming them is also counter-productive.\u00a0 We need to go back to the raw data. Can you plot actual LOS by patient in order of discharge as a run chart.<\/p>\n

\"DRAT_04\"<\/a><\/p>\n

<Bob><\/em> OK – is the maximum LOS target 8 days?<\/p>\n

<Leslie><\/em> Yes – and this shows\u00a0 we are meeting it most of the time.\u00a0 But it is only with a huge amount of effort.<\/p>\n

<Bob><\/em> Do you know where 8 days came from?<\/p>\n

<Leslie><\/em> I think it was the historical average divided by 85% – someone read in a book somewhere that 85%\u00a0 average occupancy was optimum and put 2 and 2 together.<\/p>\n

<Bob><\/em> Oh dear! The “85% Occupancy is Best<\/em>” myth combined with the “Flaw of Averages<\/em>” trap. Never mind – let me explain the reasons why it is invalid to do this.<\/p>\n

<Leslie><\/em> Yes please!<\/p>\n

<Bob><\/em> First plot the data as a run chart and\u00a0 as a histogram – do not plot the natural process limits yet as you have done. We need to do some validity checks first.<\/p>\n

\"DRAT_05\"<\/a><\/p>\n

<Leslie><\/em> Here you go.<\/p>\n

<Bob><\/em> What do you see?<\/p>\n

<Leslie><\/em> The histogram\u00a0 has more than one peak – and there is a big one sitting just under the target.<\/p>\n

<Bob><\/em>Yes. This is called the “Horned Gaussian<\/strong>” and is the characteristic pattern of an arbitrary lead-time target that is distorting the behaviour of the system.\u00a0 Just as you have described subjectively. There is a smaller peak with a mode of 4 days and are a few very long length of stay outliers.\u00a0 This multi-modal pattern means that the mean and standard deviation of this data are meaningless numbers as are any numbers derived from them. It is like having a bag of mixed fruit and then setting a maximum allowable size for an unspecified piece of fruit. Meaningless.<\/p>\n

<Leslie><\/em> And the cases causing the breaches are completely different and could never realistically achieve that target! So we are effectively being randomly beaten with a stick. That is certainly how it feels.<\/p>\n

<Bob><\/em> They are certainly different but you cannot yet assume that their longer LOS is inevitable. This chart just says – “go and have a look at these specific cases for a possible cause for the difference<\/em>“.<\/p>\n

<Leslie><\/em> OK … so if they are from a different system and I exclude them from the analysis what happens?<\/p>\n

<Bob><\/em> It will not change reality.\u00a0 The current design of\u00a0 this process may not be capable of delivering an 8 day upper limit for the LOS.\u00a0 Imposing\u00a0 a DRAT does not help – it actually makes the design worse! As you can see. Only removing the DRAT will remove the distortion and reveal the underlying process behaviour.<\/p>\n

<Leslie><\/em> So what do we do? There is no way that will happen in the current chaos!<\/p>\n

<Bob> Apply the 6M Design\u00ae method. Map, Measure and Model it. Understand how it is behaving as it is then design out all the causes of longer LOS and that way deliver with a shorter and less variable LOS. Your chart shows that your process is stable.\u00a0 That means you have enough flow capacity – so look at the policies. Draw on all your FISH training. That way you achieve your common purpose, and the big nasty stick goes away, and everyone feels better. And in the process you will demonstrate that there is a better feedback design than DRATs and RAGs. A win-win-win design.<\/p>\n

<Leslie><\/em> OK. That makes complete sense. Thanks Bob!\u00a0 But what you have described is not part of the FISH course.<\/p>\n

<Bob><\/em> You are right. It is part of the ISP training that comes after FISH. Improvement Science Practitioner.<\/p>\n

<Leslie><\/em> I think we will need to get a few more people trained in the theory, techniques and tools of Improvement Science.<\/p>\n

<Bob><\/em> That would appear to be the case. They will need a real example to see what is possible.<\/p>\n

<Leslie><\/em> OK. I am on the case!<\/p>\n","protected":false},"excerpt":{"rendered":"

[Bing Bong]\u00a0 The sound bite heralded Leslie joining the regular Improvement Science mentoring session with Bob.\u00a0 They were now using web-technology to run virtual meetings because it allows a richer conversation and saves a lot of time. It is a big improvement. <Bob> Hi Lesley, how are you today? <Leslie> OK thank you Bob.\u00a0 I … <\/p>\n

Continue reading “DRAT!”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6,7,8,12,15,17,19,20,35,41,44,46],"tags":[],"class_list":["post-3237","post","type-post","status-publish","format-standard","hentry","category-6m-design","category-baseline","category-bobles","category-carveout","category-design","category-examples","category-fish","category-flow","category-reflections","category-stories","category-three-wins-r","category-teach"],"_links":{"self":[{"href":"https:\/\/hcse.blog\/index.php?rest_route=\/wp\/v2\/posts\/3237","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/hcse.blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/hcse.blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/hcse.blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/hcse.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3237"}],"version-history":[{"count":0,"href":"https:\/\/hcse.blog\/index.php?rest_route=\/wp\/v2\/posts\/3237\/revisions"}],"wp:attachment":[{"href":"https:\/\/hcse.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3237"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/hcse.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3237"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/hcse.blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3237"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}