Case Study: The PCB Solder Crack That Cost Me Three

Last winter a Tier 1 customer hit us at 3 AM with PCB cracking during thermal cycling tests. The photo showed clean intergranular fracture along the solder pad. D3 containment cost over fifty thousand in overtime and freight. D4 took a full day building a fishbone across all six categories. The Material branch led to the breakthrough: the laminate Tg was 155 degrees versus the design requirement of 170. Under thermal cycling the inadequate Tg caused the epoxy to soften creating stress that propagated into cracks.

The biggest lesson: D2 precision is the highest-leverage activity in the 8D process. Our initial vague D2 gave D4 no direction. After refining to include crack morphology and environmental conditions the investigation had a laser focus. The failure has not recurred in eighteen months because we updated incoming inspection to require DSC testing on every laminate batch.

This experience taught me that D2 precision is not optional it is the difference between a week-long investigation and a month-long one. I now teach every new quality engineer to spend at least one hour writing and refining the D2 before moving to D4. The time invested in D2 is returned tenfold in D4 efficiency. Every quality department should have a D2 template that forces completeness of 5W2H data before the team is allowed to proceed.

The broader lesson applies to any quality investigation: invest in the problem description before investing in the root cause analysis. A well-written D2 acts as a compass for the entire 8D process. Every hour spent refining the problem statement saves days of investigation. Quality engineering teams should develop standard D2 templates that force completeness of 5W2H data including crack morphology descriptions and environmental conditions before the team moves to D4.

The fundamental principle I teach from this case is that a good D2 saves more investigation time than any analytical tool in D4. Every hour invested in refining the problem description returns at least ten hours of saved investigation time. Quality engineering teams should develop mandatory D2 templates that enforce completeness of 5W2H data including measurement details and environmental conditions.

What a Complete D2 Actually Contains

A D2 that survives contact with D4 answers 5W2H without ambiguity, and it does so in measurable terms. For this case the refined statement read roughly: intergranular fracture along the solder pad on the component side, observed after 300 thermal cycles between -40 and 125 degrees Celsius, on boards from laminate lots received in the previous quarter, at a rate of 2 of 40 samples, detected by cross-section rather than by electrical test.

That single sentence carries the crack morphology, the environmental conditions, the quantity, the detection method and the population. Compare it with the original D2, which said only that boards were cracking in thermal cycling. The first version could have pointed at flux, at reflow, at handling, at design. The second version points at the laminate.

A practical D2 template forces these fields:

• What — the defect in physical terms, with a photograph and a cross-section where possible.
• Where — board location, layer, pad, component reference, and the production line or cell.
• When — first occurrence, detection date, and the production window of affected lots.
• Who — customer, internal line, shift, and operator-independent factors such as machine.
• Which — lot numbers, date codes, supplier batches, quantity affected versus quantity inspected.
• How — the detection method and the test conditions that exposed the defect.
• How many — defect rate with the denominator stated, never a bare count.

Worked Example: From Vague to Measurable

Take the laminate finding and walk it through the numbers. The design requirement was Tg of 170 degrees; the suspect batch measured 155 degrees by DSC. Thermal cycling ran -40 to 125 degrees Celsius. Cross-sections of 40 samples showed 2 cracked joints, a 5 percent failure rate at 300 cycles. The customer's test protocol ran to 500 cycles, which is why their line saw failures we never saw in-house.

Once those numbers sat in D2, D4 had a bounded search space: laminate lots received in one quarter, one supplier, one Tg measurement. The fishbone still took a day to build, but the Material branch was confirmed by measurement rather than by argument. Without the numbers, the same fishbone would have generated a dozen plausible branches with no way to rank them.

Step-by-Step Checklist Before You Leave D2

1. Write the problem statement in one paragraph with no adjectives that cannot be measured.
2. Attach at least one photograph and, for fracture or joint defects, one cross-section.
3. State the defect rate with its denominator and the inspection method used.
4. Record the environmental and test conditions under which the defect appears.
5. List the affected lots, date codes and supplier batches, and the unaffected comparison group.
6. Confirm the containment from D3 covers every lot named in D2.
7. Have someone outside the investigation read the statement and describe the defect back to you.
8. Only then release the team to D4.

Common Failure Modes in D2 and How to Detect Them

• The symptom statement. "Boards are failing" describes a feeling, not a defect. Detect it by asking whether the sentence could apply to any product in the plant.
• The missing denominator. "Two failures" means nothing without the sample size. Detect it by scanning for a rate or a ratio.
• The single-condition description. If D2 does not say under what test or field conditions the defect appears, D4 will chase the wrong environment.
• The premature cause. Words like "because the supplier" belong in D4, not D2. Detect it by checking whether the statement asserts a mechanism.
• The untested comparison. Without an unaffected group, the team cannot tell what is different about the failures.

How to Verify the D2 Is Good Enough

The simplest test is the compass test: hand the D2 to an engineer who has never seen the case and ask which two fishbone branches they would investigate first. If their answer matches yours, the statement is precise. If they name five branches, it is still vague. A second test is the measurement test: every claim in D2 should trace to a record, a photograph or a test report. A third is the containment test: every lot named in D2 must appear in the D3 containment scope, and every lot in D3 must appear in D2.

How D2 Connects to the Neighbouring D-Steps

D2 inherits its scope from D3. Containment defines the population that D2 must describe, and a D2 that names lots outside containment, or misses lots inside it, signals a broken handoff. D2 feeds D4 directly: each measurable field in the problem statement becomes a branch to test or eliminate. D2 also constrains D5 and D6, because corrective actions must be verifiable against the same measurements that defined the problem. If D2 says the defect appears at 300 cycles between -40 and 125 degrees, then D6 validation must reproduce those conditions.

Investigation Details

The reflow oven profile had drifted over six months. Peak temperature at board center was 8 degrees below specification. This was caused by gradual heating element degradation. The weekly temperature check only measured oven edges, missing the center. Measurement location matters.

Corrective Actions

Replace aging heating elements, add thermocouples at five board locations instead of two, implement daily profile verification. Verified over 5,000 consecutive units with zero defects.

The Takeaway

The time invested in D2 before starting D4 is the single highest-leverage activity in the entire 8D process. A precise D2 acts as a compass that keeps the investigation on track. Every hour refining the problem statement returns at least ten hours of saved investigation time. Quality teams should develop standard D2 templates that enforce complete 5W2H data before the team moves to root cause analysis. I now teach this lesson to every new quality engineer: invest in the problem description before investing in root cause analysis. A well-written D2 acts as a compass for the entire investigation. Every hour spent refining the problem statement saves days of investigation time. This is the single most leveraged investment in the entire 8D process.