Root Cause Analysis Training Course

Participants can plan an investigation that identifies required evidence, sources and decision points.

• Investigation questions framed around failure mechanisms and control performance
• Evidence plans covering records, observations, interviews, samples and system data
• Chain-of-custody principles for sensitive records, samples and electronic evidence
• Interview preparation using open questions, timelines and corroboration checks
• Fact, inference and assumption labels applied throughout investigation records
• Escalation criteria for safety, regulatory, financial and customer-impacting events

Participants can map the affected process and identify where failure conditions emerged.

• SIPOC diagrams defining suppliers, inputs, process steps, outputs and customers
• Swimlane flowcharts showing handoffs, approvals, decisions and system interactions
• Process boundaries set from trigger event through final customer outcome
• Value-stream maps identifying queues, rework loops, delays and information gaps
• Gemba observation plans comparing documented procedures with actual work
• Critical-to-quality requirements translated into observable process conditions

Participants can collect and segment data to reveal meaningful patterns in performance failures.

• Check sheets designed for consistent event coding and data capture
• Sampling plans matched to event volume, risk level and available evidence
• Time-series plots revealing shifts, trends, cycles and unusual observations
• Data stratification by operator, channel, supplier, equipment and transaction type
• Scatter diagrams testing relationships between suspected variables and outcomes
• Missing-data checks before drawing conclusions from incident or defect records

Participants can prioritise investigation effort using frequency, impact and risk evidence.

• Pareto analysis ranking defect categories by frequency, cost and customer impact
• Cumulative percentages identifying the vital few categories requiring investigation
• Severity and occurrence ratings used alongside simple event counts
• Cost-of-poor-quality calculations covering rework, scrap, delay and compensation
• Priority matrices comparing urgency, controllability, exposure and resource requirements
• Problem selection criteria documented before launching detailed causal analysis

Participants can generate and organise plausible causal factors without confusing them with root causes.

• Fishbone diagrams structured around people, methods, machines, materials and measurement
• Service-process categories covering policy, systems, workload, skills and communication
• Cause statements written as observable conditions rather than opinions
• Brainstorming rules that separate idea generation from evidence evaluation
• Affinity grouping used to consolidate duplicate or overlapping causal factors
• Causal factor lists linked to specific process steps and evidence sources

Participants can use 5 Whys to trace a problem from symptom to controllable causal conditions.

• 5 Whys questioning tied to evidence at every causal step
• Causal chains distinguishing triggering events, enabling conditions and latent weaknesses
• Why questions reformulated when answers become vague, circular or blame-focused
• Branching causal paths used when multiple mechanisms produce one outcome
• Stopping rules preventing premature conclusions after arbitrary question counts
• Root cause candidates tested against recurrence, control failure and evidence criteria

Participants can analyse failure pathways and identify barriers that did not prevent an event.

• Fault tree logic connecting top events with contributing failure conditions
• AND and OR gates used to model combined causal pathways
• Barrier analysis identifying preventive, detective and recovery controls
• Control failures classified as absent, inadequate, bypassed or poorly maintained
• Bowtie thinking linking threats, top events, consequences and safeguards
• Escalation barriers examined for delayed reporting, decision-making and response

Participants can assess human performance factors without assigning simplistic individual blame.

• Human error categories including slips, lapses, mistakes and violations
• Workload, fatigue, interruptions and time pressure assessed as causal conditions
• Procedure design reviewed for clarity, accessibility, sequencing and usability
• Training records compared with task complexity, change history and supervision
• Decision points examined for information quality, authority and conflicting priorities
• Just culture principles separating accountability from system learning requirements

Participants can use FMEA to anticipate failure modes and prioritise preventive controls.

• FMEA scope defined around a process, product, service or project activity
• Failure modes identified for each process step and intended function
• Effects, causes and existing controls recorded in FMEA worksheet fields
• Severity, occurrence and detection ratings assigned using agreed rating scales
• Risk priority numbers interpreted alongside criticality and regulatory exposure
• Recommended actions targeted at prevention, detection or impact reduction

Participants can verify whether suspected causes explain the problem and support effective action.

• Evidence tests comparing suspected causes with observed event patterns
• Counterfactual questions examining whether failure occurs without proposed causes
• Data triangulation across documents, interviews, observations and system records
• Hypothesis tests framed with predicted evidence and disconfirming evidence
• Change histories reviewed for timing, configuration, staffing and supplier differences
• Verification criteria documented before approving root cause conclusions

Participants can design actions that address verified causes rather than visible symptoms.

• Corrective actions matched directly to verified causes and failed controls
• Hierarchy of controls applied before training, reminders and procedural warnings
• Poka-yoke methods designed to prevent, detect or contain predictable errors
• Action plans specifying owners, due dates, dependencies and required resources
• Interim containment actions separated from permanent corrective actions
• Change impact assessments covering procedures, systems, roles and customer communication

Participants can establish controls that sustain improvements and detect recurrence early.

• Control plans defining monitored characteristics, methods, frequencies and response actions
• Leading indicators selected to detect deteriorating process conditions early
• Standard work updated with revised controls, responsibilities and escalation points
• Visual management methods clarifying status, limits, exceptions and required actions
• Audit checks designed around critical controls and known failure mechanisms
• Management review routines tracking overdue actions and recurring event patterns

Participants can confirm whether actions worked and formally close an RCA investigation.

• Effectiveness measures defined before corrective actions are implemented
• Before-and-after comparisons adjusted for volume, mix and seasonal variation
• Verification periods selected according to event frequency and risk exposure
• Recurrence tests checking whether similar failures reappear after implementation
• Closure criteria covering evidence, approvals, documentation and residual risks
• Lessons learned records converted into standards, controls and training updates

Participants can communicate investigation findings, decisions and residual risks to stakeholders.

• RCA reports structured around problem, evidence, causes, actions and verification
• Executive summaries presenting impact, decisions, risks and required sponsorship
• Timeline exhibits showing event sequence, detection points and response delays
• Evidence appendices distinguishing verified facts from unsupported assumptions
• Action trackers reporting ownership, status, due dates and effectiveness results
• Management presentations tailored for operational, audit and governance audiences

Participants can build, review and present a complete root cause analysis report for a workplace-relevant problem.

• Problem charter refined using stakeholder feedback and available performance evidence
• Process map and data analysis assembled into a coherent investigation record
• Causal analysis reviewed for evidence, logic gaps and unsupported assumptions
• Root causes verified against failure patterns, controls and alternative explanations
• Corrective action plan tested for ownership, feasibility and prevention strength
• Final RCA report presented with effectiveness measures and closure criteria