Why "one cause" is self-deception
"The problem is the contractor" is the most frequent first formulation. A month later the problem returns, because it had ten more causes that nobody looked for. Fishbone is built on a simple assumption: a persistent failure has not one cause but a branching tree. On the Super Oracle page the method is described exactly this way: you think there is one cause — Fishbone shows 15–20, and the main one is often not the one you suspected.
Step 1: formulate the problem as an effect
The first five minutes are the exact formulation. Describe the problem as an observable effect, not as a guess: not "bad service" but "the number of returns doubled in a month". The effect becomes the "head of the fish": everything below it is the branches of causes that have to be filled in.
Step 2: lay the causes out across six categories
The next ten minutes are the six "bones" of the skeleton: people (who is involved), processes (how the work is organized), equipment (tools and systems), materials (data and inputs), environment (working conditions) and management (rules and decisions). Everything that can affect the effect goes into each category, without arguing about importance — completeness first, evaluation later.
Step 3: reach the root cause
When the tree is filled, a "why?" chain is asked inside each branch: cause → why it appeared → why it happens. The goal is not the first plausible explanation but the level at which the cause stops depending on the others. Most often the root causes turn out to be in the "processes" and "management" categories, not where the team looked first.
Step 4: mark the criticality ★ / ○
The last five minutes are the marking. ★ — the cause affects the effect directly: removing it changes the outcome. ○ — the cause reinforces the effect but does not create it by itself. A diagram-map with criticality shows where to start: first all the ★, then the ○ that feed the ★.
What you get as output
The result of the twenty-minute work is a diagram-map: six categories, 15–20 causes, the root causes and the priority by criticality. Exactly this artifact Super Oracle produces at the research stage as part of a five-method session. About how to turn the found cause into a checkable solution — in the articles "From contradiction to test" and "Solution-space expansion".
Questions and answers
How is Fishbone different from "just discussing the problem"?
An ordinary discussion stops at the first plausible explanation. Fishbone forces you to lay the causes out across six categories and reach the root cause.
How many causes does Fishbone usually find?
The practice of the sessions is 15–20 causes, and the main one is often not the one suspected before the session.
Which six categories are used?
People, processes, equipment, materials, environment and management. The categories can be adapted to the industry.
What do the ★ and ○ criticality marks mean?
★ — the cause affects the problem directly, ○ — reinforces it. The marking shows where to start the fix.
How long does the session take?
About 20 minutes for the diagram-map: formulating the effect, six categories, root causes and criticality.
Does Fishbone ensure the right cause?
No: the method systematizes hypotheses about causes. The conclusions remain material for a human decision and are checked against the data.
Where is Fishbone used on the site?
At the research stage of the Super Oracle agent: the session starts with the diagram-map of causes, then moves on to the contradiction and the solutions.
What does the team get as output?
A diagram-map: six categories, every cause with its criticality, and a short list of root causes to start from.