Protocol
Map possible causes before picking one
A cause diagram is useful because it delays the jump from symptom to favourite explanation. List plausible cause families, attach observations, and mark what is still only a hypothesis before you decide what to test.
Before you use it
- Use when
- A recurring problem has several plausible causes and the team is converging too quickly on one story.
Keep this limit in mind
- A fishbone diagram is an organizing aid, not proof of causality. Complex failures can have multiple contributing causes.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
A cause diagram is useful because it delays the jump from symptom to favourite explanation. List plausible cause families, attach observations, and mark what is still only a hypothesis before you decide what to test.
Steps
- Write the observed problem as specifically as possible.
- Create cause families that fit the system, not a generic template by habit.
- Add candidate causes under each family.
- Mark which candidates have evidence, which are assumptions and which can be tested.
- Choose the cheapest discriminating test before choosing a “root cause.”
Check your result
At least two plausible explanations are represented and the next test can distinguish among them.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingMap possible causes before picking one
From this idea
This idea is useful withSimplify before you automate or delegateThis idea is useful with
Benchmark the mechanism, not the surfaceThis idea is useful with
Reverse the default to find an optionThis idea is useful with
Use the ideal outcome to reveal costsThis idea is useful with
Reuse a proven resource before adding oneThis idea is useful with
Put buffer where variation hurts
Evidence and sources
First-party source of this practical exercise.
Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding.
Use a Fishbone Diagram to Identify the Root Causes of a Problem · data/life-os-content/fishbone-diagram-root-cause.json
Edition and review
Version 0.1.0 · Published
Edition checked · 2026-11-12