methodatlas
Operations

Fishbone Diagram

Turns workflows, data, causes, and improvements into a tangible result by defining the problem, choosing cause categories, and prioritizing likely causes.

Core question
Which possible causes across all relevant categories deserve data-driven deep validation as the next action?
LowWorkshop30-60 min
Purpose

The method helps clarify workflows, data, causes, and improvements concretely. It identifies patterns, causes, bottlenecks, or weaknesses and derives actions. The result is captured as a fishbone diagram, cause categories, and investigation backlog.

How it works

The team follows the steps: define problem, choose cause categories, collect possible causes, discuss and verify causes, and prioritize likely causes. Each step is captured visibly. At the end, a fishbone diagram, cause categories, and investigation backlog are available so decisions, tests, or actions can follow directly.

Visual orientation

Method sketch for a quick mental model.

Ishikawa Diagram · 6MFormulate a problem as effect, collect possible causes by category, then test them with evidence
Fishbone DiagramThe visual shows an Ishikawa diagram with problem head, main spine, cause categories, and validation note.Structure possible causes before choosing the actionCategories collect hypotheses while the problem head keeps the effect to explain clear.Peopleskill, handoverMachinetool, outageMethodstandard missingMaterialinput qualityMeasurementdata gapEnvironmentcontext pressureProblem / effecterror occurs repeatedlyCheckvalidate hypotheses with data, observation, and 5 Whys

Flow

  1. 1Define problem
  2. 2Choose cause categories
  3. 3Collect possible causes
  4. 4Discuss and verify causes
  5. 5Prioritize likely causes

The runsheet guides execution with 5 phases, timeboxes, 5 pitfalls, and clear stop criteria.

Open runsheet

Ideal for

  • Quality problems
  • Incident learning
  • Process errors

Not good for

  • Final proof without data
  • Ideation without problem statement

Deep dive

In detail

Fishbone Diagram follows a clear working logic: define problem, choose cause categories, collect possible causes, discuss and verify causes, and prioritize likely causes. This turns the method into a visible thinking process instead of only a discussion. Participants move step by step from raw material, observations, or options toward a shared structure. As a result, a fishbone diagram, cause categories, and investigation backlog are available for decisions, learning, and planning.

Facilitation

Prepare a clear guiding question, the right information, and a visible workspace. Plan for 30-60 min with 2-8 people and use the format in a facilitated workshop. The facilitation stays lightweight; short timeboxes, visible intermediate results, and a parking lot for open questions help.

Output artifacts
Fishbone DiagramCause CategoriesInvestigation Backlog
Tags
Artifact templates
Fishbone Diagram Working TemplateCompact working template for Fishbone Diagram with problem, cause categories, evidence, and next investigation.
canvas

fishbone-diagram-working-template.md

Compact working template for Fishbone Diagram with problem, cause categories, evidence, and next investigation.

Fishbone Diagram Working Template

Goal

Surface possible cause categories and likely root causes for a problem.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Working area

  • Problem statement:
  • Cause categories:
  • Possible causes:
  • Evidence:
  • Likely causes:

Output artifacts

  • Fishbone diagram:
  • Cause list:
  • Investigation backlog:

Open questions

  • ...

Next step

Owner, date, and success signal.

When to choose differently

Short decision aid for existing alternatives.

5 Whys

Statt Fishbone Diagram, wenn ihr eine Ursache in wenigen Warum-Fragen verfolgen wollt und keine Kategorienwand braucht.

Similar methods

All methods