feature – pl readers will likely be familiar with iov, the cancer clinic in brazil that’s become a reference for lean healthcare for countless organizations. here, dr fred looks back at iov’s 15-year journey.
words: dr frederico pinto
fifteen years ago, lean in healthcare was in its infancy. there were very few examples out there. in fact, iov has come to be known as one of the early adopters that have opened the way for the spread of lean thinking in healthcare here in brazil and south america. i am incredibly proud of what we achieved, but i also know there is still a lot more for us to do.
still, 15 years is an anniversary that somehow invites you to reflect. so, i thought it would be a good time to look back and think about what we know today about bringing lean thinking to a healthcare setting that we didn’t know when our transformation began.
lean is a learning journey, and we certainly learned a lot. interestingly, however, what was motivating us then is the same thing that is motivating us today: optimizing the system in which we operate. what has changed is our understanding of and experience in intervening on the system, rather than working on isolated improvements. when we started, we were essentially driving blindfolded: we knew the system wasn’t working, but we couldn’t do better than trying different things until we got some results. and, truth is, we did get results. remarkable ones. but without the awareness necessary to replicate them.
today, whenever we are asked to help other healthcare organizations to start their own lean transformations, our first suggestion to them is to create a model line. in practice, that’s exactly what we did ourselves 15 years ago without knowing it. so, the interesting thing about this is that, if i were to start all over again, i’d probably do it pretty much the same way.
this isn’t to say that nothing has changed since then. quite the opposite. our understanding of lean has evolved, and this has made our lives much easier. thanks to our and other organizations’ experiments and experience, we have a much clearer understanding of what lean is and how it works. throughout this time, thought leaders haven’t stopped churning out new models and theories helping us to cement our understanding of this elusive management philosophy. take john shook’s lean transformation framework, for example. it has taught us the key dimensions we need to address if we want to effect change in our organizations.
most importantly, over the years we have learned the importance of leveraging people’s knowledge and experience and of always giving them the time and space to learn. sadly, this is still not the case in most organizations out there, which seem to be married to a command-and-control type of management – even though its shortcomings have now become impossible to ignore.
lean advocates for an organization where leaders become hosts for the system and strive to create an environment where people learn continuously and eventually become autonomous problem solvers. on this note, i think it’s important to mention the white paper titled five guiding principles to transform healthcare that my lgn colleagues and i published in 2020. the five principles provide us with a great template for designing an ecosystem for learning and teaching lean thinking, in other words to develop the capabilities of people. they tell us what we need to learn in order to create the environment we want. (they are about the heuristics of knowledge generation: “if i do this, i will learn that.”)
ltf and the five guiding principles are examples of how our understanding of lean – both at iov and across the wider community – has deepened over the years. the basic information was always there – lean was always a people-centric holistic system aimed at creating more value with the same or less resources – but we have become better an unpacking its many layers and repackaging it for easier consumption by people around the world. every day, by studying and practicing lean, we are learning to use it more cleverly.
designing an environment for learning
there is a lot of talk in the lean community about the importance of leadership involvement in a transformation. while this is true, my biggest learning to date is perhaps that, when it comes to a transformation, you need more than a leader. you need someone who redesigns the system and makes it fit for continuous learning – an architect, a chief engineer.
a lot of people base their transformations on approaches that were designed for other systems and organizations. the most common example is, of course, toyota, the company that everyone wants to emulate but that nobody fully manages to. such pre-packaged, overly prescriptive models make little to no sense when it comes to lean thinking (as the ltf teaches us, every transformation is situational), because they are not a good representation of the reality they aim to change. indeed, the reason behind a lot of failed transformations is the misconception that you can copy-and-paste an approach designed for another system.
an architect is necessary to advance a lean transformation precisely because he or she provides a different perspective of the business, which managers – who are preoccupied with the daily work – don’t have. but who should this person be? it doesn’t have to be the ceo, but it should be someone (an area manager, perhaps) with a direct connection to the gemba and the ability to take a step back, see the big picture, and interact with different layers of the organization. in doing that, the architect creates the scaffolding that will support the lean transformation and enable the team to make changes, before a more “definitive” structure can be erected.
while supporting other organizations in their journeys, we learned that the scaffolding system is situational and that the system designer – the architect – is crucial in charting the course. some systems, for instance, look so chaotic at first that no basic stability can be seen. it’s there, but it’s not visible. we ran some experiments in such settings – specifically, primary care units – using daily management tools even before mapping value streams. this made patterns visible and helped teams understand the hidden basic stability in their system. we are using this approach most of the time these days, with daily management acting as a scaffolding system for basic stability that will then evolve to balance workload, allow value stream management (flow), and support problem solving.
by the way, this is why good lean coaches always look for an architect in every organization they go support. part of their intervention consists of creating an environment where experiments can take place and people can learn, but unless there is an architect accompanying the coach and building that scaffolding holding that environment up, the whole thing will fall to pieces as soon as the coaches are out of the door.
the iov lean journey has taught me that transforming an organization requires technique, and that it is a designer’s job before it is a leader’s. i wish i had known that years ago. so, keep this in mind, as it might just allow you to achieve your own transformation faster than we did.
the author
dr frederico pinto is the ceo of the iov group in brazil.