pop up image

How to Do Root Cause Analysis in 6 Steps?

Best practice to an effective root cause analysis requires performing the following steps: definition of the problem, gathering data, identifying additional causes, identifying the root cause or causes, prioritizing the causes, and implementation of the solution.

1. Define the Problem

The first step when performing root cause analysis is to analyze the existing situation. This is where the team identifies the factors that impact the problematic event. The outcome of this step is a statement that comprises the specific problem. A small team is tasked with the definition of the problem. This could be research staff who assesses and analyzes the situation. The question to be answered at this initial stage is: What is the problem? How does the problem affect customer needs? etc.

2. Collect Data about the Problem

A critical step in root cause analysis is the collection of relevant data about an incident or a problematic event. Documenting all the characteristics and specifications of the event will help you answer questions like What are the contributing factors? When did the problem occur? Is it a repeating event? What is the observed impact? etc.

3. Determine Potential Causal Factors

Creating a sequence of events is important to identify causal factors that can contribute to the observed problem or event. The project team tasked with the analysis of the problem should establish a timeline of events and brainstorm as many potential causal factors as possible by asking “Why?” questions. Using a causal graph, for instance, helps to represent the connection between events visually and enables tracking of the root cause.

4. Determine the Root Cause of the Problem

This is the time to identify as many causes as possible. The analysis team can use techniques such as the 5 Whys, Fishbone analysis, or Pareto chart to narrow down the potential underlying cause or causes of the problem and the major contributing factors. During this phase, stakeholders and other relevant teams should be involved.

5. Prioritize the Causes

Once the root causes are established, they need to be prioritized and tackled accordingly. To determine which cause or challenge to address first, the analysis team needs to assess what is the impact of the cause - the higher the impact, the greater its priority. Another point when prioritizing root causes is the number of causal factors triggered by a specific challenge - the greater the number of causal factors, the greater the impact of the root cause is and yields immediate addressing.

6. Solution, Recommendation, and Implementation

The next step upon establishing root causes and their prioritization is finding solutions to the problem and their implementation. Brainstorming is a great way to attempt and come up with a variety of potential solution scenarios. Another approach is interviewing as many people as possible. Gathering input as well as the implementation of the solution requires involvement from everyone. On one hand, every recommendation counts, and on the other, a successful implementation is the one that sticks with everyone affected. 

How to Use the Root Cause Analysis Tools to Perform Root Cause Analysis?

Root cause analysis tools represent methods designed to help you conduct RCA and determine the underlying cause of an event or a problem. Some of the most widely used RCA tools and their utilization are explained below.

The Fishbone Diagram is a technique that helps to group multiple causes into various categories. By identifying such similarities between causes, you can easily navigate through the challenges, prioritize their impact, and ultimately determine the underlying cause of the problem. To use the fishbone diagram, the head of the fish needs to represent the problem, while the primary group causes are represented along the fishbone. You can also draw additional secondary causal factors along each primary cause.

The Fault Tree Analysis (FTA) is another root cause analysis tool that uses the boolean logic to determine a problem’s root cause. Through the visualization of the problem at the top of the chart and mapping all the affected subsystems in the form of branches, the tool establishes the relationships between a problematic event and its effect on other parts of a system. FTA uses deduction to determine the root causes of events, and it is helpful to identify system risks.

The 5 Whys analysis is a technique from the Lean toolset that helps to narrow down the root cause of a problem by simply asking why questions. To arrive at the root cause of an event, you need to ask “Why” as many times as needed. Normally it takes no more than five times to identify a root cause. The evaluation method is very effective in determining how different root causes relate to one another and brings clarity into the chain of events.

Do You Need a Template to Perform a Root Cause Analysis?

Root cause analysis templates can be very helpful in establishing the foundation of the process and streamlining its progress.

Reporting RCA templates include key data such as the description of the event at fault, an established timeline of events leading to the event at fault, the team tasked with the analysis process, and the RCA method that will be used to arrive at the root cause. The information can be laid out in any form you like.

RCA tool templates are useful to visualize the entire analysis process. RCA templates such as 5 Whys or Pareto chart templates can be easily created using a variety of programs such as Excel or other niche software solutions.

Which Step Should You Write a Root Cause Analysis Report on?

All the steps in a root cause analysis should be briefly and concisely documented in an RCA report upon the completion of the analysis. The information that needs to be listed on the report is listed below:

  • Introduction. Outline the purpose of the report, and determine the intended audience and the scope of the document.
  • Problem Description. Provide a clear and detailed description of the problematic event, including the date of occurrence, the involved person or team who detected the event, the affected parties, and the extent of the effects in as many details as possible.
  • Establish Timeline of Events. Capture and describe all the events that led to the event at fault and the ones that followed it. Be punctual about the timing of each event, the involved parties, and rich details when describing the events.
  • Utilized Methods. Provide information about the used analysis methodologies to determine the root cause of the problem, the people involved at each step of the process, and their specific roles.
  • Findings Explanation. Ensure that all the findings are captured and reported, no matter how small and insignificant they may seem. The findings should clearly explain the root cause of the problem.
  • Recommendations. Explaining the problem in detail should also include all the additional causes the team analyzing the problem has found. This part of the report will help further investigate cause-and-effect relationships, and it will prevent the rise of a potential problem.

Which Approach Should You Use to Perform Root Cause Analysis?

To determine the most effective way to find the root cause of a problem it is important that you diligently perform the first steps of the process. By asking the right questions and gathering critical details about the event, you’ll manage to determine the problem and its contributing factors. Based on that information, the most suitable root cause analysis approach will correspond to factors such as the number of causal factors identified and their diversity, how they relate to one another, whether you need to apply deduction, etc.

Which Sectors Can You Perform Root Cause Analysis on?

RCA is a powerful approach to determining problems’ underlying causes, and it allows companies to create stable work processes by preventing future occurrences of the same issue. The utilization of root cause analysis in a wide range of industries and sectors stems from its ability to solve problems and support an organizational culture of continuous improvement. Some of the industries where RCA is highly applicable are listed below.

  • Manufacturing
  • Health and Safety
  • Telecommunications

How Should You Organize Your Root Cause Analysis Meetings?

Root cause analysis meetings allow teams and stakeholders to learn and improve. Through an in-depth analysis of a problem, its underlying cause, and additional causal factors, RCA meetings bring not only solutions to an existing problem but also have a preventive nature. Everyone involved in the problem should be involved in RCA meetings, team members, leaders, and stakeholders alike.

Phase 1: RCA meetings should be organized and led by leaders familiar with the specifics of the problem itself. It’s their role to clarify the meeting’s structure for all the attendees. They should also explain the goal of the meeting. 

Phase 2: To navigate through the exact sequence of events, a timeline should be established explaining how the problem was detected, when, and who raised the alarm. The root cause analysis method employed should be announced. 

Phase 3: During the next phase of the meeting, stakeholders and team members are involved in the discussion to list all the potential causes of the event, considering their valuable insights and experience. 

Phase 4: Upon listing potential causes, facts about the problem should be gathered to help narrow down the actual potential causes and eliminate the ones that fail to explain the event.

Phase 5: Once the root cause or causes are identified, everyone involved in the meeting should discuss the next logical steps to take to remedy the problem and prevent its further occurrence.

What Is the Effect of Performing Root Cause Analysis on Work Efficiency?

Root cause analysis provides the means and tools to find and eliminate problems. Most importantly, the method supports problem-solving with optimal use of resources which greatly impacts the overall work efficiency. By targeting the root causes of problems and tackling all causal factors, the technique allows organizations to be more effective and to increase their work efficiency. The logical process of capturing the root cause of a problem, the preventive nature of RCA, and the supporting real data are some of the key advantages that make the analysis model so appealing and successful.

Businessmap is the most flexible software platform

for outcome-driven enterprise agility.


In Summary

To perform an effective root causes analysis, there are six main steps that you need to do.

  1. Define the Problem.
  2. Collect Data about the Problem.
  3. Determine Potential Causal Factors.
  4. Determine the Root Cause or Causes of the Problem.
  5. Prioritize the Causes.
  6. Solution, Recommendation, and Implementation.
Iva Krasteva

Iva Krasteva

Content Creator Expert | Agile Practitioner | Kanban Certified

With a background in Intellectual Property, SEO, content writing, and training in Lean, Agile, and Kanban, Iva is an enthusiastic Agile practitioner who embraces collaboration and flexibility every step of the way. Driven by constant learning and knowledge and fascinated by people's creativity.

Start your free trial now and get access to all features.

During the 14-day trial period you can invite your team and test the application in a production-like enviroment.