Fishbone diagrams are an excellent risk management tool for the root-cause-focused aviation industry.
If you are wondering how to use fishbone diagrams, you first need to know what a fishbone diagram is.
A fishbone diagram derives its name from its fish-like appearance, with a head and several fins. Each “fin” or “branch” of a fishbone diagram describes a different element of the failure. The head of the fishbone describes the risk.
Fishbone diagrams are also known as cause-and-effect diagrams or Ishikawa diagrams. In real-world environments, they are used for three primary purposes:
The diagram uses its structure to understand all of the events and factors that lead up to the risk. Unlike a risk matrix, the fishbone diagram does not display any “subjective” elements such as likelihood or severity. Rather, it’s merely an objective way to understand root causes and subsequent events.
Also, fishbone diagrams are not concerned with the events that come after a risk, just simply the factors leading up to the risk. To create fishbone diagrams, it’s essential you understand exactly what a risk is.
There are 4 parts to a fishbone diagram:
When you understand the basic parts of the fishbone, it’s a fairly straightforward process for plugging in the appropriate data in the correct spot.
The first thing you need to do to complete a fishbone is choose your “framework.” While it’s not absolutely necessary to choose a framework, it keeps each fishbone diagram consistent. A framework could be:
Each category of your model will be a single fin. The SHELL model has 4 categories, which would correspond to six main fins in a fishbone diagram. The 5-M model has 5 categories, which corresponds to 5 fins. A custom model may have more or less categories.
Once you have chosen your framework, it’s useful to create a fishbone diagram template with each fin representing a part of your model. You will use this template every time (ideally).
The next thing you need to do is fill in the “head” of your fishbone diagram. The head is where you will input:
What this means is that when you choose a safety event on which to create a fishbone diagram, you need to understand the risk of the situation you are analyzing. Misinterpreting this can lead to an inaccurate understanding of your aviation SMS' safety events. Remember that a risk is the point at which safety control is lost. Common risks we often see are:
The following are qualifiers that indicate the part of the situation you're analyzing is NOT correct:
Your head statement should be concise and contain only the most basic wording to communicate what you are analyzing. This is usually accomplished in 5 words or less.
This step is the critical process of how-to-create fishbone diagrams. In this step, you:
The end result of this “why” root cause brainstorm is to come up with a handful of root causes for each fin category. You can highlight the root causes that are especially influential in the current situation and that you might include in a classification report.
The last thing you need to do is fill in your fishbone diagram with the data from your “why” root cause brainstorm:
In general, fishbone diagrams will be thoroughly full of information. Sometimes branches may have very few reasons – and perhaps even none.
The primary goal of fishbone diagrams is to help you understand in great detail why particular safety events occur. Basically, a fishbone diagram is a visual root cause analysis. Unlike other risk management tools that explore root cause analysis, such as a bowtie, a fishbone diagram’s root cause analysis is as thorough as it possibly could be. It includes:
This is an excellent tool to help understand where specific risk controls failed. Fishbone diagrams are best used in conjunction with another risk analysis tool that analyzes events, consequences, and impacts following a risk event.
If your aviation SMS database lacks adequate risk management tools, then you may consider the following aviation SMS database solution, which comes with the fishbone diagram.
Last updated October 2024.