8D problem solving

8D Problem Solving: Step-by-Step Guide With Example

By the QCIN team · · 3 min read

In short: 8D is a team-based method for solving recurring or customer-visible problems. Its strength is discipline: contain first, prove the root cause with data, and verify the fix before closing.

When to use 8D

8D (eight disciplines) is suited to problems that are significant, recurring or visible to a customer, and where the cause is not obvious. Many automotive and industrial customers require an 8D report in response to a complaint. For a simple, well-understood defect a shorter corrective action is usually enough.

The disciplines

StepGoalOutput
D0 PrepareDecide whether 8D is warranted and take emergency action if neededGo/no-go decision, emergency response
D1 TeamForm a small cross-functional team with the right knowledgeTeam list with a leader and champion
D2 DescribeDefine the problem precisely using factsIs / is-not description, data, photos
D3 ContainProtect the customer while you investigateInterim containment actions and their verification
D4 Root causeFind and verify the root cause and the escape pointVerified occurrence cause and detection (escape) cause
D5 Choose actionsSelect permanent corrective actions and prove they workChosen actions with verification evidence
D6 ImplementImplement actions and remove containmentImplementation record and validation data
D7 PreventUpdate systems so it cannot recur here or elsewhereUpdated FMEA, control plans, procedures, similar products
D8 RecogniseClose the 8D and recognise the teamClosure sign-off and lessons learned

Worked example (illustrative)

D2: A customer reports that 12 out of a delivery of 2,000 plastic housings have a cracked clip. Is: cracked clip on cavity 3 parts, lot 2405-B, found at customer assembly. Is not: other cavities, earlier lots, other part numbers.

D3: Stop shipment of remaining stock from lot 2405-B, 100 percent inspect all cavity 3 parts in the warehouse and at the customer, ship only inspected parts with an identification mark.

D4: Fishbone and 5-Why point to a cooling channel partially blocked on cavity 3, giving a shorter effective cooling time and higher residual stress. The cause is verified by measuring mould temperature on cavity 3 and reproducing the crack. The escape point: the final inspection checked appearance but not clip flex, so cracks that opened later were not detected.

D5 and D6: Clean the cooling channel and add a flow check to preventive maintenance. Add a clip flex test to the inspection plan. Validate by producing three lots with zero cracks under the flex test.

D7: Add the cooling flow check to every multi-cavity mould's maintenance schedule and update the process FMEA. D8: Close with the customer, share the report and record the lesson.

Tips for each step

  • Keep the team small, typically four to six people who actually know the process.
  • Write the D2 description so that someone who was not there could recognise the problem.
  • Containment must be verified. Record how many parts were checked and what was found.
  • Always find two root causes in D4: why it happened and why it was not detected.
  • Prove the root cause by turning the problem on and off, or with data, not by consensus.
  • In D7 look sideways: similar products, machines and plants.

Common mistakes

  • Jumping to D5 actions before the root cause is proven.
  • Treating D3 containment as the fix.
  • Root causes such as 'human error' or 'lack of attention'.
  • Closing the 8D before enough production has run to verify effectiveness.

Timing and communication with the customer

Customers usually expect three things quickly: confirmation that the complaint was received, containment in place to protect them (D3), and then a root cause and permanent action plan. Exact deadlines vary by customer, so check their supplier quality manual and agree dates explicitly rather than assuming. Send an interim report at each stage rather than waiting for a complete 8D; an honest D3 with a credible plan for D4 builds more confidence than a polished report that arrives late.

Keep the report factual. Include the data you used, photos of the defect and of the fix, and the verification results. Avoid promising zero defects; promise the specific controls you have added and show how you will know they are working.

Template and tooling

Download the free 8D report template from our resources section to structure your next investigation. If you manage NCRs in QCIN, the 8D report is compiled from the NCR record, root cause analysis and actions, and can be shared with the customer.

See QCIN with your own parts and processes.

Start a free 14-day trial — no card required — or book a walkthrough with our team.