When the Fix Does Not Fix Anything
Corrective actions are among the most routinely misused tools in manufacturing quality systems. Not because teams ignore them, but because the structure of most corrective action processes rewards closure over resolution.
A defect surfaces. It is logged. A cause is identified, usually quickly, usually at the level of the most recent observable variable. An action is assigned. The form is closed. Production continues.
Six weeks later, the same defect appears in a different batch. The team is surprised. It should not be.
What Gets Logged Is Not Always What Caused the Problem
Root cause analysis under production pressure follows a predictable path. The anomaly is identified. Someone offers a plausible explanation: operator technique, a material lot, a tooling setup that looked different from the last run. That explanation gets documented. The corrective action addresses it.
What rarely gets asked is whether that explanation can be verified, and whether, if it is wrong, the action taken would have any effect on the next occurrence.
In cable and harness manufacturing, crimp failures are a useful example. A pull test failure is attributed to operator technique. The operator is retrained. The form is closed. But if the actual driver was tooling drift, a calibration interval that had exceeded its reliable range under production volume, retraining does nothing. The tooling continues to drift. The failure recurs. That is not a quality escape. It is a diagnostic failure.
The Recurrence Problem
This is the operational distinction between Lean as a functioning system and Lean as a compliance activity. Both produce corrective action records. Only one produces processes that do not generate the same failures repeatedly.
In an operation where continuous improvement is embedded in daily work, a recurring defect signals that the prior corrective action was insufficient, and the system is structured to recognize that. Root cause analysis follows a structured path. Actions are not just logged; they are verified against the next production run. If the defect recurs, the prior closure is reopened, not assigned a new number and treated as a separate event.
In an operation where Lean exists primarily in documentation, the escape gets a new corrective action entry. The root cause column is filled in. The problem persists. What changes is the paperwork, not the process that generated the failure in the first place.
What Regulated Customers Are Actually Auditing
ISO 9001:2015 requires corrective action processes to address root causes and evaluate the effectiveness of actions taken. That effectiveness evaluation is where most quality systems are weakest in practice.
Defense primes and medical device manufacturers audit for this specifically. They are not looking for a corrective action log with zero open items. They are looking for evidence that closed actions changed production behavior: whether similar defects recurred after closure, whether the root cause was verified rather than assumed, and whether production data from the subsequent run was reviewed as part of close-out.
The traceability that regulated programs require does not come from documentation alone. It comes from a production culture that treats recurrence as a system failure, not as bad luck.
What a Functioning Process Looks Like on the Floor
The behavioral difference is observable. In a mature operation, a defect triggers a question before it triggers a form: what process condition produced this output, and how do we know? Calibration logs, SPC data, and work instructions are reviewed before a root cause is named, not after the corrective action needs to be closed.
Managing process capability directly, through controlled inputs, calibrated tooling tied to performance data rather than fixed calendar intervals, and cross-trained assemblers following documented procedures, reduces the conditions that generate defects before they produce failures. Fewer defects means fewer corrective actions. And when a corrective action is required, the system has the data to make it stick.
At JEM Electronics, corrective actions are verified against subsequent production runs, not just logged and closed. Our Lean Six Sigma methodology and Green Belt certified team build continuous improvement into the production system, not onto it.
If you want to understand how our quality processes support supplier qualification and regulated applications, talk to an engineer.
JEM Electronics | Custom Cable Assemblies | Wire Harnesses | Electromechanical Assemblies | Franklin, MA | jemelectronics.com
