What Is 8D Problem Solving?

Written by Jason Westland · Edited by Johanna Barnett

8D problem solving is a structured way to investigate a serious or recurring quality issue, protect the customer, establish the cause with evidence, fix the process, check whether the fix worked, and reduce the chance of the same problem coming back.

See the 8D process When to use an 8D

A good 8D does not jump straight to "root cause." It works from facts, containment, evidence, corrective action, verification, effectiveness, prevention, and closure.

8D path

D1Team setup
D2Problem facts
D3Containment
D4Cause + escape
D5Corrective action
D6Verification + effectiveness
D7Prevention
D8Recognize and close

D0 is sometimes used as a short planning or triage step before D1.

Do not jump straight to root cause.

A useful 8D moves from customer protection to evidence-based closure.

What 8D problem solving means in practice

8D problem solving is a team-based method used when a quality problem needs more than a quick correction.

8D means eight disciplines. It is broader than root cause analysis: RCA is primarily part of D4, while 8D also covers team ownership, containment, corrective action, verification, prevention and closure.

The 8D methodology is commonly used when a customer asks for a formal response, a defect has escaped, the cause is unclear, or the same issue keeps coming back. It moves through eight disciplines, usually with an optional D0 planning step before D1.

The basic flow is:

Problem facts → containment → occurrence cause and escape point → corrective action → verification → effectiveness → prevention → recognize the team and close.

The point is not to fill in eight boxes. The point is to make sure the team protects the customer, establishes the cause with evidence, fixes the right thing, and closes the issue only when the evidence supports closure.

Why completing the report is not the same as completing the investigation

Many teams first meet 8D as a customer form. That can make it feel like paperwork.

The report matters, but the investigation matters more. A useful 8D shows how the team understood the problem, protected the customer, checked the evidence, separated occurrence cause from escape point, and confirmed that the action worked.

The report is the output. The investigation is the work.

If the 8D only says "operator error" and "retrained operator," it has probably missed the real weakness in the process.

When an issue actually needs an 8D

Use an 8D when the issue needs investigation, containment, evidence, and follow-up before it can be closed. An 8D is usually appropriate when:

a customer asks for a formal 8D response;
the cause is unknown, disputed, or needs evidence;
the issue reached the customer or the next process step;
the problem is recurring after previous fixes;
more than one function is needed to solve it;
containment, cause investigation, corrective action, verification, effectiveness, and prevention all need to be shown.

A full 8D takes time. Use an 8D when the issue is serious — when structured investigation, containment, evidence, and follow-up are all needed.

Not every customer complaint needs an 8D. Use the response format required by the customer and match the method to the issue’s risk, recurrence, complexity and need for formal closure.

When the 8D is more than the problem needs

A simpler NCR, corrective action plan, or internal action record is usually sufficient when the cause is already known, the fix is local, and no customer requires a formal 8D.

Too much structure slows the team down and turns problem solving into form filling. Use the smallest record that still controls the risk and leaves sufficient evidence for review.

The 8D process: D0 to D8

The 8D process is a step-by-step problem-solving sequence. It is not just a set of boxes to complete in a report.

D0 decides whether the issue needs an 8D, D1 identifies the team, and D2 defines the problem in facts. D3 protects the customer or next process while the cause is still open. D4 uses evidence to establish why the problem happened and why it escaped. D5 and D6 choose actions and check whether they worked. D7 looks beyond the affected lot. D8 recognizes the team and closes the record only when the evidence supports it.

Each discipline should carry the investigation forward. If one section does not support the next one, the 8D usually becomes paperwork instead of problem solving.

Is an 8D actually needed?

D0 is an optional planning step. Some 8D formats start at D1.

D0 should stay short. Its job is to stop the wrong problems being forced into a full 8D and to make the launch decision clear.

A useful D0 records:

what triggered the issue;
initial risk;
customer or internal response due date;
immediate protection already taken;
why an 8D is needed.

Good D0 entry

Apex Industrial returned 12 HSG-88 housings from HSG88-LOT-0726A after leaks were found at the seal interface during incoming test. NCR-2026-120 and 8D-2026-042 were opened, 48 suspect units and related WIP were placed on hold, and Tom Alvarez owns the 8D response. The customer response was due July 10, 2026.

Weak D0 entry

Open 8D for leaking housing.

Get the right people in the room

D1 should name the people needed to solve the problem, not just the person filling out the report.

For a manufacturing quality issue, the team may include quality, production, engineering, supplier quality, inspection, maintenance, purchasing, or customer-facing support.

The team should include people who understand the product, process, records, and decision authority.

Watch-out

Do not assign a cross-functional issue to one person and call that the team.

Write a problem statement someone else can investigate

D2 should describe the problem clearly so someone else can understand the issue without guessing.

A good D2 includes:

part or product;
revision;
lot, batch, work order, or serial range;
requirement not met;
actual condition found;
where found;
affected quantity;
suspect quantity;
evidence available.

For the leaking housing example:

Strong entry

Apex Industrial returned HSG-88 housings from HSG88-LOT-0726A that leaked at the seal interface during incoming test. Requirement: DRW-HSG-88 Rev D requires the housing to seal at the mating face without leakage during the pressure hold test. Scope: 12 returned / 48 suspect. Records: NCR-2026-120 and 8D-2026-042. Evidence: EVD-120-01 customer return photos and EVD-120-02 leak test record.

Weak entry

“Customer got a bad part.”

The strong entry gives the team something to investigate. The weak entry only gives the team something to argue about.

Protect the customer before arguing about root cause

Containment is immediate protection. It is not the permanent corrective action.

A complete D3 should show affected quantity, suspect quantity, product location, customer protection, containment action, and containment verification. Depending on the issue, containment might include:

holding suspect stock;
stopping shipment;
sorting finished goods;
checking work in progress;
adding temporary inspection;
defining a clean point.

D3 should answer a simple question:

What did we do right now to protect the customer or next process step?

Good containment entry

Hold suspect HSG-88 stock and related WIP in the red-tag hold area; perform 100% seal-face visual check and leak test before release.

Weak containment entry

Leak issue contained.

Establish the occurrence cause and escape point with evidence

D4 is the section that often separates a useful 8D from a form-filling exercise.

The team needs to answer two different questions:

1. Why did the problem happen?
2. Why was it not detected before reaching the next process step or customer?

The first answer is the occurrence cause. The second answer is the escape point or detection weakness.

Do not treat possible causes as supported causes

Use evidence to support or rule out each possible cause before naming the root cause.

Possible causes might include:

seal process control gap;
gasket or seal fit issue;
assembly method variation;
inspection or test check missing the leak condition;
unclear sealing requirement;
supplier or internal process change.

Evidence should support or rule out each possible cause. For this issue, the evidence included EVD-120-01 customer return photos, EVD-120-02 leak test record, EVD-120-03 seal inspection photos, EVD-120-04 WI-ASSY-221 Rev C gap review, and EVD-120-05 IP-HSG-88 Rev B review.

Good D4 conclusion

Supported occurrence cause: WI-ASSY-221 Rev C did not require a seal-orientation confirmation after the cleaning step, and EVD-120-04 confirmed that the step was absent. Escape weakness: IP-HSG-88 Rev B required final pressure testing but did not require a seal-face visual check before packing, as confirmed by EVD-120-05.

Weak D4 conclusion

Root cause was operator error.

The weak version may be partly true, but it does not explain what in the process allowed the leak to happen or why the inspection or test check missed it.

Why it happened is not the same as why it escaped

Occurrence cause

Why the problem happened.

WI-ASSY-221 Rev C did not require a seal-orientation confirmation after the cleaning step, so a damaged or mis-seated seal could be installed before the pressure test.

Escape point

Why the issue was not detected before reaching the next process or customer.

IP-HSG-88 Rev B required final pressure testing but did not require a seal-face visual check before packing, so the team relied on the final test alone.

A good 8D usually needs both answers. If you only fix one side, the issue can come back or escape again.

Choose actions that match the supported cause

D5 should choose actions that match the supported occurrence cause and escape weakness.

WI-ASSY-221 Rev C omitted a seal-orientation confirmation, so the corrective action must add that process control.

IP-HSG-88 Rev B omitted a seal-face visual check before packing, so the corrective action must add that detection control.

Good corrective actions

Update WI-ASSY-221 to Rev D and require seal-orientation confirmation.
Update TC-SEAL-04 to Rev B and add a seal-face visual check.
Train assembly and test operators on the revised documents.
Track the seal-process action as ACT-3012 and the corrective-action follow-up as CAR-2026-031.

Weak corrective actions

tell the team to be more careful;
remind the inspector;
retrain the operator with no process or inspection change.

Training may be part of an action, but training alone is weak if the process still allows the same error.

Verify implementation, then check effectiveness

D6 should confirm what was implemented and show whether it worked.

Do not stop at "Checklist updated."

Verification

Confirm that WI-ASSY-221 Rev D and TC-SEAL-04 Rev B were issued, EVD-120-06 documents the required training, and the first three batches after release were reviewed.

Effectiveness

Effectiveness target: no repeat leaks in 90 shipped units during the defined review window.

Action completed is not the same as action effective

Confirm the result with evidence before treating an action as effective.

Look beyond the affected lot

D7 looks beyond the affected lot.

D7 should not copy D5. It should show what was checked beyond the immediate issue.

Good D7 entry

Review CP-HSG-88 Rev C, similar sealed housing parts, and related inspection and test controls to identify where the same seal-orientation or seal-face inspection weakness could exist. Assign any additional prevention action to an owner before D8 closure.

Weak D7 entry

Prevent recurrence by completing corrective action.

Recognize the team and close the 8D

D8 recognizes the team's work and closes the record only when the evidence supports closure.

Before closing, check:

problem statement is factual;
containment is released or replaced by permanent control;
occurrence cause is supported by evidence;
escape point is identified;
actions match the causes;
effectiveness has been checked;
D7 prevention actions are complete or owned;
customer response is sent if required;
final approval is recorded;
the team's contribution is recognized.

Do not close on the response alone

Do not close an 8D just because the customer response was sent. Closure means the team can defend the decision later.

MANUFACTURING EXAMPLE

Leaking housing customer return: a worked 8D example

This example shows how an 8D works as a problem-solving method, not just as a report.

8D area	Example
Issue	Leaking housing customer return from Apex Industrial
Part and lot	HSG-88 housings from HSG88-LOT-0726A
Scope	12 returned / 48 suspect
Owner	Tom Alvarez
Key dates	Containment: July 3, 2026; customer response: July 10, 2026; WI/checklist update: July 17, 2026; verification: July 24, 2026; effectiveness review: August 21, 2026.
Records	NCR-2026-120; 8D-2026-042; ACT-3012 (seal process); CAR-2026-031
Requirement and actual condition	Housing must seal at the mating face without leakage during the pressure hold test; returned housings leaked at the seal interface during incoming test.
Containment	Hold suspect HSG-88 stock and related WIP in the red-tag hold area; perform 100% seal-face visual check and leak test before release.
Correction	Affected returned housings were handled under the approved NCR-2026-120 disposition.
Occurrence cause	WI-ASSY-221 Rev C did not require a seal-orientation confirmation after the cleaning step, so a damaged or mis-seated seal could be installed before the pressure test.
Escape weakness	IP-HSG-88 Rev B required final pressure testing but did not require a seal-face visual check before packing, so the team relied on the final test alone.
Corrective action	Update WI-ASSY-221 to Rev D and TC-SEAL-04 to Rev B; add seal-orientation confirmation and seal-face visual check; train assembly and test operators.
Verification plan	Confirm the revised documents and training record, then review the first three batches after release.
Effectiveness target	Target: no repeat leaks in 90 shipped units during the defined review window.
Prevention	Review CP-HSG-88 Rev C and similar sealed housing processes for the same control weakness.
D8 closure condition	Recognize the team and close 8D-2026-042 after the evidence, effectiveness review and final approval support closure.

8D mistakes that show up in quality reviews

Mistake	Better practice
Starting with root cause before the problem is clear	Define the requirement, actual condition, location found, affected quantity, and suspect quantity first
Calling containment the corrective action	Treat containment as temporary protection while the investigation continues
Assigning the 8D to one person	Include the people who know the product, process, inspection, supplier, and customer impact
Writing "operator error" as the root cause	Ask what allowed the error and why the process did not catch it
Mixing occurrence cause and escape point	Explain why the problem happened and why it was not detected
Choosing actions before evidence is checked	Use evidence to support or rule out possible causes before selecting corrective actions
Using training as the only action	Change the process, control, document, inspection, or system where the evidence points there
Closing when actions are completed	Check whether the actions worked after implementation
Skipping D7	Review similar parts, processes, suppliers, inspection plans, and control plans
Sending a response that does not match the evidence	Check that the final customer response agrees with the record, attachments, and action status

The records that usually sit alongside an 8D

An 8D does not usually stand alone. It often connects several quality records and tools.

Tool or record	How it connects to 8D
Customer complaint	Often triggers the 8D and sets response expectations
NCR	Records the nonconforming product, affected quantity, suspect quantity, containment, and disposition
SCAR	Used when the supplier owns or shares the cause and needs to respond
5 Whys	Helps test a cause path during D4
Fishbone diagram	Helps organize possible causes before evidence is checked
Corrective action plan	Tracks actions, owners, due dates, verification, and effectiveness
Control plan / inspection plan	D7 should include review of the control plan and inspection plan for the affected process and similar processes
Evidence log	Keeps photos, records, measurements, supplier responses, and effectiveness checks easy to find

Quality terms that must stay separate

Containment, correction, and corrective action

Term	Practical meaning
Containment	Temporary action to protect the customer or next process while the investigation continues.
Correction	Action taken on the affected product or immediate issue.
Corrective action	Action taken to address the supported cause by changing the process or control.

Verification and effectiveness

Term	Practical meaning
Verification	Confirmation that the planned action was implemented as intended.
Effectiveness	Evidence that the action worked over the defined review period.

Where to go for more on the 8D method

Use these references as background, then apply your own company, customer, product, process, and industry requirements.

ASQ — Eight Disciplines (8D)
Overview of the eight disciplines problem-solving model and how the steps fit together.
AIAG — CQI-20 Effective Problem Solving Guide
Industry context and training for structured, evidence-based problem solving in manufacturing supply chains.
Your customer-specific 8D or supplier quality manual
Where applicable, follow the 8D format, fields, and approval requirements defined by your customer.

This guide follows established manufacturing quality frameworks (ISO 9001, AIAG, ASQ definitions) and is reviewed internally before publishing.

This is provided for general manufacturing quality use. Adapt it to your company, customer, product, process, supplier, and industry requirements before use. It is not intended for medical device, pharma, FDA, Part 11, or validated regulated workflows.

Templates and guides for the work around the 8D

Templates

Guides

When the 8D work moves beyond a document, the hard part is keeping the report, owners, actions, evidence, approvals, and customer PDF together. See how 8Dflow is being built to manage 8D reports.

Turn the 8D method into a completed report

Use the 8D report template when you need to turn the method into a completed record.

View the 8D report template See related templates