The Arrow Carries the Change
A convergence diagram — several causes funnelling into one hub and out to its effects — governed by the rule that keeps such a diagram true rather than merely tidy. Six fields.
Two runs of the same template. A model of what drives pattern reuse beside one of what determines morning sailings — four named causes each, one of them uncertain and drawn as uncertain, converging once. Different subjects, identical grammar.
Generated from this template with the fields shown above — every node a plain noun, direction carried only by the connector shape, the uncertain path dashed with a dashed node, and all four paths terminating on a single merge point. Read back as sentences it says what it shows. The reference's baseline is the subtlest fault this library has found. Its arrow grammar was correct — solid arrows, T-bars, dashed lines, all defined in a legend — and it named its nodes as decreases, then joined them with inhibition bars. The decrease inhibits the decrease: a double negative, drawn immaculately, meaning the opposite of what was intended. Direction stated twice is direction lost. Three more rules came from my own runs rather than the source, which is unusual. The first printed this template's own name across the top, because a field phrased as a question reads like a title field. The second left two connectors stopping short of the merge point, hanging in space. The third wrote raises and lowers beside each path — and once the words were there, every connector quietly became a plain arrowhead, since the label was doing the work. That last one is the skill's own law arriving through the back door, and it is why the connectors carry no words at all.
Generated for this library
Input
Explains what raises the chance a pattern gets reused
Upstream examples shown per template · clarity of the field
names · time to first result · template length
Hub reuse rate
Directions examples shown raises · field clarity raises · time
to first result lowers · template length uncertain
Outputs patterns copied · templates edited · work shipped
Palette low-saturation blue, teal, amber, violet on white
Returned 1 diagram · 1:1 · white ground, flat, no shadow
nodes four quantities across the top, each a noun with no
verb in it, one colour per column
paths two solid arrows, one T-bar, one dashed - direction
carried only by the connector
merge a single convergence point above the hub, all four
paths entering it separately without overlapping
hub reuse rate, larger than the nodes, no glow
outputs three below the hub on plain arrows
legend raises, lowers, uncertain - defined once at the footYou fill in 6 fields — the braced lines at the top. Everything below them is fixed.
- 1What the diagram explains
- 2The four upstream nodes
- 3The hub
- 4Which way each path acts
- 5What the hub drives
- 6The palette
The Arrow Carries the Change
Produce ONE image, square: a convergence diagram in which several upstream causes funnel into a single hub, and the hub drives its outputs. Follow every line. Replace only the FIELDS block; everything after it is fixed.
First — do you have the fields?
If any field below still has braces around it, stop and ask. Put all the questions in one short message, and show the example under each one so they can see the shape of a useful answer. Wait for the replies, then draw. Never fill a brace yourself: a value you invented is a value nobody asked for, and it will look exactly as considered as the ones they did give you.
Ask in whatever language they are writing to you in. Translate the questions and the examples; do not make someone read English to tell you what they want.
The examples are only examples. If someone answers a question, use their answer; never fall back to the example because you prefer it.
If the fields are already filled in, ignore this and carry on.
Fields — replace these six lines only
- What the diagram explains: {the question or claim} e.g. what raises the chance a pattern gets reused
- The four upstream nodes: {four quantities} e.g. examples shown per template · clarity of the field names · time to first result · template length
- The hub: {the one thing they converge on} e.g. reuse rate
- Which way each path acts: {raises, lowers, or uncertain, for each} e.g. examples shown raises · field clarity raises · time to first result lowers · template length uncertain, drawn dashed
- What the hub drives: {two to four outputs} e.g. patterns copied · templates edited · work shipped
- The palette: {low-saturation colours on white} e.g. low-saturation blue, teal, amber and violet on white
The direction law
This is what separates a diagram that is true from one that is merely tidy.
A node is a quantity. A connector is a change. The direction is stated once, in the connector, and never in the node's name.
Nodes are nouns with no verb in them: *waiting time*, *crew available*, *field clarity*. Never *waiting time falls*, never *activity decrease*, never *reduced supply*.
The reason is not style. A reference run of this template named its nodes as decreases — *activity decrease*, *hydroxylation decrease* — and then joined them with inhibition bars, so the diagram read "the decrease inhibits the decrease": a double negative that means the opposite of what was intended, drawn immaculately. Direction encoded twice is direction lost.
Read the finished diagram back as sentences — "X raises Y", "X lowers Y" — and if any sentence contains two negatives, a node has a verb in it.
The three connectors
Exactly three, with fixed meanings, defined in a legend at the foot:
- Raises — a solid line with a plain arrowhead.
- Lowers — a solid line ending in a T-bar, never an arrowhead.
- Uncertain — a dashed line, arrowhead or T-bar as appropriate, and its target node also drawn with a dashed outline.
No other connector styles. No colour-coded meanings, no double arrows, no thickness carrying weight.
The connectors are not labelled. No word beside a path saying *raises* or *lowers* — the shape says it, and the legend defines the shape. This matters more than it sounds: a run that writes the word next to the line will quietly let every line become a plain arrowhead, because the word is doing the work. That is the failure this whole template exists to prevent, arriving through the back door.
One convergence
All upstream paths meet at a single point above the hub, then one line runs from that point into the hub.
Not three merge points, not four arrows striking the hub from different angles, not paths that overlap and cross. A reference run drew three separate merge circles in three different colours, which reads as three unrelated mechanisms rather than one convergence.
Each path stays clear of the others until it reaches the merge, and every path terminates on the merge point itself — the arrowhead or T-bar touching it, not stopping short in open space nearby. A run that ends two of its four connectors a little short leaves them looking like they lower something that is not there.
Layout
- Upstream: four short vertical chains across the top, one per cause, each in its own colour, each headed by a labelled cap.
- The hub: centred, clearly the largest node, plain fill. No glow, no burst, no 3D.
- Outputs: below the hub, side by side, on plain arrows.
- Funnel shape overall: wide at the top, narrow at the hub, opening again at the bottom.
No title
The diagram carries no heading, caption or footer. The only words on it are the node labels and the legend.
The first field is the question the diagram answers. It decides what goes in the diagram; it is not printed. Neither is this template's own name — a run of this template set the words *The Arrow Carries the Change* across the top in bold, because a field phrased as a question reads like a title field and an unfilled title slot takes whatever heading is nearest.
Honesty
Nothing is asserted that the fields did not supply.
No invented magnitudes, no percentages, no counts, no named sources, no claimed findings. Where the fields say uncertain, the diagram says uncertain — that is what the dashed line is for. A diagram that looks more confident than its input is worse than no diagram.
Style
Flat modern scientific figure. White ground, no shadows, no gradients, no depth. Low-saturation colours from the palette, one per upstream chain, neutral grey for the hub and outputs. A plain sans-serif at a size that stays legible when the figure is a column wide. Generous space between chains.
Never
- ✕ a verb inside a node's name
- ✕ direction expressed in both the node and the connector
- ✕ a T-bar and an arrowhead on the same line
- ✕ a word written beside a connector
- ✕ more than one convergence point
- ✕ crossing or overlapping upstream paths
- ✕ a connector that stops short of the merge point instead of touching it
- ✕ invented numbers, percentages, sources or findings
- ✕ a title, heading, caption or footer of any kind — and above all this template's own name
- ✕ glow, shadow, gradient or 3D on any element
The result
A figure that could be read aloud as a paragraph and come out meaning what it shows: four named quantities, one of them uncertain and drawn so, converging once on the thing they act upon.
The whole template, in one piece. The steps below are the entire workflow.
How to use it
- Copy the whole template with the button above.
- Replace the six FIELDS lines. Name every node as a plain quantity with no verb in it, then put every rise and fall in the fourth field.
- Mark anything you are not sure of as uncertain. It will be drawn dashed and labelled, which is more useful than a confident line.
- Paste it into any image-capable agent or model, in one message. One run returns the diagram.
- Read it back as sentences before shipping: 'X raises Y', 'X lowers Y'. If any sentence comes out as a double negative, the direction got stated twice.
What you swap
- What the diagram explains
- what raises the chance a pattern gets reused
- The four upstream nodes
- examples shown per template · clarity of the field names · time to first result · template length
- The hub
- reuse rate
- Which way each path acts
- examples shown raises · field clarity raises · time to first result lowers · template length uncertain, drawn dashed
- What the hub drives
- patterns copied · templates edited · work shipped
- The palette
- low-saturation blue, teal, amber and violet on white
Before it runs
- Nodes you can name as quantities. 'Waiting time' is a node; 'waiting time falls' is a node and an arrow crushed together, and that is the failure this template exists to prevent.
- A direction for every path, including the ones you are unsure of. Unsure is an answer here and it has its own line style.
- A model you are willing to own. This draws what you assert; it does not check whether it is true.
When to reach for it
When several things act on one thing: what drives a metric, what determines an outcome, what feeds a bottleneck. Templates in this style define their arrow types carefully and then let the direction of an effect be stated twice, which turns a clear diagram into a double negative.
What changes
- One publication-grade diagram: several upstream causes converging on a single hub, and the hub driving its outputs.
- Direction lives in the connector and nowhere else, so the diagram cannot contradict itself.
- Three connector types with fixed meanings — raises, lowers, uncertain — and a legend that defines them.
- One convergence point, so several causes read as one mechanism rather than three unrelated merges.
- Nothing asserted that was not supplied: no invented magnitudes, no invented certainty, and uncertainty drawn as uncertainty.
Pairs with
- Count Both SidesA value-proposition canvas — a square facing a circle, three regions each — where the two halves are written as pairs, so anything unmatched shows up instead of hiding in a list. Six fields.
- Each Layer Takes Something AwayAn exploded axonometric that pulls one site apart into stacked transparent layers — kept on white and kept analytical, because the temptation is to render it dramatic and lose the drawing. Six fields.
- Every Region OccupiedA three-circle overlap diagram where every region you draw has something real in it — held to three sets, because four creates overlaps nobody can fill. Six fields.