Process mapping: method and example for an SME

Process mapping is a representation of a company's activities and how they follow one another: who does what, in what order, with which tool. It works at two levels: an overview map that sorts all the processes, and a detailed map of one process, step by step, to find where time is lost.

Most guides on the topic are written by quality consultants preparing an ISO 9001 certification, or by diagramming tool vendors who want to show you their templates. Both are useful. But an SME owner who maps their processes is rarely after a certificate or a nice diagram. They want to know what to change.

This article starts from there. You map in order to decide which step to remove, which one to simplify, which one to automate. The method fits in four steps, and the complete example of a quote-to-invoice process is at the end, with the Excel template to download that goes with it.

Process mapping: what we are talking about

The same term covers two exercises, and most of the confusion comes from there.

Overview map or detailed map: two different exercises

The overview map fits on one page. It lists the company's main processes, for example "from quote to invoice", "recruit and onboard an employee" or "handle a complaint", and sorts them by family. It says nothing about how each process runs. It is there to see the whole and choose where to look.

The detailed map takes a single process and describes it step by step: who acts, in which tool, how long it takes, how long the file waits before the next step. That is the one that shows the problems.

If you look for examples online, you will mostly find overview maps in the ISO 9001 format, with three coloured bands and arrows. It is a good starting point, but no concrete decision comes out of it. Decisions come from the detailed map.

The 3 types of processes

The most common classification, used by AFNOR in its practical guidance on the process approach, sorts processes into three families:

• Operational processes, also called core or business processes: the ones that produce what the customer pays for. Selling, producing, delivering, invoicing.
• Support processes: the ones that keep the company running. HR, accounting, IT, purchasing.
• Management processes, or steering processes: the ones that set the direction. Setting objectives, tracking indicators, deciding on investments.

One point many guides forget: the ISO 9001 (version 2015) standard asks for a process approach, but it does not impose this three-family classification. The ISO committee's guidance on the process approach says it clearly: there is "no catalogue or list of processes that have to be formally defined". The three families are a practical convention. If another split speaks better to your team, use it.

What process mapping is for in an SME

It is first of all a decision tool. Once the process is drawn with its times, you see the steps that serve no purpose, the re-keying, the approvals waiting for someone. It is the basis of any business process automation: you cannot choose what to automate in a process you have never looked at as a whole.

It also helps in situations where people do not think of it:

• Onboarding a new employee. An up-to-date map replaces a week of "ask Sophie, she knows how we do it".
• Changing tools. Before migrating to a new CRM or ERP, the map tells you what the tool really needs to do, and keeps you from copying a shaky process as is.
• Reducing dependence on one person. When only one person knows how a process works, their absence blocks everything. The map makes that knowledge visible.
• Preparing an ISO 9001 certification, if you are aiming for one. The map helps, but the ISO committee's guidance on the 2015 version states that it is not required as such.

In the Digital Wallonia 2025 barometer, Walloon companies score 29/100 on the "processes" axis. The report sees in it "a lack of automation and process transformation, with digital remaining mainly a support for existing activities" (our translation). In other words, the digital tools are there, but they were laid on top of existing processes without reviewing them. Mapping is the missing step.

Step 1: the overview map in one hour

Get the owner and two or three managers together. For one hour, list the company's processes and sort them into the three families. Stop at 10 to 15 processes. Beyond that, you are going into detail too early.

Two rules make the list useful. Each process starts with an event ("the customer returns the signed quote") and ends with a result ("the invoice is paid"). And each process is named with a verb: "recruit and onboard an employee" rather than "HR". A department is not a process. The quote-to-invoice process crosses sales, sales administration, delivery and accounting, and that is precisely why it gets stuck.

At the end of the hour, you have one page, and enough to choose the process to dig into.

Step 2: choose one process to map in detail

Do not map everything in detail at once. Choose a single process: the one that comes up often, follows a roughly stable rule and is expensive when it goes wrong. The full grid, with its five criteria, is in the article on business process automation.

In most services SMEs, the first candidate is the process that runs from the signed quote to the invoice, because it touches cash flow. In manufacturing, it is often customer order processing, from receipt to shipping.

Beware of the process that annoys the owner the most: it is not necessarily the one that costs the most.

Step 3: map the process in a workshop

Allow two hours, with the people who do the work. Not only their managers: a manager describes the process as it was designed, the person who does it every day describes it as it actually happens. They are rarely the same.

The simplest format is the swimlane diagram, what BPMN notation calls "lanes". One horizontal row per actor (sales, sales administration, project manager, accounting), and the steps placed as sticky notes in the lane of whoever does them. Every time a sticky note changes lane, there is a handoff, and that is often where the file waits.

For each step, write down five pieces of information:

• The step, with a verb: "re-key the order", "approve the invoice".
• The actor: who does it.
• The tool: in which software, or on which medium (email, Excel, paper).
• The working time: how many minutes someone actually spends on it.
• The waiting time: how long the file waits before the next step.

The last column is the most important one, and it is the one almost every mapping template forgets. It comes from lean, where it is called value stream mapping. The Lean Enterprise Institute defines it as diagramming every step involved in the material and information flows needed to bring a product from order to delivery. The method was popularised in 1998 by Mike Rother and John Shook in Learning to See. Under the map, you draw a timeline that separates the time spent working from the total lead time: the time it takes to go through the whole process, from start to finish. In practice, the person doing the step rarely knows the waiting time. You rebuild it from the dates: the quote was signed on Monday, the order entered on Wednesday.

Two traps to avoid during the workshop. The first is mapping the ideal process, the one in the procedure, instead of the real one. If someone says "normally, we…", ask what really happens. The second is the exceptions. Someone will end up saying "yes, but when the customer has two delivery addresses…". Write the exception on a separate sticky note and come back to the case that happens eight or nine times out of ten.

Step 4: read the map and decide

Once the map is laid out, add up the numbers: total working time, total waiting time, and total lead time between the start and the end. Almost always, working time is only a small share of the lead time. It is the usual surprise of the workshop, and it is good news: the gain lies in the waiting, not in how fast people work.

Then look for four signals on the map:

• Re-keying: the same information typed twice, into two tools.
• Long waits: a complete file sleeping in an inbox.
• Approvals without a rule: a sign-off that could follow a threshold, but goes through someone out of habit.
• Back-and-forth: a sticky note that returns to a lane it already visited.

For each step, choose a decision, in this order of preference: remove, simplify, automate, keep. The order matters. Automating a step you could have removed means paying for a tool that does something useless quickly.

Example: mapping a quote-to-invoice process

Here is a typical example, fictitious but realistic, to show what the result looks like. A 30-person B2B services company signs around forty quotes a month. Its "from quote to invoice" process gives this map:

1. Receive the signed quote by email. Sales, email. 5 minutes, then 24 hours of waiting.
2. Forward the quote to sales administration. Sales, email. 5 minutes, then 8 hours of waiting.
3. Re-key the order into the management tool. Sales administration. 15 minutes, then 16 hours of waiting.
4. Confirm the service schedule. Project manager, email and Excel. 10 minutes, then 40 hours of waiting.
5. Confirm the service is complete. Project manager, email. 5 minutes, then 24 hours of waiting.
6. Create the invoice. Accounting, invoicing software. 15 minutes, then 16 hours of waiting.
7. Have the owner approve the invoice. Owner, email. 5 minutes, then 24 hours of waiting.
8. Send the invoice to the customer. Accounting, email. 5 minutes.

The waiting hours are working hours: 8 hours make one working day.

The totals speak for themselves. Total working time is 65 minutes per quote. Total waiting is 152 working hours, or 19 working days. Actual work accounts for less than 1% of the lead time between signature and sending the invoice. And across 40 quotes a month, those 65 minutes still add up to more than 43 hours of work a month, mostly re-keying.

What gets decided:

• Remove step 2. If the e-signature creates the order on its own, there is no need to forward the quote.
• Automate steps 1, 3, 5 and 6. The signature creates the order, the completion note triggers the invoice, and the information is entered only once.
• Simplify step 4, by taking the schedule out of an Excel file that only the project manager updates, and step 7, with a rule: automatic approval below a certain amount, approval by the owner above it.
• Keep step 8, which is now done directly from the invoicing software.

Beyond the minutes saved, the invoice goes out several days earlier, so the customer pays earlier. On a process that touches cash flow, that is often the argument that convinces.

This example is filled in on the "Quote-to-invoice example" tab of the Excel template, with automatic calculations.

HR process mapping: the example of a new hire

HR processes lend themselves well to the exercise, because they involve many people for a low volume. Onboarding a new employee is the clearest case.

Map it from the signing of the contract to the first day the person is fully operational. You will see HR, management, IT and the future manager go by, sometimes facilities for the equipment. Each one does their part correctly. But nobody has the full list, and requests go out by email as they come.

The usual signals: IT accounts requested too late, a computer ordered the day before, tool training that depends on a colleague's availability. Working time is low. The waiting is paid for in days of lost productivity for the new hire, and in a poor first impression.

The most common decision is to have all the requests start from a single event, the signing of the contract, with a checklist everyone can see progressing. It is often the first building block of HR process automation, which also covers leave and expense reports.

Which tool to map your processes

For the workshop, a wall and sticky notes. Everyone can move a step, nobody is held back by software they do not know, and the discussion happens in front of the wall rather than behind a screen.

To clean up the map, three options are enough in an SME:

• A spreadsheet, if you want to calculate the times and track the decisions. It is the format of the template offered here.
• A diagramming tool, such as Whimsical, Excalidraw, draw.io or PowerPoint, if you want a swimlane visual to display or share.
• BPMN modelling software, if you have to maintain dozens of documented processes, for example for a certification. For a first map, it is too heavy.

The process mapping template to download

The Excel process mapping template contains four tabs:

• How to use: the rules for filling it in.
• Process overview: the three families of processes, with examples to replace.
• Process to map: a blank template, one row per step, with the actor, the tool, the working time, the waiting time, the problem observed and the decision. The sheet calculates the total lead time, the share of lead time actually worked and the monthly working time.
• Quote-to-invoice example: the example from this article, filled in.

It is free to reuse. Fill it in during or right after the workshop, while the times are fresh.

Where to start this week

Block one hour with your management team for the overview map. Choose one process. Plan a two-hour workshop with the people who do it, and fill in the template. You will have a map of your real process, with its times and a first list of decisions, in less than a week.

If you would rather we ran the workshop with your team, it is the first step of our diagnostic, before any talk of tools or automation. Book a 30-minute discovery call and we will look together at which process to map first.