Root Cause Analysis Training Course

Why this module matters: Most failed investigations fail at the start, not the end. A problem stated as "quality is poor" cannot be investigated, and evidence collected after memories have shifted is unreliable. This module builds the front end of the process, which is where the eventual quality of the answer is largely determined.

• Writing a problem statement precise enough to investigate: what, where, when, how much
• Separating the problem from its symptoms and from proposed solutions
• Evidence types and preservation: physical, documentary, positional and people-based
• Interviewing without leading: question design that surfaces what happened rather than confirming a theory
• Building a timeline and sequence of events before attempting any causal reasoning
• Scoping the investigation proportionately, so effort matches the significance of the problem

Why this module matters: Teams that know only one technique apply it to every problem, and 5 Whys applied to a complex multi-factor failure produces a confident wrong answer. This module builds fluency across the standard tools and, more importantly, judgement about which fits the problem in front of you.

• 5 Whys done properly: where it works, where it breaks, and how to avoid a single false chain
• Fishbone and cause-and-effect diagrams for problems with multiple contributing categories
• Fault tree analysis for failures with combinatorial or conditional causes
• Pareto analysis for prioritising which problem to investigate at all
• Change analysis: what was different this time, applied to problems that appeared suddenly
• Barrier analysis: which controls should have caught this, and why they did not
• Matching the technique to the problem type rather than defaulting to the familiar one

Why this module matters: A plausible cause and a true cause look identical until tested. This module covers the verification step that most investigations skip, and the cognitive and organisational traps, blame, hindsight and stopping at human error, that produce confident but useless findings.

• Testing candidate causes against the evidence: would removing this actually prevent recurrence
• Distinguishing root causes, contributing factors and coincidental conditions
• Why "human error" is a starting point, not a conclusion, and what to investigate underneath it
• Systemic and organisational causes: process design, workload, training and incentives
• Hindsight bias and blame culture, and how both corrupt an investigation
• Knowing when to stop: the point at which further analysis stops adding actionable value

Why this module matters: An analysis that produces no change is an expensive discussion. This module covers designing fixes that genuinely remove the cause, verifying they worked, and presenting findings persuasively, then applies the whole method to a real problem you bring.

• Designing corrective actions that remove the mechanism rather than adding a checking step
• The hierarchy of controls: why elimination beats procedure, and procedure beats reminder
• Defining verification up front: what evidence would show the fix actually worked
• Writing the investigation report so a decision-maker can follow the reasoning and approve action
• Presenting findings when the cause implicates a decision someone in the room made
• Capstone: a full root cause analysis on a real recurring problem from your own organisation, with peer challenge