2. Unfortunately, root cause analysis is a reactive approach,
that means an error or adverse event must happen prior to
applying RCA.
Root cause analysis is a team approach methodology, not a
single person decision. RCA should start by clearly identifying
the problem, usually an adverse event that should not be
allowed to happen again.
RCA should be applied shortly after adverse events to keep
track of all essential details. Process owners are the main
skeleton for a proper RCA, although they might not feel much
comfortable with such meetings and conversations, hence the
managers would play a major role explaining the importance of
RCA and to sustain the non-blame culture of the organization.
3. Root Cause Analysis (RCA) Tools
Root cause analysis (RCA) could be applied using a wide variety of
tools, there is no perfect method that can be used anywhere,
instead, the quality managers would select the suitable approach
for organization and team members, typically using brainstorming
technique.
•Fishbone diagram, also known as Ishikawa or cause and effect
diagram is one of the classic tools for RCA. It is used to identify
various possible causes that led to the current effect under
investigation.
5. • Five whys is another
popular tool for RCA,
also known as Gemba
Gembustu. It is a
technique that
explores the hidden
causes of the specific
problem by repeated
asked whys, the
number 5 is not fixed,
but usually the root
cause is identified
around it.