Glossary
8D problem solving is a structured methodology for resolving recurring or complex quality problems, originally developed by Ford Motor Company in the 1980s. It consists of nine steps: D0 (preparation) plus D1 through D8 (team, problem, containment, root cause, corrective action, implementation, prevention, recognition). 8D is widely used in automotive, electronics, and manufacturing; this guide covers each step with an apparel-industry worked example.
The 8D (Eight Disciplines) problem solving methodology is a team-based framework for resolving complex quality issues, especially those that recur or have unclear root causes. It was developed by Ford Motor Company in the mid-1980s and first published as the Team Oriented Problem Solving (TOPS) manual in 1987, and has since been widely adopted across automotive supply chains and beyond.
The 8D framework is more structured than ad-hoc problem solving and more team-oriented than purely procedural CAPA. The methodology emphasises rapid containment of the immediate problem (so it does not continue to harm the customer while the investigation runs), rigorous root cause analysis (so the corrective action addresses the underlying condition), and explicit recognition of the team that resolved the issue (so the organisation builds the muscle to repeat the discipline).
The discipline names changed slightly over the methodology's history. The original eight disciplines were D1 through D8; D0 (planning) was added in the late 1990s as part of Ford's Global 8D revision, making the modern framework technically nine steps.
Most practitioners still call it 8D because the core analytical work is in D1 through D8.
Each discipline has a specific purpose. The framework is sequential but iterative: insights from later disciplines often reshape the work in earlier ones.
Before forming a team, the organisation determines whether 8D is the right approach for the problem. Simple issues with obvious causes are better handled by basic CAPA; 8D is reserved for complex, recurring, or cross-functional problems that benefit from team-based investigation.
Assemble a cross-functional team with the technical knowledge, authority, and time to investigate the problem. Identify a team leader and a champion (a senior sponsor who removes barriers). Define team roles before the work begins.
Articulate the problem in clear, specific terms. Use Is/Is Not analysis to bound the scope: where the problem is observed, where it is not, when it started, when it does not occur. The problem statement is the foundation for everything that follows.
Protect the customer from the problem while the root cause is being investigated. Containment is temporary by design: quarantining affected batches, intensified inspection, customer notification. The 8D record explicitly distinguishes containment from corrective action.
Apply structured analysis to find the underlying condition. Common tools include the 5 Whys, the Ishikawa (fishbone) diagram, and fault tree analysis. The root cause is the specific underlying condition that, if changed, would have prevented the problem.
Choose the corrective action that addresses the root cause. Verify, before full implementation, that the proposed action will work and will not introduce new problems. This step uses pilot tests or simulations rather than full rollout.
Roll out the corrective action across the affected scope. Remove the interim containment from D3 once the permanent action is in place. Validate effectiveness through measurement: defect rates, customer feedback, statistical process control over a defined period.
Update systems, procedures, and standards so the underlying condition cannot return through a different surface symptom. Common preventive measures: updated training, revised procedures, design changes, supplier requirement changes. D7 distinguishes 8D from one-shot problem solving.
Formally acknowledge the team's contribution. This is not ceremonial; recognition reinforces the discipline of completing 8D properly and signals to the organisation that structured problem solving is valued.
Within the eight disciplines, several analytical tools are used repeatedly. Understanding these tools is the difference between completing the 8D template and actually solving the problem.
A questioning technique where the team asks 'why?' five times in sequence to drill from a surface symptom to a root cause. The first 'why' is the symptom; the fifth 'why' typically lands on a systemic condition. Five is a heuristic rather than a fixed rule; the team continues until they reach a level they can act on.
A visual tool for organising potential causes of a problem into categories. The standard categories are the 6 Ms: methods, machines, materials, manpower, measurement, mother nature (environment). The diagram makes brainstormed causes visible and groups them so the team can pursue the most likely category first.
A structured comparison of what the problem is and what it is not, across four dimensions: what, where, when, who. The pattern of differences narrows the scope dramatically. If a defect occurs only on a specific shift, with a specific operator, on a specific machine, the Is/Is Not table makes that pattern visible.
A top-down deductive method that starts with the undesired event and works backward through the logical combinations of causes that could produce it. More common in safety-critical industries (aerospace, nuclear) than in apparel, but valuable for complex failures.
A frequency-ranked view of contributing causes, typically showing that 20 percent of causes produce 80 percent of the effects. Useful for prioritising which root causes to pursue first when several contribute.
Consider a sporting goods brand receiving complaints about delamination on a technical outdoor jacket: the laminated membrane between the outer fabric and the lining is separating after 4 to 6 months of normal use. The complaint rate is rising; multiple production batches are affected.
D0. The quality director confirms 8D is appropriate. The problem is complex, cross-functional (manufacturing, materials sourcing, customer service), and recurring; basic CAPA will not produce the required depth.
D1. The team is formed with representatives from product development, materials engineering, the manufacturing partner's quality lead, customer service, and the warranty operations team. The team leader is the apparel category quality manager; the champion is the head of product quality.
D2. Problem description: 'Laminated outdoor jacket SKU 12X-447, produced between January and April 2026, exhibits membrane separation at the underarm and lower-back seam regions after 4 to 6 months of normal use. The defect appears in 0.8 percent of units sold during this period.' Is/Is Not analysis confirms the defect does not appear on earlier production batches, on different SKUs using the same membrane, or in lab accelerated-wear tests.
D3. Interim containment: the brand suspends sales of remaining stock from the affected batches and offers proactive replacement to customers who have purchased the SKU.
D4. Root cause analysis through 5 Whys and Ishikawa. The root cause traces to a change in the seam-sealing adhesive supplier's formulation, made in November 2025 without notification to the manufacturing partner.
The change reduced the adhesive's resistance to repeated flexing under moisture conditions.
D5. Corrective action verified: revert to the previous adhesive formulation for current production. Pilot on 200 units confirms membrane integrity under accelerated stress testing.
D6. Permanent corrective action implemented: the previous formulation is locked into the materials specification, and supplier change notification requirements are added to the contract with the manufacturing partner.
D7. Prevent recurrence: the brand implements a materials change-notification protocol with all manufacturing partners, requiring 90 days advance notice and pre-approval testing for any change to specified materials.
D8. The team is formally recognised by senior leadership; the learnings are shared across the wider quality organisation.
Several 8D variants exist. Global 8D (G8D), which Ford developed in the late 1990s, is the revision that introduced the D0 gateway step — including emergency response actions to protect the customer before the formal process begins — and added more rigorous documentation requirements suitable for supplier-tier reporting in automotive supply chains.
G8D is the current global standard for Ford and much of the automotive supply chain.
Industry-specific 8D adaptations exist for medical devices, aerospace, and automotive Tier 1 suppliers, with additional documentation and traceability requirements. For apparel, the standard 8D template is typically sufficient; the structure and rigour matter more than the variant.
Several problem-solving methodologies overlap with 8D. Understanding the distinctions helps select the right approach for a given problem.
CAPA (Corrective and Preventive Action) is a simpler, more procedural framework focused on responding to nonconformities and preventing potential ones. 8D includes CAPA as the core of D5 through D7 but adds team formation (D1), containment (D3), and recognition (D8).
Use CAPA for simpler internal nonconformities; use 8D for complex, recurring, or cross-functional issues.
FMEA (Failure Mode and Effects Analysis) is a forward-looking risk assessment tool, used during design and process planning to anticipate failure modes before they occur. FMEA produces preventive action by design; 8D is reactive (responding to a problem that has occurred).
The two are complementary: a robust FMEA reduces the need for 8D, and 8D findings feed back into FMEA updates.
DMAIC (Define, Measure, Analyse, Improve, Control) is the Six Sigma framework for process improvement, oriented to reducing process variation rather than resolving specific quality problems. DMAIC is project-based and longer running; 8D is problem-based and faster cycle.
Both methodologies can coexist within a single quality programme.
Book a 30-minute demo and we will show you how the operational data layer for rework coordination feeds 8D investigations: unit-level identifiers, time-stamped status changes, photo evidence, and supplier-side workshop records. The data your 8D team needs to find the root cause is the data your rework operation produces.