Defect Elimination
Defect Elimination
Squaring off
The top-down approach looks good in the early rounds of the simulation.
Teams are knocking out significant defects and rooting out the source of those
defects. Almost every team is successful and they all make a significant
contribution. But ultimately the short reach is its undoing versus the lower yield
but longer reach bottom-up approach. The hourly action teams are far less likely
to be completed successfully and even when they are, yield only 1/10th the
benefit, but they involve everyone. To understand the impact of this you need to
understand the nature of ownership. Ownership is defined as an employee’s
willingness to get involved in and initiate improvements. We measure it on a 0-5
scale with a 0 meaning that most people will actively resist improvement efforts
and a 5 meaning that most people will initiate improvements without
management prompting. The plant in the simulation is at an ownership level of 2,
which is pretty typical for the plants that we work with. This means that most
people will go along with improvement efforts if asked but are unlikely to initiate
them. From previous articles, you should already know the power of raising
ownership. Increasing ownership creates self-generating improvements, a desire
to find root causes and improved productivity. A move from 2-5 in ownership at
this plant is worth almost $150 million over three years. The best way to build
ownership is to give people a chance to have an impact and let them see their
results. Most people will be hungry for more when they get that opportunity. But
ownership declines over time if not fed. If you involve me today and get me
excited but then don’t give me another opportunity for several years, the
ownership that I gain slowly diminishes. This is where the reach problem hurts
top-down efforts. As we mentioned, at the very best, the top-down approach
impacts the ownership of 40% of the personnel in a year compared to 100%+in
the bottom-up approach (2 teams each person with a 55% yield). When the
ownership advantage kicks in and people start generating their own
improvements, finding root causes and working smarter, the bottom-up approach
takes the lead and never gives it up. Stated another way, the bottom-up
approach is a much more effective way of changing a culture even if it is not
quite as effective at eliminating specific defects. This is shown even more
dramatically if you turn off both programs after the first 3 years and run an
additional 3 years. The bottom-up scenario continues to improve due to the
imbedded culture change reflected in the ownership level while the top-down
approach slowly decays as the outside stimulus of teams is removed and
ownership begins to decline.
Post-fight wrap up
Western culture favors the top-down approach because we love the control
that it implies and because of the apparent advantages in terms of yield. We fail
to see the shortcomings of the reach. It would be a mistake to read this article as
an indictment of either RCM or Six Sigma. We believe and our dynamic
benchmarking shows both to be highly effective defect elimination approaches.
In fact, once ownership reaches a 4 on our scale, where many employees are
willing to initiate improvements, the top-down approach is preferable to the
bottom-up. To quote Jack Welch, “You couldn’t have Six Sigma without
Workout. You couldn’t put Six Sigma in a bureaucratic company doing
bureaucratic things. It would just have sunk it.” Our argument is that they lack
reach and in many cases fail to build the ownership necessary to make a
dramatic and lasting change. If you are using either approach or a similar
approach, the lesson from this article is to look for ways to extend the reach.
Involve more people in the implementation. One client we work with takes the
recommendations from an RCM as the starting point for action teams. Have a
simplified process for smaller problems. Use the top-down process for the big
defects and have some form of bottom-up approach for the small ones. In any
case, track your ownership and make sure that your program is moving the
needle on this critical measure.
1 1 Major Incidents