Root Cause Analysis — Facilitation Kit (5 Whys, Fishbone, Causal Mapping)

Welcome — Purpose and Promise

This facilitation kit helps teams move beyond symptom-fixing to evidence-based, targeted countermeasures. Use the short path when you need rapid insight, the fishbone when causes are spread across categories, and causal mapping when the problem is complex or system-wide. Each format includes timeboxed agendas, facilitator scripts, templates for recording evidence, and a simple action plan for turning findings into measurable countermeasures.

Which method should you choose?

• Short (15–30 min): 5 Whys — Best for clear, recent problems with a limited scope and a small team.
• Medium (60–90 min): Fishbone + evidence capture — Good when multiple plausible cause categories exist and you need to structure brainstorming and link ideas to evidence.
• Long (2–4 hours): Causal mapping — Use for complex problems, recurring issues, or when causes interact across systems, teams, or processes.

Roles and materials

• Facilitator: Guides process, neutral, keeps time, ensures evidence focus.
• Scribe: Captures findings, evidence, and action items in the template.
• Timekeeper (can be facilitator): Ensures timeboxes are respected.
• Materials: whiteboard or virtual board, sticky notes, printed templates, evidence artifacts (logs, photos, data extracts).

Short RCA — 5 Whys (15–30 minutes)

Use this when a single sequence of causes is likely. Keep the group small (3–6 people) and ground every step in evidence.

Agenda (15–30 min)

1. 0–3 min: Clarify the problem statement (where, when, what, impact).
2. 3–20 min: Run 5 Whys — ask 'why' until you reach an actionable root cause or hit evidence limit.
3. 20–25 min: Identify 1–3 countermeasures and define immediate next steps.
4. 25–30 min: Assign owners and success measures.

Facilitator script (concise)

Start by writing a specific problem statement: "What happened, where, when, and how often?" Ask the first 'Why?' and capture the answer. For each answer, ask 'Why did that happen?' until the team reaches a cause that can be acted on. Always ask for supporting evidence (logs, photos, eyewitness, metric change). If the group speculates, capture the idea but mark it as unverified.

Medium RCA — Fishbone + evidence capture (60–90 minutes)

When causes span categories, use a fishbone to organize thinking and tie each hypothesis to evidence.

Agenda (60–90 min)

1. 0–10 min: Problem statement and scope.
2. 10–35 min: Brainstorm causes by category (use pre-defined categories).
3. 35–55 min: Collect or cite evidence for top hypotheses.
4. 55–75 min: Prioritize 2–4 hypotheses to test and propose countermeasures.
5. 75–90 min: Assign owners, define measures, and schedule follow-up review.

Suggested fishbone categories

• People (skills, staffing, training)
• Process (work steps, procedures)
• Equipment/Tools (availability, maintenance)
• Materials/Supplies
• Environment (layout, conditions)
• Management/System (policies, schedules, incentives)

Evidence-capture prompts

• What data/logs confirm this happened? (time, frequency, trend)
• Who observed it? When and where?
• Is there a reproducible sequence or pattern?
• What changes preceded the event?

Long RCA — Causal Mapping (2–4 hours)

Use causal mapping when the problem is recurring, affects multiple teams, or when interactions matter. Causal maps show cause-effect links and help you test assumptions.

Agenda

1. 0–20 min: Problem framing and stakeholder alignment.
2. 20–60 min: Create an initial causal map (nodes = events/conditions, arrows = causal links).
3. 60–120 min: Add evidence to links and identify gaps; test key links by asking 'what would confirm this link?'
4. 120–180 min: Identify leverage points and design countermeasures. Prioritize with simple criteria.
5. 180–240 min: Action plans, owners, measures, and review cadence.

Facilitation notes

• Encourage specificity: prefer 'Operator missed step X at 14:05' to 'operator error.'
• Distinguish observed facts from assumptions—mark assumptions clearly.
• When linking causes, ask for supporting evidence or a plan to obtain it.

Countermeasure selection — simple prioritization

Score candidates on Impact, Feasibility, Lead Time, and Required Cost (1–5). Multiply or sum scores to prioritize. Prefer a balanced portfolio: one quick win, one medium-term process change, and one longer systemic fix when appropriate.

Action Plan template (use verb-focused actions)

• Action/Countermeasure
• Owner
• Due Date
• Success Measure (metric or observable)
• Evidence to collect
• Follow-up review date

Templates & quick worksheets (copy into your board)

5 Whys template

1. Problem statement:
2. Why 1:
3. Why 2:
4. Why 3:
5. Why 4:
6. Why 5 (probable root cause):

Fishbone quick capture

• Problem statement:
• Category: cause (evidence)
• Prioritize top causes for evidence collection

Causal mapping quick notes

Node: description — Evidence: (data, who, when) — Link strength: (assessed 1–5) — Test to confirm link:

Common pitfalls

• Stopping at first plausible cause (surface-fixing).
• Allowing blame language—keep focus on the system and conditions.
• Accepting unverified assumptions as facts—mark and plan to test them.
• Designing countermeasures without defining success measures.
• Not scheduling follow-up to verify effectiveness.

Pre-session checklist

• Define and circulate the problem statement and scope.
• Gather available evidence in advance (logs, photos, relevant metrics).
• Invite people who understand the process, data, and context.
• Reserve 30–60 minutes after the session for the facilitator and scribe to convert notes into an action plan.

After the session — follow-through

• Convert findings into the Action Plan template within 48 hours.
• Track the success measure(s) and review at the agreed follow-up date.
• If countermeasures fail, reopen the map or run a short 5 Whys on the failed intervention.

Closing note

Good RCA combines structured thinking, evidence, and disciplined follow-through. Use this kit to reduce guesswork, improve the quality of fixes, and build shared organizational learning.