The Diagram Nobody Else Drew

A diagram that genuinely explains something is one of the few assets people go looking for. Redrawing it is work, describing it in prose is worse, and so the path of least resistance is to show it and say where it came from.

The catch is that almost everything published as a “visual” is decoration, and decoration earns nothing. The difference isn’t production budget. It’s whether the picture resolves a confusion that words handle badly.

What a citable diagram does

It settles something specific. Usually one of four things:

An order of operations. Steps that people do in the wrong sequence, drawn in the right one, with the dependencies visible. Prose is bad at this because a numbered list can’t show that steps two and three are simultaneous while four blocks on both.
A decision boundary. The two or three questions that determine which path applies, arranged so that a reader can walk their own case through it and land somewhere. This is the most-reused shape, because it converts an argument into a lookup.
A hierarchy people get backwards. Where things nest, what contains what. Fields full of overlapping vocabulary generate this confusion constantly, and one correct containment drawing can be the reference for years.
A lifecycle with a step everyone forgets. Drawing the whole loop makes the missing step visible in a way that mentioning it never does.

The test is blunt: could someone use this to win an argument, or to teach a colleague? If yes, it will get reused, because those are the two moments when people reach for a picture. If it only makes a page look considered, it’s furniture.

A second test: does the diagram assert something that could be wrong? A drawing with a real claim in it can be disagreed with, which means it can also be cited. One that asserts nothing is safe and useless.

What decoration looks like

Worth naming, because the decorative version is what most sites produce while believing they’ve made an asset:

Stock hero images. Nobody has cited one.
Four-quadrant grids with no data behind them. Two axes chosen for symmetry, four boxes of plausible labels. It looks analytical and contains no information — every placement in it is opinion, and unlabelled opinion at that.
Funnel shapes that assert an order nobody established. The funnel implies both sequence and narrowing. If neither is real, the shape is doing rhetorical work the content can’t support.
“Infographics” that are a list with a background. A vertical strip of numbered statements, some icons, brand colours. This is a list, styled. It is harder to read than the list, impossible to quote, and takes ten times as long to make.

The infographic-and-embed-code era ended for a reason, and the reason wasn’t fashion. The links were the point rather than the picture: the graphic existed to carry an embed snippet, and the snippet existed to place a link with the anchor text its author wanted. Once that was the norm, the citations stopped meaning anything and everyone stopped treating them as editorial. Draw diagrams because someone needs the diagram.

Craft that makes reuse possible

Most good diagrams fail at reuse for mechanical reasons. The person who wanted to use yours couldn’t, so they made a worse one.

Readable at small sizes. It will be viewed at a third of the size you designed it. If the labels stop being legible, it stops travelling.
Legible in greyscale. Colour-coded categories become identical grey blobs the moment someone prints or photocopies it, and a diagram whose meaning lives entirely in hue has no fallback. Shape, position, and labels should carry the information; colour should reinforce it.
Labels inside the image. This is the one people get wrong most often. If the meaning of a box depends on the caption in your page, then the diagram can’t be understood anywhere else — and it will end up somewhere else, because the way pictures travel is by being lifted. A diagram must be self-contained.
A title in the image itself. Same reasoning. The picture should say what it’s a picture of.
Your domain name, discreetly, in a corner. Small, low-contrast, out of the way. Not a watermark across the middle. The purpose is that when the image is screenshotted into a deck, a thread, or someone’s notes, the attribution survives the trip and the next person can find you. This is the single highest-return five minutes in the whole exercise.

Alt text and a prose walkthrough

Write real alt text — not “diagram of the process” but a sentence that conveys what the diagram shows. And put the same content in prose on the page, walking through it in order.

Two reasons, both practical. First, a diagram that only exists as pixels is unusable by anyone who can’t see it, and unfindable by anything that reads text. Second, the walkthrough is what a writer quotes. They may reuse the image, but they’ll paraphrase your description of it, and if you haven’t written one they’ll invent their own — usually less accurate than yours.

Give it its own page

A diagram buried two-thirds of the way down a long post isn’t linkable, because there’s nothing specific to link to. Someone who wants to point at the drawing has to point at the article and hope.

Give the diagram a page: the image, the title, the walkthrough, the assumptions behind it, and the date. Then link to it from the longer posts that use it. This also makes the URL stable, which matters more than it sounds — a diagram’s whole value is links accumulated over years, and renaming the page throws that away.

When someone uses it without credit

It happens, and the normal response is a short, polite note asking for a credit line. That’s a routine request between publishers and usually granted immediately; most uncredited use is thoughtlessness, not theft.

What is not normal is requiring a keyword-anchored link in exchange for permission to reuse the image. That’s a link scheme with a licence attached, it’s the exact pattern that killed the embed-code era, and Google’s spam policies cover it. Ask for a credit. Take a credit. Don’t write the anchor text.

What to do next

Pick the confusion you explain most often out loud — the thing you find yourself drawing on a whiteboard for every new colleague — and draw it properly, once, on its own page.

For the credit question, how to ask for attribution without running a link scheme covers the wording and the line you don’t cross. Diagrams also pair naturally with worked examples, which are the prose form of the same instinct. And the general housekeeping that makes any of this pay off is in making pages easy to cite.