Protocol
Fan possible causes out before narrowing them
Widen the causal search before selecting the story.
When it fits
- A team has one plausible explanation too early or the problem spans people, process, tools and environment.
When to avoid it
- Fishbone diagrams organize hypotheses. They do not establish causal strength or exhaust all possible causes.
Why it matters
Put the observed effect at the head of a cause-and-effect diagram. Add a few context-appropriate branches such as process, information, tools, environment, interfaces and workload. Generate candidate causes under each branch, then mark which candidates have evidence, which need tests and which are already contradicted.
Steps
- The diagram contains competing candidate causes and an evidence status, not just a decorative list.
An example
Repeated upload failures branch into file format, mapping rules, permissions, runtime capacity and operator sequence before testing each candidate.
Check your result
The diagram contains competing candidate causes and an evidence status, not just a decorative list.
Keep this limit in mind
- Fishbone diagrams organize hypotheses. They do not establish causal strength or exhaust all possible causes.
Connected ideas
Useful withFollow the why-chain until the cause becomes changeable
Evidence and sources
A cause-and-effect or fishbone diagram is a structured way to lay out suspected causes across categories before deeper analysis.
The diagram generates hypotheses about causes; it does not verify them.
Cause-and-Effect Diagram · Description, uses and steps