How to Make a Flowchart for a Process: A 6-Step Method

Published October 7, 2026 · Updated October 7, 2026 · 8 min read · by the Sakura5 team

To make a flowchart for a process, write down the trigger that starts it and the outcome that ends it, list every step in between as a verb-first action, mark the points where someone has to make a yes-or-no decision, and then draw it top to bottom with ovals for start and end, rectangles for actions, diamonds for decisions and arrows for the flow. Everything else — colors, swimlanes, software — is polish on top of those four moves.

The hard part is almost never the drawing. It’s getting the steps right. Most bad flowcharts are bad because the person who drew them started dragging shapes before they knew what the process actually was, so the chart ends up describing how the process is supposed to work rather than how it does. The fix is to separate the thinking from the drawing.

This guide covers why flowcharts go wrong, a six-step method for building one, a full worked example of a refund process with real numbers, how to handle the messy cases like loops and handoffs, and answers to the questions people ask most often.

Why most process flowcharts go wrong

The most common failure is drawing from memory. You sit down, open a diagramming tool, and draw the process the way you think it runs. Then someone who does the work every day looks at it and points out three steps you skipped and a decision that doesn’t exist. A flowchart drawn from memory captures the official version of a process, which is rarely the real one.

The second failure is mixing levels of detail. One box says “Handle customer request” and the next says “Click Save in the CRM.” The first hides a whole sub-process; the second is a keystroke. When the boxes don’t sit at the same altitude, the chart becomes hard to read and impossible to improve, because you can’t compare steps that aren’t the same kind of thing.

The third is forgetting the unhappy paths. A process diagram that only shows what happens when everything works is a brochure, not a flowchart. The value of the exercise is in the diamonds — the places where the process branches, waits or loops back — because that’s where delays and errors live.

How to make a flowchart for a process in six steps

Budget 30 to 60 minutes for a process with 10 to 20 steps. Do the first four steps as plain lists or on a free-form canvas, and only open a diagramming tool for step five.

1. Define the boundaries

Write one line for the trigger (“Customer submits a refund request”) and one for the end state (“Refund paid and customer notified”). These become your start and end ovals. If you can’t name both, you’re mapping a vague area of work, not a process, and the chart will sprawl.

2. Brain-dump every step, in any order

List everything that happens between the trigger and the end. Don’t sequence yet and don’t filter. Ask the people who actually do the work, or read the existing checklist, email templates and tickets. It’s easier to cut steps later than to discover missing ones after the chart is drawn.

A mind map is a good container for this stage, because it lets you capture steps without committing to an order. In Mindmap AI, you can paste an existing SOP or a long description of the process and the AI (a Pro feature) builds a map of its parts in seconds, which gives you a first inventory of steps to correct rather than a blank page to fill.

3. Rewrite each step as a verb-first action

“Check order date,” “Approve refund,” “Email customer.” Not “Order date” or “Approval.” Verb-first labels force you to say what actually happens, and they quickly expose steps that are really two actions glued together. Split those. Then check the altitude: every box should be roughly the same size of task.

4. Put the steps in order and find the decisions

Arrange the actions in sequence. Wherever the next step depends on an answer, insert a decision phrased as a yes-or-no question: “Within 30 days?” “Amount over $200?” Each decision gets exactly two exits. If you find yourself wanting three, it’s usually two decisions in a row. Switching a map to an outline view is a quick way to see the ordered list at this point — in Mindmap AI the outline view shows the same nodes as a collapsible, ordered list you can check against the real process.

5. Draw it with the standard symbols

Now open the diagramming tool. Use the four basic shapes and nothing more unless you need it: oval for start and end, rectangle for an action, diamond for a decision, arrow for flow. Lay it out top to bottom or left to right, keep arrows from crossing where you can, and label every arrow leaving a diamond with “Yes” or “No.” The American Society for Quality has a concise reference on flowchart symbols and when to use them if you need the less common shapes.

6. Walk it with someone who does the work

Take one real recent case and trace it through the chart, box by box. Every time the case does something the chart doesn’t show, fix the chart. Then trace a second case that went wrong. Two walkthroughs usually catch most of what a first draft misses.

A worked example: flowcharting a refund process

Say you run support for a small online store and refunds keep getting stuck. The current “process” lives in one person’s head and a shared inbox. Here’s how the six steps play out.

Boundaries. Start: “Customer emails asking for a refund.” End: “Refund issued and customer emailed confirmation” — plus a second end state you only notice when you ask: “Request declined and customer told why.” Two end ovals is fine.

Brain-dump. Talking to the support lead produces 14 items: find the order, check the date, check whether the item shipped, ask for photos if damaged, get manager approval over a limit, issue the refund in the payment dashboard, update the order status, send the confirmation, and so on. Two of them turn out to be the same step described differently, leaving 12.

Decisions. Ordering the steps surfaces four decisions: “Order found?” “Within 30 days of delivery?” “Item damaged?” and “Refund over $200?” The last one matters most. Anything over $200 waits for the manager, and the manager checks the inbox twice a week — which is exactly why refunds were stalling.

Drawing. The finished chart has 2 start/end ovals, 9 action boxes and 4 diamonds. The “Order found? No” branch loops back to “Ask customer for order number.” The “Within 30 days? No” branch goes straight to the decline end state.

Walkthrough. Tracing last week’s stuck $240 refund through the chart shows it sat at the manager-approval box for four days. That one diamond is the bottleneck, and now it’s visible on a single page. The improvement — raising the threshold, or adding a second approver — becomes an obvious conversation instead of a vague complaint that “refunds are slow.”

Loops, handoffs and other tricky parts

Loops. When a step can repeat — resubmit the form, ask for more information — draw the arrow back to the earlier box rather than redrawing the steps. Put a limit on the loop in the decision label if one exists, like “Fewer than 3 attempts?”, so the chart shows how the loop ends.

Handoffs between people. If the process crosses teams, use swimlanes: one horizontal or vertical band per role, with each box placed in the lane of whoever does it. Every arrow that crosses a lane line is a handoff, and handoffs are where work waits. In the refund example, the support-to-manager crossing is the slow one.

Too many steps. If the chart passes about 25 boxes, it’s probably two processes or one process at too fine a level. Collapse a cluster of steps into a single box labelled as a sub-process and give it its own chart. Keep each page readable at a glance.

Not sure if you need a flowchart at all. If the content has no order — you’re grouping ideas, not sequencing actions — a map is the better tool. Our explainer on what a mind map looks like covers the difference, and if you’re still working out the scope of the work rather than a repeatable process, start with mind mapping for project planning and come back to the flowchart once the steps are known. For the steps-first stage, Mindmap AI on iPhone, iPad and Mac is a quick place to dump and reorder them before you draw.

FAQ

What are the basic steps to make a flowchart for a process?

Define the trigger and end state, list every step between them, rewrite each step as a verb-first action, put them in order, and insert yes-or-no decisions where the path splits. Then draw it with ovals for start and end, rectangles for actions, diamonds for decisions and labelled arrows, and test it against a real case.

What symbols do I need for a simple process flowchart?

Four cover nearly every process: an oval for start and end, a rectangle for each action, a diamond for a yes-or-no decision, and arrows to show the direction of flow. Add a parallelogram for inputs or outputs and swimlanes for multiple roles only when the process genuinely needs them.

How detailed should a process flowchart be?

Detailed enough that someone new could follow it, with every box at roughly the same level of task. If one box is a whole department’s job and the next is a single click, rebalance them. Past about 25 boxes, split the chart into a main flow and separate sub-process charts.

Can I use a mind map to plan a flowchart?

Yes, for the early stage. A mind map is good for capturing every step without committing to an order, which is exactly what you need before drawing. Once the steps are complete, convert the map to an ordered outline, add decisions, and then draw the flowchart from that list.

← All articles