Cricket scoring 8d1/3/2023 ![]() ![]() An example of a template for process steps is the FMEA or variations of it. Of course, once I decide to use process steps, then I no longer need to use a fish bone. Rather using the 6 Ms or its variants, I list the process steps. If we know, then why not just solve the problem?įinally, because brainstorming’s purpose is quantity over quality, I prefer using another set of categories that keeps the list to what is relevant: process steps. But I have never seen anyone explain how to get the answers, giving the impression that we always know the answers. For that reason, it is best suited for projects in which hard data is unavailable, or as preliminary work to identify potential causes worthy of data collection and further analysis.”įourthly, it’s easy to give examples of the Five Whys. I was happy to see you state: “its drawback is that it is based on perception and does not constitute a quantitative analysis. Thus, a less knowledgeable and capable person will ask more whys than a more knowledgeable and capable one.Ī third issue is that once a list of potential causes is generated, little is said about how to reduce the list without subjectivity. The advice I give is when by the answer you know what action to take to mitigate the effect. I’ve never seen anyone teach/explain when to stop digging deeper, i.e., when to stop asking why. ![]() It’s physical properties are due to ….? When have you reached the “true” root cause?īut often we just want to mitigate the effect, so we don’t need to get to root causes. The material’s fragility is due to physical properties. A leaky pipe maybe due to the material used. For example, a hole in a wall may be due to a leaky pipe. It’s not always possible to get to the “true” root cause. Why does the material jam? Because it is out of spec. Why are there frequent line stoppages? Because the material jams. Application of the 5 Whys at this point can help drive the team to the root cause. For instance, as shown in Figure 3, each cause coming off the main category “bone” could have one or more lines with sub-causes coming off of it. Sticky notes are particularly useful for this method – write one cause per sticky note and they are easily moved for grouping.Ī team is likely to find that once they have identified possible causes, they need to delve a little further to find a true root cause. For example, a possible cause of late deliveries of product XYZ within the Machine category could be “frequent line stoppages.”Īnother approach is to start by brainstorming the possible causes of the problem, and then determining appropriate categories based on what causes were identified. Team members – which should include subject matter experts and those who work within the processes related to the problem – then brainstorm the causes of the defined problem. However, what set of categories is used for a given analysis can be modified to fit the situation. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |