Mar 6 2012
What is the role of a manager in leading the implementation of Lean?
This is the first in a series of questions I have received from the Spanish magazine APD (Asociación para el Progreso Directivo). My answer is as follows and, perhaps, your comments will help me make it better:
The answer is different for every level of management and every functional area. Let us just take two examples: the CEO and a production supervisor.
The decision to implement Lean should be made by the CEO, and he or she must be able to communicate it to the rest of the organization. The CEO needs to understand what is at stake for the company’s business. For example, it may be that the company must excel at manufacturing rather than outsource it because the risk to intellectual property would be too high, and, since Lean is the state of the art in manufacturing, it is the way to go… This is only one example, there may be other reasons. Whatever they may be, the CEO must understand and articulate them.
The CEO must also understand the extent of the task and be committed to seeing it through. It means having a staff that is equally committed and not backing off when individual projects fail. It means giving Lean implementation the priority that it deserves, as second only to shipping product. In particular, no other initiative must be allowed to interfere with it. For example, the implementation of a new ERP system does interfere with Lean in two ways. First, it drains needed resources, and second, it locks existing practices in place, making them more difficult to change. ERP should therefore be postponed until the company reaches an appropriate level of Lean maturity. The CEO must also personally visit project teams in actions and attend report-out sessions.
Production supervisors are at the opposite end of the management ladder, and combine direct access to production operators with the authority to command support from logistics, maintenance, quality, and other groups. This places them in a unique position to be effective leaders for Lean projects on the shop floor, and it behooves their superiors to make sure that they have the time to do it.
Kevin Hop
March 6, 2012 @ 8:57 pm
Another role of top management is in the organization structure. My experience has been that managing tomorrow’s job (lean improvement projects and activity) must be separated from managing today’s job (production).
If the decision by top management is to delegate this improvement management to the individual level – meaning that each individual in the company has roles in both areas and must manage tomorrow and today together – today will always win out. Tomorrow will fail. One of the Honda Way principles is that the current customer always has priority over the future customer. In the same way current production always has priority over future production.
So a key role of top management in the implementation of lean is to set up an organization structure which allows tomorrow’s job to maintain priority along with today’s job. There are different ways to do this. But the key is to separate the management of the two worlds. We do not separate the two worlds – gemba, gembutsu, genjitsu (3 Actuals) is still the foundational principle. We just keep the daily management of the today’s job completely separated from the daily management of tomorrow’s job.
One of the best ways to do this that I have experienced is to have a centralized Continuos Improvement (CI) type group which facilitates all the projects, activity and training, has a budget, has a small core of expert lean practitioners and then rotates production supervisors through the group on an semi-annual basis. Best of both worlds. The bring a needed balance to the CI group with their intimate knowledge of the processes and machines. It is a win-win for everyone.
The production supervisors learn lean by dedicating 100% of their time on tomorrow’s job for the 6 months. When they return to the floor to do today’s job they have deep understanding of lean and ownership. At the end of 3 to 4 years you have most of the production supervision “graduated” through the rotation. Then you start over again. A very strong and deep lean organization results.
The rest of the people in today’s job (team leaders and production associates) participate in the improvements and are fully trained and engaged in the lean implementation activity but are not burdened with the dilemma and struggle of prioritizing their work on a daily basis. They can stay focused on their number one priority of production while supporting the lean improvements that come into their areas.
Jos Visschers
March 7, 2012 @ 4:36 am
Comment in the Businessleaners.com discussion group on LinkedIn:
Kamran Ahmed Syed
March 7, 2012 @ 7:27 am
Comment in the PEX Network &I QPC… discussion group on LinkedIn:
Timothy Acker
March 7, 2012 @ 7:30 am
Comment in the PEX Network &I QPC… discussion group on LinkedIn:
Kerrie Rich
March 7, 2012 @ 7:36 am
Comment in the Lean Six Sigma discussion group on LinkedIn:
Ray Oglesby
March 7, 2012 @ 8:14 am
Comment in the Lean & Kaizen discussion group on LinkedIn:
The manager should lead by example always. He/She should thrive to be the center or the grounding in all lean thinking. Think of it this way the manager is like the center of a wagon wheel always there always strong and with out them your lean work will not roll.
Muhammad Ehsan
March 7, 2012 @ 8:17 am
Comment in the Lean & Kaizen discussion group on LinkedIn:
Michel Baudin
March 7, 2012 @ 8:30 am
@Muhammad Ehsan –
Your requirement of the manager to have “a complete understanding of the system” before starting is unrealistic, because such an understanding can only be obtained through implementation. There is no alternative to starting implementation with incomplete knowledge, using every project as a learning opportunity for the whole organization, including the top managers.
Also, a successful Lean implementation produces measurable economic results in a few months, as soon as the pilot projects are completed. This is not long-term.
Lee Peacock
March 7, 2012 @ 8:37 am
Comment in the Lean Learning Center on LinkedIn:
Jordan Breindel
March 8, 2012 @ 5:35 am
Comment in the Lean & Kaizen discussion group on LinkedIn:
Michel Baudin
March 8, 2012 @ 5:53 am
You are assuming that 5S is the easiest of Lean tools, and, I suppose, that organizations should start their Lean implementation with it. Much of the Lean literature says the same. In my experience, however, organizations that start with 5S never go on to anything else. Most fail at 5S and the few that succeed consider themselves Lean because they have 5S.
5S is assumed easy because it is not technical. If fact, it is the opposite. It is difficult because it is not technical. By comparison, tools like SMED or cells are easy to implement because they have a rich technical content.
To me, telling a company to start with 5S is like telling a kid with problems in school to tidy up his room. The room probably needs it, but the kid probably won’t do it, and it won’t solve the problems even if he or she does it.
Telling a company or factory where to start is the most important recommendation a consultant can make, and should be based on an understanding of the specifics of the business — products, technology, people, economic conditions. I consider a stock answer like “Start with 5S” to be lazy consulting.
Jordan Breindel
March 8, 2012 @ 10:10 pm
Comment in the Lean & Kaizen discussion group on LinkedIn:
Mohamed Gabr
March 8, 2012 @ 5:55 am
Comment in the Lean & Kaizen discussion group on LinkedIn:
Pat Wardwell
March 8, 2012 @ 6:00 am
Comment in the Northeast Shingo Prize Conference 2012 discussion group on LinkedIn:
Paul Wojtuszewski
March 8, 2012 @ 6:04 am
Comment in the Lean Six Sigma discussion group on LinkedIn:
Gabrielle Domenge
March 8, 2012 @ 10:06 pm
Comment in the Continuous improvement, Six Sigma, & Lean Group on LinkedIn:
Robbie Howarth
March 9, 2012 @ 9:59 am
Comment in the Lean & Kaizen discussion group on LinkedIn:
Michel Baudin
March 9, 2012 @ 10:24 am
If 5S were easier than other Lean tools, you wouldn’t see the remains of so many failed attempts to implement it, with grimy banners still hanging in the shop after 5 years. The problem with 5S that it is intrinsically something you have to do plant-wide or not at all. You cannot do it in one part of the plant and hope to make it stick. If it doesn’t stick, it is just spring cleaning with the first three S’s, not 5S.
The first reason it fails as a starting project is that you have to involve everyone. The second reason is that, in a traditional job-shop, the motivation is not there. If, as a machinist, you have been operating the same lathe for 15 years, you will perceive a shadow board for tools as just a means of making it easier for somebody else to learn your job. On the other hand, if you work in a cell and rotate between positions, you will have the need.
There is a difference between doing a 5S project, which is plant-wide deployment, and using shadow boards as part of a cell project. The proper timing for plant-wide projects involving everyone is not when you start but when you have done enough local projects to give the program the momentum and the credibility to pull it off.
Also, it’s 5S, not 6S. I see Safety as a whole other subject that does not belong in a list with the other S’s that are instructions to get rid of unnecessary items, have labeled postions for necessary items, etc. 5S does improve safety, but there is more to safety than 5S.
Jordan Breindel
March 9, 2012 @ 4:08 pm
Comment in the Lean & Kaizen discussion group on LinkedIn:
Robbie Howarth
March 10, 2012 @ 7:56 am
Comment in the Lean & Kaizen discussion group on LinkedIn:
Jordan Breindel
March 10, 2012 @ 7:57 am
Comment in the Lean & Kaizen discussion group on LinkedIn:
Emilio Clausen
March 10, 2012 @ 8:02 am
Comment in the Lean & Kaizen discussion group on LinkedIn:
Michel Baudin
March 10, 2012 @ 8:24 am
The idea that managers should focus on processes rather than results keeps popping up everywhere. In other words, it doesn’t matter if the patient dies, as long as the operation was performed according to the rules. This kind of thinking is common in large bureaucracies, but you rarely encounter it in start-ups.
The key question is: do processes exist for any purpose other than achieving results?
You seem to imply that all there is to Lean implementation is Kaizen events. What about all the parts of Lean that cannot be implemented through Kaizen events?
Can managers be expected to have the technical knowledge to train their people in Lean?
Is gathering data a role for managers?
Robbie Howarth
March 10, 2012 @ 11:31 pm
Comment in the Lean & Kaizen discussion group on LinkedIn:
Wesley de Souza Brum
March 13, 2012 @ 7:25 am
Comment in the Lean & Kaizen discussion group on LinkedIn:
Asbjorn "Ozzy" Larsen
March 13, 2012 @ 7:27 am
Comment in the Lean & Kaizen discussion group on LinkedIn:
Kokou Hermann Attiogbe, MBA/HCM
March 14, 2012 @ 8:55 pm
Comment in the APICS The Association for Operations Management discussion group on LinkedIn:
Kiran kashyap
March 25, 2012 @ 11:36 pm
The role of the manager in implementing lean would be:
1) To form a team of like minded people across various levels of hierarchy which will carry forward all the systems and procedures to the next leveldown the line.
2) To ensure the systems are not diluted due to change of members in the team.
3) If any team members are added, the manager has to ensure that the new team member is completely trained in all aspects of lean.
4) Train the trainers on continous basis to sustain systems implemented.
5) Involve process owners in implementation of lean and build owner ship.
6) monitor the developments on continous basis.
Role of Management in Lean (In Spanish) | Michel Baudin's Blog
June 30, 2012 @ 5:45 am
[…] What if the role of a manager in leading the implementation of Lean? […]