What on Earth is 8D problem solving?

Do you ever have a problem that should never happen again? A problem in your organization or in a product that makes you think: “Not this again.”

Or have you been asked to join an 8D process? Maybe you work in sales, production, development — or you are doing your first one as a quality professional. We all start somewhere. 😊

8D (Eight Disciplines) is a problem-solving method and globally known. I’m really grateful that over 10 years ago I spent a full week in Germany learning it. Not everyone gets that opportunity, and while some parts were a bit boring, I still remember many examples.

Why 8D?

To get to the roots of a problem, contain it quickly, solve it, and prevent it from returning.

So what exactly are these 8 Disciplines?

Think of 8D as a systematic detective story. You solve the mystery of what went wrong, fix it, and make sure it never happens again.

Let me walk through them.

D0: Prepare and Plan (The Often Forgotten Step)

Before starting, decide if 8D is the right tool. Not every problem needs it. Use it for serious or repeating issues. Gather initial information and evaluate: “Is this fire big enough to call the whole fire department?”

D1: Form the Team

You can’t solve complex problems alone. Bring together people who understand the product, process, customer, or data. Keep the team small but capable and make sure they actually have time to work on it.

D2: Describe the Problem

This is where most problem-solving goes wrong. People jump to solutions without understanding the problem. Use data, not opinions.

What specifically happened? When? How often? How do you know it's a problem? Create a clear problem statement that everyone agrees on. If you can't measure it, you can't fix it properly.

D3: Contain the Problem (Stop the Bleeding!)

While investigating, protect your customer.

Containment might mean:

• Sorting existing inventory

• Adding extra inspections

• Informing customers about delays

• Switching to backup suppliers

These are temporary fixes – just enough to buy you time to find the real solution.

D4: Find the Root Cause

Here's where you become a detective. Use tools like:

• 5 Whys (keep asking "why" until you reach the real cause)

• Fishbone diagrams (what categories of causes could contribute?)

• Is/Is Not analysis (what's different about when the problem occurs vs. when it doesn't?)

Don't stop at the first cause you find. Often there are multiple root causes, and you need to find them all. Test your theories – can you turn the problem on and off by controlling these causes?

D5: Choose Permanent Corrective Actions

Now that you know the real causes, what will you do about them? Develop solutions that address the root causes, not just the symptoms. Important: have a backup plan! What if your first solution doesn't work? And always consider the side effects – will fixing this problem create new ones?

D6: Implement and Validate

Put your solutions in place and prove they work. This means:

• Implementing the changes carefully

• Training people if needed

• Monitoring to ensure the problem is truly gone

• Removing the temporary containment actions from D3 (don't forget this step!)

Use data to prove your solution works. Run trials, measure results, get customer feedback.

D7: Prevent Recurrence

This is about being smart – if this problem happened here, where else could it happen? Update:

• Procedures and work instructions

• Training materials

• Design standards

• Supplier requirements

• Quality check points

Share your learning across the organization. If the production line in Factory A had this problem, Factory B probably needs to know about it too.

D8: Congratulate the Team

This one often gets skipped, but it's important! Recognize the team's effort. Share the success story. Problem-solving is hard work, and people need to know their effort was valued. This also helps build a culture where people want to participate in future problem-solving efforts.

The Reality Check

Here's what they might not tell you in training: 8D takes time and discipline (hence the name). It's tempting to skip steps, especially when management is breathing down your neck for a quick fix. But skipping steps is like building a house without checking if the foundation is solid – it might look fine at first, but problems will come back.

The good news? Once you've done a few 8Ds properly, the process becomes natural. You start thinking in this systematic way automatically. And the problems you solve? They actually stay solved.

When Does 8D Make Sense?

Use it when:

• Customer complaints arrive (especially if they're angry)

• The same problem keeps coming back

• Safety is involved

• The problem could damage your reputation

• The cost of the problem is significant

Skip it when:

• The solution is obvious and simple

• It's a one-time human error with no systemic cause

• The effort would exceed the benefit

8D is a tool, not a religion. Use it when it makes sense.

Closing Thought

Quality work is always done by people, not by templates .8D simply gives a structure that helps teams think clearly, act quickly, and prevent problems permanently.

And yes, quality is always within your reach.

If you want a simple one-page version of this, I created a free 8D Cheat Sheet you can download from my Resources page.