Diagram guides · Updated October 2026

How to draw a diagram: the basics nobody teaches you

Knowing how to draw a diagram is mostly knowing what to leave out. The hard part is not the shapes, which take a minute to learn, but deciding what single question the drawing answers and then resisting everything else you know about the subject. These are the diagram basics in the order you need them: what the diagram is for, which shapes to use, where to start, and why a correct diagram can still be unreadable.

Before the first box

  • What one question does this answer?
  • What is the thing that changes?
  • Where does it stop?

Then, while drawing

  • One direction all the way through
  • Verbs in the boxes
  • Answers on the arrows out of a decision
  • Nothing you cannot read at a glance
Draw it with Flowchart Answers →Check a diagram I drew

Paper first is a perfectly good workflow. The tool is for the tidy version.

Decide what the diagram is for before you draw anything

Write the question in one sentence at the top of the page. How does a bill become law. What happens when a browser asks for a page. Why does the pressure drop. Everything that does not help answer that sentence is cut, and having it written down makes the cutting much easier than it is in your head.

This also stops the most common beginner failure, which is drawing the topic instead of a relationship. A topic produces a scatter of labelled boxes connected by arrows that were added afterwards to make it look like a diagram. A question produces a path.

Pick a shape set and stay inside it

Four shapes handle nearly every diagram a student or a teacher needs to draw. Learn these, resist the rest, and your reader will have the whole vocabulary after the first glance:

Rounded boxWhere the process starts and where it ends. Two of them in a diagram, usually, and never in the middle.
RectangleA step. Something is done, and afterwards the subject has changed. Write it as a verb phrase.
DiamondA decision. It must have a question inside it and every arrow leaving it must carry its answer.
ArrowDirection, and by default the words and then. Anything stronger than that has to be written on the line.

Written as Mermaid, those shapes are punctuation. Round brackets inside square brackets make the rounded start, plain square brackets make a step, and braces make a decision whose exits carry their answers:

graph TD
  A([Start]) --> B[Heat water]
  B --> C{Boiling?}
  C -- no --> B
  C -- yes --> D([Stop])

Start with the thing that changes

Find the subject that is in one condition at the beginning and a different one at the end: the water, the request, the application form. Put its starting condition in the first box. Then ask what happens to it next, write that, and repeat until it stops changing. You will reach the end of the process naturally, which is much harder when you start in the middle with the step you happen to find most interesting.

When you get stuck, say the last two boxes aloud joined by and then. If that sentence is true, keep going. If it needs a because or an unless, you have found a missing box or an arrow that wants a label.

One direction, chosen on purpose

Pick top to bottom or left to right and hold it for the whole diagram. Readers infer direction from the first two boxes and stop checking the arrowheads, so a diagram that runs downwards and then doubles back upwards will be misread even though it is technically correct.

Which one depends on the shape of the content. A branching process wants top to bottom, because each decision needs horizontal room for its answers to separate. A long chain with few branches wants left to right: stacked vertically it becomes a strip taller than the screen, while horizontally it reads like a timeline and fits the shape of a slide. The only exception is a loop, which is allowed to point backwards precisely because it is the exception.

Keeping it readable

A diagram earns its place by being understandable in one look. Past a certain size that stops being possible and you have made a reference document with boxes, which is worse than a numbered list because it is harder to update and harder to search.

Three habits keep the size down. Merge consecutive steps that always happen together into one box, because the reader does not need the granularity if there is no decision between them. Cut anything the sentence at the top of the page did not ask about. When what remains is still too much, split it: finish the first diagram with a box naming the second, and draw that separately.

Keep labels short enough that the box does not stretch. Long text forces wide boxes, wide boxes push their neighbours out of alignment, and the diagram starts to look messy for reasons that have nothing to do with its content.

Mistakes that make a correct diagram useless

Boxes that are nounsA box reading Temperature is a label, not a step. Heat the water to 100C is a step, and it tells the reader what changed.
A decision with one way outIf only one arrow leaves the diamond, it was never a decision. Either find the other branch or make it a rectangle.
Arrows that mean nothingRead the arrow aloud as a sentence. Weight leads to normal force is not physics, it is two labels placed near each other.
Everything on one sheetA diagram nobody can take in at a glance has become a reference document. Split it and let one box stand for the next diagram.
Colour doing the explainingIf the meaning disappears when the page is printed in grey, it was never in the diagram. Put it in the labels.

Draw it roughly, then have it rendered

Sketching on paper is still the fastest way to find the structure, because rearranging boxes is the bulk of the work and an eraser is quicker than any interface. Once the structure stops changing, describing the process to Flowchart Answers gets you a clean rendering with the Mermaid code beside it, which you can edit line by line and download as SVG.

Going the other way works too. Photograph the diagram you drew and ask Image Summary what it shows. An explanation that does not match your intention is the cheapest proofreading available, and it is honest in a way that a friend being polite about your handwriting is not.

For which diagram type suits which question, read the diagram type guide. For the mechanics of generating and editing one, the flowchart walkthrough covers the code. For a diagram that has to carry narration, see visuals in a lesson, and for the chart beginners reach for too readily, when a pie chart is wrong.

Drawing a diagram FAQ

Where do I start when drawing a diagram?

With the thing that moves through it, not with the title. Find the subject that changes state, write its first condition in a box, then ask what happens to it next and keep going until it stops changing. Starting with the title tempts you into drawing the topic rather than a relationship, and that is how you end up with a page of labelled boxes and no arrows worth reading.

What shapes should I use in a diagram?

The smallest set that distinguishes your meanings. A rounded box for where the process begins and ends, a rectangle for a step, a diamond for a decision with labelled exits, and plain arrows for direction covers nearly everything a beginner needs. Consistency matters more than correctness: a reader learns your shapes in the first few seconds and is misled every time you break them.

Should a diagram run top to bottom or left to right?

Top to bottom when it branches, because the two sides of a decision need horizontal room to separate. Left to right when it is a long chain with few branches, because a dozen stacked boxes become a tall ribbon nobody can see at once, whereas the same steps across the page read like a timeline.

How many boxes should a diagram have?

Few enough that you can look at it once and say what it means. A diagram with forty boxes has stopped being a picture and become a document you have to search, at which point a numbered list would be easier to read and far easier to keep accurate. If the subject genuinely has forty steps, draw it as several diagrams with one box in each standing for the next.

Do I need design software to draw a diagram?

No. Paper is the best first draft because it is quick to throw away, and most diagrams are rearranged two or three times before they are right. Once the structure settles you can write it as Mermaid text and get a clean rendering you can download as SVG.

Should I label the arrows?

Label every arrow leaving a decision, always. Elsewhere label the ones whose meaning is not obvious from the boxes at each end. An unlabelled arrow quietly means and then, so if it is standing for because, unless or after about an hour, the reader will not know.

Why does my diagram look messy even though the content is right?

Usually crossing lines and uneven box sizes rather than wrong content. Crossings almost always mean two boxes are in the wrong order, so try moving a box before you try routing a line around. Long labels stretch boxes and throw the alignment out, so shorten the text instead of resizing the shape.

How do I check whether my diagram is actually clear?

Hand it to someone who has not seen it and ask them to narrate it back. If you cannot find a person, photograph it and ask Image Summary what the diagram shows; when the explanation that comes back is not the one you intended, the diagram is the problem rather than the reader.

Tools: Flowchart Answers · Video Answers · Ask Questions

Draw a diagramCheck my sketch