That day, the disastrous CPK report plunged the entire conference room into a dead silence for a full three seconds. The data showed that a certain critical process had a CPK of only 0.85, far below our internal requirement of 1.33. The boss's face darkened as he stared at me and said, "Ah Han, this batch of goods is about to ship, tell me what to do?" In that instant, countless nights flashed through my mind, spent chasing yield and fixing machines, without even eating dinner, only to end up like this. At that moment, I knew it was time to initiate a Kaizen Event.
The Day the CPK Report Came Out, the Room Fell Silent for Three Seconds
To be honest, those of us who have been in the factory for a long time fear this kind of situation the most: "looks like we're working hard, but the results are still very poor." Every day we patch things up, throwing resources at whatever problem arises, but there's never a fundamental solution. This is like your house leaking; you daily use a bucket to catch water but never thought about fixing the roof. A Kaizen Event, or "Improvement Activity," is actually about helping you fix the roof instead of constantly catching water.
Where the Problem Lies
Frankly speaking, many times we know where the problem is, but we "don't have time" to properly solve it. Or rather, the problem is too complex, involves too many departments, everyone has their own say, and it ultimately fizzles out. The core concept of a Kaizen Event is to bring all relevant people together within a short period, such as three to five days, to focus intensely on a specific problem, find the root cause from start to finish, and implement solutions. It's not about letting you hold empty meetings; it's about getting directly hands-on and implementing improvements.
How It's Actually Done
A Kaizen Event, in essence, is about solving problems "quickly, decisively, and accurately."
- Choose the Right Topic: This is crucial! Don't choose a grand question like "improve overall factory yield." Choose specific, small-scope, data-backed problems. For example: "Reduce wafer breakage rate in Process A from 0.2% to 0.05%." There must be clear objectives.
- Form a Team: Assemble representatives from all relevant departments—from process, equipment, quality control, and even production line leaders must be involved. Ensure their active participation, not just nominal involvement.
- Define the Problem and Objectives: For instance, our problem with CPK 0.85 at the time was due to excessive variation in a certain parameter. Our objective was to increase the Cpk of this parameter to above 1.33 and reduce DPMO from 6210 to below 1000.
- Root Cause Analysis: Utilize tools like 5 Whys and Fishbone diagrams to step-by-step identify the true root cause of the problem. Don't just stay on the surface; dig deeper. I recall one time, we found low yield was due to equipment vibration, but digging deeper revealed it was due to a loose air compressor pipeline, which was not a process issue at all.
- Propose and Implement Solutions: This part is the most critical. Solutions must be specific and quantifiable. For example, adjusting machine parameters, modifying SOPs, training employees. Furthermore, these solutions are usually implemented directly during the event and verified.
- Tracking and Standardization: Improvement is not over once completed. The effects must be continuously tracked, and new best practices written into SOPs to make them a part of daily work.
Most Common Pitfalls
The biggest pitfall I've encountered is turning a Kaizen Event into "just another meeting." You gather everyone, but no one is prepared, or they lack the authority to make decisions, ultimately leading to aimless discussions. Another time, we chose a topic that was too broad in scope, resulting in it being impossible to complete in three days, everyone's morale plummeted, feeling it was just a waste of time.
So the key is that leaders must grant full authorization, enabling the team to make decisions and execute directly during the event. Furthermore, the chosen topic must be sufficiently focused, and the objectives clear enough to see results within a short period.
One Thing You Can Do Today
Identify a small problem your department most frequently complains about, then invite two relevant colleagues and spend an hour finding its "true culprit."
Article Category: Lean Production