Protocol

Fan possible causes out before narrowing them

Widen the causal search before selecting the story.

About 1 min read

Before you use it

Use when
  • A team has one plausible explanation too early or the problem spans people, process, tools and environment.

Keep this limit in mind

  • Fishbone diagrams organize hypotheses. They do not establish causal strength or exhaust all possible causes.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

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

  1. 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.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingFan possible causes out before narrowing them

Evidence and sources
Supports

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

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details