Note: I'm actually doing TWO free webinars on January 27. One is for Becker's Hospital Review, sponsored by Kronos on the topic of “Lean: Transforming Healthcare Delivery by Uncovering Opportunities Within Your Workforce.” (Learn about the other here). I hope you can join me.
Even with 20 years of experience in studying, applying, and teaching Lean principles (“Practicing Lean,” if you will), I have relatively limited experience with the “strategy deployment” methodology. I've never had the opportunity to work full-time in an organization that had a mature strategy deployment (SD) process and culture.
I have had, thankfully, the opportunity to learn from many visits to ThedaCare about how they do SD (including helping to lead the production of this DVD). I've been able to work as a consultant where I've been learning from other consultants who are more experienced with SD and I've supported ongoing SD efforts from the standpoint of coaching people on A3 thinking and Plan-Do-Study-Adjust (PDSA) problem solving.
Listen to Mark read this article (learn more and subscribe via iTunes):
Within the past year, I've had the chance to work with Karen Martin at a health system that is getting started with a brand new SD process. I am again supporting them in the areas where I have more experience: the A3 process, PDSA problem solving (Plan-Do-Study-Adjust), Kaizen, value stream mapping, and general Lean thinking.
But back to SD… one key reflection of mine on this work and learning is:
It seems to me that a strategy deployment process can be described as a series of hypotheses that are tested over time. Strategy deployment is a high-level annual PDSA cycle that contains embedded PDSA cycles of analysis, improvement, measurement, and adjustment.
An organization, whether they are practicing Lean or not, generally already has a defined mission, an articulated vision, and a set of stated values. Whether the mission, vision, or values are correct or not seems like something that can only be tested through an ongoing PDSA mindset and reflection over many years.
In the SD process, an organization defines four (or maybe five) key objectives and goals (called “focus areas” at ThedaCare). Pictured below is a screenshot of ThedaCare CEO Dean Gruner, MD as he talks about strategy deployment in the DVD I mentioned earlier.
Dean is standing in front of one of the walls in their executive meeting room. ThedaCare's four “true north” focus areas are:
- Safety / Quality
- Customer Satisfaction
- Financial Stewardship
These four areas are important and meaningful to ThedaCare, as they might be to other hospitals (but that doesn't make these the “right” true north objectives that all must use or copy).
But this also seems to be the first hypothesis, which could be stated as:
Hypothesis #1: “If we focus our improvement efforts and close performance gaps in these four areas, we will therefore perform well as an organization, this year and over the long-term.”
At ThedaCare, the “true north” focus areas tend to stay the same each year, since they are the compass and direction for the organization. These shouldn't change every year. These should be an example of what Dr. W. Edwards Deming called “constancy of purpose.” These areas are interconnected and mutually supportive, as a hospital and or healthcare organization are a system, as Deming would have explained.
An organization could choose to change or replace a true north focus area if that first hypothesis seemed to not be working out as expected over time. It's hard to see how doing well in a focus area like “customer satisfaction” would not improve overall organizational performance. But, maybe the broader conditions have changed and the senior team decided that a different key focus area should be brought in instead.
Under each of the four focus areas are two to three key performance indicators (KPIs) that are tracked and are watched closely by the senior leadership team (SLT) on a monthly basis, if not more frequently. These specific metrics are chosen because they are the specific areas in which the organization needs to improve this year. And, breakthrough improvement projects (managed via A3s) are chosen to drive improvement in those metrics.
So that seems to be a second hypothesis:
Hypothesis #2: “If we can improve and close our performance gaps in these key performance indicators, we will satisfy our need for improvement in our key focus areas, and therefore we will be successful as an organization, overall.”
You might call these “focus metrics,” because they are providing focus to the SLT within their true north focus areas. Instead of looking at 100 measures and trying to drive improvement in all of those measures, the SD approach tells us that it's better to pay attention to a few high-leverage areas instead of spreading our attention and efforts too thin. I visited one organization a few years ago that bragged about being down to “just 37 focus metrics.” Well, I guess that's progress. As they “study and adjust” over time (PDSA) they might realize that 37 isn't really focused enough. ThedaCare has about ten of these focus metrics each year.
These KPIs or focus metrics change more often in an organization than do the true north focus areas. Under the “Safety/Quality” area, a hospital might initially measure medication errors and patient falls. But, after making big improvements in those particular KPIs, they might shift to measuring things like hospital acquired infections and overall mortality instead. Changing the KPIs after a yearly SD cycle doesn't mean that it's no longer important to prevent medication errors. It's likely still something that's being measured somewhere in the organization. But, it means that it's not one of the key indicators that the SLT needs to be looking at constantly throughout the year.
How do we close the gaps in performance? How do we ensure we have enough organizational capacity to do so?
Is your organization using strategy deployment? What hypotheses are you testing? What are the results of those tests?
Also, see this webinar that I did in July 2016 (clicking the image below will bring you to a page with the recording):