What a workflow chart actually is
A workflow chart is a visual map of the steps in a process, drawn so anyone can see what happens, in what order, and who is responsible at each stage. It uses boxes for tasks, diamonds for decisions, and arrows to show the direction work moves. The point is to make a messy, invisible process visible — so you can spot where things slow down, where people get confused, or where a step is missing entirely.
Workflow charts are not the same as to-do lists or timelines. A to-do list tells you what needs doing. A workflow chart tells you how work actually flows from one person or department to another, what triggers each step, and what happens when something goes wrong. You might use one to document how your team onboards new hires, how a customer order moves from sales to shipping, or how a document gets reviewed and approved.
The simplest workflow charts use five basic shapes: rectangles for regular tasks, diamonds for yes-or-no decisions, circles for start and end points, parallelograms for input or output (like a form or email), and arrows showing which direction the work moves next.
Key Takeaways
- A workflow chart maps the actual sequence of tasks in a process, showing who does each step and what triggers the next one.
- Start by listing every step in the process as it actually happens now, including decisions and waiting periods, not how you wish it worked.
- Use rectangles for tasks, diamonds for decisions, and arrows to show the direction work moves; keep labels short and specific.
- Draw the chart on paper first or use free tools like Lucidchart, Draw.io, or even PowerPoint before sharing it with your team.
- Test your chart by walking through a real example from start to finish to catch missing steps or unclear handoffs between people.
Gather the actual steps, not the ideal ones
Before you draw anything, write down every single step that happens in the process right now — not the way the manual says it should work, but the way it actually works. Talk to the people who do the work. Ask them what they do first, what they wait for, what they do when something is wrong, and what they hand off to someone else. Write it all down in order.
Include the things that look like delays or workarounds. If someone always has to email a manager for approval before moving forward, write that down. If a form sometimes gets lost and someone has to track it down, write that down. If a task only happens on Tuesdays because that is when someone is in the office, write that down. These are not failures — they are the real process, and your chart should show them.
Group related steps together and number them so you do not lose track. You might end up with 8 steps, or 20. The length does not matter. What matters is that you have captured the actual sequence, including all the decision points where the path splits.
Identify where decisions split the path
As you list your steps, mark the places where the process branches — where the answer to a question determines what happens next. These are your decision points, and they become diamonds on your chart. Common decision points include: Is the request approved? Does the item meet our standards? Is the customer a repeat buyer? Has the important date passed?
For each decision, write down both paths clearly. What happens if the answer is yes? What happens if the answer is no? Sometimes one path loops back to an earlier step. Sometimes one path ends the process early. Sometimes both paths rejoin later. All of these are normal and should be shown on your chart.
If you have more than three or four decision points, your process may be too complicated to show on a single chart. That is useful information on its own — it tells you the process is hard to follow and might need simplifying.
Choose a tool and draw the basic structure
You can draw a workflow chart on paper with a pen and ruler, and many people do exactly that as a first draft. If you want a digital version, free tools include Draw.io (web-based, no account needed), Lucidchart (free tier with limits), and PowerPoint (if you already have it). Google Slides also works. None of these require special training.
Start at the top or left side with a circle or oval labeled "Start". Draw a rectangle below it for your first task. Connect them with an arrow pointing downward. Add the next task in another rectangle below that. When you reach a decision point, switch to a diamond shape, label it with a yes-or-no question, and draw two arrows leaving it — one for yes, one for no. Each arrow leads to the next task or decision.
Keep labels short and specific. Instead of "Process order", write "Check inventory". Instead of "Review", write "Manager approves budget". The person reading your chart should know exactly what happens at each step without having to guess.
Show who is responsible at each step
Once the basic flow is drawn, add information about who does each task. You can do this by color-coding the boxes — one color for sales, one for accounting, one for shipping — or by writing the person's name or role inside or next to each box. Some people add a column on the left showing which department owns each step.
This matters because it shows where handoffs happen — where work moves from one person or team to another. Handoffs are where things often get lost or delayed. If your chart shows that a task moves from person A to person B to person C in a chain, you can see that three handoffs are happening. If you can reduce that to two, the process gets faster.
If a task happens in parallel — meaning two people work on different parts at the same time — show that with arrows that split and then rejoin. This is common in larger processes where one person is gathering information while another person is preparing a document.
Test your chart against a real example
Walk through your chart using an actual case from your work. Start at the beginning and follow every arrow, every decision, every handoff. Does the chart match what actually happened? If not, fix it. If a step is missing, add it. If a decision point is unclear, reword it.
The best test is to give your chart to someone who does the work and ask them to follow it. If they get confused or find a step that is not there, you have found a problem with the chart — or a problem with the process itself. Either way, you have learned something useful.
Once your chart matches reality, share it with your team. Ask them to mark anything that is wrong or missing. A workflow chart is not a one-time document — it changes as your process changes. Keep it somewhere your team can find it and update it when you change how work flows.
Common shapes and what they mean
| Shape | What it represents | When to use it |
|---|---|---|
| Circle or oval | Start or end point | Mark the beginning and end of your process |
| Rectangle | A task or action | Someone does something: "Send invoice", "Update spreadsheet", "Call customer" |
| Diamond | A decision | A yes-or-no question that splits the path: "Is it approved?", "Does it pass inspection?" |
| Parallelogram | Input or output | A form arrives, a report is generated, an email is sent |
| Arrow | Direction of flow | Shows which step comes next and which way the work moves |
Frequently Asked Questions
Do I need special software to make a workflow chart?
No. Paper and pencil work fine for a first draft. For digital versions, Draw.io and Google Slides are free and require no training. PowerPoint also works if you already have it. Lucidchart has a free tier but with limits on how many charts you can make.
What if my process has too many steps to fit on one page?
Break it into smaller sub-processes. For example, instead of showing every step in "Customer onboarding", create one chart for "Initial signup", another for "Background check", and another for "First day orientation". Link them together so people know how they connect.
Should I include time estimates on my workflow chart?
You can, but it is not required. If you add timing, write it next to each task — for example, "Review process (2 days)" or "Ship order (1 day)". This helps people see where delays happen, but it makes the chart busier and harder to read at a glance.
What if the same task happens in multiple places in the process?
That is normal. Draw it each time it happens. If it happens many times, that might be a sign the process could be simplified. But show it as it actually is, not as you wish it were.
Can I use a workflow chart to train new employees?
Yes. A clear workflow chart is one of the best training tools because it shows the whole process at once and explains how each person's work connects to everyone else's. Print it out or share it digitally, and walk new hires through it step by step using real examples from their first week.