startthat.work home

TC1-02 Fishbone diagram (Ishikawa diagram, cause and effect diagram)

Groups brainstormed causes of one problem under category branches and produces a fishbone diagram with the problem as its head.

Trace cause and test claimsEvidence: DocumentedPrimary technique, runs in step 5.3Strongest statement: describe

What it does

Groups brainstormed causes of one problem under category branches. Artefact: a diagram with the problem as head and categories as ribs; read categories holding many causes and empty categories.

When to use it

Use when a team needs to list and sort the many possible causes of one problem before deciding which to investigate.

When it does not fit

Many causes fit two categories, a large 'other' rib appears, or problems, causes and symptoms are confused.

Result format

The result is a diagram with the problem as the head and category branches as ribs, with the brainstormed causes listed under the category each belongs to. It names the categories holding many causes and the categories left empty.

Requirements on the material

PropertyRequirement typeRequirement
Content typeAlways appliesrequires=text
Unit of analysisAlways appliesrequires=topic
Appraises source credibilityApplies in some casesno

Not restricted on: Structure, Variable types, Time structure, How the sample was chosen, Level of detail available, Number of sources, Whether sources can be joined, Amount of material, Known data problems, Producer interest, Source dependence, Origin, Document genre, Language, Personal information, Security classification, Licence.

Minimum materialA defined problem, a list of causes (brainstormed or taken from documents) and a category scheme chosen before grouping.
Additional sources needednone
Not for (rules)stakes_tier=high-stakes & insight_wanted=cause :: the diagram lists proposed causes and does not test any of them
Not for (text)Wrong choice when many causes fit two categories, a large other branch appears, or problems, causes and symptoms are confused. Misused when the number of causes on a branch is read as its importance.

Choosing and ordering

Kind of techniquePrimary technique, runs in step 5.3
Phase taganalyse
Other phase tagsnone
Kind of findingcause; pattern
Question answeredwhy
Strongest statement it supportsdescribe
Needs as input
Makes as output
Must exist firstNone
Loop targetreturn to analyse

Library checks by stakes

Each stakes level includes the checks of the level below it. Checks that need a person apply at high stakes only, so the process leaves them out at lower stakes (decision 38). Repeatability: judgement dependent.

StakesCheckPerson involvedCounts as a different method
exploratoryassumption and limitation statementnoneno
decision-informingassumption and limitation statementnoneno
decision-informingspot checkoptionalno
high-stakesassumption and limitation statementnoneno
high-stakesspot checkoptionalno
high-stakesindependent reviewneededno

Failure modes and limits

Model suitabilityhuman judgement required
Typical model failureFills every category with generic causes that were not raised by anyone and treats the count of causes on a branch as evidence of importance.
Error sourcesinput data; coder or rater judgement; expert opinion
Certainty limitsCertainty is low because the diagram records proposed causes and not tested ones. It falls further when all causes come from one brainstorming group.
  • pairs with TC1-01 Five whys: a why chain follows one branch of the diagram in depth; should follow :: family:Frame the question :: the problem must be stated before causes are grouped

Evidence and tag basis

Documented. One of the seven basic tools of quality control; application claims on the page have 'citation needed' tags; the BMJ commentary lists it among alternatives to five whys without effect evidence. (Wikipedia, Ishikawa diagram; BMJ Quality and Safety 2017;26:671, on the five whys)

Tag basis: input profile inference; selection inference; sequencing inference; robustness inference. All tag values are inference unless a source is named.