Tuesday, April 5, 2016

Resourses for Lean Veterinary Medicine

Here are some recommendations for further reading and web resources. At some point in the future, this post will be moved to a separate page of this blog to facilitate future additions and updates.
Enjoy! And, be sure to let us know what you think or if you have a recommendation for an addition to the list. 

Suggested Reading:
Follow the Learner: The Role of a Leader in Creating a Lean Culture by Sami Bahri, DDS
Management on the Mend, by Dr. John Toussaint
The High Velocity Edge, by Steven J. Spear
Transforming Health Care: Virginia Mason Medical Center's Pursuit of the Perfect Patient Experience by Charles Kenney
The Toyota Way: 14 Management Principles From the World’s Greatest Manufacturer by Jeffrey K. Liker
Lean Thinking: Banish Waste and Create Wealth in Your Corporation by Daniel P. Womack and Daniel T. Jones
Lean Lexicon: A Graphical Glossary For Lean Thinkers; 5th Ed. by the Lean Enterprise Institute
Value Stream Mapping for Healthcare Made Easy by Cindy Jimmerson
Toyota Production System: Beyond Large-Scale Production by Taiichi Ohno
Workplace Management by Taiichi Ohno
Managing to Learn: Using the A3 Management Process to Solve Problems, Gain Agreement, Mentor, and Lead by John Shook
A3 Problem Solving for Healthcare: A Practical Method for Eliminating Waste by Cindy Jimmerson
Out of Crisis by W. Edwards Deming
Harvard Business Review article, "Time-and-Motion Regained



Web Resources:
Lean Enterprise Institute              
Mark Graban’s Lean Blog              
Kaizen Institute                 
Shingo Institute                  
Toyota TSSC                    
Toyota’s TPS page        

Tuesday, March 22, 2016

Ohno's Circle and Gemba Walks

While Mark Graban and I were at the recent TVMA Convention and Expo presenting our Lean lecture a couple of weeks ago, a veterinarian came up to us and said that he routinely schedules each of his staff to spend 30 minutes several times each week to just observe procedures and flows around the hospital. In Lean terms, these are called a “gemba walks.” We, of course, think this is a great idea, and it reminded me of the story of Taiichi Ohno and his chalk circle (Ohno’s circle).

Taiichi Ohno was an engineer at Toyota in the 50s. He is considered to be one of “The Fathers of TPS” (Toyota Production System). The story says that when a new engineer was assigned to him for mentoring, he would take the individual to the shop floor (gemba), draw a four foot circle on the floor, near one of the processes of the production line, and “ask” him to stand inside the circle and observe for any improvements he could find. With no other instructions, Mr. Ohno would leave. 

After several hours, he would return and ask the young engineer what he had observed. If Ohno was not satisfied with the response, he would again “ask” that the trainee remain in the circle and continue to observe, and, again, leave for several hours. Evidently, some of these “students” spent as much as an entire eight hour shift standing in Ohno’s circle and considered it an honor to do so; to learn from the master. The improvement they suggested could be as small as moving the pneumatic wrench two inches to the right, so it would be easier, and faster, for the worker to do his job. Now, you know there have already been several hundred (or thousand!) iterations of kaizen when moving a tool two inch is the only improvement you can find!

What Ohno was trying to demonstrate to these young managers is quintessential Lean. It is not enough to just “look.” One must truly “see”; to deeply understand the process and how it affects the value stream, the greater systems, the customer and the worker at the gemba. Even more importantly, he was trying to instill into their “being” the process of how to think, to analyze, to pursue perfection through continuous improvement (kaizen).

Now, I think most of us here in the west would consider Ohno’s circle to border on the “cruel and unusual,” but I celebrate the veterinarian I talked to for his vision, understanding and the investment in the long term effects of assigning “gemba walks.” I hope he is also carving out time for himself and the other doctors to observe the work that occurs around them. I think we, as doctors, owners and practice managers, act like we know everything that is going on in our hospitals (our gembas), yet we know that isn't true. We just put off dealing with it, and the problems keep recurring. When was the last time we went into our “waiting room” and just observed what was really happening? Might we be surprised at what we saw?

The other thing that I hope is happening at this vet’s practice during these “walks” is that everyone is stretching their comfort zones. In other words, the surgery tech should spend some observation time at the exam room gemba, the receptionist should go to the surgery gemba, the kennel tech should go to the reception gemba, etc. 

After a few “walks”, I think it is important to schedule an additional period of group reflection (hansei). Did you discover something you weren't expecting? How did your idea(s) of how processes were occurring compare with reality? Did you find some opportunities for improvement (kaizen)? Were you able to see your value stream from your client’s point of view? How would your staff change things? Why? Use the Socratic method of teaching by asking questions, so everyone deeply understands, learns to think and create ideas for solutions.

“Gemba walks” are an easy, inexpensive, enlightening experiment into the Lean culture.  Schedule them at your gemba, and then be sure to share your experiences with the rest of us by adding a comment to this post.

Wednesday, March 16, 2016

Benchmarks

Toyota has long been very generous in allowing other organizations serious about beginning a Lean initiative (even competitors!) access to their Toyota Production System, even to the point of mentoring these companies as they attempt to implement a Lean initiative. See how their TSSC group does this with suppliers and non-profit organizations.

However, Toyota has been very forthright in stressing that the TPS that works for them may not be the form of TPS that is right for others. They are very careful to help these companies find the particular form of TPS that will work best in that industry, organization and culture. The tools can be extrapolated, but the goals, processes and outcomes will be unique.

This brought to mind the use of industry benchmarks, especially for a practice that is embarking on the unique journey of Lean. Are they useful?  Should the performance of others set  the goals for a Lean veterinary initiative?  Should they represent the future state aims and goals? Could those benchmarks actually set limits to our own progress?

Every practice is different, with unique visions, talents, clientele, resources, floorplans, etc.  The tools and specific methods that work for one might not be right for another (but the philosophy is very transferrable). The goal to a Lean thinker is to be better tomorrow than you are today; to get closer and closer to perfection or your ideal state, not just an industry benchmark. Besides, with a culture and mindset of kaizen, a Lean practice will probably leave these benchmarks “in the dust.”

So, in my mind, it is more important to focus on your particular practice processes. Concentrate on closing the gap between your current state and future state using the PDCA / PDSA cycle (blog on PDCA/PDSA), kaizen and continuous improvement (blog on Kaizen).

Also, a Lean practice will come up with Key Performance Indicators (KPIs) and benchmarks that are unique to this mindset, such as Door-to-Doc time, Doc-to-Discharge time, # of kaizens submitted per staff member per month, # of kaizens completed, etc.

The competition (or the goal!) is not the hospital down the street, it is yourself. Strive not to emulate, but to innovate and experiment...and learn!  This takes effort, creativity, and persistence. If you can find that... the rest will take care of itself. 

Tuesday, March 8, 2016

Introducing Lean to the Texas Veterinary Medical Association Conference 2016

Mark Graban and I had the pleasure of presenting a two and a half hour lecture introduction to the Toyota Production System, Lean, entitled "What Veterinary Medicine Can (and Should) Learn From Toyota," at the 2016 TVMA Convention and Expo, held March 3-6 in San Marcos, Texas.

Although the convention was small, compared to regional and national conventions, and primarily a working meeting for the different TVMA committees, we had about 40-45 attendees. Everyone appeared truly interested and engaged. In fact, everyone returned to the lecture after the break, which was very good sign.

As mentioned, the lecture only lasted two and a half hours, which was a real task,  as the material to cover, even for a basic introduction to Lean, could have easily filled four hours or more. But, we got through all of the material with time left at the end for a short Q and A session.

Responses and feedback after the lecture were very positive, such as, "I wish my practice manager could have been here" and  "I wish I had this information years ago."  One practice owner caught me in the exhibits hall and said the information was "an epiphany. " Really, an epiphany?  Well, who am I to argue!  I felt the same way when I first discovered Lean, so I definitely understand.

The material presented included topics such as value, value streams, "pull" systems, kanban, Just in Time philosophy,  flow, visual management, and problem solving. The written notes published in the Proceedings totaled 16 pages and, in fact, form most of this blog's posts to date.

All and all, Mark and I were extremely pleased with this "experiment" of working together and introducing the Toyota Production System to veterinary medicine. Both of us have strong feelings concerning the positive effect Lean could have on our profession, and are ready, willing and able to teach more veterinarians and staff in the future.

Here is Mark's post about this at www.LeanBlog.org.

Monday, February 29, 2016

Kaizen

Kaizen is a Japanese word that can be translated to mean “good change,” “change for the better,” or “continuous improvement.” The methodology strives for, as Masaaki Imai says, “everybody improving, everywhere, and every day.” Toyota says the two pillars of its “Toyota Way” management system are continuous improvement and respect for people. These go hand in hand, as we are driven to improve because we respect our clients, staff, suppliers, and other stakeholders. A practice can achieve a culture of continuous improvement only by respecting and engaging everybody in improving and redesigning the way work is done.

It’s tempting for people to dream up large, expensive improvements. “We need to expand our parking lot” or “Give us better health benefits” might be two things suggested by employees. In a kaizen model, we are focused on small problems that we can solve within our span of control. Doctors and practice managers can ask staff to speak up about small problems that they encounter during the day - frustrations, annoyances, causes of delay and rework - and then ask for their ideas or “countermeasures” that could reduce waste or making things better in the practice. No idea is too small to be considered in the practice of kaizen. In fact, starting with small ideas can be a very effective way to get the process of culture change under way.

Kaizen improvements often involve low-cost and low-risk changes, putting “creativity before capital.” It’s not to say money should never be spent, but throwing money at problems or just asking for more resources doesn’t always solve problems in a sustainable way.

A kaizen process, it should be noted, is not managed like a traditional suggestion box system. Suggestion box systems have been dysfunctional for a number of reasons, including suggestions sitting in a box for weeks or months, a vast majority of ideas being rejected by management, and a disconnect between identifying suggestions and implementing them.

In a kaizen process, we start with a problem or opportunity statement followed by an idea, rather than starting with a solution. The role of management shifts from accepting and rejecting ideas to collaborating with staff to find a countermeasure that can work - solving the problem or, at least, making things a bit better. If an initial suggestion is impractical or too expensive, a practice manager should work with the employee and team to find something else to try. In a suggestion system, managers might get overburdened by having to implement everything themselves. In a kaizen process, staff and veterinarians play a major role in testing and evaluating ideas - but the practice needs to find ways to make time for improvement work.

In a simple and effective kaizen process, as explained more fully in the book Healthcare Kaizen, we follow five high-level steps:


  1. Find opportunities for improvement
  2. Discuss them with others
  3. Implement or test the idea (following the PDSA model)
  4. Document the before and after in a simple way
  5. Share what was implemented with colleagues and other offices


People everywhere can be creative, and that’s true in every role. With kaizen, we understand that the people doing the work are the experts in that work. Sure, managers and improvement specialists can play a role, but that role is more of a coach and facilitator instead of telling people what do. Creating a culture of continuous improvement requires the right leadership mindsets and behaviors.

In one practice the authors visited, an employee was cut badly by a sharp edge on a cabinet. Staff said that, on about 12 previous occasions, an employee had a minor scrape caused by that cabinet. In a kaizen culture, somebody would have spoken up to point out that problem, long before a serious injury occurred. Instead of downplaying the risk or saying “Well, don’t touch that edge,” a practice manager in a kaizen culture would work with staff to implement some countermeasure, such as putting a foam piece over the edge, that would reduce the risk of injury.

In a kaizen model, this problem and idea would be written down on a simple, standardized card. The card would be displayed visually and transparently on a bulletin board. The idea would be discussed informally or in a team huddle. Ownership would be assigned to an employee or small team, and they would then update the status of the improvement on the card. As improvements are implemented, if successful, protocols would be updated as needed and a simple “before and after” summary would be created and shared across the practice. In larger organizations with multiple practice locations, the “cloud” or software systems could be used to share and spread ideas more widely. If a practice in Dallas finds a problem and solves it, the other practice location in Fort Worth might benefit from seeing what was done. Sharing and spreading ideas can help prevent each office from having to reinvent the wheel. Or, seeing the ideas implemented by others might inspire our own.

Our view is that a practice with a solid culture of continuous improvement, along with simple methods for facilitating and tracking ideas, would outperform clinics where staff and doctors are told to just show up and do their jobs. As Toyota and Lean healthcare organizations say, “Everybody has two jobs... to do the work and to improve the work.” Kaizen will lead to better client service and outcomes for patients, a better workplace, and better financial results for the practice owner.

Read more in the book Healthcare Kaizen by Mark Graban and Joe Swartz.

Thursday, February 25, 2016

A3 Reports

A3 reports are the written documents that succinctly record the PDCA cycle problem solving effort, often providing a bit more structure than the four steps. The thought process and steps are very similar to the Practical Problem Solving method. This is sometimes called “A3 thinking.” The PDCA thought process is more important than the specific A3 report format.

The name A3 comes from the international size of paper that’s approximately 11 by 17-inches (in landscape orientation) traditionally used by Toyota and Lean organizations for these reports.

The left side of the A3 is for the Plan step of PDCA. It should include a title, a statement of the problem and a description of the current state. This side is filled out with such information as facts, graphs, charts, key performance indicators, value stream maps and 5 Whys root cause analysis, to name a few. The fact that the Plan step takes close to fifty percent of the entire report is an indication of the importance Toyota places on planning.

The right side of the document contains the Do, Check and Act steps of the cycle. This side might contain the implementation plan (along with the “who”, “what”, “where”, “when” and “how”), the future state value stream map, a short cost/benefit analysis, the result of the implementation plan, the root causes that were eliminated (or not), the changes in policy and procedures (the new standardized work) and a date to revisit the issue in order to continually improve.

Tuesday, February 23, 2016

Lean Veterinary Articles on DVM360

We've written a few introductory articles on the DVM360 site:

Cut the fat—get Lean

VETERINARY ECONOMICS - Mar 01, 2015
What Toyota has to teach veterinary hospitals.


Growing the Lean veterinary practice

VETERINARY ECONOMICS - Mar 06, 2015
Dr. Chip Ponsford explores how to "tend" your veterinary practice in order to harvest an efficient, successful business.

Put the Lean concept into action at your veterinary practice

VETERINARY ECONOMICS - May 21, 2015
Begin and maintain this system's philosophy to make your practice more productive and efficient.

Check them out!

Monday, February 22, 2016

PDCA (PDSA) Cycle

We're all familiar with the diagnostic and treatment process. First, we collect as much subjective and objective data as possible. Then, we formulate the tentative diagnosis. Next, we test our diagnosis by prescribing a series of drugs, surgeries or other treatment modalities. If the patient responds, then we continue the course, usually at home with drugs we dispense and instructions for the client. If the patient does not respond, we seek new data and/or formulate a new treatment plan and try again. This process is based on the scientific method of problem solving.


When we have a problem or a question, we design an experiment, we evaluate the results and then we formulate a conclusion. The PDCA cycle is also based on the scientific method. It stands for Plan, Do, Check and Act. It is the Lean method of diagnosing and treating problems at the gemba. 

Created by Walter Shewhart at Bell Labs in the 1930s, it was introduced to post World War II Japan by W. Edwards Deming. It is also known as the Deming Cycle or the Shewhart Cycle. (Some refer to it as the PDSA cycle; Plan, Do, Study, Adjust).

Everyone at Toyota, from executives to managers to floor workers, is taught, understands and utilizes the PDCA cycle. It is a methodology to deeply understand the reasons of the problem(s); to discover what is known and what is unknown. It helps to propose and test countermeasures based on workplace observation, data collection, and consensus from all stakeholders and to evaluate the results of the test. In many workplaces, people “know” the solution and are afraid to (or are unwilling to) admit that their solution didn’t really work out in practice. The PDSA process emphasizes learning both on an individual and an organizational level, and continually improving systems and processes. It requires humility and a scientific spirit - again, one that should be familiar to those in veterinary medicine.

Plan
The plan step involves the critically important step of defining the problem. Instead of talking about problems in an office or conference room, this step should take place at the gemba as much possible, with all stakeholders present, so the problem may be observed where it occurs, when it occurs, and as it occurs. It is also during this step that any other data such as costs, charts, statistics, 5 Whys analysis results, current value stream maps, etc. are presented.

Based on all of this information, a team might propose some potential countermeasures to discuss, test, and evaluate. 

Do 
In the do step, we do an initial test of the proposed countermeasures as small experiments of change. If we have an idea, we might test it first in one exam room or one office, instead of rushing to implement something throughout the organization. Doing a small test of change helps mitigate and minimize risk. That way, if the change we test turns out to not actually be an improvement (or if it creates unintended side effects), less harm is done. If the initial test of change is promising, we can move forward in the area and spread the improvement to other areas.

Check (Study) 
At this point in the cycle, we evaluate the initial results of our countermeasures and compare them with our hypotheses and expectations. Did we accomplish our objectives or fall short? Were there any unexpected results? What did we learn along the way?

Act (Adjust)
If the results are positive, then we can more formally implement the new changes, write new standardized work, train others, and sustain. If the results have fallen short, adjustments are made, and the PDCA / PDSA cycle is repeated with new countermeasures.

Saturday, February 20, 2016

Root Cause Problem Solving and The 5 Whys

Do you ever feel like you’re playing a game of “Whack-A-Mole?” The same problems, previously thought to be solved, keep popping up in different areas of your practice at different times. One of the reasons may be that the root cause of the problem has not been identified and dealt with effectively. Lean offers a number of solutions to this situation.

Toyota uses a method called “Practical Problem Solving” or 8-Step Problem Solving, that provides a structured way to investigate and solve problems.

These steps are, as mapped to the PDSA cycle:

Step #                      Step                         PDSA Phase
1                  Clarify the problem              Plan
2             Break down the problem
3                   Target setting      
4               Root cause analysis
5          Develop countermeasures
6       See countermeasures through        Do
7  Monitor the results and processes      Study
8   Standardize successful processes      Adjust

In step 4, one method for root cause analysis is called “The 5 Whys,” which suggests that you ask “why” five times, sequentially, in order to find the root cause.
Why does that problem occur? Why is that? We keep drilling down deeper, rather than just answering the original why five different ways.

The number five is somewhat arbitrary - it’s not always five whys that are required. The idea is to ask enough times to get to a root cause or causes, to get beneath the surface of a problem. Once suspected root cause(s) are identified, countermeasures can be tested and, if they are effective, standardized work can be updated or written to prevent recurrence. It is important that this take place at the gemba, where the problem occurs, with all stakeholders present in order to build consensus about an appropriate countermeasure to test.  If, at this point, you continue to have recurrences of the same problem, then it’s possible that the correct root cause was not identified, or there’s a different root cause this time, or standards that have been put in place are not being followed.

For example, at a large animal veterinary clinic, there was a hydraulic rotating machine that was used to turn cows on their side for treatment. One day, there was some hydraulic fluid on the ground near the machine. The tech noticed this and, instead of just cleaning up the grease, she stopped to investigate. We can start asking why:

Why was there fluid on the ground? Because the hydraulic cylinder had stopped working.
Why had the hydraulic cylinder stopped working? Because the filter was clogged.
Why was the filter clogged? It had not been changed in a long time.
Why hadn’t it been changed in a long time? There was not a standardized work method for doing so. 

There were not clear roles and responsibilities, nor was there a standard changing frequency.
So, instead of just putting out the fire and replacing the filter, a Lean organization would look for a more systemic cause and countermeasure. Not having standardized work could have caused the machine to fail in a catastrophic way, possibly harming an animal or a tech. Just replacing the filter would not have fixed the process in a root cause to prevent the same problem from occurring in the future. Asking “why?” and digging deeper allowed the tech and engineering to come up with a better solution.


Wednesday, February 17, 2016

Visual Management

5S is just one example of a Lean concept called “visual management.” We can also think of visual management as a form of “standardized work” for everyone in the practice.

As explained in the book Lean Hospitals (3rd edition), the goal of visual management is to make waste, problems and abnormal conditions readily apparent to employees and managers. As Fujio Cho, honorary chairman of Toyota says, “One of the worst situations… is not being able to tell whether things are standard or out of standard (normal or abnormal).” Our aim should be to expose problems so they can be fixed, as opposed to the old approach of hiding problems to make things look good. Jamie Bonini of the Toyota Production System Support Center organization says, "The ideal is to be notified of any abnormality immediately and to solve problems as they occur, while the situation is still fresh."

Visual management has two main tenets: first, make problems or status visible; and, second, manage those situations, reacting as needed in the short term and solving root causes of those problems over the longer term. Even before Lean, healthcare organizations might put multi-colored plastic “flags” up in the hallway outside each exam room. These flags, if used consistently by staff, can provide a clear visual indicator that answer questions such as, “Is there a client in that room yet?” or “Where does Dr. Y need to go next?”

While visual management is ideally used for real-time decision making and problem solving, Lean organizations tend to also post performance measures (or metrics) on the wall for everybody to see. Understanding the performance of a practice (in areas such as safety, quality, patient satisfaction, or financials) can help everybody focus their kaizen improvement efforts (as described later). Posting metrics cannot become an exercise in blaming or just pressuring people to perform better. Everybody must work together to improve the systems and processes that lead to those results.