How much detail belongs in a flowchart?
How much detail belongs in a flowchart? Pick the reader and the decision first, watch for signs of too much or too little, and move the rest to a sub-process.
Ask five people to flowchart the same incident response process and you get five levels of detail, each defended as correct. None of them is correct until you know who is going to read it.
Quick AnswerA flowchart needs enough detail for one named reader to make one decision, and no more. Show a step if it changes what that reader does next. Move the rest into a sub-process or another diagram. If the chart can’t fit on a screen at a readable zoom, it is doing too much.
Pick the reader and the decision first
“How much detail?” has no answer until you can finish this sentence: this chart helps a particular person decide a particular thing. Take that incident process and three readers.
- The on-call engineer at 3 a.m. has to decide what to do next. They need every decision, the thresholds and who to call. Literal steps are a kindness here, because nobody is thinking clearly.
- Alex Morgan, as head of engineering, has to decide whether escalation has gaps. Alex needs the stages, the points where severity changes who gets involved, and who owns each one. Individual commands would only get in the way.
- A new support agent has to decide when to pass a problem to engineering. They need their own part in full. Everything after the handoff can be one box: “Engineering takes over”.
That makes three honest charts of one process, and each would be wrong for the other two readers.
When you are unsure about a box, ask whether removing it would change what the reader does next. If not, it goes. Our working rule is that a step earns its own box only if it branches, moves work to another person or takes real time. Anything else can fold into the step before it.
When you are really torn, start with less. A reader’s question tells you exactly what was missing, while nobody reports the boxes they skipped. If you are starting from a blank page, the flowchart guide covers the symbols and the method.
Signs of too much detail in a flowchart
- You have to zoom out until the labels are unreadable to see the whole chart.
- There are long runs of boxes with no decision and no change of person. “Open ticket, click refund, enter amount, confirm” is one step: “Issue refund”.
- Labels describe the interface (“Click the blue button”), so the chart breaks with every redesign.
- A case that comes up twice a year takes as much room as the path you follow every day.
- People ask you for “the simple version”.
Signs of too little detail
- The chart is a straight line. Real processes branch, so the hard part is hidden inside one of those boxes.
- Boxes use vague verbs: “Handle request”, “Process refund”, “Review”. Two readers would do two different things.
- A decision has only one exit, or failures have nowhere to go.
- Several teams are involved and you can’t see who does which step.
- After reading it, the person still has to ask someone what to do.
The last one is the surest sign and the easiest to test. Hand the chart to the reader, say nothing, and watch where they stop. Add what they needed there, and nothing else.
Move detail instead of deleting it
Detail you cut from a chart usually still matters to somebody. It needs a better address, and there are three.
A sub-process. Fold a group of steps into one box in the main chart and draw the inside separately. Flowcharts have a symbol for this: the predefined process, a rectangle with an extra line down each side. A group is ready to fold when it has one way in, one way out and can be named in a few words.
Take an incident chart where triage has grown to nine boxes: read the alert, rule out a false alarm, find the affected service, and so on. In the main chart those become one box, “Triage”, followed by a diamond, “Customers affected?“. The nine boxes move to their own chart for the on-call engineer, who is the only person who needs them.
Another diagram. Some detail is a different kind of detail. If you keep adding team names, you may want a swimlane. If arrows are picking up API calls, you want a sequence diagram. Each of those is a different question, and it deserves its own picture.
A note or a spec. Thresholds, policy wording and reasons don’t belong in boxes. A short annotation beside the shape can hold one number. Anything longer goes in the written spec, with the diamond’s exact words as its heading.
In FlowDraw, the Flowchart library has “Predefined process” and “Annotation” cells, and a frame for each sub-process keeps the overview and its parts on one board. “Export” can then take any frame as its own file, so the on-call engineer gets the triage chart alone. One limit to plan for: there is no way to add a link to a shape, so the label has to do the directing. Write the target’s name in the box, such as “Triage (see Triage frame)“.
A chart that keeps growing is usually a sign that its readers have changed. If the on-call engineer’s runbook now also has to satisfy an auditor, that is two readers and two decisions, so draw a second chart.
FAQ
No number holds for every reader. Test it instead: the whole chart should fit on one screen with the labels still readable, and your reader should be able to follow it without asking anyone. If it fails the first test, fold a group of steps into a sub-process.


