A flowchart turns a process into a picture: boxes for steps, arrows for flow, and diamonds for decisions. It is the fastest way to explain a process to someone else, or to spot a gap in your own thinking. This guide shows you how to build one from scratch.
Learn the basic shapes
- Oval: start and end points.
- Rectangle: a step or action.
- Diamond: a decision, with one arrow in and two arrows out, usually yes and no.
- Parallelogram: an input or output, such as reading data or printing a result.
- Arrow: the direction of flow. Arrows always point forward, never backward, unless a loop returns to an earlier step.
Step-by-step: build your flowchart
- Write the process as a numbered list first. If you cannot list the steps, you do not understand the process well enough to draw it yet.
- Mark every decision point. Each one becomes a diamond with two exits.
- Draw the start oval, then add one shape per step, in order.
- Connect the shapes with arrows. Label each arrow leaving a decision with yes or no.
- Follow every path from start to end. Each path must reach an end oval; a path that dead-ends is a missing step.
- Simplify: merge duplicate steps, remove steps that change nothing, and keep labels short.
A worked example: making tea
Start: fill the kettle. Decision: is the water boiled? No arrow loops back to waiting; yes arrow moves on. Step: pour water over the tea bag. Step: wait three minutes. Decision: milk wanted? Yes adds milk, no skips it. End: serve. Even this tiny example shows the power of the method: the two decisions are exactly where a written recipe gets vague.
Common mistakes
Beginners draw flowcharts that are really just lists with arrows, with no decisions at all. Others cram whole paragraphs into each box; a box should hold a short phrase, not a sentence. The worst mistake is crossing arrows everywhere, which usually means the process needs to be split into two smaller flowcharts.
Try it the faster way
Build your flowchart in the tool below, with shapes, arrows, and export options.
Prefer the full page? Open the flowchart creator directly.
Quick tips
- One flowchart, one process. Split big processes into linked charts.
- Keep labels to five words or fewer per box.
- Walk every path before sharing; a dead-end path is a bug in your process.
A good flowchart does not just document a process. It tests it, by forcing every decision and every path out into the open.
Frequently asked questions
How detailed should a flowchart be? Detailed enough that someone else can follow it without asking you questions, but not so detailed that it becomes a manual. A good test: each box should be one action, and each decision should have exactly two exits. If a box needs a paragraph, split it into smaller steps.
What is the difference between a flowchart and a diagram? A flowchart shows a process in sequence, with decisions and loops. A diagram shows structure or relationships, such as an organization chart or a network map. Use a flowchart when order and decisions matter, and another diagram type when they do not.
When should I split a flowchart into two? When arrows start crossing heavily, when one chart covers two different processes, or when a single chart no longer fits on one screen. Linked sub-charts, where one box expands into its own flowchart, keep large processes readable.
Worked example
Map a simple decision: should you bring an umbrella? Start: check the forecast. Decision: does it predict rain? If no, end with no umbrella. If yes, decision: will you be outside long? If no, end with a small umbrella; if yes, end with a big umbrella and a raincoat. This tiny chart has two decisions and three endings, and it already shows the method’s value: every path reaches an ending, and no outcome is left vague. Real processes work the same way, just with more boxes.