Home About Experience Projects Case studies Resources Articles Briefs Playbook Tools FAQ How we start Security Get in touch

AI in practice

Making Diagrams When You Do Not Have a Designer

Small businesses do not have a designer waiting for the one-pager. The honest alternative to a generated diagram is usually no diagram at all.

Every diagram on this site was made this way, which is either the strongest recommendation I can offer or a warning, depending on what you think of them.

WHAT A SMALL BUSINESS ACTUALLY NEEDS MADE Internal and functionalone-pagers, comparison sheets, process diagrams Client-facing but routineproposal covers, report layouts, simple decks Explanatorythe diagram that makes an idea land in one look Brand and identityhire a designer, and mean it Three of these four were previously either expensive or simply never made at all.
Figure 1: the gap this fills is not replacing designers. It is the work that was never going to get a designer.

The gap this actually fills

Not replacing designers. Small businesses do not have a designer waiting for the one-pager, and the honest alternative to a generated diagram is usually no diagram at all, or a screenshot of a spreadsheet.

The work that benefits is the large volume of internal and semi-external material that was never going to justify a professional brief: the process diagram in a proposal, the comparison sheet for a decision, the explanatory figure that makes an idea land in one look.

The comparison is not against a designer. It is against nothing, which is what most of this material got before.

THE ORDER THAT DECIDES THE OUTCOME Know what it must sayone sentence, written down Then describe the shapestructure, not styling Then iterateon specifics Starting with "make it look good" produces something that looks fine and says nothing. A diagram is an argument with a layout. If the argument is not settled, no amount of styling rescues it.
Figure 2: decide the message before the visual, every time. This is where most attempts go wrong.

The order that decides everything

1. Write the one sentence it must communicate

Before anything visual. If I cannot state in one sentence what a diagram is arguing, the diagram will not argue it. Most failed attempts trace to skipping this, and no amount of iteration on colours recovers from it.

2. Describe the structure, not the styling

Two columns comparing before and after. A timeline with four points where the third is the failure. A decision tree with two branches. Structure carries the meaning; styling only carries the tone.

3. Give the actual content, not placeholders

Real labels, real numbers, real categories. A diagram built on placeholder text has to be rebuilt once the real content arrives, because real content is always longer and messier than placeholders.

4. Iterate on specifics rather than impressions

Make the second panel wider. Move the caption below. Use one accent colour, not three. Vague feedback such as make it cleaner produces random change.

5. Check it against the sentence from step one

Does somebody who reads only this diagram get that sentence? If not, it is decoration, and decoration is worse than nothing because it takes up space that suggests meaning.

6. Keep a consistent set of conventions

Same palette, same type, same conventions for what a red box means. Consistency across a set of diagrams does more for how work is perceived than the quality of any single one.

What it is good for, and where it stops

What it is good forWhere it stopsWhat it costs me
Explanatory diagrams and process figuresGenuinely strong, and this is where I use it most.Time to settle the argument first.
Comparison layouts and simple tablesReliable and fast.Almost nothing.
Document and slide layoutsServiceable, and it will not surprise anyone.Editing, and lowered expectations about originality.
Brand identity, logos, anything that must be distinctiveNot the tool for it. Hire a designer.The cost of a designer, which is the correct cost.

What it is honestly worth

The measurable effect is volume. This site carries ninety-plus original diagrams. Under any previous arrangement it would carry none, and the articles would be walls of text with stock photography, which is what most professional sites are.

The quality is competent rather than distinctive, and I would rather say that than pretend otherwise. A good designer would produce better work, and would also produce it at a pace and price that means this material simply would not exist.

The genuine benefit is that explanation improves. Being forced to state what a diagram argues before making it has made the writing clearer too, which I did not expect.

How it breaks

Decoration masquerading as explanation. The commonest failure. A visual that looks purposeful and communicates nothing is worse than plain text, because it occupies the space where an explanation should be.

Inconsistency across a set. Twelve diagrams in twelve styles reads as careless. Fix conventions early and apply them.

Too much in one figure. If it needs a legend and a key and four colours, it is two diagrams.

Using it where identity matters. Anything that represents the business itself deserves a professional. That is not a limitation of the tool; it is a correct allocation of money.

How to tell whether it is working

Cover the caption and the surrounding text, and look at the figure alone. If the point is still clear, it works. If you need the paragraph to explain the picture, the picture is not doing anything.

A note on this article. A first-person account of my own practice rather than a product review. I have no affiliation with Anthropic beyond being a paying user. On the wider question of original visuals versus stock photography, the evidence is reasonably consistent that original diagrams which explain a concept outperform generic stock imagery for both credibility and engagement; I have kept that claim general rather than attaching a specific percentage, because the figures in circulation are largely from marketing sources.

Paul Prado Pacardo is a Senior Executive Assistant and Operations professional with over ten years supporting C-level leaders, and the solo founder of a multi-product software studio. Available for remote Chief of Staff, Operations, Senior Executive Assistant and Project Manager roles.