One Model Fixed, Others Still Failing? —— Revisit the Five-Step Method for Lateral Deployment

A car parts company supplies two models of a chassis assembly to two original equipment manufacturers (OEMs) on the same platform, using almost identical welding processes, raw materials, and suppliers. In the first half of the year, the A model's chassis experienced weld point separation at the client's site. The team worked overnight to identify the root cause, which was found to be welding current fluctuations exceeding the process window. They immediately adjusted the parameters and increased post-weld sampling inspections. The 8D report was approved and closed by the client, and everyone breathed a sigh of relief.

Three months later, the same weld separation issue erupted on the B model, causing the client's production line to halt for 6 hours. The quality manager, Mr. Zhang, immediately reviewed the 8D report for the A model and discovered that the corrective actions were only documented in the A model's work instructions. Both models shared the same supplier and the same welding parameter baseline file—no changes were made to the supplier's general process document, meaning the B model "inherited" the same latent risk. What made Mr. Zhang even more embarrassed was the client's SQE's question: "I approved the 8D for the A model. Where is your evidence of lateral deployment?"

Mr. Zhang searched through the archived documents and only found the phrase "lateral deployment completed" in the D8 section of the 8D report, with no records of investigation, difference analysis, or verification data.

This scenario is not uncommon in manufacturing. During client audits, "lateral deployment" is almost always a key question: Have similar issues been investigated in other products, other production lines, and other suppliers? Most companies' answers do not hold up to scrutiny. If lateral deployment is not done well, preventive measures only address one point, and the problem can reappear in another model, another production line, or another supplier. This article will explain the five-step method for lateral deployment: what to deploy, how to define the scope, how to prioritize, how to address, and how to close, ensuring that every 8D corrective action can "take flight" and reach all the necessary places.

1. Lateral Deployment: The "Second Foot" of Preventing Recurrence

Preventing recurrence involves answering two questions: Will the same issue reoccur at the same location? Will similar issues occur elsewhere? The former relies on vertical deployment, while the latter depends on lateral deployment.

Vertical deployment involves solidifying measures over time—revising standard operations, updating control plans, supplementing FMEAs, and installing error-proofing devices—to ensure that the same failure mode does not recur at the same location. This is what most companies do after an 8D.

Lateral deployment (also known as horizontal deployment) involves projecting corrective actions across all similar objects—other models, other production lines, other shifts, other suppliers, and other equipment families—investigating and addressing each one. To use an analogy: vertical deployment is like sealing the hole where the mole pops up, while lateral deployment is like checking the entire field to see if there are other holes that haven't been exposed yet.

Why is lateral deployment essential? Because issues are never isolated events but rather localized manifestations of systemic vulnerabilities. The same design platform, the same process document, the same supplier, and the same equipment family mean that defects are "contagious": if Model A exposes a problem, Model B is likely to have the same issue, just not yet triggered. The 8D addresses the "exposed point," while lateral deployment addresses the "unexposed points."

In the 8D process, lateral deployment is a core action in the prevention of recurrence stage and is a frequent point of inquiry in system audits like IATF 16949 for the effectiveness of corrective actions. Well-performing companies have checklists, records, and verification data for lateral deployment, ready to present when auditors ask. Poorly performing companies only have a vague "lateral deployment completed" in their 8D reports.

2. Five-Step Method for Lateral Deployment

Step 1: Define Deployment Dimensions, Avoid Relying on Feel

The first challenge in lateral deployment is "where to deploy." If the scope is too narrow, issues will continue to slip through; if the scope is too broad, it can lead to a complete shutdown and cost overruns. In practice, it is recommended to review each of the five dimensions:

Creating a checklist for these five dimensions, specifying "investigation object, responsible person, and completion deadline," and ticking each box during meetings can help. Mr. Zhang's mistake was that he only investigated "same model, different batches," missing the "different models on the same platform" and "different materials from the same supplier" dimensions—both of which were relevant to Model B.

Step 2: Translate Root Causes into "Search Features"

Lateral deployment is not about mass-distributing the 8D report and asking everyone to "self-check." Instead, it involves translating the 8D conclusions into searchable and comparable "feature words." Otherwise, different interpretations can lead to superficial investigations. Three types of features need to be translated:

• Failure Mode Features: Weld separation, incomplete welding, porosity, shrinkage, missing parts... Clearly describe the typical manifestations and judgment criteria of the defect.
• Root Cause Mechanism Features: Welding current fluctuations, abnormal material batches, lubricant residue, torque decay... This is the most critical basis for lateral deployment—mechanisms that are the same must be investigated, regardless of the distance; mechanisms that are different can be bypassed even if the objects look similar.
• Applicable Conditions for Measures: Parameter windows, inspection methods, error-proofing devices, training requirements... Clearly state the conditions under which the corrective actions are applicable, preparing for subsequent difference analysis.

For the A model case, the features can be translated as follows: Failure mode "weld point separation (0.8% incomplete welding rate)"; root cause mechanism "welding current exceeding the process window ±5%, combined with electrode wear"; measures "re-verify current parameters to the midpoint of the window, reduce electrode replacement cycle from 2,000 to 1,500 cycles, and add 100% visual inspection after welding." With this set of features, investigators can quickly compare any product using the checklist, providing an initial judgment in minutes rather than relying on impressions to say "it should be fine."

Step 3: Risk Assessment and Prioritization, Handle in Three Tiers

There may be many investigation objects, and efforts should not be evenly distributed. Score each object using three factors: severity of failure (S, how serious the failure consequences are), likelihood of occurrence (O, the probability of the mechanism recurring in the object, with higher scores for higher similarity), and exposure range (E, the number of batches/units involved). The composite score can be divided into three tiers:

• High Priority (High S×O×E): Immediate deployment, complete investigation and corrective actions within one week, such as objects on the same platform, with the same supplier and parameters.
• Medium Priority: Planned deployment, included in the monthly improvement plan, with clear responsible persons and deadlines.
• Low Priority: Registered for observation, recorded for review during the next change evaluation or annual audit.

Mr. Zhang's team scored and prioritized six investigation objects: Model B scored 72 points (immediate deployment), Model C on the same platform scored 54 points (immediate deployment), another bracket from the supplier scored 36 points (planned deployment), and three other products with significantly different structures scored 18 points or less (registered for observation). Once the priorities were set, the scope became clear: only two models required immediate and significant attention, while the rest could be handled systematically.

Step 4: Difference Analysis Determines the Approach

For each investigation object, a simple "yes/no" answer is insufficient. A difference analysis should be conducted: compare the design, materials, process, equipment, and environment of the object with the product that experienced the issue, and provide one of three conclusions:

The most common mistake is "ignoring differences." Differences must be proven to "block the mechanism" to be valid, not just "look different." The difference analysis for Model B is a good example: compared to Model A, Model B had an additional reinforcing rib at the weld point, leading some to claim "different structure, no problem." However, after a detailed comparison, it was found that the reinforcing rib did not affect the current path, and the failure mechanism still held—differences did not block the mechanism, so rectification was necessary. This judgment proved correct: the weld separation on Model B occurred at the same weld point.

Step 5: Verification and Closure, Embed Experience into the System

The closure of lateral deployment should not be marked by "measures issued" but should have three solid pieces of evidence: first, the investigation checklist is fully completed, with a disposition conclusion for each object; second, the corrective actions have verification data, such as the incomplete welding rate dropping from 0.8% to below 0.05% after rectification; third, no similar issues recur during the observation period (usually 3 to 6 months).

At the time of closure, the experience should be embedded into the system to prevent a reset when a different person or project is involved: supplement the failure mode and measures in the FMEA, update the inspection frequency and error-proofing requirements in the control plan, revise standard operations, update the supplier's general process document, and finally store the entire set of feature words and disposition records in the lessons learned database.

Mr. Zhang this time completed the full set: the supplier's general process document was revised and re-signed, the parameters for Models B and C were re-verified, and no weld separations occurred in the three-month observation period. The client's SQE, upon reviewing the complete investigation checklist and difference analysis table, signed off on the lateral deployment section.

3. Five Common Misconceptions

• Misconception 1: Treating lateral deployment as a "company-wide cleanup." Without setting boundaries, investigating all products and all production lines can lead to cost overruns and complaints. The correct approach is to define the scope according to the five dimensions and prioritize based on risk scores, focusing efforts on the most similar and dangerous objects.
• Misconception 2: Investigating only the same model, missing the same process and supplier. Even if the models are different, the same process documents and suppliers can still spread the latent risk. Mr. Zhang's mistake was in this area.
• Misconception 3: Relying on memory for investigations, not creating a checklist. Asking a round of questions in a meeting, "Does anyone think there's a problem?" and considering the investigation complete when no one speaks up. Without a written checklist and item-by-item conclusions, there is no evidence to present during audits, making the effort futile.
• Misconception 4: "Ignoring differences." Difference analysis is superficial, not verifying whether differences block the mechanism. Remember: differences are the basis for evaluation, not an excuse for exemption.
• Misconception 5: Writing only "lateral deployment completed" without an evidence chain. The five words in the 8D report do not earn client trust or prevent nonconformities in the next audit—investigation records, difference analysis tables, and verification data are all essential.

4. One Sentence Summary

Lateral deployment is the "second foot" of preventing recurrence: define dimensions, translate features, prioritize risks, conduct difference analysis, and verify closure. Follow these five steps, and similar issues will truly have nowhere to hide.

Solid lateral deployment ensures similar issues do not recur

Knowledge Number: 5.2.1

Knowledge code: 5.2.1

Version: v20260828

Author: QTank QTank is dedicated to providing quality management professionals with systematic knowledge, methodologies, and practical tools to continuously enhance corporate quality capabilities.