How do you use the Fishbone diagram model to diagnose and resolve change problems?

1 What is the Fishbone diagram model?

The Fishbone diagram model is a visual method that helps you analyze the causes of a problem or an undesired outcome. It is called a Fishbone diagram because it resembles the skeleton of a fish, with a head, a spine, and several bones. The head represents the problem or the effect, the spine represents the main categories of causes, and the bones represent the sub-causes or factors that contribute to the problem. The model helps you organize your thoughts, identify the root causes, and find potential solutions.

2 How to create a Fishbone diagram?

To create a Fishbone diagram, you need a clear statement of the problem or the effect that you want to solve or improve. For example, if you are implementing a new software system, your problem statement could be "Low user adoption of the new system". Then, you need to brainstorm the main categories of causes that could affect the problem. These categories could be based on the 6 Ms (Manpower, Method, Machine, Material, Measurement, and Mother Nature), the 4 Ps (People, Process, Product, and Place), or any other framework that suits your context. For example, you could use the 4 Ps to group the causes of low user adoption. Next, you need to brainstorm the sub-causes or factors that fall under each category. For example, under People, you could list factors such as lack of training, resistance to change, or low motivation. You can use the 5 Whys technique to dig deeper into each sub-cause and find the root cause. For example, you could ask "Why is there resistance to change?" and then "Why is there fear of losing skills?" and so on. Finally, you need to draw the Fishbone diagram by placing the problem statement at the head, the main categories at the spine, and the sub-causes at the bones. You can use a paper, a whiteboard, or a software tool to create the diagram.

3 How to use the Fishbone diagram for change management?

The Fishbone diagram is an invaluable tool for change management, as it aids in understanding the current situation, recognizing the gaps, and planning the actions. To use the Fishbone diagram for change management, start by defining a specific, measurable, and relevant problem or effect to change. Involve stakeholders in creating the diagram to gain different perspectives and buy-in. Review the diagram and prioritize the causes that have the most impact on the problem. Generate and select the best solutions for each cause using brainstorming, affinity diagrams, or criteria matrices. Then, create an action plan to implement these solutions using a SMART framework. Lastly, monitor and evaluate the results of your action plan with indicators, feedback, or surveys.

4 What are the benefits of the Fishbone diagram model?

The Fishbone diagram model can be beneficial for change management in many ways. It helps you focus on the root causes of the problem, not the symptoms or the blame, and it allows you to visualize the relationships and interactions between the causes and the problem. Additionally, it can help generate and compare multiple solutions and alternatives, as well as engage and communicate with stakeholders to foster collaboration and problem-solving. Moreover, it can align your change actions with your change goals and strategy.

5 What are the limitations of the Fishbone diagram model?

The Fishbone diagram model is not a perfect tool and has some limitations, such as subjectivity and bias depending on the knowledge of the people creating it, complexity and confusion if there are too many causes or sub-causes, incompleteness or inaccuracy if some causes are overlooked or misinterpreted, static and outdated if the problem or environment changes over time, and ineffective if the solutions are not implemented or monitored properly. Therefore, it is important to use the Fishbone diagram model with caution and critical thinking, as well as to complement it with other tools and methods for change management.

6 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?