Project Management ABC: I for Ishikawa Diagram

Identify Causes, Solve Problems

What is an Ishikawa diagram?

The Ishikawa diagram was developed in the 1960s by Japanese quality management expert Kaoru Ishikawa. The goal was to provide a method for analyzing the causes of a specific problem in a structured way. It is presented in the form of a fishbone diagram: The problem (the effect) is on the right, and from there the main categories of causes branch out as lines—the so-called “bones”—to the left. Initially, there were four categories, but these were gradually expanded to six and then eight as the business world became more complex and more factors needed to be taken into account. Each of these main categories is further subdivided to identify possible individual causes. The result is a clear, graphical representation of complex relationships that promotes both analytical thinking and creative solutions.

Structure and Elements of the Ishikawa Diagram

On the right is the effect—that is, the problem to be analyzed. From there, there are usually six main branches, which typically represent the following categories:

1. Human (Personnel): This category includes errors caused by human behavior, insufficient knowledge, communication issues, conflicts, or lack of motivation
2. Machinery (Technology): Technical defects, outdated systems, or, for example, a lack of maintenance fall into this category.
3. Material: This refers to the quality of the materials used, as well as the availability and specifications of raw materials and auxiliary materials.
4. Method (Processes): Workflows, standards, procedures, or, for example, the project management method fall under this category.
5. Environment: All environmental conditions—including the physical or organizational environment—that occur outside the company but still influence the process fall into this category. These can include, for example, environmental factors such as temperature or humidity, as well as competitors, legal requirements, and industry trends.
6. Management: Managers also often have a significant influence on problems. Management errors, inadequate planning, or poor communication on the part of managers therefore fall into this category
7. Measurement (data): This refers, for example, to erroneous or missing measurement data, or incorrect interpretations.
8. Money: Cost pressures, budget cuts, or poor investment decisions often have a significant impact as well and should therefore be taken into account.
   These categories serve as a framework for structured brainstorming. They can be adapted or expanded depending on the industry and the specific problem at hand.

Areas of Application in Project Management

The Ishikawa diagram has a wide range of applications in project management, particularly in the following areas:

• Quality Management: Analysis of Deviations in Product or Process Quality
• Risk Management: Identifying Potential Sources of Error in Advance
• Error Analysis: Investigation of Malfunctions or Problems in the Project Process
• Lessons Learned: Structured Review After Project Completion
• Team Communication: Promotes the exchange of different perspectives and a shared understanding

Step-by-Step Guide to Creating

1. Define the problem:
The problem to be investigated must be formulated clearly and unambiguously. It should be a concrete, observable phenomenon (e.g., “Project delay of 4 weeks”). Now draw a template for the diagram and write the problem on the right side as the head of the fish.

2. Identify Causes (Brainstorming):
The team then works together to identify possible causes for each main category and notes them on the corresponding branches. This requires creativity, but also factual knowledge. The goal at this stage is not merely to collect high-quality causes, but to examine the problem from a wide variety of perspectives in order to identify even less obvious causes.

3. Analyze causes:
Next, each cause is examined: How plausible is it? Is there any evidence or circumstantial evidence? The causes are evaluated based on relevance, frequency, or impact on the problem, for example, using an ABC analysis. Use this approach to identify the most likely causes, or the causes with the greatest impact.

4. Develop Actions:
An analysis of the root causes is only useful if actions are subsequently developed based on the results. You should now define specific steps to resolve the problem or prevent it from recurring.

Advantages and Limitations of the Ishikawa Diagram

Advantages:

• Systematic analysis: Enables a structured examination of complex problems.
• Team-oriented: Promotes collaborative work and diverse perspectives.
• Visually appealing: The graphic representation makes it easier to understand.
• Flexible: Can be used in a wide variety of contexts and industries.

Borders:

• No weighting of causes: The diagram shows only possibilities, not probabilities.
• Requires facilitation: Without a clear structure, brainstorming can become disorganized.
• Not suitable for simple problems: When the causes are clear and obvious, the effort required is disproportionately high.

Case Study: Analyzing a Project Delay

A project team is facing the challenge of a significant delay in an IT project. The project management team decides to use an Ishikawa diagram. The following insights are gained during a workshop:

• People: Inadequate resource planning, overburdening of individual team members
• Method: Lack of agile processes, no clear sprint goals
• Machine: Outdated development environment, long load times
• Context: High communication demands due to remote work
• Material: Incorrect requirements due to unclear customer specifications
• Management: Unclear division of roles, lack of leadership in prioritizing goals
• Measurement: Inadequate monitoring; delays are not detected in a timely manner
• Money: Budget constraints are hindering important technical upgrades and external support

Based on the analysis, targeted measures will be identified, including adjustments to the team structure, the implementation of appropriate agile methods, and improvements to the technical infrastructure.

Tips for Effective Use

• Interdisciplinary teams: Involve various departments to avoid blind spots.
• Facilitation: An experienced facilitator ensures structure and a focus on results.
• Combining the 5 Whys Method: To dig deeper into the root causes rather than staying on the surface, you can use the 5 Whys Method.
• Regular Updates: The chart is a living document and should be updated as new information becomes available.

Conclusion

The Ishikawa diagram is a proven tool in the project management toolkit. It helps teams systematically analyze problems, identify root causes, and develop sustainable solutions. Especially when dealing with complex challenges involving many influencing factors, the fishbone diagram is a valuable tool for increasing transparency and efficiency throughout the project. With a clearly defined problem, a structured approach, and an open team culture, the Ishikawa diagram reaches its full potential.

Find out more about the myPARM project and portfolio management software:

Would you like to get to know myPARM in a demo? Then make an appointment with us right away!