The fishbone diagram (also known as the Ishikawa or cause-and-effect diagram) is a common tool to identify or prevent a particular event. The diagram was popularized in the 1960's in the Kawasaki shipyards by Kaoru Ishikawa, who would become a founding father of modern management. It gets its name due to the resemblance of a fish skeleton, with the effect at the fish's head and the grouped causes extending out like fish bones. The Ishikawa diagram is a cause analysis tool (along with the 5 Whys, Pareto chart, or Scatter diagram) used during root cause analysis to group causes into different sub-categories that are used as the "bones" of the diagram (measurements, materials, methods, etc.). Used effectively, the diagram helps teams brainstorm and categories all potential causes for a failure rather than focus only on the symptoms. By classifying issues under the appropriate category, teams can systematically explore sub-causes associated with each primary factor.
Introduction to Problem-Solving
Effective problem solving is at the heart of successful maintenance management. When equipment fails or processes break down, it's essential to not just fix the immediate issue, but to identify the root cause and implement a solution that prevents recurrence. The fishbone diagram, also known as the Ishikawa diagram or cause-and-effect analysis, is a powerful visual tool that supports this systematic approach. By visually mapping out all contributing factors—such as materials, methods, machines, measurement, manpower, and environment—maintenance teams can conduct a comprehensive exploration of the problem. This methodical process helps teams move beyond surface-level symptoms to uncover the underlying cause of a problem. Using a fishbone diagram as part of root cause analysis ensures that all possible factors are considered, making it easier to identify the root cause and develop effective, lasting solutions.
Understanding Ishikawa Diagrams
Ishikawa diagrams, commonly referred to as fishbone diagrams, are designed to help teams identify the root cause of a problem by visually organizing all contributing factors. The diagram starts with a horizontal line representing the problem statement—the "fish's head"—and branches out into major categories such as environmental factors, materials, methods, and more. Each major category forms a "bone" of the fish, with sub-branches detailing specific contributing factors. This visual representation makes it easier to see how different elements interact and lead to the cause of a problem. By breaking down the problem into major categories and then drilling down into sub-branches, teams can systematically identify the root cause. Ishikawa diagrams are especially useful in maintenance and quality management because they provide a clear, structured way to analyze complex issues and ensure that no potential cause is overlooked.
When to Use Fishbone Diagram
The Ishikawa diagram is a versatile tool that can be used in almost any system or process to break down varying causes. During a root cause analysis, the diagram should be used during the cause and effect analysis phase to categorize contributing factors.
The tool can also be used:
- To dissect a problem statement
- To improve a process or system
- To evaluate a new design and identify factors
A brainstorming session involving various stakeholders can help identify and categorize potential causes of issues, allowing for a more comprehensive analysis leading to effective solutions.
General procedure
Fishbone diagrams are used during a root cause analysis as a way visualize the relationship between variable causes and a particular problem. Historical data can provide valuable insights into past performance and issues, guiding the troubleshooting process effectively. Below is the general procedure when using the fishbone diagram:
- Determine the problem or effect and place it to the far right of the graph (the fish's head). A Job Plan and Job Package should be created by the Maintenance Planner to ensure structured processes.
- Categorize the major causes of the effect and use these as the headings for each fishbone
- Brainstorm all causes for the effect and group these horizontally along the main causal categories, utilizing data from real-time and historical information.
- Determine sub-causes by using the 5 Whys technique (also including environment). Understanding effect relationships is crucial in this step to see how various factors influence one another.
Creating a Solution
After identifying the root cause of a problem using a fishbone diagram, the next step is to develop and implement a solution that addresses the underlying issue. This process begins with a thorough analysis of the problem, including a review of maintenance history and an examination of the production process to ensure all relevant factors have been considered. The solution should be tailored to eliminate maintenance problems at their source, whether that involves updating equipment, revising processes, or providing additional training. It's important to create a detailed action plan that outlines specific steps, assigns responsibilities, and sets measurable goals. Once implemented, the effectiveness of the solution should be monitored and adjustments made as necessary to ensure the problem does not recur. By following this structured approach, maintenance teams can not only resolve the immediate issue but also improve overall operational efficiency and reliability.
Advantage and disadvantages
While the Ishikawa diagram is an important tool to identify the underlining root causes of a effect, like all tools, it comes with its own advantages and disadvantages.
Advantages
- Ishikawa diagram is a visual brainstorming tool that's helpful for visualizing issues to stakeholders. It encourages examining various systems, such as machinery, processes, and maintenance management, to identify root causes.
- By visually brainstorming various causes, the diagram prevents teams from limiting their scope or thinking. Including quality control personnel in these sessions ensures a comprehensive approach to problem-solving.
- Repeatedly asking "why" at various stages drills down the root cause. Utilizing mind mapping alongside the Ishikawa diagram can further uncover deeper insights into potential issues.
- Displays multiple causes simultaneously and gives high-level view
Disadvantages
- Effects that are the result from multiple causes the diagram to become overly complex and unwieldy
- The interrelationship between causes are not readily apparent
- Not all listed causes have a direct impact on the effect being studied. It can be difficult to differentiate relevant and non-relevant causes which leads itself to low success rates as teams do not have the time or resources to address every possible cause
Get Inspired
Struggling with reactive maintenance and constant firefighting? Discover six proven steps to reduce breakdowns, improve reliability, and turn maintenance into a driver of business value.
Five common spare parts challenges that we encounter regularly, illustrated by solutions based on real-world examples.
Ontdek tijdens dit webinar hoe organisatiecultuur het succes van onderhoudsstrategieën bepaalt en hoe je cultuur kunt inzetten als versneller van duurzame verandering. Met praktische voorbeelden laten we zien hoe je cultuur bespreekbaar maakt en benut voor blijvend resultaat.
