8D Problem Solving: Steps, Template and Example

8D (Eight Disciplines) is a structured, team-based method for solving a specific problem, usually a customer complaint or serious nonconformity. It moves from emergency response and containment through root cause analysis to permanent corrective action, prevention of recurrence and recognition of the team, with each discipline documented in a single report.

Many retailers and manufacturers ask suppliers for an 8D report after a complaint. Running one properly, rather than filling in boxes after the fact, is a valuable skill for QA and production staff.

Where 8D comes from

The method was developed and published by Ford Motor Company in its Team Oriented Problem Solving (TOPS) manual in the late 1980s. A later Ford version, known as Global 8D, added a preparation step, D0. 8D has since spread from automotive into food, packaging and medical device supply chains.

The disciplines, D0 to D8

D0: Plan and emergency response

Confirm that 8D is the right tool, gather initial information and take any emergency response action needed to protect the customer, such as stopping shipments.

D1: Form the team

Assemble a small cross-functional team with product and process knowledge, a team leader and a sponsor with authority to approve resources.

D2: Describe the problem

Describe the problem in specific, measurable terms. 5W2H (who, what, where, when, why, how, how many) gives a full picture. An is / is not analysis sharpens it by comparing where the problem occurs with where it could occur but does not.

D3: Interim containment

Protect the customer while you investigate: hold stock, sort or inspect, add temporary checks. Verify that containment works.

D4: Root cause and escape point

Identify the root cause of the problem occurring, and the escape point: the earliest point in the process where the problem should have been detected but was not. Use tools such as 5 Whys, fishbone diagrams and data analysis, and verify the cause, for example by turning the problem on and off.

D5: Choose and verify permanent corrective actions

Select actions that address both the root cause and the escape point. Verify, before full implementation, that they will work and will not create new problems.

D6: Implement and validate

Implement the permanent corrective actions, remove interim containment once it is safe to do so, and validate effectiveness with data over time.

D7: Prevent recurrence

Update procedures, FMEAs, control plans, training and specifications. Apply the learning to similar products, lines and sites.

D8: Recognise the team

Close the 8D formally and recognise the team's contribution.

8D template

Use this as the skeleton of your report.

Worked example: lid seal leaks at a Ras Al Khaimah food plant

A dairy plant in Ras Al Khaimah fills flavoured yoghurt into cups on a four-lane filling and sealing machine. A supermarket chain reports leaking cups and sticky trays in several stores, and asks for an 8D.

D0. The QA manager stops dispatch of the affected product, informs the customer and agrees that the retailer removes affected stock from sale. Because leaking seals can allow contamination and spoilage, she checks whether the situation needs to be reported to the authority under the plant's recall and withdrawal procedure.

D1. The team includes the QA manager (leader), the production supervisor, a maintenance technician, a filling machine operator and the packaging buyer. The plant manager is the sponsor.

D2. Using 5W2H and is / is not:

D3. All stock from filler 2 since week 12 is held. Every tray is inspected and squeeze-tested, and good stock is released only after QA approval. A 100% visual seal check is added on lane 3 until the fix is confirmed.

D4. The team finds that during servicing, the lane 3 sealing head was refitted slightly out of level, giving lower and uneven pressure on that lane. Restoring the original setting on a trial run removes the defect; reintroducing the misalignment brings it back, which verifies the cause. The escape point is the hourly seal check, which sampled only lanes 1 and 2, and the absence of a post-maintenance seal test.

D5. Actions chosen: re-level and lock the sealing head, introduce seal strength checks on every lane at start-up and at set intervals, and require a documented seal test before the line restarts after any sealing-head maintenance. A trial production run confirms the checks detect a deliberately mis-set head.

D6. The actions are implemented and lane 3 containment is removed after a period of clean results. Seal check data and complaint records are monitored for the following weeks to validate effectiveness.

D7. The preventive maintenance procedure, FMEA and operator training are updated. The same post-maintenance check is applied to filler 1 and to the plant's other cup lines.

D8. The plant manager closes the 8D, thanks the team at the monthly meeting and sends the report to the customer.

Common mistakes

• Skipping containment. Starting root cause work while suspect product is still shipping exposes customers.
• Vague problem statements. "Packaging issue" is not a description; quantify the defect and where it is and is not.
• Stopping at the first cause. "Operator error" is rarely a root cause; ask why the process allowed it.
• Ignoring the escape point. Fixing the cause without fixing detection leaves the next problem free to escape.
• No verification. An unverified root cause is a guess.
• Closing before validation. An 8D is not complete until data show the fix works.

Key takeaway: 8D works because it protects the customer first, then forces the team to prove both why the problem happened and why it escaped, before standardising the fix across similar processes.

Frequently Asked Questions

What are the 8 disciplines of 8D?

In the commonly used Global 8D form there are nine steps, D0 to D8: plan and emergency response, form the team, describe the problem, interim containment, root cause and escape point, choose and verify permanent corrective actions, implement and validate them, prevent recurrence, and recognise the team. Names vary slightly between companies.

What is the difference between 8D and CAPA?

CAPA (corrective and preventive action) is the overall process a quality system uses to handle nonconformities and prevent recurrence. 8D is a specific, structured method that can be used within CAPA, especially for customer complaints and significant problems. Many organisations use 8D reports as the CAPA record for complaints, and simpler formats for minor issues.

What is an escape point in 8D?

The escape point is the earliest point in the process where the problem should have been detected but was not. 8D asks teams to identify it alongside the root cause, because a complete fix must stop the problem occurring and also make sure that, if it ever does occur, it is caught before reaching the customer.

When should you use 8D instead of 5 Whys?

Use 8D for significant, recurring or customer-reported problems that need a team, containment and formal documentation. 5 Whys is a root cause tool, and is often used inside D4 of an 8D. For a simple, low-risk issue with an obvious cause, a short 5 Whys and a corrective action may be enough.

Next steps

To build these skills, Root Cause Analysis and CAPA covers problem description, cause analysis tools and effectiveness checks. If your problems involve product in the market, Food Traceability, Recall and Crisis Management covers withdrawal and recall decisions. Both are offered online to learners in India and the GCC.

Read next: Root cause analysis: 5 Whys vs fishbone, CAPA process: from finding to prevention and PDCA cycle explained with real workplace examples. Unsure which course fits? Speak to a counsellor.