BonoficiGrade your business
Menu
Lesson 1 of 5 · 6 min read

What is business process mapping, and what is it for?

Business process mapping explained: the four levels of documentation, the eight things to record for every step, and when a map is worth making.

Business process mapping is writing down how one piece of work actually moves through a company: each step, who does it, which system it happens in, where it is handed to someone else and where it waits. A useful map is not a diagram for a binder. It is the shared record you need before you train someone, change a system or automate a step.

What a process map is

A process is a repeatable piece of work with a start and an end: a customer order from the first email to the invoice, a supplier invoice from arrival to payment, a new hire from signed contract to first payslip. Mapping it means following that one job across every team it touches and recording what happens at each step.

Most companies already have something that looks like a map: an org chart, a flowchart drawn for an ISO audit, the setup notes from the ERP project. Those describe how the work is supposed to run. A process map worth having describes how it runs now, including the parts nobody is proud of.

The four levels of process documentation

Process documentation works at four levels of detail. Mixing them is the most common reason a map becomes unreadable: a value chain with keystrokes in it, or a work instruction that tries to explain the whole company.

LevelWhat it showsExampleWho reads it
Value chainThe handful of end-to-end processes the company runsWin work, deliver it, get paidLeadership
ProcessOne end-to-end job across teams, step by stepOrder to cash: email, quote, order, picking, delivery, invoiceTeam leads, anyone changing a system
Procedure (SOP)How one team carries out its part, with rules and exceptionsEntering a sales order in NetSuite and checking creditThe people doing it, new starters
Work instructionHow to do one task in one systemCreating a credit note in XeroWhoever does that task this week

You may also see processes grouped as core (the work customers pay for, such as sales, production and delivery), management (planning, budgeting, quality review) and support (finance, HR, IT). That classification comes from quality management standards such as ISO 9001 and is handy for an inventory. For improvement work, start with a core process: that is where customers feel the delays.

This course works mostly at the process level, then goes down to procedures in how to write an SOP.

The two processes every company runs

Every process exists twice. There is the documented one: the flowchart, the policy, the ERP configuration. And there is the one people follow on a Tuesday when a supplier is late and the customer is on the phone.

The second one lives in a layer of habits around the official systems. The price that is checked in a spreadsheet before it goes into SAP. The order that is confirmed by phone because the portal is slow. The approval that happens in an Outlook thread rather than in the workflow tool. This layer is where exceptions get handled, and it is usually invisible to the people who designed the official process.

A map that only records the documented version will look tidy and be wrong. Automate from it and the automation breaks on the first real exception, and people go back to the spreadsheet.

When to map a process

  • Before you automate. Automating a process you have not mapped means automating your assumptions. The map tells you which steps follow rules and which depend on judgement.
  • Before a new system. An ERP or CRM change is when the habits around the old system get lost. Map them first, or rebuild them by accident later.
  • When onboarding takes too long. If a new starter needs weeks of shadowing, the process lives in someone’s head. A map and an SOP shorten that.
  • When you are growing. What works with one person handling every order breaks with three. Hand-offs multiply, and so do the gaps between them.
  • When something keeps going wrong. Repeated errors, late deliveries or invoices that keep failing to match usually trace back to one step nobody owns.

What to record for each step

A map earns its keep through what it records about each step, not through the shapes. For every step, write down eight things.

FieldQuestion it answersExample
TriggerWhat starts this step?Customer email arrives in the sales inbox
ActionWhat does the person do, in one verb?Check stock for each line
OwnerWhich role does it, and who stands in?Sales coordinator; cover: sales manager
SystemWhere is the record kept?HubSpot, then the stock spreadsheet
Hand-offWho gets the work next, and how?Warehouse, by forwarded email
WaitHow long does it usually sit before the next step?Half a day, longer on Fridays
ExceptionWhat goes wrong, and what do people do then?Item out of stock: call the customer, offer a substitute
EvidenceWho told you this, in their words?Interview with the sales coordinator, 3 March

The last field is the one most templates leave out, and it is the one that keeps the map honest. Use a simple rule: no quote, no claim. Nothing goes on the map unless someone who does the work said it. If a step is there because a manager assumed it, mark it as unconfirmed until someone doing the work confirms it.

The hand-off and wait fields matter most for improvement. Work rarely gets slow because a single task takes long. It gets slow because it sits in inboxes between tasks.

What a finished map looks like

For a mid-size company, a useful first map covers one process, fits on a screen or two and has somewhere between ten and thirty steps. It has a swimlane for each role, marks the systems, highlights the hand-offs and waits, and lists the exceptions next to the steps where they happen. It comes with a short list of open questions: steps where two people gave different answers, or where nobody could say who owns it.

That last list is often the most valuable output. A step everyone relies on and nobody owns is where work stalls, gets done twice or falls to whoever happens to notice.

The next lesson walks through building one: how to map a business process step by step, with a template you can paste into Excel. Lesson 4 covers the part most maps skip, documenting the exceptions.

If you would rather know where to start before mapping anything, the free Bonofici grader reads your company’s public pages and shows which work is worth looking at first.

Start with what your team already knows.

Book a 30‑minute call.We come back with the first three tools worth building, in writing.

Not ready for a call?

See where your company stands and which jobs are worth the most, from your public pages.