Successfully reported this slideshow.



Published on

  • Be the first to comment


  1. 1. 8D Problem Solving Strategy100 seconds presentationQITC<br />Sania Tufail<br />Fa-10-149<br />
  2. 2. The 8 Disciplines of Problem Solving<br />Structured approach to continuously improve quality<br />popularized by Ford Motor Company as Global 8D<br />Eliminate route cause<br />And prevent their reoccurrences<br />
  3. 3. D1- Assemble the Team<br />Determine the personnel required for the resolution of the current issue. <br />Generally, a cross-functional team works best, but it’s more important to ensure the correct people are on your team than it is to have a true cross-functional team. <br />Determine your team’s leader.<br />
  4. 4. D2- Define the Problem<br />Provide as much detail regarding the current issue. <br />Writing an outstanding problem statement is critical to the success of problem solving efforts. <br />
  5. 5. D3- Implement and Verify Interim Containment Actions (ICAs)<br />Determine the impact of the customer’s issue within your organization. <br />Identify all possible suspect material and segregate that material for further review. <br />List the date codes, lot numbers, etc. that are considered suspect. <br />Determine a method that clearly shows the customer that all product shipped from this date was inspected and known to be acceptable.<br />
  6. 6. D4- Identify and Verify Root Cause<br />D4 is the important and most difficult step of the 8 disciplines of problem solving.<br />The team investigates the problem and begins to develop theories regarding where and how this issue occurred. <br />Common methods for root cause analysis are: Data Mining,Pareto Charts, Brainstorming Fishbone Diagram (also known as an Ishikawa Diagram or Cause and Effect Diagram)<br />Also in the D4 step, team determines the “escape point,” that is, where in your process did this issue fail to get identified. <br />As the process is followed backwards, it identify the location within your system that the root cause should have been identified but wasn’t.<br />The team must be able to verify that they have indeed identified both the root cause and the escape point, and be able to take action upon the root cause. <br />Returning to the process, the team should be able to make the issue come and go at will, indicating verification of root cause.<br />
  7. 7. D5- Choose and Verify Permanent Corrective Actions (PCAs)<br />After verifying the root cause, the team assembles to generate potential PCAs.<br />The team will consider topics such as: customer satisfaction, cost, elimination of the root cause, and others when attempting to choose the best PCA from the list of potential PCAs.<br />
  8. 8. D6- Implement and Validate PCAs<br />Use the selected PCA from D5. Implement this solution. <br />Like in D4, the team should be able to make the problem come and go at will by alternately applying and removing the PCA. <br />Continue to measure the process to ensure effectiveness.<br />
  9. 9. D7- Prevent Recurrence<br />Sustain the Gains! Regularly follow up on the process measures, again to ensure effectiveness and prevent backsliding. <br />Update all documentation in your Quality Management System. <br />Mistake-proof the process if possible. <br />Identify any potential areas where the same issue could occur and implement the same or similar PCA in those areas.<br />
  10. 10. D8- Recognize the Efforts of the Team<br />D8 is the most underutilized of the steps in the 8 disciplines of problem solving. <br />While most companies will obtain formal sign-offs for the 8D structure, some fail to commend the team participants for the excellent work they accomplished. <br />It is through this feedback that the team members feel appreciated, making them likely participants for the next issue (when it develops).<br />
  11. 11. Thanks.<br />