Table of contents
Seeing a “Red Flag”
I took a tour of three different facilities in Juarez that were no more than 100 yards from each other. The facilities were all part of the same organization. These facilities were separate business units and they all had implemented their own “flavor” of CI (Continuous Improvement). This variation I saw in CI deployment methods was the red flag that led me to investigate another line of investigation to get to the potential root problem.
During my tour, I was particularly interested in the current Lean Six SigmaSix Sigma Definition: Six Sigma is a set of techniques and t... projects that each business unit was working on. What I found was a lot of redundancy in the LSS projects between facilities. There were many similar processes between each BU. These processes were experiencing the same problems, and each of the BU’s had their own individual LeanLEAN Definition LEAN is a production method aimed primarily ... Six SigmaSix Sigma Definition: Six Sigma is a set of techniques and t... Projects to resolve the same problems. None of the CI teams knew that the other CI teams existed or that they were working on similar projects.
When little (or no) alignment exists
I’ve seen this in many organizations that I have visited in my career. The CI deployment is pushed to the site or BU levelStatistics level A statistics level is the value of input in... and there is little to no communication nor alignment between the BU’s. In an organization with similar processes between BU’s or sites, this can lead to a huge wasteMuda (無駄, on'yomi reading) is a ... in resources. It also leads to different improvements implemented to resolve the same problem.
This is partly due to a CI deployment that was not well-planned, and, in many cases, starts because the initial deployment was not a corporate initiative. Many facilities start out Continuous Improvement at a facility level because that BU leader understood the value. After wins at the BU level, the wins become visible to the “C” level, and then the CI initiative gets picked up at a corporate level. The lack of understanding at the “C” level, of the organization part of the CI methodologies leads to a mandate that each facility implement using local sources to develop their own individual deployment. And this leads to it’s own variation which is outside the scope this article.
A Major Step to align CI Initiative
How do you start to align the CI initiative?: If you find yourself in the situation described above and you are not at the “C” level, you may find aligning BU’s difficult. There is one major step that you can initiate, and those in the “C” level will see the value in: implementing a central database for CI Project Data. If you are at the “C” level and you are starting the CI Deployment journey, then implementing a central database for CI Project Data is imperative.
When a CI project idea is developed, what should be your first thought? It should be: “have we solved this problem already?” A lack of a central repository for project information makes it very difficult to find that information, especially between BU’s that do not communicate. We like to use a system called “My Hawkeye.” We have worked with many of the Lean and Six Sigma Project Management Systems and have come to the consensus that “My Hawkeye” is the most effective solution, for a fraction of the cost of others.
A Turn Key System for Alignment
Watch this short YouTube video about the “My Hawkeye” PM system and judge for yourself. Let us help align your organizations CI initiative.
I agree that it would be important to recognize the comment and take action.I ‘m intrigued by Bea’s last suggestion using other tools and I have a question. Are we inviting the group to leave Action Learning and use a different approach altogether? I like many of the other suggestions especially the interventions that focuses on the group deciding on pace. I also like the intervention of using our standard approach on consensus on the problem. If the group is in the solution generating or commitment to action phase, then they reach consensus quicker. The question is a great one.
I do agree with why reinvent the wheel as long as we make sure its the right wheel. Ever too often I have seen it being misused. We got to make sure its the same car and not end up using a tractor tire on a car and forcing it to work. Have seen this all too many times hence all for it with first understand ur vehicle and make sure the wheel fits. 🙂
I agree with your assessment of the problem. Having a ‘Project Office’ or at least 1Black Belt who has responsibility f
…a Black Belt who has responsibility for overseeing and coordinating to share best practices and use Yokoten. Also Minitab has a new product this year, similarly to your Hawkeye, to allow a central repository for multiple project information and over 100 templates and tools. It is called Companion for Minitab.
I have seen this play out in mid-size companies as well.
Another issue that arises in smaller companies is the idea of starting up CI is started by a lower level manager or director. They hire a Black Belt (like myself) to start up a program, but go into cost cutting mode 1-2 months afterwards.
Because they don’t see million $ returns in the first 6 months of starting up a brand new program, they scrap the whole program and blame the Black Belt.
The real problem is that they were too disconnected to begin with and did not have C-Level buyin and support.