Root Cause Analysis
Go Page
|
 You
will not have time to gather essential items after receiving a call to lead
a Latent or Root Cause Analysis. Although you might have been trained in Latent
or Root Cause Analysis, or even have lead them in the past, you will need to fall back
on a defined process, and use predetermined tools. If you do not, your
organization will be inconsistent in its approach to investigating its problems
because different people will investigate in different ways, use varying
vocabulary, and dig to different depths. Inconsistency
is a death-knoll of a Latent Cause Analysis effort.
This Latent or Root Cause Analysis Go Page was actually developed for
Failsafe Network's Licensed Affiliates. They requested guidance from
Failsafe to help them abide by the contract they had signed which stipulated
that they follow Failsafe's Network's methods. Once this Root Cause
Analysis Go Page had been developed, they suggested that it be made
available to everyone.
Many highly successful investigative agencies use the Root
Cause Analysis Go Page Principle to assure their readiness to respond in
a rapid manner.
The following Root Cause Analysis Go Page items are being made available to you to help
you be consistent in your Latent or Root Cause Analysis. With exception of the
last item (Failsafe's Recommended Practice), they are presented in the order
in which you will probably need them. The Recommended Practice is a
comprehensive reference that encapsulates all of these items.
 |
Definitions Let us know if we're missing
something and we will add it. |
|
 |
Guiding Beliefs
Read when you receive an assignment to
lead a Latent or Root Cause Analysis, and each day you are leading the
investigation. |
 |
Guiding Purpose
Read when you receive an assignment to
lead a Latent or Root Cause Analysis, and each day you are leading the
investigation. |
 |
Essential Elements of the ROOTS Process
Do not call your effort an Latent or Root Cause Analysis unless you follow these
basic steps!! |
 |
Detailed Checklist for Conducting an Latent
or Root Cause Analysis
This checklist provides a lot of detail for those who want
follow the process "by the book." |
 |
Accountability Contract (Amnesty Policy)
To suggest to your "client" prior to beginning your
Latent or Root Cause Analysis.
If the client is not willing to embrace this policy, BEWARE! They are
going into the endeavor with the WRONG motive! |
 |
The 5 Items To be forwarded
to the "client" as soon as you get the call. Do NOT proceed with
the investigation until you have these 5 Items! |
 |
An Example of an Actual Go-Box Put
together by a practicing rootician -- an example for us all! |
 |
Interview Guidelines To be
given to the People Evidence Gatherers to use during the interviews. |
 |
Stakeholder Preparation Slides
To be used to prepare stakeholders for their meeting. |
 |
Stakeholder Meeting Agenda Slides
To be used during the stakeholder meetings to keep people on
track. |
 |
The Golden Rule of a Latent
or Root Cause Analysis
To print-out and enlarge so that you place it in the
stakeholder meeting room for all to see. |
 |
Situation-Filter-Outcome (SFO) Model Slides
To be used during the stakeholder meeting to guide them
into Latent Causes. |
 |
Physical, Human, and Latent Causes Defined
To help you, your evidence team, and the stakeholders
define these kinds of causes. |
 |
Schematic of Physical, Human, and Latent Causes
To help you, your evidence team, and the stakeholders
understand the difference between these kinds of causes. |
 |
Failsafe's Latent or Root Cause Analysis Report Template (coming soon)
To be used whenever doing a Maxi or Midi-Latent or Root
Cause Analysis to help
assure consistency. |
 |
Failsafe's Suggested Translation Contents (coming soon)
To be used when brainstorming how to TRANSLATE your Latent
or Root Cause Analysis
learning's so that others will think about it. |
 |
Mother-Source-Scoring Sheets
A suggested evaluation form to grading investigations. |
 |
Failsafe's Recommended Practice
Click the link to download a PDF-file of the whole
approach suggested by Failsafe. |
|
