Root Cause Problem Solving - Fishbone Diagram
Root Cause Problem Solving - Fishbone Diagram
Root Cause Problem Solving - Fishbone Diagram
Fishbone Diagram
Benefits:
Cause and effect analysis identifies core problems which, when modified, may significantly impact a process and its outcomes Whenever multiple possible explanations exist for a single issue, root cause analysis enables the team to better understand the issues and prioritize their improvement efforts Generates a large quantity a variable ideas in a short space of time May identify foci for data collection Need to understand why a process is not performing properly or producing the desired or intended results
When to use
Fishbone Diagram
Describe Prepare
Problem
ID Root Cause
Develop Actions
1. As a general guideline, the team can use the following questions to formulate their initial discussion:
What is the problem? Why does the problem need to be fixed? Where is it occurring (e.g. which department)? Who is involved? (e.g. doctors, nurses, staff)? When has this occurred? How often does it occur? How have you validated the problem exists? Who needs to buy into the solution?
2. The team should make sure they document in writing the description of the problem and scope of the possible solution space (See Template at end of Root Cause Problem Solving Section of Toolkit)
In the long run, the team will benefit from developing a clear description of the challenge. They should make sure to:
Identify the problem often, it relates to quality, service delivery and/or cost Make sure the problem exists Gather the necessary information (facts)
Fishbone Diagram
Describe Problem
ID Root Cause
Develop Actions
List the problem or issue at the head of the fish Label each bone of the fish with the following categories manpower, materials, machines, methods, measurement and environment (more categories can be added to address the issue)
3. Use an idea generating technique (e.g. brainstorming) to identify the factors in each category that may be contributing to the issue or effect being studied 4. For each category, ask what may be causing or contributing to the issue
For example, what machine related issues are we having? Answer: not reliable, breaking down, can find them, not capable, etc... Continue until you no longer get useful responses to the question5 whys. Add sub-factors to the appropriate bone
5. Repeat this procedure with each factor and create sub-factors by asking why is this happening?.
The fishbone diagram can be thought of as a visual representation of the information generated during a 5 whys exercise. In fact, 5 why analysis forms the basis of constructing a fishbone diagram
Fishbone Diagram
Describe Prepare
Problem
ID Root Cause
Develop Actions
Manpower
Method
Machines
CONSIDER... What Factors contribute to the issue/effect in each category? Note there may be sub factors...
Issue / effect
Environment
Materials
Measurement
Consider the use of ground rules for the team. Dialogue should be: Respectful, Non-judgemental, Objective, Open, Honest, Blame-free, Pertinent and Factual Hint: The team may not have to ask why five times to identify the root cause. In some cases, teams may have to ask why nine times and in other cases they may only have to ask why three times
Fishbone Diagram
Describe Problem
ID Root Cause
Develop Actions
1. Analyse the fishbone diagram: Look for themes or causes that appear in more than one column (e.g. a lot of time spent looking for people or things, training) as these are the most likely causes List most likely causes and determine which ones are the actual likely causes; you and the team may need to gather more information about these potential causes by observing the process as it occurs In many cases, a large number of the sub-factors are relevant and need improvement. Prioritise these based on impact versus effort 2. 3. Prioritise improvement work based on the list of actual and most likely causes of the issue Create written and detailed action plans for improvement work
Decision matrices that incorporate impact and effort are simple and useful tools to prioritise improvement work (e.g. high impact/ low effort causes would be a priority while low impact/ high effort would not)
Fishbone Diagram
Lets use an example to help illustrate how fishbone diagrams help identify the root causes...
Manpower
MD order illegible MD not avail to read results
Method
Many handoffs Batching work Porter Do not follow redirected FIFO
Machines
Pager malfunction
Lab equip
Inadequate training
Environment
Materials
Interpretation...
Using the Materials bone of the fish as an example, it says that the reason there are long turn around times for lab results related to materials are: There is a supply issue (caused by breakage, out of stock or spoiled materials) There are specimen issues (caused by breakage, out of stock or spoiled materials) There is a high volume of requisitions.
6
Fishbone Diagram
In some cases, you may find that using a process to understand root cause using the fishbone diagram tool is more intuitive for the team members to discuss
Fishbone diagram for Lab Turn Around Times
No requisition
Heavy workload
Fishbone Diagram
Establish and use a parking lot to address problems or issues that are identified but out of scope for the current root cause analysis Remember to use the 5 why technique to create the sub-factors in a fishbone diagram
Establish team norms and rules before embarking on root cause analysis specifically, teams must resist the temptation to assign blame, intent or emotion