Root cause analysis in IncidentXP

IncidentXP already allows users to choose between multiple barrier-based incident analysis techniques. However, we continued to get a lot of requests for one particular method: traditional Root Cause Analysis (RCA). This method is the fourth we're adding to IncidentXP and joins BSCAT, Tripod Beta and Barrier Failure Analysis.

What is RCA?

Root Cause Analysis is a simple and straightforward incident analysis technique. It starts with an incident and drills down into the chain of events that led to that incident until the root causes are identified. This method is widely used throughout the world, and the idea of drilling down to the root cause is also present in all of our other incident analysis methods.

Solving RCA problems

However, a traditional root cause analysis has the potential to turn into a jumble of elements. We felt this could be improved, so we did two things. First, we added some more subtle categorisations so you can see at a glance where the real problem areas are. You don't need to use them, but if you do, we think you will create better analyses, and it will be easier for your audience to see what you're trying to communicate. Second, you can cut up a large diagram into smaller pieces, and link them together. Separating the main diagram from sub-diagrams avoids a situation where the diagram becomes so large you lose overview. We hope these changes to RCA will help you create better analyses.

Features

RCA will include all the features you expect like reports, case file overviews, import/export options, easy manipulation of the diagram, scrap book support, find and replace, spell checking, undo/redo, auto-save, and many others

Barriers vs RCA

The main difference between RCA and our other incident analysis methods, is that RCA is not barrier based. Everything in RCA is an event, including those things that would be considered barriers in BSCAT, Tripod or BFA. This doesn't matter if you just want to use RCA, but there is one important caveat. Whereas the barrier based incident analysis methods like BSCAT and Tripod can be mapped back onto the bowtie because their structure is similar, RCA cannot be linked back to a bowtie, because the bowtie structure depends heavily on identifying barriers, which RCA does not do. We will examine other possibilities in the future, like classifying events. But we will base that development on real world feedback.