Please enable JavaScript.
Coggle requires JavaScript to display documents.
R11.2 The process of applying root cause analysis to problems - Coggle…
R11.2 The process of applying root cause analysis to problems
The purpose of RCA is the process of discovering the root causes of problems in order to identify appropriate solutions.
The purpose is to help you achieve, WHAT IS THE PROBLEM?
WHAT CAUSED THE PROBLEM?
HOW CAN THE PROBLEM BE SOLVED?
DEFINE THE PROBLEM- what is the problem, what happens if u don't solve it
COLLECT DATA RELATING TO THE PROBLEM-
IDENTIFY WHAT CAUSED THE PROBLEM- identify as many causes as possible, involve all key stakeholders
PRIOTISE THE CAUSES- confirm the methodology you want to use
IDENTIFY SOLUTIONS TO THE UNDERLYING PROBLEM- to prevent the problem from happening again.
IMPLEMENT THE CHANGE- who will implement the change?, when?
MONITOR AND SUSTAIN- how will the solution be monitored?
THE 'FIVE WHYs'- The method for performing RCA is known as the Five Whys approach.
Involves every answer to a 'why' question being followed by a further and deeper, 'Why question'.
WHEN TO USE RCA- Should take place when an issue occurs that results in outcomes that disadvantages an organisation.
CRITERIA TO DETERMINE IF AN RCA SHOULD BE CARRIED OUT ARE?
Loss of data, complaints, system downtime, failure of service
HOW TO USE RCA- Identify what the problem is and the impact that it has on the stakeholders involved.
Gather info, how did it happen?
Use a method such as the 5 WHY's approach. You ask a WHY question and for the answer you ask further 'why' questions until the root cause of the problem is exposed.
The final step in the process is to establish how end when the system will be tested to ensure that it is performing as required.
Consider the impact, the main focus is to eliminate the problem and therefore suitable solutions have to be identified.
FISHBONE DIAGRAMS
A visual RCA tool to identify the possible causes of the identified problems.
Allows you to get down to the real root cause of the issue, rather than solving it's symptom.
You should consider using a fishbone diagram: To identify possible causes to an issue. When your teams thinking and brainstorming tends to get stuck.
STEP 1- Agree on a problem statement
STEP 2- Identify the major categories causing the problems
Step 3- Write the categories of causes as branches off the central line
STEP 4- Identify all the possible causes of the problems by asking why. Add ideas as a branch from the categories
STEP 5- Continue to ask why about each cause and write sub causes branching off the causes identified above.
STEP 6- When you run out of ideas, focus attention to places on the diagram where ideas are limited.