One diagram, one question: a rule for clearer visuals
The clearest diagrams answer one question. Learn the one diagram, one question rule and how to split a checkout diagram that is doing three jobs.
When a diagram confuses people, the usual fix is more labels or a tidier layout. More often the trouble is that it is answering several questions at once, and no layout rescues that.
Quick AnswerThe clearest diagrams answer one question, and you can write that question at the top. One diagram, one question means drawing the same process more than once when people ask different things about it: what can happen, who does it, which system talks to which. Split any diagram doing more.
Why one diagram should answer one question
A page gives you two directions to work with. A flowchart spends them on order and branching. A swimlane spends one of them on who. Once those are used, everything else has to travel as decoration: colors, dashed lines, notes on arrows, a legend in the corner.
Every reader then pays for questions they did not ask. A support lead looking for who picks up a failed payment has to read past the API calls. An engineer tracing those calls has to read past the team colors. Both give up and ask a colleague, which is what the diagram was meant to prevent.
People object that they want everything in one place. One place is fine. A single board can hold several diagrams side by side, and the rule applies to each diagram, not to the board.
A checkout diagram doing three jobs
Say Alex Morgan draws the checkout for a review. It starts as a clean flowchart: review cart, shipping details, payment, a check on whether the payment is valid, create order, email receipt.
Then the questions arrive. Support asks who deals with a failed payment, so Alex colors the boxes by team. An engineer asks what calls the payment provider, so the arrows pick up labels like POST /charges. Finance asks where the order is stored, and a database appears with dashed lines running to it. By the third review there is a legend, three line styles and a diagram nobody can follow from start to end.
The fix is three diagrams, each with its question written at the top.
What can happen to the customer at checkout?
Use a flowchart. Keep every step the customer experiences and every way it can fail: card declined, address rejected, the retry limit reached. Drop the team colors and the API calls. A product manager or a new support agent can read this one without help.
Who deals with a failed payment?
Use a swimlane with lanes for the customer, support and billing. Only the failure path needs drawing. The whole happy path shrinks to one box, because nobody asking this question cares about it.
Which systems talk when the card is charged?
Use a sequence diagram with the browser, the API, the payment provider and the database as participants, and the messages in order. The engineer gets what they came for, including what comes back when the provider times out.
Finance’s question about storage would be a fourth diagram, an ER diagram of orders and payments. We would wait until someone asks it twice before drawing that one.
How to split a diagram that does too much
List the questions people ask about it
Read the comments, and ask the last few people who opened it. Write each one as a full sentence with a question mark. “Payments” is a topic. “Who deals with a failed payment?” is a question.
Cross out the ones nobody needs answered
Every question left needs a person behind it. If you can’t name who would ask, remove it.
Match each question to a form
Order and branches call for a flowchart. Who does what calls for a swimlane. Messages between systems call for a sequence diagram, and how data relates calls for an ER diagram.
Copy the original, then delete
Make one copy per question and remove everything that doesn’t answer it. This is faster than redrawing, and the names stay identical across diagrams.
Write the question at the top
If you can’t phrase it as one question, the diagram still has more to lose.
On a FlowDraw board, each diagram can sit in its own frame, with the question as the frame’s title: double-click the title to rename it. Copying a frame brings its contents along, “Present” shows one frame at a time, and “Export” can take any frame as its own file under “Page”.
When to stop splitting
Splitting has a real cost. Three diagrams need three updates when the checkout changes, and a diagram nobody maintains goes stale. So the rule cuts both ways: draw a diagram only for a question someone really asks, and merge two diagrams when they have the same reader making the same decision.
Some diagrams look as if they break the rule and don’t. A swimlane shows both who and when, yet “who does what, in what order?” is one question, and readers hold it as one. The test we use is whether a reader can say what the diagram is for in a single sentence, without “and also”.
Be wary of the opposite failure as well. A team that splits by habit ends up with six small diagrams that each need the others to make sense, and readers lose the thread moving between them. If the people using these diagrams keep opening two of them together, that is a sign the pair was one question after all.


