# Map possible causes before picking one

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Map possible causes before picking one

ID: MHC-D-BRALI-0102 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/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.

Knowledge source release: MHC-RPUB-20261112-20287590
Source corpus commit: 20287590ddd3999b7492df232822b6a0f7d114b1
Source manifest SHA-256: 2a987660d12de0ce2bde77a421424f7762af1ff77872ef41093fecc33db74a95
Source projection SHA-256: 2807da39bbe6a3dee2db32a76675ac5185f5a33e8b0a5cdd0c22a4731f3378a0

### Use when

- A recurring problem has several plausible causes and the team is converging too quickly on one story.

### Avoid when

- A fishbone diagram is an organizing aid, not proof of causality. Complex failures can have multiple contributing causes.

### Explanation

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

At least two plausible explanations are represented and the next test can distinguish among them.

### Limits

- A fishbone diagram is an organizing aid, not proof of causality. Complex failures can have multiple contributing causes.

### Evidence and sources

- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-b4a44f8ab33e3250d5b2. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/fishbone-diagram-root-cause.json)
- FP-BRALI-SRC-b4a44f8ab33e3250d5b2: Use a Fishbone Diagram to Identify the Root Causes of a Problem — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/fishbone-diagram-root-cause.json

Review: agent · Agent editorial and scoped source review · 2026-11-12T18:37:40Z
Published: 2026-11-12T18:37:40Z
Related (useful_with): https://vedokrok.com/knowledge/simplify-before-you-automate-or-delegate
Related (useful_with): https://vedokrok.com/knowledge/benchmark-the-mechanism-not-the-surface
Related (useful_with): https://vedokrok.com/knowledge/reverse-the-default-to-find-an-option
Related (useful_with): https://vedokrok.com/knowledge/use-the-ideal-outcome-to-reveal-costs
Related (useful_with): https://vedokrok.com/knowledge/reuse-a-proven-resource-before-adding-one
Related (useful_with): https://vedokrok.com/knowledge/put-buffer-where-variation-hurts
Related (useful_with): https://vedokrok.com/knowledge/change-one-parameter-then-observe
Related (useful_with): https://vedokrok.com/knowledge/reconstruct-a-timeline-from-artifacts
