Root Cause Analysis

Choose this exercise

Purpose: Map and prioritize systemic contributors to a specific operational problem or risk using categorical branches.

Use it when: Use when a team faces a recurring issue or operational bottleneck and needs to look past surface symptoms before committing to solutions.

Skip it when: Skip when the core problem statement has not yet been agreed upon, or when the team needs simple divergent brainstorming rather than structural causal analysis.

Group arrangement: Subgroups of 2 to 3 people assigned to 1 or 2 diagnostic categories (or combined categories for smaller cohorts), coming together for diagram compilation and whole-room prioritization.

Timing: Source documents suggest 30 to 120 minutes; 45 minutes represents an effective standard baseline for a single problem focus.

Materials and tools

• 1 roll of painter tape
• 1 large sheet of butcher paper or whiteboard space (at least 2x1 meters)
• 4 pads of 3x3-inch sticky notes (different colors for categories if possible)
• 15 fine-tip dark markers
• 45 small dot-voting stickers (3 per participant)
• 1 digital countdown timer

Before participants arrive

1. Mount the large butcher paper or clear a central whiteboard wall.
2. Draw the fishbone spine: draw a heavy horizontal line across the center ending in an arrowhead on the right pointing to a box for the problem statement.
3. Draw diagonal rib lines branching outward for the agreed categories: People, Processes, Materials, Equipment, and Environment (combine Materials and Equipment if running with fewer subgroups).
4. Distribute sticky notes and markers to group tables.

Say this to open

Today we are analyzing the underlying drivers of a specific challenge using a fishbone diagram. Our goal is to uncover structural causes rather than blaming individuals. We will split into small groups to investigate specific categories, map the factors onto our shared diagram, and select top priorities to address.

How to run it

1. Define problem statement 5 minutes

   Read the opening script. Write the specific problem statement inside the box at the right head of the fishbone diagram (example: 'Quarterly reports delivered 5 business days late'). Check for group consensus on the wording. If someone disagrees with the scope, adjust the text until all participants confirm it describes the observable symptom accurately.

2. Generate causes in small groups 12 minutes

   Divide participants into teams of 2 or 3. Assign 1 or 2 categories to each team (combine categories like Materials and Equipment if there are only three pairs). Teams brainstorm contributing factors under their heading, writing one clear cause per sticky note. Prompt them to ask 'Why does this happen?' to look past symptoms. Participants may write notes individually before sharing with their subgroup.

3. Build the shared fishbone 10 minutes

   Call the room back to the central wall. One representative from each category team takes up to 90 seconds to read their notes aloud and stick them along their assigned diagonal rib line. Facilitate minor reorganization: merge exact duplicates or move a note if the group agrees it belongs on a different branch.

4. Prioritize root causes 6 minutes

   Give each participant 3 dot stickers. Direct participants to walk up to the diagram and place their dots on the causes they believe are the most significant systemic drivers of the problem. Participants may place up to 3 dots on a single note or distribute them across branches. Anyone may opt out of voting.

5. Identify actions and debrief 12 minutes

   Spend 6 minutes examining the 2 or 3 notes with the highest vote counts. For each top cause, invite brief proposals for immediate preventive or corrective actions, recording owners or action items directly beside the notes. Spend the remaining 6 minutes facilitating a debrief using the debrief questions, spending roughly 2 minutes per question and hearing from 2 or 3 participants per prompt.

Debrief questions

• Which identified causes are within our direct operational control to change?
• Did any category reveal hidden assumptions that surprised the group?
• What is our immediate first step to address the highest-voted root cause?

Finished output: A completed fishbone diagram documenting categorized causes of the problem, with the top 2 or 3 prioritized root causes and agreed immediate mitigation actions recorded.

Remote

Set up a digital whiteboard (such as Miro or Mural) with a pre-drawn fishbone diagram and sticky note pads beside each category rib. Assign breakout rooms of 2 to 3 people to specific categories for the brainstorm step. Bring everyone back to the main room, have representatives drag their notes onto the diagram, use the digital platform's dot-voting tool for prioritization, and capture action items directly on screen.

Hybrid

Maintain the single digital whiteboard as the primary display. Project it in the room for physical participants. In-person participants type their notes directly into the shared board via personal laptops or work with a designated in-room digital scribe so remote members can view and organize notes simultaneously. Conduct voting entirely inside the digital board.

Access and participation choices

• Participants can contribute ideas via verbal dictation to a partner, direct writing on physical notes, or typing in a digital board.
• Voting and whole-room speaking are entirely optional; individuals may choose to pass without giving a reason.

If the session gets stuck

Participants list solutions instead of causes during the brainstorm.

Pause the subgroup and ask: 'What breakdown or condition makes that solution necessary?' Have them write the underlying condition on the sticky note instead.

Notes describe interpersonal blame (e.g., 'Bob forgets to email').

Reframe the note toward the process or system (e.g., 'Notification relies on manual email instead of automated trigger').

Terms used here

• Fishbone diagram: A visual cause-and-effect mapping framework, also known as an Ishikawa diagram, that organizes contributing causes into distinct categorical branches leading into a central problem head.