If you’re like most growing SMEs, your “systems” weren’t designed. They evolved. A spreadsheet here. A new app there. A quick website tweak. Someone builds a workaround… and suddenly that workaround becomes “the process.” Then one day, you hit a wall, that’s why I’m going to take you through my business process mapping workshop.

If youre suffering with any of the below, this one is for you.

• Too many manual tasks
• Data duplicated (and never quite matching)
• Leads falling through the cracks
• Stock, orders, and invoicing not lining up
• Reporting takes hours (or days)

The instinct is often:

“We need a new system.”

But before jumping to that conclusion, there’s a step that makes everything else easier.

Sit down with the people doing the work and map the flow from start to finish.

This blog walks through how to do that in a practical way.

Why Mapping Comes Before Improving

In recent client meetings, I’ve heard all sorts of goals:

• “We want to remove manual admin.”
• “Our website needs updating, and we want enquiries to be more consistent.”
• “We need tools that help us generate leads.”
• “We’re outgrowing spreadsheets and it’s starting to hurt.”

All valid goals.

But if you don’t understand how work actually moves through your business today, you risk:

• Improving the wrong thing
• Buying software that doesn’t fit
• Automating a broken process

A good flow map does two simple things:

1. Shows the real process (not the version in someone’s head)
2. Lists every piece of tech involved (including the hidden stuff)

Once you can see it clearly, you can start fixing it. Let’s begin the business process mapping workshop.

Step 1: Pick One Process (Define the Start and Finish)

Don’t try to map the entire business at once.

Start with a single workflow that matters, such as:

• Lead → Quote → Order
• Order → Fulfilment → Delivery
• Purchase → Goods In → Stock
• Job Booked → Job Done → Invoice Paid

Then define the boundaries.

Start:
What triggers the process?

Examples:

• Website enquiry
• Phone call
• Order received
• Repeat customer email

Finish:
What does “done” look like?

Examples:

• Delivered
• Paid
• Closed
• Reconciled

Keep it simple. You can always add detail later.

Step 2: Get the Right People in the Room

This is where many businesses go wrong.

If you only speak to leadership, you’ll hear the intended process.

If you speak to the people doing the work, you’ll discover:

• The real steps
• The workarounds
• The “we do this because the system can’t…” moments
• The manual tasks that waste time every day

Whenever possible, run this in person. It helps build trust, read the room, and uncover the details that rarely surface in formal meetings.

Step 3: Build the Flowchart Together (Live)

When running these sessions, I usually start by saying:

“Let’s build your process from start to finish.”

The goal is not a perfect diagram.
The goal is shared understanding.

Structure the discussion around a few simple questions:

• What happens first?
• Who does it?
• Where does the information come from?
• Where does it go next?
• What can go wrong?

If you’re doing this internally, you can do this over Teams in Canva, or in-person whiteboard and sticky notes work brilliantly.

Step 4: List Every Tool Used (Including Spreadsheets)

As you map the process, keep a running list of every piece of technology involved.

This often includes:

• Website and forms
• Email and inbox rules
• CRM (or “the spreadsheet that acts like a CRM”)
• Accounting software (Xero, Sage, QuickBooks)
• Stock systems
• Shipping tools
• Project management tools
• Shared drives
• Any niche apps one person uses

This is often where businesses get surprised.

Over time, tools get added to solve problems in the moment. Rarely does anyone step back and ask:

• Are we still using this?
• Are we paying for duplicates?
• Does this tool create extra admin elsewhere?
• Is there a better option now?

Step 5: Mark the Pain Points

Once the process is mapped, start highlighting the friction.

Look for:

• Manual steps – copying, pasting, re-keying data
• Bottlenecks – where work piles up
• Double handling – entering the same information twice
• Break points – where errors happen
• Waiting time – for stock, sign-offs, or missing information

Next to each issue, add two simple notes:

• Why does this happen?
• What would “better” look like?

At this stage, don’t jump straight to solutions. Just capture the truth.

How Long Does This Take?

It depends on the size of the business and how many people are involved.

In most cases:

• 1 hour for a small team and a single workflow
• Half a day for a busier operation with multiple handoffs
• A full day if mapping several departments

Even the quick version is worth doing.

Why Every Business Should Do This

Processes evolve.

People change.
Tools get bolted on.
Customer expectations shift.

Without occasionally stepping back, businesses end up with:

• Extra costs (tools you don’t need)
• Extra admin (manual work that shouldn’t exist)
• Slower service (information scattered everywhere)
• Higher risk (because the process only exists in someone’s head)

A simple flow map gives you a baseline, and it makes every improvement decision easier.

What Happens After the Map?

Once the flow and technology are visible, you can start making smarter decisions.

For example:

• What can be automated quickly without changing systems
• Whether your website should feed leads into a CRM properly
• Whether you need a new tool or better use of existing ones
• Whether it’s time to move from spreadsheets to a proper system

Most importantly, you can prioritise improvements based on impact rather than guesswork.

Want Help Running a Business Process Mapping Workshop?

If you’d like to run one of these sessions properly with your team, I’m happy to help.

A practical session to get everything out of people’s heads and into a clear, shared flow.

Drop me a message and we’ll arrange a quick chat.