Process mapping for small business

Writing down how the work actually moves, from the moment it starts to the moment it’s done.

Most processes in a small business were never designed. They grew: someone did it one way, someone else added a step, a workaround became the rule. A process map puts that on paper so everyone can see it, including the waits, the double handling and the steps that depend on one person.

A map isn’t the same as an SOP. The map shows the whole flow across people: who hands what to whom. An SOP is the step-by-step for one task inside it. You map first to see what’s wrong, then write SOPs for the steps that need them.

You don’t need special software. A whiteboard, sticky notes or a single page in a doc is enough. What matters is that it shows the work as it really happens.

The process that costs you the most: in your time, in errors, or in customers.

• The process that stops when you’re not available.

  The clearest sign of where the business still runs through you.

• The process you explain more than once.

  If you keep explaining it, it isn’t written down.

• The process that produces the most errors.

  Wrong orders, missed invoices, rework.

• The process that touches the most customers.

  Quotes, orders, delivery, support: problems here are felt outside the business.

Pick one. Mapping everything at once turns into a project nobody finishes. One process mapped and fixed beats ten half-mapped.

Trigger, steps, roles, waits, breaks. On one page.

1. 01

   Start with the trigger.

   What starts the process: a customer order, a phone call, the first of the month.

2. 02

   Write every step.

   In order, in plain words, as it actually happens today. Include the workarounds.

3. 03

   Name the role for each step.

   A role, not a person’s name: sales, warehouse, office manager, owner.

4. 04

   Note where it waits.

   Every place the work sits in an inbox, on a desk or in a queue, and roughly for how long.

5. 05

   Note where it breaks.

   Where mistakes happen, where things get lost, where someone has to chase.

6. 06

   Mark the end.

   What “done” looks like: the order delivered, the invoice paid.

Map it with the people who do the work, not from your desk. Walk through a real recent example from start to finish. People will tell you the steps that never made it into anyone’s description of the job. Keep it to one page. If it takes more, split it into two processes.

A simple map of a typical order process. Yours will look different; the format is the point.

• 1. Customer asks for a quote

  WhoSales

  Where it waits or breaksWaits in the shared inbox until someone sees it.

• 2. Quote is priced and sent

  WhoOwner

  Where it waits or breaksWaits for the owner. Only they know the pricing rules.

• 3. Customer accepts, deposit taken

  WhoSales

  Where it waits or breaksBreaks when the deposit isn’t recorded and production starts anyway.

• 4. Order goes to production

  WhoOffice manager

  Where it waits or breaksRetyped from the email into a spreadsheet. Errors creep in here.

• 5. Order is made and checked

  WhoProduction

  Where it waits or breaksWaits when materials weren’t ordered in time.

• 6. Order ships, invoice sent

  WhoWarehouse, office manager

  Where it waits or breaksBreaks when nobody tells the office it shipped, so the invoice is late.

On one page, the problems are obvious: two waits on the owner and the inbox, one retyping step, and two handoffs nobody owns. That’s the fix list.

Fix the steps only you can do, the waits and the breaks. Then decide what to automate.

• Steps only the owner can do

  What it meansThe process stops when you’re busy or away.

  What to doWrite the rule down and hand the step to a role.

• Waits

  What it meansWork sits still while customers and cash wait.

  What to doName an owner and a time limit for each handoff.

• Breaks

  What it meansErrors, rework and chasing.

  What to doAdd a check at that step, or remove the step that causes it.

• Retyping and copying

  What it meansThe same information entered twice.

  What to doEnter it once. This is often the first thing worth automating.

Then write the fixed version down. Each step that needs instructions gets an SOP. the free SOP template gives you the one-page format and a filled example. To map the whole business rather than one process, run a 30-day systems audit.

Don’t automate a process you haven’t mapped. You’ll just make the mess faster.

Automation repeats whatever you give it. If the process has an unnecessary step, a wait nobody owns or a rule that only lives in your head, automating it bakes those problems in. Map it, fix it, run it by hand for a few weeks until it holds, then automate the repetitive, rules-based steps.

The map also shows you where automation pays: the retyping, the copy-paste between tools, the status updates people chase by email. Our guide on how to automate business processes covers where to start.

Pick one process. Write the trigger and every step. Name the roles. Note where it waits and where it breaks. That’s the map. Then decide what to fix.

If you’d rather have the mapping, the fixes and the written processes done with you, that’s our Systems & SOPs work: processes mapped, written and handed over running.

Scope your project →