That Day When the CPK Report Came Out, Silence Fell for Three Seconds
I still remember one evening, A-Wen from Process and Xiao-Pang from Equipment and I were called into the conference room by the boss. A batch of products on the production line suddenly experienced a catastrophic yield drop, plummeting from the original 99% to below 90%, and the client was already fuming. The boss immediately demanded, "Where's the 8D report? D1 to D8, how far have you gotten?" We all looked at each other; D1 and D2 were written with great earnestness, and a lot of root cause analysis was included. But when D3 and D4 were presented, the boss read them and slammed the report onto the table. The entire room instantly fell silent, with only the sound of the air conditioning. The boss simply said, "This D3/D4, it's as good as unwritten!"
What Was the Problem, and What Exactly Should D3/D4 Contain?
Frankly speaking, D3 is "Define Corrective Actions," and D4 is "Verify Corrective Actions." Sounds simple, right? Our most common mistake is filling D3 with ambiguous statements like "strengthen personnel training" or "optimize machine parameters." Then, D4 would simply state "training completed" or "parameters adjusted." Please, if you submit a report like that, the boss certainly won't accept it, and the client will be furious.
So the key is that D3 must be specific and quantifiable actions. You can't just say "strengthen training"; you need to write, "For the issue of new hires misoperating SOPs, plan a two-hour practical training session and add an online test, requiring a passing score of 85% or higher." That's what specific means.
How to Actually Make D3/D4 Substantive?
For example, last time, our production line had a defect where the DPMO was originally 6210 but suddenly surged to 15000. After D2 analysis, it was found that machine parameters had drifted.
- How to Write D3?
* Correct Example: "For parameter X of Machine A, adjust the tolerance from ±0.5 to ±0.2; for parameter Y of Machine B, update the automatic calibration frequency from once every 8 hours to once every 4 hours, and upgrade the firmware version to 2.3.1 during the next maintenance." See, it includes time, action, and goals, doesn't it?
- How to Write D4?
* Correct Example: "After adjusting parameter X of Machine A, the DPMO of three consecutive batches of products dropped to 5800, and the Cpk value increased from 1.08 to 1.35. After updating the calibration frequency for parameter Y of Machine B, continuous observation over two weeks showed no abnormal fluctuations, confirming the effectiveness of the improvement."
In other words, D4 is not just about "was it executed?", but more importantly, "was it effective?" You must use data to prove that your improvement is effective, rather than just feeling good about it.
The Most Common Pitfall: Why D3/D4 Become Useless?
To be frank, many times D3/D4 cannot be written properly because D2 was simply not analyzed thoroughly enough. If the root cause analysis in D2 is only superficial, you won't know what to target with your remedies. For instance, we once had a client complain about scratches on product appearance. After extensive D2 analysis, it was concluded that it "might be improper operation." Consequently, D3 stated "strengthen training," and D4 stated "training completed." What was the result? The scratching problem was not solved at all, and the client was so furious they almost pulled the order. Only after further in-depth investigation was it discovered that a certain fixture had a design flaw, causing products to easily rub against it during transportation.
Therefore, simply put, the quality of D3/D4 largely depends on the depth of D2. If the root cause is not found, writing D3/D4 will merely be scratching an itch. You must pinpoint the "point" that truly affects the outcome for your corrective actions to be effective at a single stroke.
One Thing You Can Do Today
Next time you write D3/D4, please examine your corrective actions from three perspectives: "Goal, Action, Measurement."