Why Are Missing Installations Still Unavoidable Despite Standard Operating Procedures? —— A Case Study of SOS Poka-Yoke Transformation in an Automotive Parts Company

1. Introduction: Clearly Written, Yet Inconsistently Executed

An automotive parts company that supplies components for braking systems has been implementing Standard Operating Procedures (SOS) for two years: each workstation is equipped with a standard operation ticket, detailing the cycle time, work sequence, and standard work-in-progress. Team leaders conduct work observations weekly, and new employees must memorize the standards before starting their jobs. However, the quality department remains frustrated — the client PPM remains high, and upon inspecting the returned complaint items, it is found that 80% of the issues are of the same type: missing washers, missing snap rings, and missing torque applications. It's not that the workers don't know how to do it; the SOS is clearly written, and they can all recite the steps. But once they return to the production floor, missing steps are like grass that grows back after being cut.

The quality department conducted a statistical analysis: within a year, 72% of the functional defects in customer complaints and internal nonconformities stemmed from "missing standard actions" rather than "not knowing how to do it." In other words, the problem lies not in the standards themselves, but in the fact that "people follow the standards but cannot ensure every step is executed." The company later spent eight months transforming the SOS for four critical processes — from "requiring employees to follow the standards" to "making it impossible to proceed without following the standards." This article provides a comprehensive review of this transformation.

2. Why "Writing Clearly" Does Not Equal "Executing Correctly": Human Reliability Has Limits

First, let's answer a question: why do steps still get missed when the SOS is written down to the action level?

Because SOS addresses "whether one knows how to do it," while missing steps occur when "one knows but fails to execute." Human attention is a limited resource: during the night shift at 2 or 3 AM, during peak seasons with continuous overtime, when production is interrupted by order changes, or when new employees are busy and confused — in any of these scenarios, maintaining action consistency through memory and self-discipline is unrealistic. A basic conclusion in human factors engineering is that any step that relies on "remembering to do it or forgetting to do it" will eventually be missed over a long production cycle.

More insidiously, work observations are often ineffective in preventing such issues. Team leaders observe one or two cycles, during which employees are fully focused and perform the actions correctly. However, once the observer leaves, fatigue and habits return. This company achieved 100% coverage in work observations, yet missing installations still occurred, for this very reason.

Therefore, managers must accept the fact that: SOS is the carrier of "prescribed actions," but its execution relies on people; as long as critical steps depend on human memory and attention, the quality baseline is unstable. To truly secure the baseline, it must be made impossible to make mistakes — this is the essence of poka-yoke: not checking if the actions are done correctly, but designing the system so that incorrect actions cannot be performed and missing steps cannot be overlooked.

3. Case Analysis: Three Steps to Transform SOS into "Impossible to Miss"

The company's transformation was carried out in three steps, each grounded in data and the production floor.

Step One: Extract the "Critical Steps List" from Nonconforming Data. The quality department created a Pareto chart of customer complaints, final inspection nonconformities, and after-sales data over the past year, focusing on four workstations in the assembly shop: brake caliper assembly (missing washers), snap ring press-fitting (missing or improperly installed snap rings), tightening station (missing torque applications), and bracket welding (missing weld points). For each process, they asked: "What are the consequences if this step is missed?" — missing washers affect braking performance and are safety-related defects; missing torque applications directly lead to customer complaints. After the assessment, the critical steps of these four processes were listed as "must be done correctly, no mistakes allowed" and included in the poka-yoke transformation scope.

Step Two: Select Poka-Yoke Methods Based on Failure Types, Not Just Equipment. The transformation was not simply about buying sensors, but about selecting appropriate poka-yoke principles for each type of "miss":

• Missing Torque Applications (Forced Function Poka-Yoke): Replace ordinary torque wrenches with electric tightening spindles equipped with torque sensors and interlocked with the tooling fixtures — if the torque does not reach the set threshold, the fixture does not release, and the part cannot move to the next process. Tightening data is uploaded to MES in real-time, ensuring traceability for each piece. Missing torque applications changed from "possible" to "physically impossible."
• Missing Washers (Detection Poka-Yoke): Install photoelectric sensors on the washer racks. If the employee does not take a washer, the green light at the workstation does not turn on, and the assembly action cannot continue. The washer racks were also redesigned to a "take one, replace one" quantitative delivery system to prevent shortages at the source. The assembly sequence was re-engineered to link washer retrieval with part placement, and any reversal triggers an alarm.
• Improper Snap Ring Installation (Detection Poka-Yoke): Add displacement sensors to the press-fitting station. If the press-fitting depth is insufficient, the equipment automatically alarms and locks, requiring re-pressing to clear the alarm.
• Incorrect or Reversed Installation (Physical Poka-Yoke): Redesign the tooling locating pins to be asymmetrical, making it impossible to install parts in the wrong direction. For two visually similar parts, install shape recognition sensors on the material racks to trigger an alarm if the wrong part is placed.

Step Three: Integrate Poka-Yoke Back into SOS, Making Standards and Devices a Unified System. This is the most easily overlooked but critical step. After the transformation, the company revised the SOS for the four processes: each critical step's operation instructions were supplemented with a "poka-yoke confirmation" section, detailing "what the poka-yoke device is, what its normal state is, and what to do if it alarms." The first article inspection now includes poka-yoke device effectiveness verification. Pre-shift inspections incorporate poka-yoke devices into the checklist, merging them with the TPM maintenance plan for the equipment. The work observation checklist also added a "poka-yoke device status" item — observers must not only watch the employee's actions but also confirm whether the poka-yoke devices are being bypassed or have failed. As the workshop supervisor put it: "The old SOS told employees 'you need to do this,' the new SOS tells them 'in addition to doing this, there is an extra layer of insurance watching you.'"

4. Results and Review: Poka-Yoke Is Not a One-Time Fix

In the twelve months following the transformation, the number of nonconformities due to missing installations in the four critical processes decreased by 92%. The client PPM dropped from an average of 38 per month before the transformation to less than 4, saving the company approximately 1.8 million yuan annually in rework, scrap, and claims costs. The total investment for the poka-yoke transformation of the four processes was about 400,000 yuan, yielding a return on investment of approximately 1:4.5. More importantly, the welding and tightening stations, with their traceable data, passed customer audits on the first attempt and secured a new project.

Two details are worth mentioning. First, poka-yoke devices also require continuous improvement: three months after the transformation, night shift employees found that the surface reflection of a batch of parts caused the photoelectric sensor to misfire, leading to three production line stops per day. The company did not simply adjust the sensitivity but treated it as a genuine quality issue, completing the loop by changing the detection method, updating the poka-yoke device ledger, and revising the poka-yoke instructions in the SOS within a week. Poka-yoke devices are also "devices" and can fail; they must be included in the same maintenance and improvement system as the product.

Second, a lesson learned: during the initial transformation, the interlock function at the tightening station slowed the cycle time by 6 seconds, leading some teams to want to "optimize" it out. The team leader temporarily bypassed the sensor with a mechanical method to keep the line running. The quality department immediately halted this practice, declaring "bypassing poka-yoke devices" a red-line behavior, and added poka-yoke device alarm rate statistics to MES — any workstation with an abnormal zero alarm rate is automatically flagged. The biggest enemy of poka-yoke is not malfunction, but "poka-yoke fatigue": with too many false alarms, employees want to bypass the system; thus, poka-yoke design must minimize false alarms, and management must monitor bypassing behavior. Both are essential.

In retrospect, the true gain from this transformation was not just a few sensors, but a set of principles: SOS addresses "how to do it correctly," while poka-yoke ensures "it cannot be done incorrectly"; SOS is the skeleton of the process, and poka-yoke is the lock. Any step that, if missed, could lead to significant issues and is difficult to detect, should be poka-yoked and integrated into the standard operating procedures.

5. One-Sentence Summary

No matter how detailed the standard operating procedures are, they cannot prevent a momentary lapse in attention. Integrating poka-yoke into critical steps and synchronizing it with the SOS ensures "impossible to miss," which is the true insurance for the quality baseline — poka-yoke devices, like standard operating procedures, require maintenance, improvement, and serious attention.

SOS addresses "how to do it correctly," poka-yoke ensures "it cannot be done incorrectly": integrating critical steps with poka-yoke devices and writing them back into the SOS ensures the quality baseline is not dependent on human memory and self-discipline.

Knowledge code: 5.3.2

Version: v20260827

Author: Quality Think Tank The Quality Think Tank is dedicated to providing systematic professional knowledge, methodologies, and practical tools to quality management practitioners, helping companies continuously enhance their quality capabilities.