The Leading Source Of Original Research And Insights On Business Model Strategy, Digital & Tech Business Models
The Fishbone Diagram In A Nutshell
The Fishbone Diagram is a diagram-based technique used in brainstorming to identify potential causes for a problem, thus it is a visual representation of cause and effect. The problem or effect serves as the head of the fish. Possible causes of the problem are listed on the individual “bones” of the fish. This encourages problem-solving teams to consider a wide range of alternatives.
A Fishbone Diagram is simply a visual representation of cause and effect. The problem or effect serves as the head of the fish. Possible causes of the problem are listed on the individual “bones” of the fish and where possible, are grouped into categories on each bone.
Through the use of categories, Fishbone Diagrams encourage problem-solving teams to consider a wide range of alternative, less-obvious causes.
Cause and effect diagrams can also:
Help businesses understand where or why a process is not working.
Be used in product development where the product concerned is intending to solve a consumer problem.
Identify potential problems before they arise, such as the teething problems associated with new product launches.
For example, Mazda used the Fishbone Diagram to design their now iconic MX-5 sportscar. Engineers even used the diagram to identify that the current design of the door would not allow the driver to rest their arm on it while driving.
How to use the Fishbone Diagram
Using the Fishbone Diagram in practice is relatively simple, but the technique is nevertheless a powerful way to unearth causes to problems.
Teams of employees should follow this 5-step process:
Define the problem, and then write it at the mouth of the fish. The problem itself should as clear and concise as possible. Make sure there is an agreement between all team members before proceeding.
Define the categories of causes, and then write them along the bones of the skeleton of the fish. Categories will vary from industry to industry, but common categories include the environment, procedure, human resourcing, and equipment.
Brainstorm potential causes. Begin with the question “Why does this happen?” and then write each response as a branch of the relevant category.
Probe further. For the answers gleaned in step 3, ask the same question once more. These “sub-causes” can be written as secondary branches and are particularly important for large or complex causes that need further investigation.
When the group has run out of ideas, it’s time to investigate the causes in more detail. Look for causes that appear more than once but with slightly different wording. Employee or consumer surveys can also be used to verify the validity of particular causes.
Fishbone Diagram best practices
Creative a diverse team
Although the temptation may be to create a team who has direct experience with the problem, it’s more beneficial to include other employees too. Outside employees who do not directly deal with the problem can bring a balanced, unbiased, and objective stance.
Fishbone Diagrams with many potential causes quickly become cluttered and confusing. Consider asking each member of the team to vote for their four most probable causes. From there, choose the four categories that received the most votes and begin the process.
The Fishbone Diagram is a root cause analysis that assists in accurately identifying the causes of an effect, event, or problem.
The Fishbone Diagram is a collaborative and thorough five-step process involving teams of employees.
To be effective, the Fishbone Diagram technique requires a diverse range of perspectives and the ability to correctly identify the most likely causes.
Other root cause analyses, frameworks, and product portfolio tools
Strictly Necessary Cookies
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.