Print Friendly, PDF & Email

Root Cause Analysis (RCA) is a popular and often-used technique that helps people answer the question of why the problem occurred in the first place. It seeks to identify the origin of a problem using a specific set of steps, with associated tools, to find the primary cause of the problem.

Finding the genesis of a problem can be a difficult task. The nature of RCA is to identify all and multiple contributing factors to a problem or event. This is most effectively accomplished through analysis methods such as:

  • Barrier Analysis — Investigation method that involves the tracing of pathways by which a target is adversely affected by a hazard, including the identification of any failed or missing countermeasures that could or should have prevented the undesired effect(s).
  • Change Analysis — Looks systematically for possible risk impacts and appropriate risk management strategies in situations where change is occurring.
  • The “5-Whys” Analysis — A simple problem-solving technique that helps users get to the root of the problem quickly. It was made popular in the 1970s by the Toyota Production System. This strategy involves looking at a problem and asking “why” and “what caused this problem.”
  • Causal Factor Tree Analysis — An investigation and analysis technique used to record and display, in a logical, tree-structured hierarchy, all the actions and conditions that were necessary and sufficient for a given consequence to have occurred.
  • Fish-Bone Diagram or Ishikawa Diagram — Derived from the quality management process, it’s an analysis tool that provides a systematic way of looking at effects and the causes that create or contribute to those effects. The design of the diagram looks much like the skeleton of a fish.
  • Failure Mode and Effects Analysis — A “system engineering” process that examines failures in products or processes.
  • Fault Tree Analysis — The event is placed at the root (top event) of a “tree of logic.” Each situation causing effect is added to the tree as a series of logic expressions.
  • Pareto Analysis — A statistical technique in decision making that is used for analysis of selected and a limited number of tasks that produce significant overall effect. The premise is that 80 percent of problems are produced by a few critical causes (20 percent).

Organizations with staff skilled in effective problem-solving and root cause analysis have the benefit of providing tangible evidence of cause and effect and solutions to solve real problems as well as developing solutions to problems that are effective and long lasting.

Root Cause Analysis Training

Tonex offers a 3-day Root Cause Analysis Training course as well as a 2-day Root Cause Analysis Training for Supervisors, a 2-day Root Cause Analysis Training for Engineers, a 2-day Root Cause Analysis Training for Beginners class and a 3-day Root Cause Analysis Training for Healthcare Professionals.

Participants learn about many topics related to RCA such as:

  • Problem-solving tools
  • Root cause elimination
  • Statistical hypothesis
  • Human factors
  • Cause mapping
  • Using data
  • Developing corrective and preventative actions

Why Tonex?

— For over 30 years Tonex, while presenting highly customized learning solutions, has worked with organizations in improving their understanding and capabilities in topics often with new development, design, optimization, regulations and compliances that, frankly, can be difficult to comprehend.

— Ratings tabulated from student feedback post-course evaluations show an amazing 98 percent satisfaction score.

–Reasonably priced classes taught by the best trainers is the reason all kinds of organizations from Fortune 500 companies to government’s most important agencies return for updates in courses and hands-on workshops

Contact us for more information, questions, comments.

 

 

Request More Information

  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.