How to avoid Lean & Six Sigma deployment mistakes


Organizations around the world spend impressive amounts of time and capital in training, consultants, books and other resources for learning and deploying performance improvement initiatives such Lean & Six Sigma. However, very few of these improvement programs actually produce significant and sustainable results. Studies show that the majority of Lean & Six Sigma initiatives failed to achieve their anticipated results despite the vast number of resources nowadays available.

What causes this large failure rate? What can we learn to increase our own odds of success implementing Lean or Six Sigma? 

Most of the available work addressing these questions provide superficial analysis offering lists of a number of reasons without actually understanding the root-causes for failure. In this article, I reflect on the underlying dynamics that cause well-intentioned and knowledgeable practitioners to fail when actually implementing Lean & Six Sigma.

What is the Lean & Six Sigma implementation failure rate?
Data shows that the majority of Lean & Six Sigma deployment, around 80 percent, efforts fail. 
  • A Bain & Company's survey in 2008 found that 80 percent of 184 companies responding claimed that "Lean Six Sigma efforts are failing to drive the anticipated value" and 74 percent said "they are not gaining the expected competitive edge because they haven't achieved their saving targets." (2) 
  • The 2007 IndustryWeek survey identified that "only 2 percent of companies who responded to the survey have fully achieved their objectives" and "74 percentage of the responding companies admitting that they are not making good progress with Lean" (3).
  • In an article entitled "Why Lean Programs failed", Jeffrey Liker and Mike Rother, citing the IndustryWeek survey mentioned above, stated "only 2 percent of the companies that have a lean program achieved their anticipated results."(4). An assertion that does not accurate reflect the actual IndustryWeek data (see reference 3). 

Regardless of the precise failure rate value, the key takeaway from these studies is that Lean & Six Sigma efforts fail significantly. If you are involved or will be in Lean or Six Sigma efforts read this post. It might help you.  

It is important to recognize that when Lean & Six Sigma initiatives fail, they don't abruptly disappear. Typically, these programs gradually fade away starved by the lack of resources. In some cases, their formal extinction is the official announcement of a new performance improvement initiative. In most cases, it is a slow process in which people are relocated little by little to other activities or eliminated from the organization.    

Lean & Six Sigma popularity  
Lean & Six Sigma are currently the most two popular performance improvement approaches worldwide. Their relevance can be recognized by measuring the market demand for Lean & Six Sigma professionals. In 2011, it was identified by The Avery Point Group (5) that "the combined demand for Lean and Six Sigma talent has almost doubled, rising by over 90 percent versus last year's recession levels." A much faster recovery than other occupations.

The reason given to this dramatic increase is that "companies are seeking Lean and Six Sigma talent as a way to help their organizations better leverage their performance during the ongoing recovery." Moreover, IndustryWeek (2007) identified that "nearly 70% of all plants in the U.S. are currently employing Lean Manufacturing as an improvement methodology."(3) In addition, recent large investments in applying Lean in leading organizations such GE (6) shows that industry leaders recognize their relevance as performance improvement methodologies.

Lean & Six Sigma have reached other industries beyond manufacturing including service sectors such Healthcare, Banking and IT. 

Lean & Six Sigma abundance supply
The abundance and quality of  resources available to learn and implement Lean and Six Sigma is impressive. For instance, a search in Amazon.com results in over 3,200 book titles related to Lean Six Sigma. Nowadays, top-notch organizations such the American Society for Quality (ASQ), Shingo Prize, Associations for Manufacturing Excellence (AME), Lean Enterprise Institute (LEI), Kaizen Institute (KI) among many others offer a large and comprehensive supply of training courses, videos, certifications, plant visits and professional services about Lean & Six Sigma. 

With all these abundance and diverse supply of Lean & Six Sigma resources, access to quality knowledge in terms of material and experts can't be a main reason for the large number of unsuccessful Lean & Six Sigma implementations.      




So far we have covered three key points:
  1. Lean & Six Sigma deployment failure is quite high around 80 percent. It is a real problem
  2. Lean & Six Sigma are the most well-know performance improvement methodologies. Leaders and large number of companies recognize their value.
  3. Lean & Six Sigma  resources are ubiquitously available. There is not lack of learning resources about Lean & Six Sigma.   
The list of common reasons for Lean & Six Sigma failure
A common approach for many lean practitioners is to provide a list of top 5 or 10 reasons why Lean & Six Sigma deployment efforts fail. Most of these lists include the follow reasons:
1. Senior management's lack of commitment/understanding of Lean or Six Sigma
2. Senior management's unwilling to accept that cultural change is often required for Lean to be a success.
3. Lack of Lean/Six Sigma skilled people in the right positions. (7)
4. The company has chosen Lean as their process improvement methodology when a different process improvement program -- or none at all -- would have been the better choice.
While these are great checklists, they do not really explain the interaction that really happen within an organization that make or break a Lean, Six Sigma or any performance improvement deployment. It is like stating "we must have air in your tires for your car to run properly". However, if you understand how air pressure relates to your tires and interacts on how you run your car, you can make better decisions when your tires are under or over inflated. In the same way, "senior management's lack of commitment" is an obvious reason for most performance initiatives to fail. However, the question here is "why would senior management not commit to continuous improvement initiatives?" If anything, I ask you to look into the interactions that affect your organization and the success of its performance improvement initiatives.

In my next post "Beyond the check lists for Lean Six Sigma failure or success", I would discuss the most common dynamics that really make or break a performance improvement initiative. Until then, the force be with you.  

Important note: The ideas above are built on my own experience and the experience and studies of outstanding practitioners such Jim Womack, Mike Rother, Nelson Repenning, Jeffrey Pfeffer, Robert Sutton and many others from MIT and Stanford. 

References:

What is the Auto Quality Matrix?

I learned about the Auto Quality Matrix from our friends in Kaizen Institute Europe. As any lean tool, you need to understand it in the context of a system instead of just copy and paste. Here some key points if you are interested on implementing it:

What is it?
A visual display of where the defect are created and where they are detected.

Why to use it?
It is part of a quality management system to quickly identify the source and prevent defects from moving downstream.

How to use it?

Here is an example:




Creating Leaner Value Streams: Are the pacemaker and the bottleneck the same?

When designing leaner value streams, one key step is to define where to locate the pacemaker. However, a common misconception is to believe that the bottleneck process is the pacemaker. While a pacemaker could coincide with the bottleneck process, they mean different things.

What is the bottleneck? 
The bottleneck is the constraint process in your value steam that defines your actual throughput capacity. The bottleneck will define if you can or cannot meet your customer demand.
For instance, if you have four processes as shown in the figure to the right, the bottleneck is process 2. Notice that the takt time is greater than the bottleneck. If the bottleneck cycle time (the highest cycle time in your value stream) is greater than the takt time, then we are not able to meet customer consumption. If it is lower, then you have overcapacity (waste).   
What is the pacemaker?
The pacemaker is the single scheduling point in your value stream. It sets the mix of products to produce in order to meet customer demand. Because it is the scheduling point, the pacemaker is then the point in which push flow starts and pull ends. 

So what is the difference?
The difference between pacemaker and bottleneck is about what question you are trying to answer:  
  • Can we meet customer demand? Answer this question by comparing the bottleneck throughput to the required throughput. In other words, we compare the takt time to every process cycle time, including the bottleneck process, to ensure that the consumption rate can be satisfied with the production rate.
  • Can we use flow in our value stream? Ask this question at each process, starting at the end of your value stream and going upstream, to identify the pacemaker. If the answer is not, then that specific process is the  pacemaker. 
In conclusion, bottleneck is about throughput while pacemaker is about flow and pull.
Working on the right problem at the right time
Value stream design not only requires to focus on the right problem, but also to do it at the right time and following the right order. Start with takt time to balance each of the processes, including the bottleneck, with two objective: (1) you are able to meet demand (enough capacity) and (2) remove unnecessary resources (too much capacity). Only when this first step is completed, you can focus on creating flow by setting your pacemaker.  

Why is the pacemaker important? 

By having only one scheduling point we stop overproduction as no more material will be released.  It is like putting only one "driver" and linking our processes so each of them run at the same speed instead of having several "drivers" at different speeds. With the pacemaker, our value stream  is not only simpler, but also less expensive (we only need one driver!) and creates less work-in-process (which could be related to the distances between each truck.)

Theory of Constraints and the Lean Pacemaker 
Here is an interesting link about TOC and Lean in which pacemaker and bottleneck are also discussed: http://lssacademy.com/2007/04/19/toc-bottleneck-versus-lean-pacemaker_19/ 

Kaizen Culture: The Secret to Sustained Success

Sharing this post that explores how Jabil has turned to a Lean manufacturing philosophy to sustain competitiveness and build a company culture focused on continuously driving out waste.

Jaime Villafuerte in Chihuahua, Mexico

Kaizen Culture: The Secret to Sustained Success
Posted on October 2, 2013
Published on Aim Higher, Jabil's blog

Changing the Organizational Behavior

Lean transformation is about turning “lean” behaviors into habits so people develop a new better way to do things. The key question is how to create these new habits? Here is an interesting post that I explain how to change organizational behavior:

Behaving Badly – Can Lean Continuous Improvement be Sustained?
Posted on October 7, 2013
Published on Aim Higher, Jabil's blog

Gemba walks versus Waste walks

After visiting several plants in Asia, not long ago, I found a lot of confusion among practitioners about why we do gemba walks, what really is, and how we should do it. Below is a summary of key points from practicing gemba walks for many years and from great lean practitioners such as Masaaki Imai, Jon Miller and others.

What is Gemba Walk?
Gemba walk is a "go and see" practice with aim to understand the current condition of your value creation process (value stream) with the purpose to develop the problem solving capabilities of your people.

Gemba walks shape behaviors based on at least four lean values or principles:
  1. Observe problems first hand (go and see)  
  2. Embrace scientific problem solving (PDCA)
  3. Focus on value streams
  4. Lead with humility (respect people intelligence)  
Gemba walks versus waste walks
It worries me that some lean practitioners are confusing gemba walks with waste walks. They are quite different. Waste walks purpose is to develop "eyes for waste". As Shigeo Shingo rightly stated “The most dangerous kind of waste is the waste we do not recognize”, a waste walk aims to recognize the waste by actually going to see the gemba with the help of a seasoned lean practitioner.
A great reference to learn more about waste walk and even to download a template is provided by LEI in the book "Perfecting patient Journeys": http://www.lean.org/common/display/?o=2222      
"The Seven deadly wastes" were created by Taiichi Ohno as he also recognized the challenges to help people see the waste within their own processes. However, Ohno's approach to develop "eyes for waste" was less walking and much more standing and observing.

Ohno's approach to Waste walks: Stand in the Circle
Ohno's approach makes managers to draw a chalk circle around and stand in to observe a process for hours without leaving the circle. Jeffry Liker in his book "The Toyota Way Field" describes this approach with a little more color: "members are left standing for eight hours or more before the sensei is satisfied that they have seriously seen the waste."  While it may appear a harsh approach, this exercise makes evident how difficult is to identify waste particularly in processes we are familiar with.
Jon Miller provides a little less harsh approach to Ohno's one in these two posts:  Give me 60 minutes and I'll give you a lean transformation and 101 Kaizen Templates: Stand in the Circle.  

Similarly, I use waste walks to teach managers how to identify waste in their processes and less about walking. In fact, I asked them to stand and don't walk at all.  

The purpose of gemba walk: Beyond waste hunting
The purpose of gemba walk is to understand the current condition of your value creation process (value stream) at four levels: purpose, process, people and problem solving.
  • Purpose: What customer's problem are we solving (value creation)? 
  • Process: How do our processes work?
  • People: How do our people work? 
  • Problem solving: How are problems identified and solved? 
Gemba walks are about continuous improvement which drives waste out of processes. However, it should not be about waste hunting at all. Gemba walks that focus on generating to-do improvement lists without developing the level of the problem solving, process and people do little to sustain or create continuous improvement. The wrong mindset will drive the wrong behaviors.
Jim Womack explains the purpose of the gemba walk: "...truly understand the value stream and its problems rather than review results or make superficial comments": http://www.lean.org/womack/DisplayObject.cfm?o=1869
Where:
Gemba walks must be done where the value is created: at the gemba.

How:
1. Select a particular value stream: start at the closest process step to your customer and follow the value flow backwards through different departments, functions and areas. Keep in mind that value creation process is a horizontal flow while most organizations are vertically structured
2. Invite every value-stream owner: employees, middle managers and leaders who are part of the value stream
3. Ask about: purpose, process, people and level of problem solving

A gemba walk is not the place or the time to fix problems, but to understand the level of problem solving. For instance, when walking throughout a value stream start by asking the following questions:
  • Is the TARGET condition at each process step understood?
  • Is the ACTUAL condition at each process step known? 
  • Do the obstacles/problems that prevent to reach the target condition identified?
  • Which obstacles are being addressed right now?
  • What are the next obstacles to be addressed later? 
  • Do learning and sharing is occurring?
Notice that above questions are not aimed to fix problems or suggest solutions.
Jon Miller proposes 10 practical rules to follow when leading a gemba walk: http://www.gembapantarei.com/2012/01/10_rules_for_good_gemba_walks.html
Who:
Every value-stream owner including leaders, functional managers, supervisors and all employees who are involved in the value stream.

When:
Frequency of gemba walks should increase for people closer to the value creation. Daily gemba walks must be part of daily management systems in order to understand the current condition. Middle and senior management should do it several times a year as a way to break silos and functional barriers and grasp the value creation process.