The Ishikawa Diagram: Definition and Maintenance Example!

reading time : 2 min

Picture of Lucie Monnot
Lucie Monnot

Content Marketing Manager

In maintenance professions, identifying and understanding the causes of a problem is essential. The faster an issue is brought under control, the sooner production can resume. This saves both time and money. In this context, the Ishikawa diagram is a tool that should not be overlooked. Discover how to implement it.

Table of Contents

Couverture d'un document professionnel structuré autour de l'analyse des causes et effets dans les opérations terrain, en lien avec la démarche du diagramme d'Ishikawa appliquée à la gestion des services.

What is the Ishikawa diagram?

Definition of the Ishikawa diagram

The Ishikawa diagram, also known as the cause-and-effect diagram or fishbone diagram, is a quality management tool.
 
It makes it possible to identify, organize, and analyze the potential causes of a specific problem. It is often used in the context of maintenance problem-solving, to identify the various root causes of equipment or process failures.

The principle of the Ishikawa diagram

The principle of the Ishikawa diagram consists of graphically representing the possible causes of a problem, classifying them into major categories (such as methods, machines, manpower, materials, etc.). These categories are then subdivided into sub-causes, enabling an in-depth analysis of the factors contributing to the problem. The diagram takes the form of a fish, where the head represents the problem to be solved and the main bones represent the cause categories.

The 5Ms of the Ishikawa diagram

The Ishikawa diagram often uses the 5Ms to categorize the potential causes of a problem. Here is what each “M” represents:
  1. Manpower (Man): human factors, such as the skills, training, motivation, or attitude of employees.
  2. Materials (Material): the quality and availability of the materials used in the process.
  3. Methods (Method): the procedures, processes, and rules followed, as well as the way in which the work is organized.
  4. Machines (Machine): the equipment, tools, and technologies used in the process.
  5. Milieu (Environment): environmental factors, such as working conditions, temperature, humidity, or company culture.
These categories help to structure the analysis of the potential causes of problems in a process.

How to create an Ishikawa diagram?

Identify the problem

Start by clearly defining the problem to be solved. This problem is placed at the head of the diagram, often on the right, like the head of a fish.
Draw the skeleton of the diagram
Draw a horizontal line representing the spine of the fish. This line starts from the problem and extends to the left. From this line, draw main branches for each cause category, generally the 5Ms: Manpower, Materials, Methods, Machines, and Milieu.
Field service management solutions SMEs SMIs

Brainstorming causes

For each main category (the branches), identify the possible causes of the problem. You can use brainstorming techniques with your team to collect as many potential causes as possible. For each cause identified, draw sub-branches to detail and break down the causes into more precise elements. For example, under “Manpower,” you might include sub-causes such as “lack of training” or “operator fatigue.”

Analyze and prioritize causes

Once all the causes have been identified and listed, analyze them to assess their potential impact on the problem. Some causes will be more critical than others. It may be useful to use prioritization techniques to determine which causes should be addressed first.

Develop and implement corrective actions

For each priority cause identified, propose specific corrective actions. Then implement these actions while monitoring their effectiveness to ensure they resolve the identified problem.

Monitoring and review

After implementing corrective actions, it is important to monitor the results to ensure the problem has been resolved. If necessary, the diagram can be revised and updated based on new information or changes in the process.

Example of an Ishikawa diagram in maintenance

Problem: frequent breakdowns of a production motor
1. Manpower
  • Lack of training among technicians.
  • Improper handling of equipment.
  • Absence of preventive maintenance procedures.
  • Operator negligence.
2. Machines
  • Wear of components.
  • Manufacturing defect in the motor.
  • Inadequate corrective maintenance.
  • Lack of specific spare parts.
3. Methods
  • Maintenance plan not adhered to.
  • Poor organization of operations.
  • Absence of up-to-date technical documentation.
  • Non-standardized maintenance process.
4. Materials
  • Poor-quality spare parts.
  • Inadequate or insufficient lubricants.
  • Wrong choice of components during repairs.
  • Use of materials not compliant with specifications.
5. Milieu (Environment)
  • High ambient temperature.
  • Excessive humidity conditions.
  • Accumulation of dust and debris.
  • Poor ventilation around the motor.
Each category of the Ishikawa diagram makes it possible to identify the potential causes related to the motor breakdown, thereby facilitating the development of an action plan to prevent or correct these failures.

How to combine it with project management?

  • Combining the Ishikawa diagram with project management makes it possible to identify and analyze the potential causes of problems at every stage of the project. Here is how to integrate it effectively:
    1. Risk identification: use the diagram to explore the causes of risks in each phase of the project.
    2. Cause analysis: classify causes using the 5Ms to understand the influencing factors.
    3. Planning corrective actions: prioritize and develop solutions for critical causes.
    4. Project monitoring: monitor the effectiveness of corrective actions.
    5. Using an appropriate tool: adopt project management software capable of creating and managing Ishikawa diagrams, thereby facilitating collaboration and real-time updating of analyses. This ensures greater traceability and efficiency in project risk management.
    Integrating the Ishikawa diagram into project management and maintenance processes is a proactive approach that makes it possible to anticipate problems and improve overall performance. By combining this tool with project management software, it is possible to maximize the efficiency of analyses and ensure more rigorous and transparent risk management. Adopting this approach contributes to better decision-making and to the success of projects.

  Projet, demande de démonstration ou d’essai gratuit ?

Frequently Asked Questions

FAQ – The Most Frequently Asked Questions About Nomadia

Why Choose Nomadia?

As France’s leading publisher of Smart Mobility SaaS solutions, Nomadia supports more than 175,000 field professionals every day. Our solutions are easy to use, quick to deploy, and deliver significant and immediate return on investment.

Drawing on the expertise of both a software publisher-integrator and a consulting firm, Nomadia’s teams provide tailored support, from data consulting to the deployment of mobile devices. Finally, our technical support team is available 24/7 to assist you.

Who Are Nomadia Solutions Designed For?

Nomadia solutions support the digital transformation of all mobile professionals: field sales representatives, delivery drivers, technicians, auditors, healthcare workers, inspectors, service providers, security patrol officers, experts, and more.

Whether for SMEs or large enterprises, our solutions adapt to businesses of all sizes and across all industries.

How Much Does It Cost?

Nomadia Delivery offers transparent and flexible pricing, which primarily depends on the number of users (for example, planners and dispatchers) rather than a fixed cost per parcel.

Thanks to this model, you can control your delivery costs based on the number of resources (users) involved in route management, providing great flexibility to adjust your subscription according to the size of your fleet and your operational needs.

Is It Compatible with My Current ERP System?

Yes! Nomadia Delivery has been designed to integrate quickly and easily into your existing environment thanks to our powerful and secure APIs. Our solution is compatible with most ERP systems on the market. API integration enables the automatic synchronization of your transport orders, customer orders, and customer information, ensuring smooth and error-free delivery tracking. The solution also offers user-friendly import capabilities with data validation controls, as well as export options in multiple customizable formats.

Is It Suitable for Our Delivery Volume?

Yes, Nomadia Delivery is ideal for companies that manage a high volume of deliveries and want to optimize their routes, create balanced territories for their drivers, and ensure precise tracking of every parcel. Nomadia Delivery adapts to fleets of all sizes!

Can Multiple Warehouses or Depots Be Managed?

Yes, our solution allows you to manage multiple warehouses or depots. It centralizes data and optimizes routes or service operations for each of them.

Is There a Limit to the Number of Stops in Route Optimizations?

No, there is no strict limit to the number of stops in route optimizations. Our solution can handle large volumes of stops and quickly calculate optimized routes.

         Project, request for a demonstration or a free trial?

nomadia logo

Geoconcept becomes Nomadia

Geoconcept brands are officially
evolving into Nomadia

nomadia logo

TourSolver becomes
Nomadia TourSolver