When not to draw a diagram

When not to draw a diagram: three questions to ask first, what to write instead, and what unneeded diagrams cost a team in time, upkeep and trust.

Written by
FlowDraw Team
Published
Reading time
5 min read
The words "Sometimes skip the diagram" in large type, beside a small FlowDraw board with a Pros and cons drawing.

We make a diagram tool, and part of using one well is knowing when not to draw a diagram. A neat drawing can take an afternoon to say what “Refunds over $500 need finance sign-off” says in six words.

Quick Answer

Do not draw a diagram when a list, a table or a sentence says it just as well. Ask three questions first: does the idea have a shape that words would hide, who will do something differently after seeing it, and who will keep it true? Without clear answers, write it instead.

When not to draw a diagram: three questions

Does the idea have a shape?

Diagrams earn their cost when structure is the message: branches, loops, handoffs between teams, many things linked to many things. If you can read it aloud as a numbered list with no “unless”, “if” or “meanwhile”, it is a list. Rotating an API key is five steps in a line, and a flowchart adds boxes without adding information.

Who will do something differently after seeing it?

Name the person and the decision. “It would be good to have a picture of the architecture” fails this test. “Lisa needs to see which services touch card data before Friday’s audit review” passes, and it also tells you what to draw, because one diagram should answer one question.

Who will keep it true?

A published diagram is a small promise to maintain it. A sentence in a doc gets fixed by whoever notices the error. A diagram gets fixed by someone with the tool open, some feel for the layout and time to spare. If nobody owns it and it will outlive this week, put the same facts somewhere that is already maintained, such as the runbook or the README.

Sketching to think is exempt from all three. A rough drawing you make alone to understand something, or in a meeting and then throw away, owes nobody anything. These questions are for diagrams you hand to other people.

What to write instead

What you haveUseExample
One ruleA sentenceRefunds over $500 need finance sign-off
Steps in a fixed order, no branchesA numbered listRotating an API key, cutting a release branch
Several options compared on the same pointsA tableThree payment providers by fees, payout time and currencies
A statusA sentence with a dateOn track for November 18, two risks open
A decision and its reasonA short paragraphWe chose a queue over cron because jobs must survive a restart

Text has advantages a drawing does not. You can search it, copy it, quote it in a ticket and have a screen reader read it out. FlowDraw’s search, for one, does not read the text on a board, so a rule that exists only on a board cannot be found by searching for it. A wiki page can.

The picture on this post is FlowDraw’s “Pros and cons” template, and at heart it is two lists and a decision. We would use a board for it when several people are adding points at the same time and arguing over the weights. For one person weighing one choice, a table in a doc does the job.

The cost of diagrams nobody needs

Time, twice. There is the afternoon of drawing, and then every later change. Polishing a layout also feels like progress, which makes it easy to spend the afternoon without noticing.

Arrows that skip the thinking. A sentence forces a verb, and an arrow lets you leave it out. Between two boxes, an arrow could mean calls, depends on, sends data to or reports to. Writing “the worker sends email through Postmark” makes you know which. A tidy diagram can look settled when its author never had to decide what the arrows mean.

Copies nobody updates. Diagrams that nobody needs are the ones nobody maintains, and they sit in the list next to the ones that matter. Readers who open a wrong one learn to distrust the rest, which is how process diagrams lose their value. Extra boards also make finding the right one harder.

The reader’s time. Scanning a drawing to find one fact is slower than reading the fact. For a person who needs only the refund limit, a whole approval flow is a detour.

When to draw anyway

None of this is an argument for fewer pictures in general. The same test cuts the other way. A long paragraph describing a process with three exceptions and two teams is a flowchart waiting to be drawn. So is a doc that people keep reading and getting wrong, and so is an argument that returns every month because each person holds a different picture of the process.

When you are unsure, write it first. If the writing stays short, you are finished. If it fills up with “unless” and “except when”, you have found the part worth drawing, and you already know what the labels should say.

Continue Reading

Ready to create your first diagram?

Turn your ideas, notes, or documents into a clear,
editable flowchart in seconds.

Get Started Free