Apr 7 2013
The Truth about Lean Failures | Vivek Naik
See on Scoop.it – lean manufacturing
The truth is, most lean implementations are a failure over long duration.Some of them are the major causes, as identified by the people involved in the implementation. They may be the right or maybe these are just the symptoms.
In this post, Vivek Naik presents the results of a survey about the causes of Lean implementation failures conducted among the readers of his blog.
The respondents, of course, are not representative of anything except a self-selected subgroup of followers of a blog on Lean, but Naik, to his credit, asked open-ended essay questions like:
- What is your Biggest problem to implement lean in your organisation?
- What would help you overcome this challenges?
And he didn’t tally percentages of responses, which would not have been meaningful. What he does is simply list and categorize the causes that the respondents have put forward.
What I find striking in this list is that no one mentioned insufficient mastery of the engineering and management tools of Lean. ‘Lack of understanding” appears only under Culture. What about the ability to achieve SMED, generate heijunka schedules, or design a bonus system that supports improvement without turning employees into bounty hunters?
Along with the majority of Lean implementers in the US, Naik’s responders take the tools for granted. In that attitude, I see a major cause of Lean failures.
See on viveknaik.net
Aug 10 2013
Guidelines for Fast Lean Transformation | M. Zinser & D. Ryeson | HBR Blog
See on Scoop.it – lean manufacturing
One of the most common mistakes that companies make when embarking on a lean program is trying to do too much at once. These “boil-the-ocean” initiatives are long, costly and often end up stalling under the weight of their own…
Scoop It just brough my attention to this 2 1/2-year old article by BCG consultants Michael Zinser and David Ryeson. Their key point is that a successful Lean implementation must start with a small number of well-chosen, pilot projects, and I agree.
I do, however, part company with them on two other issues. First, they only speak the language of money, relentlessly bringing up costs, savings, payoffs, metrics and incentives. I understand that this language is familiar and attractive to top management.
The article only cites examples of improvements that have a direct economic impact, but there are many aspects of Lean for which the relationship is indirect. Scoring a goal in tonight’s game has a direct impact on performance; building a championship team doesn’t.
Which brings me to my second disagreement with the authors: there is no consideration in their article of the need to develop the organization’s technical and managerial skills. They are just assumed to be there.
Lean is about developing a team that is able to compete at the highest level in your industry. If you already have such a team, you are probably not looking to implement Lean. If you don’t have it, you can’t start projects as if you did. Instead, you have to focus on projects that your team can do today and that will start it on its way. The biggest payoff and the practically possible do not always match.
This perspective is missing in their guidelines.
See on blogs.hbr.org
Share this:
Like this:
By Michel Baudin • Blog clippings • 1 • Tags: Lean, Lean implementation, Management, Organization development, Strategy