Documentation · Thinking
Fishbone
The title is the effect, in the head. Each bone is a category of cause, and what is written inside it are the causes themselves.
When to use it
Organize possible causes of an effect into categories, including nested causes.
The title is the effect at the head. Categories organize proposed causes; the diagram itself does not prove which cause is responsible.
Working example
Copy this complete example into the Source tab, then press Generate. Change its labels or values to make your first version.
fishbone "The part is produced the wrong size" {
bone "Material" {
"Wrong specification of the material"
"Poor storage conditions"
"Worn out material"
}
bone "Method" {
"Wrong production procedure"
}
bone "Measurement" {
"Wrong size of the mould"
"Blueprint mistake"
}
bone "Environment" {
"Wrong production conditions"
}
bone "Machine" {
"Machine malfunction"
"Machine defect"
}
bone "People" {
"Employee mistake"
"Mistaken machine settings"
}
}Syntax reference
The same reference used by the editor and AI briefing. Syntax is notation-specific; use the keywords listed here.
Diagram
| Syntax | Meaning |
|---|---|
fishbone "The effect" { | open one; the title goes in the head |
Bones
| Syntax | Meaning |
|---|---|
bone "Material" { | a category of cause; close it with } |
"A cause" | one cause on that bone |
"A cause" { | a cause with what is behind it |
bone "Material" "#e34948" | a bone in a colour of its own |
Look
| Syntax | Meaning |
|---|---|
style formal | formal, boxed, bold |
head arrow | arrow, box, curve |
angle 60 | how steeply a bone leaves the spine |
arrows on | arrowheads where a cause meets its bone |
colors colorful | auto, single, colorful, warm, cool, ink |
size 820 460 | how big it is drawn |
# comment | line comment (also //) |
Language rules
- The file is one fishbone "Title" { ... } block. Nothing may sit outside it.
- The title is the effect, and it is written in the head.
- Each category of cause is bone "Name" { ... }, and the causes inside it are captions in quotes.
- A cause may take a { ... } block of its own for what is behind it, one level deep.
- Bones alternate above and below the spine in the order they are written.
- Settings are written as name value, in any order.
- Do not invent settings. Every one the language has is listed above.
Edit on the canvas
- Select a bone to add a cause; select a cause to add a cause behind it.
- Rename captions in place and use the fishbone panel to edit categories and structure.
Generate replaces the drawing from source. Save before generating again if you want to preserve manual finishing touches.
Read Saving & exportingWrite it with an assistant
Tingraph AI already knows this notation. For another assistant, copy the tutorial below, describe your diagram under MY DIAGRAM, then paste the returned source into the editor. This prompt includes every syntax row, rule and working example above.
Read the complete prompt
You are writing Tingraph source. Tingraph is a small text language that draws a fishbone diagram. Answer with Tingraph source only.
SYNTAX
Diagram
fishbone "The effect" { open one; the title goes in the head
Bones
bone "Material" { a category of cause; close it with }
"A cause" one cause on that bone
"A cause" { a cause with what is behind it
bone "Material" "#e34948" a bone in a colour of its own
Look
style formal formal, boxed, bold
head arrow arrow, box, curve
angle 60 how steeply a bone leaves the spine
arrows on arrowheads where a cause meets its bone
colors colorful auto, single, colorful, warm, cool, ink
size 820 460 how big it is drawn
# comment line comment (also //)
RULES
- The file is one `fishbone "Title" { ... }` block. Nothing may sit outside it.
- The title is the effect, and it is written in the head.
- Each category of cause is `bone "Name" { ... }`, and the causes inside it are captions in quotes.
- A cause may take a `{ ... }` block of its own for what is behind it, one level deep.
- Bones alternate above and below the spine in the order they are written.
- Settings are written as `name value`, in any order.
- Do not invent settings. Every one the language has is listed above.
WORKED EXAMPLE
fishbone "The part is produced the wrong size" {
bone "Material" {
"Wrong specification of the material"
"Poor storage conditions"
"Worn out material"
}
bone "Method" {
"Wrong production procedure"
}
bone "Measurement" {
"Wrong size of the mould"
"Blueprint mistake"
}
bone "Environment" {
"Wrong production conditions"
}
bone "Machine" {
"Machine malfunction"
"Machine defect"
}
bone "People" {
"Employee mistake"
"Mistaken machine settings"
}
}
OUTPUT
- Reply with one fenced code block and nothing else.
- The block starts with `fishbone "…" {` and ends with `}`.
- Do not invent keywords: use only the ones listed above.
- Keep labels short enough to read inside a box, and keep every ID unique.
MY DIAGRAM
Describe what you want here, then send this message.Something unclear? Contact support or read the Privacy Policy.