What a workflow chart does and why you need one

A workflow chart is a visual map of how a task or process moves from start to finish. It shows each step in order, who does what, where decisions happen, and what comes next. Instead of describing a process in paragraphs, a workflow chart uses boxes, arrows, and shapes so anyone can see the path without reading instructions.

You build a workflow chart when a process is confusing to explain in words, when multiple people need to follow the same steps, or when you need to find where things slow down or go wrong. A manager might chart how a customer complaint gets resolved. A small business owner might chart how an order moves from purchase to delivery. A team might chart how a document gets reviewed and approved.

The chart becomes a reference everyone can point to. New people learn faster. Bottlenecks become obvious. You can spot steps that don't belong or decisions that should happen earlier.

Key Takeaways

  • A workflow chart uses rectangles for actions, diamonds for decisions, and arrows to show the direction the process moves.
  • You can draw a workflow chart on paper, in a spreadsheet, or in free online tools like Lucidchart, Miro, or Google Drawings.
  • Start by listing every step in order, then decide which steps are actions, which are decisions, and where the process branches.
  • Test your chart by walking through a real example from start to finish to catch missing steps or unclear paths.
  • Keep shapes simple and labels short so the chart is easy to read at a glance.

Gather the steps before you draw anything

Before you open a drawing tool, write down every single step the process includes. Talk to the people who actually do the work. Ask them what they do first, what comes next, where they have to wait, where they make a choice, and what happens at the end.

Write each step as a short phrase: "Customer submits order", "Manager reviews request", "Item ships", "Invoice sent". Don't worry about order yet. Just capture what happens. If you skip this step, you'll draw a chart, realize you forgot something halfway through, and have to redraw it.

Once you have the list, arrange the steps in the order they actually happen. Cross out anything that doesn't belong. Combine steps that are really the same thing. This list is your outline.

Choose the right shapes for actions and decisions

Workflow charts use standard shapes so anyone can read them. A rectangle means an action or task — something someone does. A diamond means a decision point — a yes-or-no question that sends the process down different paths. A circle or oval marks the start or end. An arrow shows which direction the process moves.

Some charts add other shapes: a parallelogram for input or output (like a form or report), a cylinder for stored data, or a trapezoid for a document. For most workflows, rectangles, diamonds, circles, and arrows are enough.

Keep the shapes consistent. If you use a rectangle for "Customer submits order", use a rectangle for every other action too. If you use a diamond for "Is the order over $100?", use a diamond for every other decision. Consistency makes the chart easier to follow.

Build the chart from top to bottom or left to right

Decide whether your chart flows top to bottom (like reading a page) or left to right (like reading a timeline). Top to bottom is easier to read on a screen or printed page. Left to right works well for processes that happen over time.

Start with a circle or oval labeled "Start" at the top or left. Draw a rectangle below or to the right for the first action. Connect them with an arrow. Add the next rectangle, then the next, each connected by an arrow.

When you reach a decision, draw a diamond. Label it with a yes-or-no question. Draw two arrows leaving the diamond — one labeled "Yes" going to the next step, one labeled "No" going to a different step. Both paths eventually rejoin or lead to the end.

End with a circle or oval labeled "End". Every path in the chart should lead to the end, even if some paths take longer than others.

Tools you can use without learning software

Google Drawings is free and works in any web browser. Open Google Drive, click "Create", select "Drawing", and you'll see a blank canvas. The toolbar on the left has shapes — click the shape tool, pick a rectangle or diamond, and draw it on the canvas. Type inside the shape. Use the connector tool (looks like a line with arrows) to connect shapes. Save automatically.

Lucidchart has a free version with limited diagrams. It's designed for flowcharts, so shapes snap into place and connectors align automatically. The learning curve is slightly steeper, but the result looks more polished. You can share the chart with others and they can view it without signing up.

Miro is a free online whiteboard. It's less structured than Lucidchart but more flexible. You can draw, add shapes, write notes, and move things around easily. Good if you're building the chart with a team in real time.

Paper and pencil still work. Draw rectangles and diamonds by hand, label them, and use arrows to connect them. Take a photo when you're done. This is fastest if you're working alone and don't need to share the chart with others.

Walk through a real example to test your chart

Once you've drawn the chart, pick an actual case — a real customer order, a real complaint, a real request — and trace it through your chart from start to finish. Does every step match what actually happened? Did you miss anything? Is there a step that doesn't make sense?

If the real case doesn't follow your chart, fix the chart. If the real case branches in a way your chart doesn't show, add that branch. If a step in your chart never actually happens, remove it.

Test with at least two different examples. Different cases often follow different paths, especially if your process has multiple decision points. If both examples follow the chart without confusion, the chart is probably ready to share.

Keep labels short and the chart readable

Write action labels as short phrases: "Send invoice", "Approve request", "Update database". Don't write "The system sends an invoice to the customer after the order is confirmed and all items are in stock." That's too long and hard to read in a small box.

For decision diamonds, write the question as a yes-or-no: "Is stock available?", "Did customer approve?", "Is total over $500?". Label the arrows leaving the diamond "Yes" and "No" so it's clear which path each answer takes.

Don't cram too many steps into one chart. If the process has more than 15 or 20 steps, break it into smaller charts — one for the main process, separate ones for each decision branch. A chart that fills a screen is easier to read than one that requires scrolling.

Frequently Asked Questions

What if the process has steps that happen at the same time?

Use a shape called a "fork" or "parallel gateway" — usually two vertical lines — to show where the process splits into parallel paths. Both paths happen at the same time. Use another fork shape to show where they come back together. If your tool doesn't have this shape, you can use two rectangles side by side with arrows showing they're parallel.

Should I include every tiny detail or keep it high-level?

Start high-level. Show the main steps and decisions. Once people understand the big picture, you can create a more detailed chart for specific parts if needed. A chart with too much detail becomes hard to read and defeats the purpose.

What if the process changes depending on who's doing it?

Add a column on the left showing who does each step — "Customer", "Manager", "Warehouse", "Accounting". This is called a "swimlane" chart. Each person's steps stay in their lane, and you can see where handoffs happen between people.

Can I update the chart if the process changes?

Yes. If you used a digital tool, open the file and edit it. If you drew it on paper, redraw it or take a new photo. Share the updated version with everyone who uses the process. The chart is only useful if it matches what people actually do.

Do I need special software or can I use what I already have?

Google Drawings, Microsoft Word, or even PowerPoint can create a basic workflow chart. Specialized tools like Lucidchart make it faster and the result looks cleaner, but they're not required. Use what you have and upgrade later if you need more features.