![]() ![]() At this point you might reason that it’s better to focus on the larger problem, and attempt to resolve the undercooking problem another day. The problem statement could be refined as “4% of double chocolate chip cookies are burnt, and 0.5% are undercooked, and have to be thrown away”. ![]() This might be enough detail, but it’s probably worth detailing “what”, “where”, “when” and “how much” to get a better understanding of the problem. The problem statement could be “Cookies are sometimes burnt or undercooked and have to be thrown away”. Let’s take the fictitious example of a Cookie making process. Okay, you’ve assembled your team – now you have to agree on a problem statement. If your ideal team list is long, your problem is possibly too complex to solve in one hit, so consider breaking your problem up into more manageable (and edible!) chunks. It’s best to gather a team of people who have the right skills, knowledge and experience of the problem to collectively identify all the reasons why the problem may be occurring. The process to follow is basically the same, regardless of industry or problem. The tool allows a team to identify, explore and display in increasing detail, all of the possible causes of a problem, to eventually flush out the root cause(s) of the problem. If you want to discover the root cause of a problem and need a structured method to guide a team through a problem solving process, then the cause and effect diagram is for you. In this Process Improvement Made Easy series, is the fishbone diagram explained in everyday language. Dr Kaoru Ishikawa, an esteemed quality expert, gave his name to this simple, yet effective problem solving tool. The Ishikawa diagram comes under many guises cause and effect diagram or fishbone diagram, but it’s generally referring to the same problem solving tool. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |