Understanding what 8D really is
Estimated reading time: 7 minutes
When I ask quality professionals, engineers or operations leaders what problem solving method they use, one of the most common answers I hear is “8D” – and every time I hear it, I know we need to have a deeper conversation.
Why? Because 8D is not a problem solving method. It never has been.
So what is 8D?
The Eight Disciplines (8D) methodology was originally developed by Ford Motor Company in the 1980s and was formalized in their Team Oriented Problem Solving (TOPS) manual published in 1987 as a structured framework for managing corrective action investigations. It provides a disciplined roadmap for organizing teams, containing problems, implementing corrective actions, and preventing recurrence.
However, what 8D does not do is tell you how to actually solve the problem.
8D is essentially a project management scaffold for problem investigation. It answers questions like:
- Who should be on the team? (D1)
- How do we describe the problem accurately? (D2)
- What interim actions do we take to protect customers? (D3)
- How do we verify that our solution works? (D5)
- How do we prevent this from happening again? (D7)
These are critical steps. But notice what’s missing in the middle.
D4: The “Black Box” of the 8D methodology
Discipline 4 (D4) states: “Determine, identify, and verify root causes”. That’s it.
8D doesn’t tell you how to determine the root cause. It doesn’t specify which analytical method you should use. And it doesn’t provide a structured critical thinking process for isolating causal mechanisms. D4 is a placeholder.
It’s the step where the actual problem solving work happens. However, 8D itself provides no methodology for doing that work.
8D and problem solving methodology: the origins
What is particularly revealing is the relationship between the structure of 8D and established problem solving methods that existed long before Ford’s 1987 publication.
The Kepner-Tregoe Problem Analysis methodology, which includes the now-famous IS/IS NOT comparative analysis technique, was developed in 1958 – almost 3 decades before 8D was formalized. In addition, if you examine the 8D framework closely, especially D2 (Define the Problem) and D4 (Root Cause Analysis), the structure maps remarkably well to Kepner-Tregoe’s systematic approach to problem analysis.
This connection is not speculative – it has been officially acknowledged. The German Association of the Automotive Industry (VDA) writes: “Die 8D-Methode wurde in den 1980er Jahren von Ford mit Beteiligung von Kepner-Tregoe entwickelt” (The 8D method was developed in the 1980s by Ford with the participation of Kepner-Tregoe).
More significantly, in the VDA’s authoritative publication 8D – Problemlösung in 8 Disziplinen; Methode, Prozess, Bericht (Berlin, 2018), the organization explicitly recommends Kepner-Tregoe Problem Analysis as best practice for conducting root cause analysis in D2 and D4. The VDA specifically refers to IS/IS NOT analysis, Kepner-Tregoe’s signature comparative analysis tool, as the standard for achieving an “Excellent” audit rating in 8D problem-solving.
What this means: 8D needs a problem solving method
This acknowledgment clarifies something critical: 8D was never intended to stand alone. To complete step D4 effectively, you need to apply an actual problem solving method, such as:
- Kepner-Tregoe Problem Analysis (Comparative IS/IS NOT Analysis and systematic cause testing)
- 5 Whys (Iterative causal questioning)
- Ishikawa/Fishbone Diagrams (Categorical hypothesis generation)
- Fault Tree Analysis (Deductive logic modelling)
- DMAIC (Define-Measure-Analyze-Improve-Control from Six Sigma)
- A3 Thinking (Structured problem solving on a single page)
These are all problem solving methodologies. They all have logical structures. They guide thinking and help you move from symptom to cause through rational inquiry.
8D provides none of this. 8D is an excellent investigation framework. That said, the problem solving method you choose to apply at steps D2 and D4 determines whether you actually find the real cause of the problem.
The confusion: Why do people think 8D is a problem solving method?
This misconception is understandable. The 8D methodology is widely taught in quality management programs, required by automotive supply chains (such as IATF 16949), and embedded in corrective action systems across industries. It is often the only formal framework that quality teams are trained on.
So, when someone asks, “What problem solving method do you use?” people answer with the only framework they know: 8D. But that’s like saying that your project management software is the project, even though the Gantt chart doesn’t build the bridge! Similarly, the 8D report doesn’t solve the problem.
What this means in practice
Here is the operational reality:
If your team completes an 8D report, but never applies a rigorous root cause analysis method at stage D4, you end up with:
- Superficial causes, instead of root causes
- Corrective actions that don’t resolve the issue, because the real mechanism wasn’t understood
- The same problem reappears under slightly different conditions
- 8D reports that satisfy the compliance requirement but don’t deliver actual problem resolution
I’ve seen it hundreds of times. An 8D report is closed and the customer accepts it. However, 6 months later, the same failure mode reappears, because the team never actually solved the problem. They did complete the report as required, but they never found and eliminated the true root cause.
What should organizations do instead?
If you want your teams to solve problems effectively, you should:
Train them in actual problem solving methods, not just 8D
Teach them how to think through cause isolation. Teach them Kepner-Tregoe Problem Analysis! Or teach them another kind of structured root cause analysis, or perhaps hypothesis testing and evidence validation. The VDA’s recommendation of Kepner-Tregoe Problem Analysis for D2 and D4 isn’t arbitrary. On the contrary, it is based on decades of proven effectiveness in automotive quality systems.
Recognize that 8D is the container, not the content.
8D organizes the investigation. However, the problem solving method you apply at stage D4 determines whether you find the real cause. At Kepner-Tregoe, we would argue that if you don’t just want to fill out the 8D form but actually perform effective root cause analysis, you need KT process.
Integrate problem methods into your 8D process and make this explicit
Your D4 template should specify: “Root cause determination conducted using [Method]. Evidence attached.” Don’t allow teams to skip from problem description (D2) to proposed corrective action (D5) without demonstrating a logical, evidence-based causal analysis in between. The VDA guidelines are clear: conducting a thorough IS/IS NOT analysis isn’t optional, it’s the standard for excellence.
Stop conflating compliance with capability
Completing an 8D report is a compliance activity. Solving the problem is a capability activity. They’re not the same thing. You can have perfect 8D documentation and terrible problem solving. Or, you can have brilliant problem solving poorly documented in an 8D format. The goal is of course to have both the perfect documentation and the brilliant problem solving.
Final thoughts
The 8D methodology is a valuable framework, which brings discipline to corrective action. It ensures that problems are contained, solutions are verified and systemic improvements are made. But it is not a substitute for critical thinking. Nor is it a substitute for root cause analysis. And it is certainly not a problem-solving method.
The acknowledgment by the VDA, the authoritative voice of the automotive industry, that Kepner-Tregoe was involved in 8D’s development and that Kepner-Tregoe Problem Analysis represents best practice for the critical disciplines, validates what many of us in the field have known for years: 8D provides the structure. You still need to provide the thinking.
If your organization wants to build real problem solving capability – the kind that prevents recurrence, reduces warranty costs, and protects your customers, you need to invest in teaching people how to think, not just how to fill out a form.
8D gives you the framework. Problem-solving methods like Kepner-Tregoe give you the substance.
Key Takeaways
- 8D is not a problem-solving method; it is a framework for managing corrective action investigations.
- While 8D organizes the process, it lacks guidance on determining root causes, which is crucial for problem solving.
- Successful application of 8D requires integrating a structured problem-solving method like Kepner-Tregoe or 5 Whys at key stages.
- Quality teams often misuse 8D because it is the only methodology they are taught, leading to compliance without effective problem resolution.
- To improve problem-solving capability, organizations should train teams in actual methodologies and emphasize critical thinking alongside 8D.
About the author
Phillip Thompson is Senior Vice President of Client Experience at Kepner-Tregoe Inc., a consulting firm specializing in critical thinking and rational problem-solving methodologies. With nearly 40 years of experience, Phillip has worked with Fortune 100 companies across 15 industries to build organizational capability in systematic problem solving and decision making.
