Fishbone Root Cause Analysis — User Guide

Root Cause Analysis Tool

When to use a Fishbone analysis

Use the Fishbone / Ishikawa Root Cause Analysis tool to structure transformation problem discussions, group causes by category, score severity, assign owners and next actions, and generate an AI facilitation brief.

Launch Fishbone Tool
View Quick Reference

What this tool helps you do

The Fishbone / Ishikawa tool helps change and transformation teams move from a broad problem to a structured root-cause discussion. Use it when adoption, readiness, operating model, process, technology, governance, or culture problems need practical diagnosis.

Define the problem

Capture the project context and a clear fish-head problem statement.

Add root causes

Brainstorm possible causes and group them under transformation-specific categories.

Score severity

Use 1 to 5 scoring to identify which causes matter most.

Assign owners and actions

Add owners, evidence, and next actions so the fishbone becomes operational.

Generate AI facilitation brief

Create a root-cause synthesis, validation questions, mitigation playbook, and sponsor summary.

Export and document

Export JSON, SVG, Markdown, or PDF outputs for workshop records and transformation status packs.

Before you start

You do not need a login. Your data is saved locally in your browser while you work, so the tool remembers your work on the same browser and device, but clearing browser storage may delete saved work.

Use Export JSON when you want to save, share, or move the analysis.
Use the tool during a workshop, project review, adoption review, readiness discussion, or lessons-learned session.
For sensitive work, avoid personal data and consider redact mode before AI analysis.

Basic workflow

Define the project and problem

Write the transformation, project, or initiative name and a specific observable problem statement.

Add possible root causes

Capture causes one by one, classify them, score severity, and add evidence.

Review the fishbone and register

Use the diagram, cause register, filters, and category concentration to see where the discussion should focus.

Generate an optional AI brief

Use Quick or Deep mode to create a facilitation brief, sponsor summary, or mitigation playbook.

Step 1 — Add project context

In the Project context panel, enter the project or initiative and a problem statement. The problem statement becomes the fish head of the Ishikawa diagram.

Project / initiative examples

ERP rollout, AI-enabled customer service transformation, new operating model implementation, CRM adoption program, or finance process standardization.

Good problem statements

“Frontline users are not adopting the new ERP process after go-live” or “Managers are not reinforcing the new operating model.”

Avoid vague statements

Do not use “People resist change,” “Communication is poor,” or “The system does not work.” Be specific and observable.

After entering context: click Save context so the fishbone diagram and analysis sections use the right problem frame.

Step 2 — Add root causes

Use the Add root cause form to capture each possible cause. Write one cause per entry and make it specific enough to test and act on.

Strong cause	Weak cause	Why it matters
Managers do not know what behavior they are expected to reinforce.	No ownership.	The strong version can be validated and assigned.
Training explains the system, but not the new business process.	Training issue.	The strong version points to corrective action.
Sponsors are supportive but do not remove prioritization conflicts.	People resist.	The strong version avoids blame and names a system problem.

Choose the right category

Each cause must be assigned to a category. The default categories are tailored for change and transformation management.

Leadership & SponsorshipSponsor behavior, senior alignment, decisions, escalation, and visible leadership.

Stakeholders & Buy-inResistance, commitment, stakeholder alignment, middle management, and affected groups.

Communication & NarrativeThe story of the change, clarity of messages, channels, and meaning.

Capability & TrainingSkills, learning, confidence, practice, role readiness, and support.

Process & Operating ModelRoles, workflows, decision rights, handoffs, process design, and future ways of working.

Technology & DataSystem usability, integrations, data quality, access, reporting, automation, and constraints.

Governance & MetricsAccountability, KPIs, tracking, decision forums, adoption metrics, and escalation.

Culture & IncentivesHabits, incentives, informal norms, performance expectations, fear, trust, and behavior.

Add severity

Each cause has a severity score from 1 to 5. Use the score to show how strongly the cause contributes to the transformation problem.

Score	Meaning	Use when
1	Low	The cause is minor or uncertain.
2	Moderate	The cause matters but is not blocking progress.
3	Meaningful	The cause has a clear impact and should be discussed.
4	High	The cause is a serious barrier to adoption or delivery.
5	Critical	The cause may block the transformation if not addressed.

Facilitation question: “What evidence would make us confident this is truly a 4 or 5?”

Add owner, evidence, and next action

Owner

Enter the person, role, or team best placed to investigate or resolve the cause, such as executive sponsor, process owner, training lead, PMO, or local deployment lead.

Evidence

Add survey results, workshop feedback, adoption dashboards, support tickets, process observations, interview notes, issue logs, or SteerCo decisions.

Next action

Write a practical step specific enough that someone can start it, such as validating the root cause with users or adding an adoption metric to governance.

Read the fishbone diagram

The live diagram updates automatically as causes are added. The main problem appears in the fish head, categories appear as major bones, and causes appear as bubbles connected to the relevant category.

LeadershipStakeholdersCapabilityTechnology/Data

Problem statement

CommunicationProcessGovernanceCulture

Ask whether the team is identifying root causes or only symptoms.
Look for concentration in one category and gaps in empty categories.
Check whether high-severity causes are backed by evidence.
Confirm owners and next actions are clear for priority causes.

Use the cause register

The cause register shows all causes in a structured list. It is useful when the fishbone becomes visually busy.

Search for a cause.
Filter by category or severity.
Show or hide details.
Edit existing causes or delete causes that are no longer relevant.

Use facilitation insights

The facilitation insights section provides a quick summary of where the next discussion should focus, execution gaps such as missing owners or actions, and category concentration.

Use the concentration bars to see where causes are clustered, then decide whether that concentration reflects the real issue or simply who was in the room.

Generate an AI facilitation brief

The AI panel is optional. Use it when you want the tool to turn the fishbone into a structured facilitation output.

Quick mode

Use Quick mode for workshop wrap-up, project team discussion, sponsor check-in, and fast prioritization.

Deep mode

Use Deep mode for workshop preparation, transformation recovery planning, SteerCo preparation, change strategy, or consulting deliverables.

Redact metadata

Use redact mode to reduce sensitive information before sending the fishbone map for AI analysis.

AI can create a root-cause synthesis, strongest evidence-backed causes, validation questions, mitigation playbook, 30-day action plan, sponsor summary, and data-quality cautions.
After generating the brief, use Copy Markdown, Download .md, or Clear.

Export and import your fishbone data

Export JSON

Save a backup, continue later, share with a colleague, or move the analysis to another browser or device.

Import JSON

Load a saved fishbone file. This replaces current browser data, so export first if you need to keep it.

Export SVG

Save the fishbone diagram for PowerPoint, Word, workshop reports, whiteboards, or status packs.

Print / PDF

Use landscape orientation, Save as PDF, and check the preview before saving.

Load sample data

Populate the tool with example transformation causes. Export your own work first because sample data replaces current content.

Reset the tool

Clear the current fishbone and start again. Use reset carefully and export JSON first if you need a backup.

Recommended workshop format

You can use the tool in a 60 to 90 minute session.

Time	Activity
5 min	Define the problem statement.
10 min	Confirm affected groups and transformation context.
20 min	Brainstorm possible causes across categories.
15 min	Score severity and add evidence.
15 min	Assign owners and next actions.
10 min	Review category concentration and high-severity causes.
10 min	Generate AI facilitation brief and discuss recommendations.

Good facilitation questions

What makes us believe this is a root cause, not a symptom?
What evidence supports this cause?
Which cause would have the biggest impact if resolved?
Which causes require sponsor intervention?
What would frontline users or managers say is missing?
What should be fixed in the next 30 days?

Common mistakes to avoid

Writing symptoms instead of causes

“Users are not adopting the tool” is a symptom. A better cause is “Users do not understand how the tool changes their daily process.”

Blaming people

Replace “employees resist change” with a cause about unclear benefits, missing reinforcement, or lack of manager support.

No evidence

A fishbone becomes stronger when causes are linked to real evidence.

No owner

A cause without an owner usually remains a discussion point, not an action.

Too many critical scores

If everything is critical, prioritization becomes impossible.

Treating AI as the answer

AI should support the discussion, not replace judgment, stakeholder validation, or evidence.

Example completed cause and completion criteria

Field	Example
Category	Capability & Training
Cause	Training explained system navigation but did not give users enough practice with real process scenarios.
Severity	4 — High
Owner	Training lead
Evidence	Post-training feedback, support tickets, super-user comments
Next action	Add role-based practice scenarios and run two follow-up clinics before the next deployment wave.

A clear problem statement.
Several well-described root causes.
Severity scores that reflect real impact.
Evidence, owners, and next actions for priority causes.
A short facilitation or sponsor summary plus exported JSON, SVG, or PDF documentation.

Troubleshooting

Previous work is missing

You may be using a different browser, device, or private browsing mode. Import a saved JSON file if you exported one.

AI button does not work

The backend may be temporarily unavailable or in mock mode. Refresh, export JSON, and contact the site owner if the issue continues.

Diagram is too wide

Use the horizontal scroll area under the diagram or click Fit view.

Cause list is too long

Use search, category filter, severity filter, or compact view.

Data was deleted

If you exported JSON, import it again. If not, deleted browser data may not be recoverable.

Practical rule of thumb

A good Ishikawa session does not end when the diagram looks complete. It ends when the team can say: “These are the few causes we believe matter most, this is the evidence, these are the owners, and these are the next actions we will take.”

Guide	Use when
Complexity Assessment	You need to assess overall transformation complexity.
Stakeholder Analysis	You need to map stakeholder groups and engagement priorities.
Change Impact & Mitigation Register	You need to list specific changes and track mitigation.
Transformation RAID Log	You need to track risks, assumptions, issues, and dependencies.
5 Why Root Cause Analysis	You need to trace a specific problem through a why-chain.

Ready to map the causes?

Open the Fishbone / Ishikawa Root Cause Analysis tool to define the problem, group root causes, score severity, assign owners and next actions, and generate an AI facilitation brief.

Launch Fishbone Tool Back to top