Process Mapping: How to Map a Business Process in 6 Steps
How to map a business process step by step, which kind of process map to use, an example, and the mistakes that make a process map useless.
Process mapping is drawing one piece of work from the event that starts it to the result it produces: the steps in order, the decisions, and who does each part. To map a process, pick one process with a clear start and end, list its steps with the people who do them, draw the steps and decisions in order, then walk through the map with those people and correct it.
The six steps below work on paper, on a whiteboard or in any diagram tool.
What a process map is, and which kind to draw
A process map is any picture of how work flows. Three kinds cover almost every need:
| Kind | Shows | Use it when |
|---|---|---|
| Process flowchart | Steps and decisions in order | One person or one team does the work |
| Swimlane diagram (cross-functional flowchart) | The same, divided into a lane for each role | Work passes between people or teams |
| High-level map | Five to seven big steps, no decisions | You need to agree on scope before the detail |
If you are unsure, start with a flowchart and add lanes when the question becomes "who does this?".
Step 1: Pick one process and its boundaries
Name the process by its result ("pay a supplier invoice", not "finance"). Then write down two things: the event that starts it and the result that ends it. "An invoice arrives by email" and "the supplier is paid and the invoice is filed" are boundaries; "invoicing" is not.
A map without boundaries grows until nobody can read it.
Step 2: List the steps with the people who do them
Ask the people who do the work, not the person who designed it. Write each step as a verb and a thing: "Check the invoice against the order", "Approve the payment". Beside each step, write who does it.
Collect what really happens, including the workarounds. If a manager approves by replying to a chat message, that is the step.
Step 3: Put the steps in order and find the decisions
Arrange the steps from the start event to the end result. Wherever the next step depends on something, you have a decision. Write it as a question with a short answer: "Does the invoice match the order?".
Every decision needs a line for each answer. The answer people forget is the unwelcome one: the invoice does not match, the approver is on holiday, the customer does not reply. Those branches are where the real process lives.
Step 4: Draw it
Use the same few shapes throughout:
- A rounded shape for the start and for each end.
- A rectangle for a step.
- A diamond for a decision, with a label on each line that leaves it.
- An arrow for "then".
Keep the main path in a straight line, top to bottom or left to right, and let the exceptions branch off to the side. If work passes between people, divide the page into lanes and put each step in the lane of whoever does it.
You can describe the process to VamimiAI's process flowchart maker and get this drawing made for you, with the lanes if you name the roles.
Step 5: Walk through it with the people who do the work
Take one real case from last week and follow it through the map, step by step. Then take a case that went wrong. Each time the map and the story disagree, the map is what you change.
This review is the point of the exercise. People who have worked side by side for years often find they describe the same process differently.
Step 6: Mark what to fix, then keep the map alive
With an accurate map, look for:
- Hand-offs. Every line that crosses from one lane to another is a place where work waits.
- Loops. A step that sends work back ("return for correction") shows where information was missing earlier.
- Decisions with no owner. If nobody can say who decides, the decision is being made by whoever is least busy.
- Steps nobody can explain. Ask what would break if the step were removed.
Give the map an owner and a date. When the process changes, change the map the same day, or it becomes a picture of how things used to work.
A process mapping example
Take a purchase request as an illustration. The start event is an employee needing something; the end result is a paid invoice. Suppose that drawing it shows the manager approving before anyone checks the budget, so finance sometimes refuses an approved request and the requester starts again. Moving the budget check before the approval removes that loop. Nobody had noticed it, because each person saw only their own part.
The swimlane diagram maker page has a similar example with one lane for each role.
Mistakes that make a process map useless
- Mapping the process as it should be. Map what happens now first. The improved version is a second map.
- Too much on one page. If a step needs its own flowchart, give it one and keep a single box for it here.
- Only the path that goes well. A map with no refusals, errors or delays describes a process that exists only on good days.
- Vague step names. "Processing" tells the reader nothing. Use a verb and a thing.
Questions
What is process mapping?
Process mapping is drawing a process from its start to its end, showing the steps in order, the decisions and who does each part, so that everyone involved sees the same picture of the work.
What is the difference between a process map and a flowchart?
A process map is the general term for a picture of how work flows. A flowchart is the most common form of process map. A swimlane diagram is a flowchart divided into lanes, one for each person or team.
How detailed should a process map be?
Detailed enough that a new person could follow it, and no more. If the map does not fit on one page, split it: keep one box for the sub-process and draw that sub-process on its own page.
Who should be involved in mapping a process?
The people who do the work every day, plus whoever receives the result. A map drawn by a manager alone usually shows the designed process, not the real one.
How often should a process map be updated?
Whenever the process changes. In practice, give the map an owner and review it when a step, a tool or a role changes, and at least once a year.