{"id":5818,"date":"2019-02-09T09:26:37","date_gmt":"2019-02-09T08:26:37","guid":{"rendered":"http:\/\/www.improvementscience.co.uk\/blog\/?p=5818"},"modified":"2024-09-07T07:37:03","modified_gmt":"2024-09-07T07:37:03","slug":"from-push-to-pull","status":"publish","type":"post","link":"https:\/\/hcse.blog\/?p=5818","title":{"rendered":"From Push to Pull"},"content":{"rendered":"<p style=\"text-align: left;\">One of the most frequent niggles that I hear from patients is the difficultly they have getting an appointment with their general practitioner.\u00a0 I too have personal experience of the distress caused by the ubiquitous &#8220;<em>Phone at 8AM for an Appointment<\/em>&#8221; policy, so in June 2018 when I was approached to help a group of local practices redesign their appointment booking system I said &#8220;<em>Yes, please!<\/em>&#8220;<\/p>\n<hr \/>\n<p style=\"text-align: left;\">What has emerged is a fascinating, enjoyable and rewarding journey of co-evolution of learning and co-production of an improved design.\u00a0 The multi-skilled design team (MDT) we pulled together included general practitioners, receptionists and practice managers and my job was to show them how to use the health care systems engineering (HCSE) framework to diagnose, design, decide and deliver what they wanted: <em>A safe, calm, efficient, high quality, value-4-money appointment booking service for their combined list of 50,000 patients<\/em>.<\/p>\n<hr \/>\n<p style=\"text-align: left;\">This week they reached the start of the &#8216;<em>decide and deliver<\/em>&#8216; phase.\u00a0 We have established the diagnosis of why the current booking system is not delivering what we all want (i.e. patients and practices), and we have assembled and verified the essential elements of an improved design.<\/p>\n<p style=\"text-align: left;\">And the most important outcome for me is that the Primary Care MDT now feel confident and capable to decide what and how to deliver it themselves.\u00a0 \u00a0That is what I call <a href=\"https:\/\/www.improvementscience.co.uk\/blog\/?p=5759\"><em>embedded capability<\/em><\/a>\u00a0and achieving it is <strong>always<\/strong> an emotional roller coaster ride that we call <a href=\"https:\/\/www.improvementscience.co.uk\/blog\/?p=1548\"><em>The Nerve Curve<\/em><\/a>.<\/p>\n<p style=\"text-align: left;\">What we are dealing with here is called a <em>complex adaptive system<\/em> (CAS) which has two main components: Processes and People.\u00a0 Both are complicated and behave in complex ways.\u00a0 Both will adapt and co-evolve over time.\u00a0 The processes are the result of the policies that the people produce.\u00a0 The policies are the result of the experiences that the people have and the explanations that they create to make intuitive sense of them.<\/p>\n<p style=\"text-align: left;\">But, complex systems often behave in counter-intuitive ways, so our intuition can actually lead us to make unwise decisions that unintentionally perpetuate the problem we are trying to solve.\u00a0 The name given to this is a <a href=\"https:\/\/en.wikipedia.org\/wiki\/Wicked_problem\"><em>wicked problem<\/em><\/a>.<\/p>\n<p style=\"text-align: left;\">A health care systems engineer needs to be able to demonstrate where these hidden intuitive traps lurk, and to explain what causes them and how to avoid them.\u00a0 That is the reason the diagnosis and design phase is always a bit of a bumpy ride &#8211; emotionally &#8211; our Inner Chimp does not like to be challenged!\u00a0 We all resist change.\u00a0 Fear of the unknown is hard-wired into us by millions of years of evolution.<\/p>\n<p style=\"text-align: left;\">But we know when we are making progress because the &#8220;<em>ah ha<\/em>&#8221; moments signal a slight shift of perception and a sudden new clarity of insight.\u00a0 The cognitive fog clears a bit and a some more of the unfamiliar terrain ahead comes into view.\u00a0 We are learning.<\/p>\n<p style=\"text-align: left;\">The Primary Care MDT have experienced many of these <em>penny-drop<\/em> moments over the last six months and unfortunately there is not space here to describe them all, but I can share one pivotal example.<\/p>\n<hr \/>\n<p style=\"text-align: left;\">A common symptom of a poorly designed process is a <em>chronically chaotic queue.<\/em><\/p>\n<p style=\"text-align: left;\">[NB. In medicine the term chronic means &#8220;long standing&#8221;.\u00a0 The opposite term is acute which means &#8220;recent onset&#8221;].<\/p>\n<p style=\"text-align: left;\">Many assume, intuitively, that the cause of a chronically chaotic queue is <em>lack of capacity; h<\/em>ence the incessant calls for &#8216;more capacity&#8217;.\u00a0 And it appears that we have learned this reflex response by observing the effect of adding capacity &#8211; which is that the queue and chaos abate (for a while).\u00a0 So that proves that lack of capacity was the cause. Yes?<\/p>\n<p style=\"text-align: left;\">Well actually it doesn&#8217;t.\u00a0 Proving causality requires a bit more work.\u00a0 And to illustrate this &#8220;<em>temporal association does not prove causality trap<\/em>&#8221; I invite you to consider this scenario.<\/p>\n<p style=\"text-align: left;\">I have a headache =&gt; I take a paracetamol =&gt; my headache goes away =&gt; so the cause of my headache was lack of paracetamol. Yes?<\/p>\n<p style=\"text-align: left;\">Errr .. No!<\/p>\n<p style=\"text-align: left;\">There are many contributory causes of chronically chaotic queues and lack of capacity is not one of them because the queue is chronic.\u00a0 What actually happens is that something else triggers the onset of chaos which then consumes the very resource we require to avoid the chaos.\u00a0 And once we slip into this trap we cannot escape!\u00a0 The chaos-perpretuating behaviour we observe is called <em>fire-fighting<\/em> and the necessary resource it consumes is called <em>resilience<\/em>.<\/p>\n<hr \/>\n<p style=\"text-align: left;\">Six months ago, the Primary Care MDT believed that the cause of their chronic appointment booking chaos was a mismatch between demand and capacity &#8211; i.e. too much patient demand for the appointment capacity available.\u00a0 So, there was a very reasonable resistance to the idea of making the appointment booking process easier for patients &#8211; they justifiably feared being overwhelmed by a tsunami of unmet need!<\/p>\n<p style=\"text-align: left;\">Six months on, the Primary Care MDT understand what actually causes chronic queues and that awareness has been achieved by a step-by-step process of explanation and experimentation in the relative safety of the weekly design sessions.<\/p>\n<p style=\"text-align: left;\">We played simulation games &#8211; lots of them.<\/p>\n<p style=\"text-align: left;\">One particularly memorable &#8220;A<em>h Ha!<\/em>&#8221; moment happened when we played the <em>Carveout Game<\/em>\u00a0which is done using dice, tiddly-winks, paper and coloured-pens.\u00a0 No computers.\u00a0 No statistics.\u00a0 No queue theory gobbledygook.\u00a0 No smoke-and-mirrors.\u00a0 No magic.<\/p>\n<p style=\"text-align: left;\">What the <em>Carveout Game<\/em> demonstrates, practically and visually, is that an easy way to trigger the transition from calm-efficiency to chaotic-ineffectiveness is &#8230; to impose a carveout policy on a system that has been designed to achieve <em>optimum efficiency<\/em> by using averages.\u00a0 Boom!\u00a0 We slip on the twin banana skins of the <em>Flaw-of-Averages<\/em>\u00a0and <em>Sub-Optimisation<\/em>, slide off the performance cliff, and career down the rocky slope of Chronic Chaos into the Depths of Despair &#8211; from which we cannot then escape.<\/p>\n<p style=\"text-align: left;\">This visual demonstration was a cognitive turning point for the MDT.\u00a0 They now believed that there is a rational science to improvement and from there we were on the step-by-step climb to building the necessary embedded capability.<\/p>\n<hr \/>\n<p style=\"text-align: left;\">It now felt like the team were <strong>pulling<\/strong> what they needed to know.\u00a0 I was no longer <strong>pushing<\/strong>.\u00a0 We had flipped from push-to-pull.\u00a0 That is called the <a href=\"https:\/\/en.wikipedia.org\/wiki\/The_Tipping_Point\"><em>tipping point<\/em><\/a>.<\/p>\n<p style=\"text-align: left;\">And that is how health care systems engineering (HCSE) works.<\/p>\n<hr \/>\n<p style=\"text-align: left;\">Health care is a complex adaptive system, and what a health care systems engineer actually &#8220;designs&#8221; is a context-sensitive\u00a0 incubator that nurtures the seeds of innovation that already exist in the system and encourages them to germinate, grow and become strong enough to establish themselves.<\/p>\n<p style=\"text-align: left;\">That is called &#8220;<em>embedded improvement-by-design capability<\/em>&#8220;.<\/p>\n<p style=\"text-align: left;\">And each incubator needs to be different &#8211; because each system is different.\u00a0 One-solution-fits-all-problems does not work here just as it does not in medicine.\u00a0 Each patient is both similar and unique.<\/p>\n<hr \/>\n<p style=\"text-align: left;\">Just as in medicine, first we need to <strong>diagnose<\/strong> the actual, specific cause;\u00a0 second we need to <strong>design<\/strong>\u00a0some effective solutions; third we need to <strong>decide<\/strong> which design to implement and fourth we need to <strong>deliver<\/strong> it.<\/p>\n<p style=\"text-align: left;\">This how-to-do-it framework feels counter-intuitive.\u00a0 If it was obvious we would already be doing it.\u00a0 But the good news is that the evidence proves that it works and that anyone can learn <a href=\"http:\/\/www.hcse.org.uk\">how to do HCSE.<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>One of the most frequent niggles that I hear from patients is the difficultly they have getting an appointment with their general practitioner.\u00a0 I too have personal experience of the distress caused by the ubiquitous &#8220;Phone at 8AM for an Appointment&#8221; policy, so in June 2018 when I was approached to help a group of &hellip; <\/p>\n<p class=\"link-more\"><a href=\"https:\/\/hcse.blog\/?p=5818\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;From Push to Pull&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,6,13,14,15,16,4,22,30,32,33,36,38,41,46],"tags":[],"class_list":["post-5818","post","type-post","status-publish","format-standard","hentry","category-4n-chart","category-6m-design","category-chimpware","category-delivery","category-design","category-diagnosis","category-hcse","category-healthcare","category-operations","category-productivity","category-quality","category-resilient","category-safety","category-stories","category-teach"],"_links":{"self":[{"href":"https:\/\/hcse.blog\/index.php?rest_route=\/wp\/v2\/posts\/5818","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=5818"}],"version-history":[{"count":2,"href":"https:\/\/hcse.blog\/index.php?rest_route=\/wp\/v2\/posts\/5818\/revisions"}],"predecessor-version":[{"id":6328,"href":"https:\/\/hcse.blog\/index.php?rest_route=\/wp\/v2\/posts\/5818\/revisions\/6328"}],"wp:attachment":[{"href":"https:\/\/hcse.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=5818"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/hcse.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=5818"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/hcse.blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=5818"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}