![]() |
|
| Home > Methodologies > Kaizen | Search: | for |
|
Fast and Intense: Kaizen Approach to Problem-Solving
By Mark Price and Tim Williams Perhaps it was impatience with how long traditional projects take. Often it was an awareness of how hard it is for people to concentrate on improvement when they keep thinking about getting their work done. To some extent it was a matter of their innate respect for the people who do the work. For all these reasons, years ago the Japanese inventors of the Lean improvement systems came up with a different improvement model they called Kaizen. Kaizens (or blitzes, as they are sometimes called) are improvement events where people work only on improvement for a few days, up to a full week. In a traditional Kaizen project, the people from a particular work area come together with a few experts for four or five days straight and complete most or all of a DMAIC cycle on a narrowly targeted high-priority issue. ("We need to process loan applications faster.") The model has been so successful that this basic approach has been adapted to other uses such as service design sessions. Example of a Bank's Use of KaizenA major national bank started using the five-day Kaizen approach whenever it wanted to attack process speed and efficiency problems. The bank's Kaizen events all share four characteristics:
A Typical Kaizen ScheduleHere is a sample agenda which the bank uses for the five days: Day 1 is an afternoon spent training participants on topics that cover basic concepts related to the goals of the project. This could include teaching relevant Lean or Six Sigma concepts and reviewing relevant data. Day 2 is spent looking at the process with new eyes. Participants do a "unit walk," a tour of operations affected by the problem or situation being studied where they simulate being a work item flowing through the process. The group visits each portion of the process, where, because there is cross-functional representation, they have the opportunity to hear insights from someone who works in that area. The group creates a value stream map (a picture of the "as-is" situation) that captures the basic process steps, such as cycle times, number of steps, rework loops, queuing delays, work in progress (WIP) and transportation time. Day 3 is designed around clarifying problems and brainstorming solutions. The team re-organizes the value stream (on paper) or creates a "should" map that depicts how the process would need to function to solve the identified problems. The outcome includes developing action plans for implementing solutions or trial simulations for the next day. Day 4 is used to test the solutions, conducting a simulation within the operations if possible. The group quantifies the improvement if the proposed changes are implemented, using estimates of reductions in travel time, queuing time, work in process, number of steps, number of forms, and so on. Day 5 is when participants prepare and present their findings to the sponsor in a formal report-out session. Making It Work and the ResultsThe bank makes this model work by having its internal consultants (equivalent to Master Black Belts) partner with the manager/sponsor to pick problems that are extremely high priority, not only for that work area but also for the business as whole. This makes it much easier to justify taking people off their regular jobs. Also, the goal of the event is a little more modest than a traditional Kaizen. Instead of having solutions up and running full-bore after five days, teams are expected only to get through the simulation and piloting of solution ideas. The internal consultant will then assist the team with full-scale implementation. In the many Kaizens this bank has run, it has achieved results such as:
An Alternative Kaizen FormatWhile consecutive days of intense work is the ideal, some companies have found it impossible to pull an entire work group, or even a subset of a work group, off the job for the better part of a week. One company worked around this issue by using the following structure:
This alternative Kaizen structure works well in this company because:
Conclusion: Concentrating on CreativityKaizen events are a powerful improvement tool because people are isolated from their day-to-day responsibilities and allowed to concentrate all their creativity and time on problem-solving and improvement. Companies which use Kaizens have found they generate energy among those who work in the area being improved, and produce immediate gains in productivity and quality. About the Authors: Mark Price is a vice president with George Group and has led Lean Six Sigma deployments for Global 500 clients in service and product companies. He has been working with corporate teams to design and implement successful performance improvement programs for the last 16 years. He can be reached at mprice@georgegroup.com. Tim Williams is a Master Black Belt at George Group. He is experienced in applying Lean Six Sigma to the financial services industry to drive bottom-line results. He has assisted organizations in scorecard development, business review practices, and process improvement strategies. Mr. Williams has been a speaker at conferences for the Banking Administrative Institute and the Institute of Business Forecasting. He also contributed to the book Lean Six Sigma for Service by Michael George. He can be reached at twilliams@georgegroup.com. Reproduction Without Permission Is Strictly Prohibited Copyright Requests Publish an Article: Do you have a Six Sigma tip, learning or case study? Share it with the largest community of Six Sigma professionals, and be recognized by your peers. It's a great way to promote your expertise and/or build your resume. Read more about submitting an article. "The Bottom Line" Links
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Home | Discussion Forum | Event Calendar | Job Shop | |
| Link To iSixSigma | Rate This Page | Report A Problem | Free Content For Your Site | Submit Article For Publishing | |
| Terms of Service. �2000-2009 iSixSigma. All rights reserved. v3.0lb, 0.2 |
About iSixSigma � Contact Us � Privacy Policy � Site Map. |