Advanced RCA Quiz - KS

After conducting a 5 Whys session, a team concludes that "operator carelessness" is the root cause. As an RCA-trained facilitator, what is the most appropriate next step?

• Document the cause and close the case

• Recommend disciplinary action for the operator

• Guide the team to reframe the cause into a system-level issue

• Skip to FMEA to assess recurrence risk

Answer explanation

Justification: Blaming individuals is a common RCA trap. True root causes usually lie in system design, training, process clarity, or organizational factors.

Your RCA team identifies multiple possible causes during brainstorming. Which tool is most appropriate to prioritize which cause to investigate first?

• KT Is/Is Not

• FMEA

• Pareto Chart

• SIPOC

Answer explanation

Justification: FMEA ranks causes based on severity, occurrence, and detectability, making it ideal for prioritizing high-risk causes.

Which of the following is the most appropriate control action after confirming a true root cause in RCA?

• Increase end-product inspection frequency

• Retrain all operators regardless of involvement

• Implement a poke-yoke (error-proofing) device that addresses the actual root cause

• Add a new KPI to monitor defect rate

Answer explanation

Justification: Poke-yoke devices prevent recurrence by addressing the root cause directly at the source.

In Kepner-Tregoe Problem Analysis, which of the following questions helps narrow down the unique characteristics of the problem?

• What is the extent of the problem?

• What is not happening that would be expected?

• What is different compared to a normal case?

• What part of the process is not affected?

Answer explanation

Justification: Identifying distinguishing features helps isolate the specific failure condition, crucial in KT analysis.

A production line shows an increase in defect rate, but only when materials are sourced from a secondary vendor. Which RCA tool is best suited as the first step to understand this situation?

• Is/Is Not Analysis

• 5 Whys

• Fault Tree Analysis (FTA)

• Pareto Chart

Answer explanation

Justification: Is/Is Not helps define the boundaries of the problem clearly by comparing what it is and what it is not.

Which of the following best differentiates FMEA from Root Cause Analysis (RCA)?

• FMEA is corrective; RCA is preventive

• FMEA occurs after a failure; RCA occurs before a failure

• FMEA is a proactive risk assessment tool; RCA is a reactive investigative tool

• FMEA and RCA are interchangeable within CAPA

Answer explanation

Justification: FMEA is proactive and used in design or planning stages; RCA is used after a problem has occurred.

When using Is/Is Not analysis, which of the following represents a flawed approach to defining what the problem is not?

• Saying "It is not affecting Machine B" when Machine B is unrelated to the process

• Saying "It is not occurring during night shift" while evidence shows 24/7 occurrence

• Saying "It is not part of the new process" without historical context

• Saying "It is not caused by Operator A" because Operator A was on leave

Answer explanation

Justification: The 'Is Not' category should involve relevant contrasts; Machine B is irrelevant and misleading.

In a SIPOC diagram, which element is most useful for tracing upstream root causes of quality issues?

• Customer

• Output

• Process

• Supplier

Answer explanation

Justification: Supplier issues are upstream and can impact input quality, which then cascades downstream.

Which of the following scenarios best justifies using Fault Tree Analysis (FTA) over 5 Whys?

• A minor packaging defect due to operator negligence

• A one-time billing error caused by data entry

• An intermittent equipment shutdown involving multiple interacting systems

• A missing SOP that delayed raw material receipt

Answer explanation

Justification: FTA handles complex, multi-cause problems better than linear 5 Whys analysis.

When conducting a 5 Whys analysis, which common pitfall is MOST likely to occur without strong facilitation?

• Including stakeholders too early

• Deriving multiple root causes from one branch

• Stopping at symptoms rather than reaching systemic root causes

• Overcomplicating the logic tree

Answer explanation

Justification: Teams often stop at superficial causes like 'operator error' rather than digging into systems or process design.