How to create an Ishikawa diagramCreating an Ishikawa diagram is a simple process. First, you need to identify the problem or issue that you want to investigate. Then, you draw a large bone shape on a piece of paper or whiteboard. This will be the main ‘spine’ of your diagram.
Next, you need to identify all of the potential causes of the problem. These will be the ‘bones’ that branch off from the main spine. There are typically six main categories of causes:
People categoryThis could include training, skills, experience or knowledge. For example, if you are investigating a problem with a product that you manufacture, the people category would include the workers who make the product, as well as the designers and engineers who created it.
Methods categoryThis includes the processes and procedures that are used to make or do something. For example, if you are investigating a problem with a product that you manufacture, the methods category would include the steps in the manufacturing process.
Materials categoryThis includes the raw materials, parts and components that are used to make a product. For example, if you are investigating a problem with a product that you manufacture, the materials category would include the types of materials used to make the product.
Environment categoryThis includes the physical conditions under which something is made or done. For example, if you are investigating a problem with a product that you manufacture, the environment category would include the temperature and humidity of the factory, as well as the lighting conditions.
Measurement categoryThis includes the tools and methods that are used to measure something. For example, if you are investigating a problem with a product that you manufacture, the measurement category would include the gauges and instruments used to measure the dimensions of the product.
Management categoryThis includes the policies, decisions and actions of management. For example, if you are investigating a problem with a product that you manufacture, the management category would include the decisions that were made about the design of the product, as well as the production quotas that were set.
How to use the Fishbone diagramOnce you have identified all of the potential causes, you can start to investigate which ones are actually contributing to the problem. This is where the fishbone diagram comes into its own, as it provides a structure to help you systematically eliminate potential contributing factors until you identify the root cause of the problem.
Under each category add sub 'bones' for each activity, element, tool or person involved and think about what causes might be present. For example, let's say you need to reduce the time it takes to pay your suppliers invoices. Under people you would list everyone involved in the payment process and then establish if they contribute to the problem. In the example below, the buyer failure to create a purchase order and accounting's backlog delay payment, but supplier management don't seem to have an impact.
When to use itThe Ishikawa diagram is an extremely powerful tool for root cause analysis, and can be used in a wide variety of situations. Here are some examples:
- When you need to identify the cause of a problem
- When you need to improve a process or product
- When you need to brainstorm ideas for a new product or service
- When you need to make a decision about which solution to implement
When to avoid using itThe Ishikawa diagram is not always the best tool for the job. Here are some situations where it might not be the most appropriate:
- When the problem is very simple and there is only one possible cause.
- When you need to identify all potential causes of a problem (in which case, a brainstorming session might be more appropriate).
- There could be many causes for complex defects, which can make the diagram cluttered. In this case you could use pareto analysis to identify the top 20% of causes for further analysis.
- The relationships between different causes can be difficult to identify. Using a flow diagram may be more appropriate, particularly for processes that cross multiple teams or functions.
Top tips for getting the most out of Ishikawa diagrams
- Keep it simple - don't try to include too many factors on your diagram. Remember, the aim is to help you focus on the most important causes of a problem.
- Be specific - when you identify a cause, make sure it is as specific as possible. For example, rather than writing "lack of training", you could write "employees not receiving sufficient training on the new software".
- Get input from others - Ishikawa diagrams are most effective when they're created by a team. So, if you're working on a problem with others, make sure to get their input.
- Use colour - using different colours for different categories of causes can help to make your diagram more visually appealing and easier to understand.