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.

About 1 min read

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.

Keep reading

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

  1. Write the observed problem as specifically as possible.
  2. Create cause families that fit the system, not a generic template by habit.
  3. Add candidate causes under each family.
  4. Mark which candidates have evidence, which are assumptions and which can be tested.
  5. 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.

Use email
Keep exploring

Connected ideas

You are readingMap possible causes before picking one

Evidence and sources
Provides context

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

All sources (1)
Edition and review

Version 0.1.0 · Published

Edition checked · 2026-11-12

Read this idea as JSON · Release details