Learn how to use an Ishikawa diagram to improve quality control. Find out what the 6Ms are in the Ishikawa diagram and more.
Published 28 Apr 2023
Ishikawa diagram, also called the Fishbone diagram, is a tool used to identify problems in a system. It shows how causes and effects are linked and helps analyze what is going wrong with systems, processes, and products. The name comes from Japanese engineer Kaoru Ishikawa who developed the method in the 1960s.
Using the Ishikawa diagram, engineers may better understand manufacturing process defects. But today, many marketers use the Ishikawa diagram to analyze complex situations and find the most effective solution for their businesses.
Ishikawa diagrams can be helpful in any situation where there is a need to analyze complex problems or identify the causes of issues in a system. Teams often use them in manufacturing, marketing, product development, and other fields that involve working with people, processes, and procedures. Some common situations where Ishikawa diagrams may be helpful include:
There are several advantages of Ishikawa diagrams, including:
There are a few disadvantages of Ishikawa diagrams to consider, including:
The 6Ms in the Ishikawa diagram are critical factors used to identify and analyze problems in a system. These factors include:
When generating an Ishikawa diagram, there are a few steps to follow:
Start by clearly defining the problem you are trying to address using your fishbone diagram. It could be a quality issue, employee dissatisfaction, or any other issue that you want to understand and improve. You can use paper checklists or spreadsheets to define the problems or use specific tools such as SafetyCulture (formerly iAuditor) to capture and organize your specified issues.
Problem Definition Tips:
Sorting potential causes into different categories makes it easier to identify root causes later on. You can use the 6Ms as a starting point to help you decide on key types.
Once you have decided on your key categories, you can begin brainstorming possible causes for each one. Consider all of the factors that could affect your process or product and note them down as potential causes. Below is an example of possible causes in each category using the 6Ms (Material, Method, Machine, Measurement, Manpower, and Mother Nature).
Once you have a list of possible causes, it is helpful to sort and prioritize them based on their likelihood of being root causes. It will help you focus your efforts on the most likely reasons. There are a few different quality management tools you can use to sort and prioritize potential causes; some of these include:
After you have sorted and prioritized your potential causes, it is time to start testing them to see if they are root causes. Trying to find out what might be the possible causes can be done in several ways:
Below is an example of a fishbone diagram for a manufacturing company. In this scenario, the company uses the 6Ms to better understand the causes of the problem, which is that a part of the product is in the wrong size.
The problem is stated on the right, with possible causes of the problem listed in the ribs under each 6Ms category.
One of the main challenges remote teams face when conducting root cause analysis is coordinating and communicating effectively. It can be difficult, primarily if team members are spread across different time zones.
Another challenge is ensuring that tasks or follow-ups are assigned to the correct person or team. In a remote setup, it’s easy to forget who’s responsible for what and to track tasks that aren’t assigned right away. However, there are tools like SafetyCulture (formerly iAuditor) that can help with this issue.
Eliminate manual tasks and streamline your operations.
As an Ishikawa tool and hazop software, SafetyCulture makes it easy to create and share checklists, assign tasks, and track the status of audits or investigations. It also allows remote teams to collaborate more efficiently through real-time notifications and updates. Moreover, it has built-in templates for conducting root cause analysis, which can help guide your team through the process.
Rob Paredes is a content contributor for SafetyCulture. He is a content writer who also does copy for websites, sales pages, and landing pages. Rob worked as a financial advisor, a freelance copywriter, and a Network Engineer for more than a decade before joining SafetyCulture. He got interested in writing because of the influence of his friends; aside from writing, he has an interest in personal finance, dogs, and collecting Allen Iverson cards.
The MDSAP audit overviews a manufacturer’s quality system and processes to ensure products ...
Benefits Since the primary purpose of gathering and maximizing the Voice of the Customer data is to ...
SATs are important because they help to ensure that the system works as expected and that the ...