(EN) The Eight Disciplines Problem Solving (8D)—D7 and D8

In this series of posts I go through the Eight Disciplines Problem Solving (8D) in more detail. In my last post, I talked about D5: Develop Permanent Solution and D6: Implement Permanent Solution. In this post I will go into more detail on the last two points, D7: Prevent Recurrence and D8: Close Problem and Recognize Contributors. This would close the review of the 8D, but I have one more post on my general comments on 8D in comparison to other methods like the Toyota Practical Problem Solving. Read on!

Recap: Eight Disciplines Problem Solving

Just for reference, here are the eight (nine) steps of the Eight Disciplines Problem Solving (8D).

• D0: Preparation and Emergency Response Actions
• D1: Establish a Team
• D2: Describe the Problem
• D3: Develop Interim Containment Plan
• D4: Root Cause Analysis and Escape Points
• D5: Develop Permanent Solution
• D6: Implement Permanent Solution
• D7: Prevent Recurrence
• D8: Close Problem and Recognize Contributors

D7: Prevent Recurrence

The discipline D7 aims to prevent the recurrence of the problem. Albeit, for me it gets a bit fuzzy here. A lot of the „Prevent Recurrence“ would already be done as part of D6: Implement Permanent Solution by updating the standards and training the employees. Depending on which „flavor“ of the 8D you are looking at, verification that the problem is solved, updating standards and training is sometimes found in discipline D6 and sometimes found in discipline D7. To me, it does not matter whether you verify, update your standards, and train your employees as part of the discipline D6 or as part of the discipline D7 AS LONG AS YOU DO IT!

It also feels like the discipline D7 is one of the shorter ones, and sometimes feels a bit neglected or like an afterthought. Some sources suggest to audit your solution. The purpose of this audit is to check whether the problem is officially solved. (This, too, overlaps a bit with the checking if the problem is solved in discipline D6.)

Another approach in discipline D7 is to check whether there are other, similar problems that would benefit from the same solution. Is there a similar product that could have a similar problem. Is there a second production line that could have the same issue? Systematically check all products if the problem (and the solution) would apply there, too. Depending on what you find, you may launch another project to solve the similar problem for another product or process.

Furthermore, can you share your solution with others? Does your company have a shared database for solved problems and lessons learned that others can look at when trying to solve their own problem (at Toyota this would be the Yokoten).

D8: Close Problem and Recognize Contributors

Finally, we are at the last discipline D8: Close Problem and Recognize Contributors. Now it is time to wrap up the 8D project and celebrate. You should finalize the documentation on your 8D project (sometimes called the 8D report) and file it. Depending on your company, this may need yet another approval.

If you have not yet done so, you should inform the customer about the closure of the problem.

As well, recognize and congratulate the contributors. This can be a small celebration, a small presentation, or simply some praise at the next meeting (or meetings, i.e. praise them at the internal meeting, but also praise them at the next higher level meeting). This is easy to do, and will help to raise morale and motivation and general work satisfaction for the contributors. It reinforces positive behavior, helps skilled people in their career, and should be a given for a good company. Some companies even have some awards or small gifts. Note that, for example, a free pizza is seen as more valuable and supporting by the employees as the monetary value of that pizza. In fact, praise is often seen as the strongest contributor to employee morale.

Such a wider acknowledgement can also helps with the knowledge transfer. Just make sure you don’t forget one contributor in your praise, because that would be a real downer for that forgotten person. This closes the eight (actually nine) disciplines of the 8D (9D?) Eight Disciplines Problem Solving. But it does not yet close this by now rather long blog series. In my next post, I will have a look at the pros and cons or the strength and weaknesses of the Eight Disciplines Problem Solving. But now, go out, celebrate your success and recognize the contributors, and organize your industry!