How to map your SME's processes in 5 steps (before automating anything)

When I walk into a business to design a system, I never start with the technology. I start with a blank sheet and one question: how is this actually done today? The answer hardly ever matches what management says, and that's where everything important lies. That sheet ends up as a process map, and it's the most useful tool I know for getting an SME in order before automating anything.

What is a process map?

A process map is a visual representation of how work flows through your business: which steps are followed, who does each one, with which tools and how long it takes. You don't need special software: a whiteboard, some sticky notes or a spreadsheet are enough to get started.

Its value isn't in looking nice, but in bringing to light what nobody sees: duplicated tasks, data copied from one program to another, delays nobody has measured or steps that depend on a single person.

Step 1: Choose one specific process (not the whole business)

The most common mistake is trying to map everything at once. Start with a process that meets two conditions: it repeats a lot and it hurts. Some good candidates:

• Handling supplier invoices.
• Following up a quote until it's accepted.
• Managing a sale from booking to delivery.
• Answering customer enquiries.

One well-mapped process is worth more than ten half-finished ones.

Step 2: Define where it starts and where it ends

Every process has a trigger and an outcome. Write them down first:

• It starts when: an invoice arrives by email.
• It ends when: the invoice is recorded, approved and ready to pay.

It seems obvious, but it heads off half the arguments: if it isn't clear where a process ends, nobody feels responsible for closing it.

Step 3: Draw the real steps with the people who do them

This is the key to the whole method. The map is built with the people who do the work every day, not from an office. Sit down with them and ask them to show you how they do it, step by step, with their screen in front of them.

For each step, note down three things:

1. What is done (for example, "copy the amount into the accounts").
2. Who does it (person or department).
3. With which tool (email, ERP, Excel, WhatsApp, paper).

You'll see things appear that weren't in any manual: the parallel Excel file "just in case", the WhatsApp message to confirm something that's already in the system, or the step only one person knows how to do.

Step 4: Measure time and frequency

A map without numbers is an opinion. For each step, estimate how long it takes and how many times it happens a week or a month. You don't need stopwatch precision: "about 5 minutes, around 40 times a month" is enough.

When you multiply, the surprises appear. A 5-minute step repeated 40 times a month adds up to more than 3 hours a month. If there are four steps like that in the same process, you're already looking at a day and a half of work every month in a single process.

Step 5: Mark the bottlenecks and errors

With the map complete, go through each step and mark it if it meets any of these conditions:

• Information is copied from one tool to another.
• There's a wait (someone has to approve, reply or review).
• It depends on one person and stops if they're away.
• It repeats the same way every time, with no complex decisions.
• It often causes errors.

Those marked steps are your best candidates for improvement. And not all of them are solved by automating: sometimes it's enough to remove a step that no longer makes sense or to merge two tools.

From map to automation: what to do first

With the map in front of you, prioritising is much simpler. Rank the marked steps by two criteria: how much time they take up and what impact they have on the customer. Start with the ones that score high on both.

A real example: at a car dealership, the map of a vehicle sale showed that the paperwork for each deal passed through four pairs of hands and three tools before reaching the agency handling registration. Putting that route in order and then automating it freed up a good part of a working day of admin.

If you'd like to dig into why this order matters so much, we explain it in why automating a messy process is expensive. And if you'd rather not do it alone, in our free audit we build the first map of the processes that take up most of your time with you. You can see how we work in services.

What I take away from every map

After many maps, the conclusion is always the same: businesses don't lose time through lack of effort, but through lack of visibility. When the team sees the process drawn out, the improvements appear on their own. Technology comes afterwards, and it lands much better.