How to Make a Work Flow Chart: A 7-Step Method

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

To make a work flow chart, pick one piece of work with a clear start and finish, list every person or team who touches it, write each step as a short verb-first action, and draw the steps in columns or lanes — one lane per person — with arrows showing where the work moves and diamonds where someone has to decide. The lanes are what make it a workflow chart rather than a plain flowchart: they show who does what, and where the work changes hands.

That handoff view is the whole point. Most work doesn’t slow down inside a single task. It slows down in the gap between one person finishing and the next person noticing, and a chart without lanes hides those gaps completely.

Below: why most workflow charts end up decorative, a seven-step method, a worked example with real numbers, how to handle loops and parallel work, and short answers to common questions.

Why most workflow charts never get used

The first problem is drawing the ideal instead of the real. Someone senior sits down and charts the workflow the way it was designed two years ago. The people doing the work glance at it, recognise almost none of it, and keep working the way they always have.

The second problem is leaving out the people. A process flowchart can get away with a single column of boxes, because it describes what happens. A workflow chart has to describe who makes it happen. When every box floats in one column, you can’t see that the same person approves three separate steps, or that the work bounces between two teams four times before it ships.

The third is charting too much at once. “Our marketing workflow” is not a workflow; it’s a department. Pick one repeating unit of work — one blog post, one invoice, one new hire — and chart that. You can always chart the next one later.

How to make a work flow chart in seven steps

Budget about an hour for a workflow with three to five people and 10 to 20 steps. Do the first four steps as plain lists or on a free-form canvas, and only start drawing at step five.

1. Name the unit of work and its boundaries

Write one line for the trigger and one for the finish. “Writer gets a topic assigned” and “Post is live and shared.” If you can’t name both in a sentence, the scope is too wide. Narrow it until you can.

2. List every role that touches the work

Use roles, not names, unless the team is tiny: writer, editor, designer, approver. Include outside parties if the work waits on them — a client, a legal reviewer, a vendor. Each role becomes a lane. Three to six lanes is comfortable; more than seven usually means you’ve combined two workflows.

3. Brain-dump every step, in any order

Ask the people who do the work to list what they actually do, including the small steps they consider too obvious to mention, like “chase the approver on Slack.” Those are often where the time goes. Don’t sequence anything yet.

A mind map is a good container for this stage because you can group steps by role without committing to an order. In Mindmap AI you can paste a rough description of the workflow, or an existing checklist, and with Pro the AI builds a first map of its parts in seconds. Make each role a branch and hang its steps underneath, then correct what the AI got wrong.

4. Rewrite steps as verb-first actions and put them in order

“Draft post,” “Review draft,” “Request images.” Verb-first labels expose steps that are really two actions glued together — split those. Then order them. Switching the map to its outline view helps here: Mindmap AI shows the same nodes as a collapsible, ordered list, which is easier to sequence than a radial map.

5. Draw the lanes, then place the steps

Draw one horizontal or vertical lane per role. Place each step in the lane of whoever does it, in time order from left to right or top to bottom. Use the standard shapes: oval for start and finish, rectangle for an action, diamond for a decision. If you need a refresher, our guide to flowchart symbols and their meanings covers the full set, and the American Society for Quality has a concise reference on flowcharts and when to use them.

6. Draw the arrows and mark every handoff

Connect the steps. Every arrow that crosses from one lane into another is a handoff, and handoffs are where work waits. Mark each one. Label every arrow leaving a diamond with “Yes” or “No,” and make sure each diamond has exactly two exits.

7. Walk a real recent case through it

Take one piece of work that finished last week and trace it box by box. Note how long it sat at each handoff. Wherever the real case did something the chart doesn’t show, fix the chart.

A worked example: a four-person team’s blog workflow

Maya leads content at a small software company. Her team publishes two blog posts a week, and posts keep landing days late. Nobody can say exactly why. She decides to chart the workflow for one post.

Boundaries. Start: “Topic assigned in the content tracker.” Finish: “Post published and shared in the newsletter.”

Lanes. Writer, editor, designer and product lead — the product lead signs off on anything that describes a feature. Four lanes.

Steps. The brain-dump produces 16 items. Two turn out to be duplicates (“send to editor” and “move card to Review” are the same action), leaving 14: draft, self-edit, submit, edit, return with comments, revise, request images, create images, check feature claims, approve, format in the CMS, schedule, publish, add to newsletter.

Decisions. Ordering the steps surfaces two diamonds: “Edit needs changes?” after the editor’s pass, and “Mentions a feature?” before publishing. The second one only routes to the product lead when it’s a Yes — about half the posts.

Handoffs. Drawing the arrows shows nine lane crossings for a post that mentions a feature, and seven for one that doesn’t.

Walkthrough. Maya traces last Tuesday’s post. Writing took one day, editing one, images one. The product-lead review took four days, because the product lead only clears that queue on Fridays. The chart makes the problem obvious: a single diamond sends half the posts into a lane that moves once a week. The fix isn’t to work faster. It’s to move the “Mentions a feature?” check to the topic stage, so the product lead reviews the outline on day one instead of the finished draft on day four.

The revised chart has the same 14 steps in a different order, with the feature check running alongside drafting.

Handling loops, parallel steps and exceptions

Real workflows rarely run in a straight line. A few patterns cover most of the mess.

• Loops. When work goes back for revision, draw the “No” arrow from the decision diamond back to the step that gets redone. Add a note if there’s a limit, such as “max two rounds, then escalate.” A loop with no exit is a workflow that can run forever.
• Parallel work. If two lanes work at the same time — the designer makes images while the editor edits — split the arrow into two and join them again before the next step that needs both. Make the join explicit, or someone will publish without images.
• Waiting. If work routinely waits on a schedule, like a weekly meeting, put that wait in a box: “Wait for Friday review.” It feels odd to chart doing nothing, but it’s often the most important box on the page.

If the workflow is mostly one person working through decisions rather than work passing between people, you probably want a plain process chart instead. Our guide on how to make a flowchart for a process walks through that version step by step.

Keeping the chart alive after the first draft

A workflow chart starts going stale the week you finish it. Three habits keep it honest.

Put a date and an owner on the chart so it’s clear who updates it. Re-walk one real case every quarter, or whenever someone says “that’s not how we do it anymore.” And keep the source material — the brain-dump and the step list — somewhere editable, so updating the chart means changing a few nodes rather than redrawing from memory. Keeping that source as a map in Mindmap AI works well for this, since it syncs across your iPhone, iPad and Mac through iCloud and you can export the outline as a PDF to hand to whoever redraws the final chart.

FAQ

What is the difference between a workflow chart and a flowchart?

A flowchart shows the steps and decisions in a process. A workflow chart is a flowchart that also shows who does each step, usually by placing steps in lanes, one per person or team. The lanes make handoffs visible, which is where most delays happen when work passes between people.

What symbols do you use in a work flow chart?

Most workflow charts need only four: an oval for the start and finish, a rectangle for each action, a diamond for each yes-or-no decision, and arrows for the direction of work. Add lanes to show who owns each step. Use specialised symbols only if your readers already know them.

Can I make a workflow chart in Word or Excel?

Yes. Both have shape tools, and you can draw lanes as long rectangles or table rows, then place the steps inside them. It works fine for small workflows. For anything over about 20 steps, a dedicated diagramming tool makes moving shapes and rerouting arrows much less painful.

How detailed should a workflow chart be?

Detailed enough that a new team member could follow the work from start to finish, and no more. Each box should be a task of roughly the same size. If one box says “Handle request” and the next says “Click save,” split the first or merge the second until they match.

← All articles