Complete firstClear effect
Deviation, standard, time and magnitude are described.
A vague effect creates arbitrary cause lists.
Method guideOperations
Fishbone Diagram
A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.
ComplexityLow
Time30-60 min
Participants2-8
FormatWorkshop
MaturityCanonical
01
Prerequisite
What needs to be finished first
Complete firstProcess knowledge
People who know the actual work participate.
Without direct knowledge, important influence areas are missed.
02
Preparation
What needs to be ready before start
Materials
Large whiteboard or paper, cards, markers, process data and an evidence-status legend.
People / roles
Facilitator, scribe and two to eight people from relevant process areas.
Pre-read
Gather defect cases, expected standard, process sketch, timing data and known counter-evidence.
Time needed
30–60 minutes plus follow-up cause tests
Setup
Place the effect on the right, prepare major bones and leave space for subcauses. Use the 6Ms only as starting vocabulary.
03
Core question
The one question this method answers
Which possible causes and mechanisms could create this observed effect, and how will we test them?
04
Flow
Phases with goal, actions, output and pitfall
The Fishbone Diagram, also called Ishikawa or cause-and-effect diagram, places an observable effect at the fish head. Major branches organize possible causes; sub-branches describe deeper mechanisms. The diagram generates hypotheses, not automatic causal confirmation.
Fishbone diagram
Fictional example
Fictional cause landscape for delayed course activations. Every bone remains a hypothesis until tested.
People
Roles, knowledge, capacity?
Approval deputy unclear
Machine
Systems, equipment, software?
Import job waits in queue
Method
Flow, rules, handoffs?
Manual check duplicated
Effect
Observable deviation
18% of courses activated after 24h
Material
Inputs, files, components?
Metadata incomplete
Measurement
Definitions, signals, capture?
Start timestamp missing
Environment
Environment, load, external factors?
Monday load peak
- 1
Effect
Describe the effect precisely
Goal
The diagram examines an observable deviation rather than an assumed cause.
Inputs for this step
- Defect, quality deviation or unwanted outcome
- Expected standard and case boundary
Actions
- State the effect with object, time, magnitude and deviation from standard.
- Make scope, included cases and exclusions visible.
Output
Effect statement
Object · deviation · time · magnitude
Quality check
Does the statement contain only the observed effect and no cause?
Pitfall
The fish head already contains an explanation or blame statement. Compare observation and standard only; park explanations as possible causes.
Timing: 5–8 minutes
- 2
Categories
Lay out cause categories
Goal
Broad categories prevent the group from searching only familiar areas.
Inputs for this step
- Effect statement
- Knowledge of the affected process
Actions
- Choose relevant major branches; test the 6Ms as a starting point: people, machine, method, material, measurement and environment.
- Rename or add categories when they represent the process more accurately.
Output
Fishbone frame
Effect · major branches · process fit
Quality check
Do branches cover distinct influence areas of the actual process?
Pitfall
The 6Ms are copied mechanically while important process areas remain absent. Follow one real case and adapt categories to its areas of influence.
Timing: 5–10 minutes
- 3
Causes
Branch possible causes
Goal
Possible causes and subcauses are collected broadly without treating them as confirmed.
Inputs for this step
- Fishbone frame
- Process experts and initial evidence
Actions
- For each major branch ask what could create the effect and add concise cause bones.
- For important causes ask further about the mechanism; allow duplicates and mark knowledge gaps.
Output
Cause landscape
Possible causes · subcauses · knowledge gaps
Quality check
Does every subcause describe a plausible mechanism to its parent branch?
Pitfall
Vague labels such as communication or training replace concrete mechanisms. Ask for the observable state, transition and possible path of influence.
Timing: 12–25 minutes
- 4
Test
Test causes with evidence
Goal
The diagram leads to prioritized investigations rather than asserted root causes.
Inputs for this step
- Cause landscape
- Available data and test options
Actions
- Select causes by possible contribution, existing evidence and testability.
- For each priority define evidence, counter-evidence, test, owner and date; label confirmed causes later.
Output
Cause test plan
Hypothesis · evidence · test · owner · date
Quality check
Do untested bones remain explicitly possible causes?
Pitfall
The group votes for the most likely cause and calls it proven. Use voting only to order tests and keep evidence status visible.
Timing: 8–15 minutes
05
Artifact
What comes out at the end
Sketch: what the artifact looks like
Form
Cause landscape with effect, domain-relevant branches, possible causes, knowledge gaps and prioritized test plan.
Versioning / ownership
Record effect definition, date and participants; track each cause as open, supported or rejected.
Tool alternatives
- Paper fishbone
- Digital whiteboard
- Data table for cause tests
fishbone-diagram-working-template.md
Prepare the whole flow or one selected phase with real inputs.
Fishbone Diagram: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Complete fishbone analysis Time: 30–60 minutes plus follow-up cause tests
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Large whiteboard or paper, cards, markers, process data and an evidence-status legend.
- Roles: Facilitator, scribe and two to eight people from relevant process areas.
- Advance information: Gather defect cases, expected standard, process sketch, timing data and known counter-evidence.
- Overall time needed: 30–60 minutes plus follow-up cause tests
- Setup: Place the effect on the right, prepare major bones and leave space for subcauses. Use the 6Ms only as starting vocabulary.
Prepare for the work steps
Effect: Describe the effect precisely
- Defect, quality deviation or unwanted outcome
- Expected standard and case boundary
Categories: Lay out cause categories
- Effect statement
- Knowledge of the affected process
Causes: Branch possible causes
- Fishbone frame
- Process experts and initial evidence
Test: Test causes with evidence
- Cause landscape
- Available data and test options
Fishbone diagram
People
Roles, knowledge, capacity?
...
Machine
Systems, equipment, software?
...
Method
Flow, rules, handoffs?
...
Effect
Observable deviation
...
Material
Inputs, files, components?
...
Measurement
Definitions, signals, capture?
...
Environment
Environment, load, external factors?
...
Effect: Describe the effect precisely
Expected artifact: Effect statement
Object · deviation · time · magnitude
Entry:
...
- Does the statement contain only the observed effect and no cause?
Categories: Lay out cause categories
Expected artifact: Fishbone frame
Effect · major branches · process fit
Entry:
...
- Do branches cover distinct influence areas of the actual process?
Causes: Branch possible causes
Expected artifact: Cause landscape
Possible causes · subcauses · knowledge gaps
Entry:
...
- Does every subcause describe a plausible mechanism to its parent branch?
Test: Test causes with evidence
Expected artifact: Cause test plan
Hypothesis · evidence · test · owner · date
Entry:
...
- Do untested bones remain explicitly possible causes?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/fishbone-diagram/run-sheet
06
Example output
Concrete filled scenario, fictional example
Fictional example for orientation. Counts and timings describe this case and are not universal requirements.
fishbone-diagram-beispiel.md
Concrete filled scenario, fictional example
Fictional example: delayed course activation
Effect: 18% of courses in August were activated more than 24 hours after payment; the target is at most 2 hours.
Possible causes: queue wait (Machine), duplicate manual check (Method), incomplete metadata (Material), missing start timestamp (Measurement).
Test: Operations compares queue time and activation duration for 30 cases by Friday. No bone is confirmed yet.
07
Pitfalls
Recognize symptoms and steer against them
Quick overview, the full text is in the matching phase in the flow
- Describe the effect preciselyThe fish head already contains an explanation or blame statement.View in phase
- Lay out cause categoriesThe 6Ms are copied mechanically while important process areas remain absent.View in phase
- Branch possible causesVague labels such as communication or training replace concrete mechanisms.View in phase
- Test causes with evidenceThe group votes for the most likely cause and calls it proven.View in phase
Trap
Describe the effect precisely
Symptom
The fish head already contains an explanation or blame statement.
What to do
Compare observation and standard only; park explanations as possible causes.
Trap
Lay out cause categories
Symptom
The 6Ms are copied mechanically while important process areas remain absent.
What to do
Follow one real case and adapt categories to its areas of influence.
Trap
Branch possible causes
Symptom
Vague labels such as communication or training replace concrete mechanisms.
What to do
Ask for the observable state, transition and possible path of influence.
Trap
Test causes with evidence
Symptom
The group votes for the most likely cause and calls it proven.
What to do
Use voting only to order tests and keep evidence status visible.
08
Stop criteria
When to pause, resolve prerequisites, or choose another approach
The effect already contains a cause or blame.
Relevant process areas are absent.
Categories produce only vague umbrella terms.
Untested bones are called root causes.
Prioritized causes lack evidence or a test plan.
Finished the method guide?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.