Discipline 2 (D2) is the foundation of the entire 8D. In the words of Charles Kettering, "A problem well-stated is a problem half-solved." D2 uses the 5W2H framework to create a precise, data-driven "Problem Statement" that eliminates ambiguity.
1. The 5W2H Deep Dive
A professional D2 description answers these seven questions with specific data, not generalizations:
**Who**: Which customer reported it? Which operator was on the line? Which inspector missed it?
**What**: What exactly is the defect? Describe the physical failure mode in technical terms (e.g., "0.5mm radial crack at the P3 solder joint").
**Where**: Where was the defect detected? (At the customer? Final test? IPQC?). Where on the part is the defect located? (Top, bottom, internal?).
**When**: When was it detected? When was the part manufactured? This requires looking at shift logs and date codes.
**Why**: Why is this a problem? This refers to the specification. For example, "Spec requires >10kg pull force; actual batch tested at 4kg."
**How**: How was the defect detected? (Manual inspection, AOI, Functional test, or field failure).
**How Many**: What is the magnitude? Total suspect population vs. actual defect count. Calculate the PPM (Parts Per Million) to understand the severity.
Is/Is-Not vs 5-Why: Which Comes First?
One of the most effective tools in D2 is comparing the problem to what it is *not*.
**Is**: The crack appears on parts made with Tool A.
**Is Not**: The crack never appears on parts made with Tool B.
This comparison immediately narrows the investigation to Tool A's specific variables, saving the team weeks of unnecessary research.
3. Visual Evidence and the "Dossier"
A professional D2 always includes a visual "dossier":
High-resolution macro-photography of the defect.
CAD drawings highlighting the failure zone.
Comparison photos of a "Good Part" vs. a "Bad Part."
Marked-up schematics or circuit diagrams.
4. Consensus on the Problem Statement
Before moving to D3 or D4, every team member and the Champion must agree on the Problem Statement. If the description is "The motor is noisy," the team will fail. If the description is "Motor Model X-123 exhibits a 45dB high-frequency whine at 3000 RPM," the team has a clear target.