Guest Post: The Chain of Improvement
Mark's note: Today's guest post is from Dr. Mark Jaben. I first met Mark in person at Cindy Jimmerson's Lean Healthcare West conference in Montana last year. I'm happy to publish this new guest post to follow up his previous post, inspired by New Zealand.
This is really born out of a recent medical trip to Bolivia, reading Drive by Daniel Pink, my wife's struggle as curriculum director in a pre K-12 private school and the faculty's frustration at students' seeming lack of motivation, and a dinner I had with Ricardo Peyerda, a Bolivian businessman who works with large corporation boards. His main focus is to help these boards think about how they develop relationships. As an emergency physician and in trying to promote Lean concepts and practices in health care, I have struggled with how to help people take the leap from an attraction to Lean ideas to being willing to carve out some time and effort to devote to their use. It seems that, despite their interest, nobody has any time or energy.
In Bolivia, I watched as my 13 year old son, David, and a retired engineer, named Dick, both without any medical experience, gradually become more and more involved in figuring out ways to help our eye surgery go better in our makeshift operating room. We didn't ask them to do more; they took it upon themselves. Their motivation and engagement only took off once they had enough mastery in the tasks we asked them to do, like running the A scan machine ( a device that measures patients for the right size lens implant), sterilizing the equipment, turning the room over between operations, coordinating surgeries with consults, performing eye screenings, and medicating patients. We all understood our hope was to improve people's eyesight.
This is what I think I learned:
Purpose + Mastery = Motivation + Autonomy = Engagement
PURPOSE, reason to act; what is needed to be successful; recognition that the problem at hand impacts your ability to be successful at what you are doing; this creates an interest to act
MASTERY, enough competence to act, which creates the sense you can be successful
So, RELEVANCE, the reason to act, and
ABILITY, the competence to act, together create a foundation for
MOTIVATION, the willingness and confidence to extend oneself
ADD AUTONOMY, the latitude to act;
LEADS to ENGAGEMENT, actually extending oneself to act
In practical terms, engagement requires establishing an atmosphere where people can act without having to fear the consequences, if their actions fail to achieve the aims. Dan Pink's research indicates that once fair compensation is established, autonomy is promoted through giving people control over their time, tasks, technique and team.
His work also indicates that mastery requires training and appropriate feedback. Mastery includes not only the skill and knowledge to perform the task at hand, but also the skill and knowledge in how to solve problems and learning to improve.
But what creates relevance and purpose? This is where Ricardo's insights were illuminating. Purpose and relevance are built upon establishing mutual goals; and this depends on each party understanding what each needs to be successful; and this is based on their assumptions about their world, how to be successful in it, and what does work and what won't work. The dialogue necessary to expose these assumptions will only occur once a relationship is established, where the parties recognize they need each other to be successful.
For David, once he understood that removing the cataract was only the first step, and that the right implant was crucial to getting the desired result, he recognized that his job running the A scan machine was incredibly important and a valuable step- he had a reason to act. Once he gained enough skill, by using TWI (training within industry) methods to get him up and running quickly, he was motivated and then found better ways to also keep the schedule on track and document the work. He was engaged in the work because we provided him enough skill and because we gave him the encouragement and support to act (we had little choice if we wanted to get all the surgeries done!). Sharing in the happiness of removing the eye patch of a patient the next day and discovering that person could now actually read for the first time in years was feedback enough.
Sometimes, however, what constitutes success is not so obvious. Often, we have not clearly defined what success entails, or the workplace environment makes this sharing difficult or even risky. Occasionally, people are very willing to share their beliefs about what success means to them, but often this is difficult because it revolves around deeply held, personal beliefs that people don't often feel comfortable sharing with others. Unless these assumptions are acknowledged, and either validated or refuted, it is hard to move further up the chain of improvement. And this is the importance of relationship building.
Purpose <– shared goals <–understanding success <– surfacing assumptions <–dialogue <– relationships
Ricardo is very interested in how societies and cultures over time have developed their rituals to foster these relationships, particularly, when the topic is difficult or painful. Perhaps there is some guidance in how best to advise us on relationship building.
Peacebuilding, by Lisa Schirch, suggests that rituals work to inactivate social structures that feed conflict. Creating shared identities through rituals helps individuals alter their world views and perceptions, allowing problems to be reframed and approached in new and novel ways.
Lean practice supplies its own set of rituals, most of which do establish a common method and language to allow such dialogue to occur when it is otherwise difficult or too risky. For instance, a kaizen event places everyone in the same room, removes the obstacles of their day to day work lives, and puts those with the insight together with those who have the ability to make the changes happen. A value stream map puts the actual current situation on paper, enabling everyone to agree on a common place to work from. The A3 format creates a platform to focus on the truly important information and acts as a guide for how to proceed. A PDCA cycle might really be needed to test the validity of an assumption, so as to better understand someone's notion of success. Unless these aspects are addressed, you may never get to the engagement needed to learn how to get results.
Cultures and religions certainly have defined protocols for the proper way to initiate communication inside the group, with outside parties and even with adversaries, and certainly with their central figure. So where people find it difficult to share their assumptions in the workplace, we can create rituals to assist.
For instance, a communication kata might establish these ground rules:
- How I will give information to you, ie, email, visual board, newsletters, communication book, calls, personal contact
- How exactly you can give information to me, ie, visual board, email, personal contact,
- A pledge as to how I will respond, ie, ‘I will always listen earnestly and take into account your views'; ‘my default response to any issue is to examine the process, not cross examine the person.'
- What to do if you feel at any time I am not fulfilling this pledge, ie, establish a personal “andon cord”, a visible sign, for example, like raising a finger, that we agree will serve a your signal to me that it does not appear I am complying with this pledge.
- What we will do together with the information, ie, problem solving.
In the Lean community, we all recognize how to get the results and learning through continuous improvement. It is the engagement I have struggled with. Now I think I have a better insight and understand that sometimes before I even first work to put the Lean practices in place, I really need all of us to understand that getting results:
- depends on learning how to get those results (ie, innovation)
- this requires people to even be interested in pursuing these results, (ie, engagement)
- this depends on relationships: what success actually means for people, and establishing an infrastructure for sharing difficult, closely held assumptions.
I believe this is where the basic concept of Respect for People applies, and why it is so essential to the chain of achieving results.
RESULTS <– LEARNING <— ENGAGEMENT <– RELATIONSHIPS
These linked steps in the chain of improvement provide a troubleshooting guide to assess your organization, or those you have been tasked with helping, to better understand what needs to be in place before learning and results can occur and where efforts need to be focused when there is resistance and push back.
The point is to be mindful of where you are along this chain. It may be that in your current situation, the purpose of the lean tool you choose is not really to achieve a result, or even to make the problems visible, but to be a ritual that creates the conditions where a relationship can be established, a common denominator can be found, a dialogue can emerge and an assumption can be safely challenged. As my lean mentors always repeat, “what's the problem?” Determining the right need is always the first step.
Dr. Mark Jaben currently resides in North Carolina, where he is a board certified emergency physician with over 25 years in community practice. After more than 20 years at one institution, he has spent the past 5 years doing locums work at more than a dozen hospitals, from small rural to large volume urban facilities, which has afforded him the great opportunity to experience both the unique challenges as well as common issues shared by health care institutions in the US and around the world.
Note: Comments have been turned off for the time being to try to shut down excessive spam/bot traffic to the site. If you'd like to add a comment, please share the post on LinkedIn or Twitter with your comments and thoughts.
Subscribe to get notified about posts via email daily or weekly.