Process mapping for small business: a step-by-step guide

Process mapping means drawing how work moves through your business: who does what, in what order, with which tools. You do not need special software or a big project. For a small business, the steps are:

1. Pick one process and set its start and end.
2. Interview the people who do the work.
3. Draw a swimlane map of what happens now.
4. Mark handoffs, waiting time and rework.
5. Agree the fixes in a short workshop.

This guide covers each step, with a worked example and a 60-minute workshop agenda.

What a process map is for

A map is a tool for finding problems, not a document for its own sake. Use it to answer three questions:

• What really happens between the trigger and the finished result?
• Where does work wait, bounce back or get done twice?
• Which steps could be removed, simplified, documented or automated?

If a map does not lead to a decision, it was too detailed or too early. A single page is often enough.

Process map, SOP and workflow: what is the difference?

• A process map shows how work flows across people and systems. It is for finding problems.
• An SOP tells one person how to do one task. See how to write an SOP.
• A workflow is the same flow set up in a tool, often with some automation.

Map first when the work crosses teams. Write SOPs for the steps that need them.

Step 1: Pick one process and set its edges

Start with one process, not the whole company. Good first choices cross teams and cause complaints: quote to cash, order to delivery, hire to first day, support request to resolution. A process that depends on one person’s memory is also a good candidate.

Write down:

• Start trigger: what sets it off (“customer places an order”).
• End state: how you know it is done (“customer has the item and the invoice is paid”).
• Owner: one person who cares if it improves.
• Out of scope: what you will not look at this time.

Edges stop the map from growing into everything the company does.

Step 2: Interview the people who do the work

The best source of truth is the people doing the task, not the manager. Interview each person who touches the process, one at a time. Twenty to thirty minutes each is usually enough.

Useful questions:

1. Walk me through the last time you did this, from the first thing you did.
2. What do you need before you can start?
3. Where do you get that from, and how long does it take to arrive?
4. What do you do when something is missing or wrong?
5. Who do you hand it to next, and how?
6. What do you re-type, copy or check twice?
7. What would you change first?

Ask about a recent, specific case. Do not ask “how do you usually do it?”. Nielsen Norman Group’s guidance on interviewing warns that human memory is fallible, and that asking how people “usually” do something produces an idealised workflow without the real shortcuts and deviations (NN/g). A recent, specific case is our way around that. Where you can, also watch the person do the task. What people do and what they say they do can differ.

Record the steps on sticky notes or a shared board during the interview, and read them back to check. Interview separately before you meet as a group, so one loud voice does not shape everyone’s account. You will find disagreements that you can then settle in the room.

For each step, capture four things: who does it, which tool they use, roughly how long it takes, and what they need before they can start.

Step 3: Draw a swimlane map of what happens now

A swimlane map is a flowchart divided into lanes, one per person, team or system. Each step sits in the lane of whoever does it. Arrows show the order. When an arrow crosses from one lane to another, that is a handoff. Lanes can run as rows or as columns. Rows with time running left to right are easy to read on a wide screen or wall.

To draw one:

1. Make the lanes. One per role or system, for example Sales, Operations, Finance, Customer, and the store admin.
2. Place the steps. Put each step in the correct lane, in time order.
3. Keep the symbols few. The common flowchart convention is a rectangle for a step, a diamond for a decision, and an oval for start and end. That is enough.
4. Label decisions with both branches. “Over 500? Yes / No”.
5. Add the tool to each step. Email, spreadsheet, admin, phone. This shows where data moves between systems.

Map the process as it runs today (the “as-is” map). Do not map the ideal. You can sketch a “to-be” version after you have found the problems.

Do you need BPMN?

Probably not. BPMN (Business Process Model and Notation) is a formal standard from the Object Management Group. Version 2.0.2 is the latest formal version on OMG’s site (OMG). It has its own symbols for tasks, events and gateways, and it suits teams that will model processes in software or hand them to developers. For a first map of a small business process, plain flowchart shapes are enough. If you later move to BPMN, your lanes and steps carry over.

Which tool?

Use the simplest one you have: a whiteboard, sticky notes, or a free diagram tool. A shared digital board is better if people work in different places or you want to keep the map. The tool matters far less than getting the steps right.

Step 4: Find handoffs, waiting and rework

Once the map is on the wall, mark three things in different colours.

Handoffs. Every arrow that crosses a lane is a place where work can stall or details can be lost. Count them, and ask of each one whether it is needed.

Waiting time. In lean terms, lead time is the time one piece of work takes to move through a process from start to finish (Lean Enterprise Institute). That includes every delay between steps, not only the time spent working. The gap between the two is often large. For each handoff, ask how long the item sits before someone picks it up. Write a rough number next to it: “2 hours”, “next morning”, “until Friday”.

Rework and loops. Look for arrows that go backward: corrections, “missing info” emails, approvals that bounce. Each loop usually points to a problem upstream.

Also look for:

• steps done by one person only (a single point of failure),
• the same data typed into two systems,
• approvals that are never refused (candidates for removal or a simple rule),
• steps where people say “it depends” (a hidden rule that should be written down).

Worked example: a back-order

The numbers below are illustrative, not measured. They show how to total working time against waiting time for a customer order with an out-of-stock item.

In this example, 35 minutes of work is spread over about two days. Making the packing step twice as fast saves a few minutes. Checking stock on every order instead of twice a day, or agreeing a standard reply time with the supplier, saves hours. Do not assume that speeding up the work helps. If a task takes 10 minutes and then waits two days, the gain is in the wait.

Step 5: Run a 60-minute mapping workshop

If interviews are done, one hour in a room (or on a video call) is a good length to agree the map and pick fixes. This is a suggested format, not a rule. Invite four to eight people, covering every lane.

Before the session

• Draft the map from your interviews on a big board or a shared canvas.
• Send the process name, start and end to everyone in advance.
• Bring sticky notes in three colours.

The agenda

NN/g suggests giving each person roughly a quarter as many votes as there are options. Three votes suits a list of about a dozen problems. It also warns that group voting can be swayed by persuasion and copying, and suggests private votes or letting junior people vote first (NN/g on dot voting).

Facilitation tips

• Keep your hand on the clock. Park side topics on a separate list.
• Ask “who does this?” and “what happens if it is wrong?” more than “why?”
• Let the person who does the step speak first, not their manager.
• Finish with decisions, not just observations.

Send the cleaned-up map and the action list to everyone within a day.

Turn the map into action

A map usually leads to one of four moves:

1. Remove a step nobody needs.
2. Simplify by merging steps or cutting a handoff.
3. Document it, so the process runs the same way each time. See how to write an SOP and our free SOP templates.
4. Automate the repeated, rule-based steps. See what to automate first.

The order matters. Simplify before you document, and document before you automate. Automating a messy process tends to make the mess run faster.

Treat the map as a living page. When the process changes, change the map, and give it an owner and a review date. A map that nobody updates will mislead the next person who reads it.

For help with a map across several teams, our consulting and SOPs service covers interviews, mapping and rollout.

Common questions

How long does process mapping take?

It depends on the size of the process. As a rough guide, allow 20 to 30 minutes per interview, a few hours to draw the first draft, and one hour for the workshop. These are our estimates, not a research finding. A short process with two or three people can be done in a day. A process across several teams takes longer.

Where should a small business start?

With the process that causes the most complaints, rework or errors, or that only one person knows how to do. Pick one, finish it, then choose the next.

How detailed should the map be?

Detailed enough to show handoffs, decisions and waiting. If it needs more than one page, split it into sub-processes and map the one that hurts first.

Common mistakes

• Mapping the ideal process. Map what happens now, including the workarounds.
• Skipping the people who do the work. A map built by managers alone is usually wrong.
• Mapping without a goal. Decide in advance what you want to learn.
• Stopping at the map. Without owners and dates, it ends up in a folder.

Key takeaways

• Map one process at a time, with a clear start, end and owner.
• Interview the people who do the work, one at a time, using a recent real case.
• A swimlane map shows who does what and makes handoffs visible.
• Look for handoffs, waiting time and rework. Waiting is often the biggest cost, so measure it.
• A 60-minute workshop can confirm the map and pick three fixes.
• Simplify first, then document, then automate.

If you would like an outside view of where your handoffs and delays are, we offer a free audit.