How to process map your small business in five steps

Executive overview

Most small businesses can't scale or reduce stress because their core processes are invisible. Process mapping makes those processes visible — turning a sequence of actions into a story you can analyse and improve.

Pick one painful but high-value area. Map what actually happens today, not what should happen. Then add layers to expose the root cause.

The only question you need to keep asking is: what happens next?

The six questions that define a systemised business

• Why are we doing it?
• What needs to happen?
• Who is doing it?
• When is it happening?
• How do we do it?
• Where do we keep track of it?

Process mapping primarily answers the why — it reveals how individual steps connect to the big picture.

Step 1: Pick one painful area

• Choose a process that is both valuable and broken.
• Common candidates: onboarding, sales, vendor sourcing, client change requests.
• Small teams have an advantage — you already know which area hurts.

Step 2: Set the scope

• Define a clear start and end point.
• Sales: lead in → sale closed (or lead disqualified).
• Fulfillment: client starts → client off-boarded.
• Vendor sourcing: we need a vendor → we have a vendor.
• Keep the scope tight enough to stay useful.

Step 3: Map the four symbols

• Rectangle — a step or action where something happens.
• Diamond — a decision point where the path branches (yes/no).
• Folder (predefined process) — a collapsed sub-process too complex to expand here.
• Arrow — shows flow and sequence between shapes.

These four are sufficient. Ignore the rest of the formal notation.

Step 4: Build the map

• Start at the left; write the first action, then keep asking "what happens next?"
• Break every action — automated or human — into one box per task (one person, one sitting, one discrete date).
• Parallel paths (e.g. client actions and internal actions happening simultaneously) can run side by side to preserve sequence.
• Map the current state, not the ideal state. Note improvement ideas separately.
• Use digital tools or multiple sheets — you will run out of space.

Step 5: Add layers to expose problems

Add swim lanes only if the map doesn't reveal the problem on its own.

• People — assign a person to each step; look for confusing handoffs.
• Software — label which tool handles each step; fragmented tooling shows up fast.
• Time — note how long each step takes; reveals cost overruns or bottlenecks.
• Emotions — track how the client feels at each step; identifies drop-off points and where to create earlier wins.

Turning the map into action

• A process map that changes nothing is procrastination.
• Connect findings back to the six systemisation questions.
• Act on the map: set up software, create templates, assign ownership, hire where gaps exist.