A flow chart is one of the original 7 QC tools, and it’s still the fastest way to make any process visible, repeatable, and easy to improve. This guide covers what it is, every standard symbol, how to draw one correctly, and how it fits alongside the other six quality tools.
What Is a Flow Chart?
A flow chart is a diagram that maps out a process step by step, using standardized shapes connected by arrows to show the exact sequence of actions, decisions, and outcomes. It’s one of the 7 QC tools — the core toolkit used in quality management, Six Sigma, and Lean manufacturing to visualize, measure, and improve a process.
Unlike a written procedure, a flow chart lets someone unfamiliar with a process understand it in seconds: where it starts, every decision it depends on, and every way it can end. That’s why it’s usually the first tool a quality team reaches for before applying any of the other six.
Where the Flow Chart Fits Among the 7 QC Tools
The 7 QC tools (sometimes called the 7 basic quality tools) were popularized by Kaoru Ishikawa as a simple, visual toolkit any team member could use — no statistics degree required. They are:
Flow Chart — maps the steps of a process
Cause-and-Effect Diagram (Fishbone / Ishikawa) — identifies the root causes of a problem
Check Sheet — a structured form for collecting data as events happen
Control Chart — tracks a process over time to spot unusual variation
Histogram — shows the distribution of a data set
Pareto Chart — ranks causes by frequency to find the “vital few”
Scatter Diagram — shows the relationship between two variables
The flow chart usually comes first for a reason: you generally can’t fix, measure, or find the root cause of a problem in a process you haven’t actually mapped out yet. A clear flow chart is what makes the other six tools point at the right target.
Flow Chart Symbols and What They Mean
Flow chart symbols follow ISO 5807:1985 — Information processing — Documentation symbols and conventions for data, program and system flowcharts — the international standard behind the shapes almost every diagramming tool uses today, descended from the same tradition as the American standard ANSI X3.5 / Y32.14.
Sticking to these standard symbols — instead of inventing your own — is what makes a flow chart readable by any trained reader, not just the person who drew it.
How to Read a Flow Chart in 5 Steps
Find the Start terminator — that’s your entry point.
Follow the arrows in the direction they point (top-to-bottom or left-to-right).
At every diamond, answer the question it asks and follow the arrow that matches your answer.
Repeat until you reach an End terminator.
If a diagram has more than one End, each one is a distinct, valid outcome of the process — not a mistake.
How to Draw a Flow Chart Step by Step
Write your steps as a plain list first — on paper is fine. Inventing the process while drawing it is what causes messy, backtracked diagrams.
Identify every start and end point — a process can have one start but several valid endings.
Mark every decision point — anywhere the next step depends on an answer becomes a Decision diamond.
Place your Start terminator, then add a Process box for every action, in order.
Add Decision diamonds for branching logic, phrased as a real question (“Approved?” not “Check approval”).
Connect every shape with arrows, labeling each branch out of a decision (Yes / No, or the specific condition).
Add an End terminator for every distinct outcome.
Review it start to finish — confirm there’s exactly one entry point, no dangling arrows, and every decision has at least two labeled ways out.
Flow Chart Best Practices
One clear start, one or more clearly-marked ends — never leave a path hanging.
Consistent flow direction — top-to-bottom or left-to-right; avoid mixing both in the same diagram.
Short, action-based labels — a verb and an object (“Verify payment”), not a full sentence.
Minimize crossing lines — rearrange shapes before resorting to a long detour.
Use color with intent — highlight the critical path or group related steps, not for variety’s sake.
One shape, one meaning — don’t reuse a Process box to represent a decision because it’s quicker to place.
Flow Chart vs. the Other 7 QC Tools — When to Use Which
In practice, teams often use two or three of these together: a flow chart to map the process, a check sheet to collect data at the point where a defect happens, and a Pareto chart to decide what to fix first.
Common Flow Chart Mistakes to Avoid
Two arrows leaving a Process box with no Decision diamond — branching without a stated question is ambiguous.
A Decision with only one way out — if there’s truly one outcome, it isn’t a decision.
A missing End — an arrow trailing off into nothing reads as an error, not an ending.
Vague labels — “Process” or “Check” tell the reader nothing; name the actual action.
Non-standard symbols — inventing your own shapes defeats the entire purpose of a standard.
Free Flow Chart Tools You Can Use Today
You don’t need expensive software to build a standards-compliant flow chart. Look for a tool that:
Uses real ISO 5807 symbols, not generic boxes
Lets you build from a typed list or a spreadsheet, not just drag-and-drop
Exports to PNG, PDF, and PowerPoint for sharing across a team
Runs entirely in your browser, with nothing to install
Try Flowchart free →
FAQ
Is a flow chart one of the 7 QC tools?
Yes. The flow chart is the first of the seven basic quality control tools, alongside the cause-and-effect diagram, check sheet, control chart, histogram, Pareto chart, and scatter diagram.
What is the standard for flow chart symbols?
ISO 5807:1985 is the international standard for flow chart symbols and conventions, closely related to the American ANSI X3.5 / Y32.14 standard.
What’s the difference between a flow chart and a process map?
They’re often used interchangeably. In practice, “flow chart” usually refers to the standard-symbol diagram described here, while “process map” sometimes includes broader techniques like swimlane diagrams that also show who performs each step.
Can a flow chart have more than one ending?
Yes — and it should, if the process genuinely has more than one valid outcome. Merging unrelated outcomes into a single End terminator hides real information from the reader.
Building your own? Try FlowChart free — draw a standards-compliant flow chart from a typed list, a plain-language description, or a spreadsheet upload, then export straight to PNG, PDF, or PowerPoint.
