Business process mapping is the practice of writing down how work actually flows through a business — every step, decision, and handoff — so the work can be improved, automated, or delegated. For UK SMEs, five steps cover most of the value: pick the process, walk the path, capture the steps, find the friction, redesign.

You can''t systemise what you can''t see. Process mapping is the cheapest tool for making operations visible.

Step 1 — Pick the right process

Don''t try to map everything. Start with:

• A process that runs at least weekly (so improvements compound).
• A process owned by someone who currently does it (so the mapper has knowledge).
• A process where mistakes are costly (so fixing it returns real value).

Common high-value starting points: client onboarding, invoice raising and chasing, new-hire setup, customer support ticket workflow, sales follow-up.

Avoid: one-off projects, processes you''re about to redesign for unrelated reasons, processes nobody actually does anymore.

Step 2 — Walk the path with the person doing it

Schedule 60-90 minutes with the operator. Watch them do the work, not in theory — in real time, with a real piece of work in front of them. Take notes on every:

• Action they take (open this tab, fill this form, send this email).
• Decision they make (if X, then Y; else Z).
• Handoff to another person or system.
• Wait for something or someone (waiting for approval, waiting for data, waiting for a reply).
• Workaround they''ve invented (the actual real way, not the official way).

The workarounds are gold. They tell you where the documented process and reality have diverged — and the reasons usually point at the highest-leverage improvements.

Step 3 — Capture the steps visually

Don''t write the process as paragraphs. Use one of:

• A flowchart (rectangles for steps, diamonds for decisions, arrows for flow). Tools: Lucidchart, Miro, FigJam, draw.io.
• A swimlane diagram when multiple people / teams are involved. Each lane = one role.
• A simple numbered list with sub-bullets for decisions — fine for processes under 15 steps.

Aim for one page. If it doesn''t fit on a page, the process is too coarsely chunked — break sub-processes out.

Step 4 — Find the friction

For each step, ask:

• Why does this step exist? Many steps exist because someone added them years ago for a reason that no longer applies.
• Is this step manual when it could be automated? Data entry duplication is the textbook example — same data into 2-3 systems.
• Does this step wait on something? Waits over 24 hours are usually structural (a person who only acts in batches, a system that runs nightly) — and structural waits compound.
• Does this step routinely produce errors? If yes, what causes them?
• Can this step be deleted? The fastest improvement is removing a step entirely.

Mark each step: KEEP (essential), CHANGE (works but could be better), AUTOMATE (clear automation candidate), DELETE (no longer needed).

Step 5 — Redesign

You now have a current-state map plus a list of changes. Draft the future-state map:

• Remove DELETE steps.
• Replace AUTOMATE steps with the new automation (named tool, not vague intent).
• Rewrite CHANGE steps with the improved version.
• Keep KEEP steps.

Calculate the time saved per cycle and the implementation effort. Sort by ratio. Implement the top-3 improvements first; don''t try to do everything at once.

What good process mapping looks like

The map should be:

• Specific enough that a new hire could follow it. "Send an email" is not a step. "Open the [Template Name] in [System], change the placeholders for {client name}, send to the client" is.
• General enough that it survives small variations. If you''re writing IF-THEN branches for every conceivable case, you''re writing a flow chart, not a process map.
• Owned by someone. Every process has a process owner. They are responsible for keeping the map current.

Anti-patterns to avoid

• Mapping in isolation without watching the work. The result is a process map of how someone thinks the work works, not how it actually works.
• Mapping to 200 levels of detail. The 80/20 of the value lives at one page per process.
• Mapping a process the day before redesigning it. The map is the foundation for the redesign, not a tickbox before the redesign starts.
• Treating the map as a one-off. Processes change. The map should be updated quarterly or when the process materially changes.

What to do this month

• Pick one high-value process you run at least weekly. Block 90 minutes with the person who does it.
• Map it on one page (flowchart, swimlane, or numbered list).
• Find the top 3 friction points and pick the one with the best effort-to-impact ratio.
• Implement it. Update the map. Move on to the next process next month.