Business Process Mapping: A Practical Guide for Growing Businesses

Business process mapping means drawing out how a piece of work actually happens, step by step: who does what, which system or spreadsheet it's in, what waits on what, and where information is copied from one place to another. The simplest way to start is to pick one process that causes trouble, walk through a few real examples with the people who do the work, and draw every step, including the workarounds, as a swimlane diagram with one lane per person or team. Once it's drawn, the problems usually jump out: work waiting in inboxes, the same details typed into several systems, and steps that depend on one person. This guide walks through how to do it and how to turn the map into real improvements.

Step 1: Pick one process

Don't try to map the whole business. Pick one process that clearly causes trouble, for example:

• Quote to cash: from enquiry to quote, job, invoice and payment.
• Purchase to pay: from purchase request to approval, order, receipt, bill and payment.
• Order to delivery: from customer order to picking, dispatch and invoice.
• Month-end: from last transaction to management report.
• New starter or new subcontractor: from approval to fully set up.

Choose the one with the most delays, rework or complaints. Give it a clear start and end point.

Step 2: Walk through real examples

Sit with the people who do the work and follow two or three real examples from start to finish, such as actual jobs, orders or invoices from last week. Ask:

• What triggers this step?
• Where does the information come from, and where does it go?
• Which system, spreadsheet, email or piece of paper is used?
• What happens when something is missing or wrong?
• Who does this when you're away?

The workarounds are the important part. "I keep a spreadsheet for that" or "I just ring them" is where the real process lives.

Step 3: Draw it as a swimlane diagram

A swimlane diagram is the most useful format for most businesses. Each person or team gets a horizontal lane, and the steps flow from left to right, crossing lanes at each hand-off.

1. List the people or teams involved and draw a lane for each.
2. Add each step as a box in the lane of whoever does it.
3. Use arrows for the order of steps and the hand-offs between lanes.
4. Mark decisions as diamonds, such as "approved?" or "stock available?".
5. Note the system or spreadsheet used under each step.

A whiteboard and sticky notes are fine to start. Diagram tools such as Visio, Lucidchart or Miro make it easier to share and update. The tool matters much less than drawing how work really happens, not how it's supposed to.

Step 4: Mark the problems

With the map drawn, go through it with the team and mark:

• Waiting: where work sits in an inbox, tray or queue.
• Retyping: where the same information is entered into more than one system.
• Checking and fixing: where errors are found and corrected, especially late in the process.
• Single points of failure: steps only one person knows how to do.
• Steps that add nothing: approvals nobody checks, copies kept "just in case".

For each problem, note roughly how often it happens and how long it takes. For example, if invoices wait three days for approval and you raise forty a week, that's a lot of cash sitting still.

Step 5: Turn the map into improvements

Improve in this order:

1. Simplify. Remove steps that add nothing and agree one way of doing the work.
2. Fix the hand-offs. Make it clear who does what and when, so work stops waiting.
3. Connect the systems. Where information is retyped between systems, connect them so it flows.
4. Automate the repetitive steps. Once the process is simple and the systems are connected, automate what's left.

Automating before simplifying just gives you a faster version of a messy process.

Keep the map alive

A process map is only useful while it's accurate. Store it where the team can find it, review it when the process or systems change, and use it to train new staff. A current map, together with written procedures for the key steps, is one of the best protections against depending on one person.

When it's worth getting help

Most businesses can map a process themselves. It's worth getting help when:

• the process crosses several systems and the fix means connecting them,
• people disagree about how the process works or should work,
• nobody has time to own it,
• or you want a fixed-price outside view across several processes at once.

See business process mapping, or our $5,000 Process & Systems Audit, which maps your key processes and systems and gives you a written, prioritised plan.

Frequently asked questions

What is business process mapping?

It's drawing out how a piece of work actually happens, step by step, including who does it, which systems are used, and where it waits or gets retyped. It's the starting point for improving slow or error-prone processes.

What is a swimlane diagram?

A process map where each person or team has its own horizontal lane. Steps sit in the lane of whoever does them, so hand-offs between people are easy to see. That's often where delays happen.

What's the best tool for process mapping?

A whiteboard and sticky notes are fine to start. Diagram tools such as Visio, Lucidchart or Miro are useful for sharing and keeping maps up to date. The method matters more than the tool.

How detailed should a process map be?

Detailed enough to show every hand-off, system and decision, but not every mouse click. If someone new could follow it to understand how the work flows, it's about right.

What comes after process mapping?

Simplify the process, fix the hand-offs, connect the systems where information is retyped, then automate the repetitive steps, in that order.

If your map shows the problem sits between your systems, book a free initial chat. We'll tell you which fixes you can make yourselves and where we can help.