Issue link: https://iconnect007.uberflip.com/i/1520956
36 PCB007 MAGAZINE I MAY 2024 truly understanding the problem. Guessing to implement solutions without having an accu- rate picture of the problem rarely leads to suc- cess. is is when I love to open the idea of using 8D to solve the problem at hand. Here are my tips for success when performing an investigation using 8D. Discipline 1: Form a Team In my opinion, forming a team is the most important step. It's critical to have not only the right people but also the right number of peo- ple in the room. e team members should come from different departments and profes- sions. As a general rule, I tend to add someone from process engineering, quality, and opera- tions at a minimum. Typically, teams of three to six work best so there is enough diversity in thought to solve the problem but not so much that the problem is lost. Discipline 2: Define the Problem e problem, defined by the team, is the foundation for the rest of the 8D model. Only once the problem is defined can the team properly contain all parts involved, develop a corrective action, and create preventative actions. My favorite technique for defining the problem is to use "is" and "is not" statements until I whittle the problem to the most basic definition. Another tech- nique I oen see used is the 5W2H or "who, what, when, where, why, how, and how many/much." No matter what method is used to define the problem, it's important to spend time fully understanding the problem at hand. Discipline 3: Containment Plan and Actions Now that the team knows what to look for, it's important to formulate a containment plan to prevent further occur- rences and escapes. is is the time to review WIP, stock, finished goods inventory, equip- ment, and materials as needed. Actions should be assigned to members to help quickly "plug the holes." Although containment holds its own containment step, it should be an ongoing process through the rest of the 8D's lifespan. Discipline 4: Identify Root Cause It's finally time for the team to determine the root cause. is is where I see beginners start to stumble. It's so convenient to guess at what's causing issues. But the guesswork must be removed to get to the "root" of the problem. I am very partial to the 5-Why method but have seen methods like fishbone diagrams and fault trees work well for others. is step must com- pletely entail an investigation. It's not the time