Business Process Mapping, With a Real Example

Search for business process mapping and page one is an encyclopedia entry, a few large software companies and a row of diagramming tools. They explain the symbols, and several of them sell the software you draw in. What they rarely show is a map of a real small business, drawn from the people who do the work, and what happened to the process once it was on paper.

We build operating systems for service businesses, and our builds start by mapping how the work actually runs. This guide covers what a process map is, how to make one that is actually useful, and a real eight-step onboarding process we mapped and then automated end to end.

What is meant by process mapping?

Process mapping means drawing a process as a sequence of steps, showing who performs each one, what triggers it, which decisions branch it and where it ends. Business process mapping applies that to how a company actually operates, so a team can see the work as it really runs, find the waste, and agree on how it should run instead.

The term covers a family of diagrams, from a quick sketch on a whiteboard to formal notations, and Wikipedia’s entry on business process mapping traces it back to the flow process chart Frank Gilbreth presented to engineers in 1921. The diagram matters less than the conversation it forces. Most owners have never seen their own operation drawn out, and the first map usually surprises them.

What are the 5 levels of process mapping?

The five levels of process mapping run from the whole business down to a single task. In the hierarchy APQC uses in its Process Classification Framework, they are category, process group, process, activity and task. Each level breaks the one above it into smaller parts, and different questions need maps at different depths.

Other guides number the levels differently, and some start from a value chain at the top, but the idea is the same everywhere. For a small business, the useful maps sit at levels 3 and 4: one process at a time, broken into the activities people actually do. Level 5 is where automation happens, so it gets written down once a process is being rebuilt.

What is the difference between a flowchart and a process map?

A flowchart shows the logic of a process: the steps, their order and the yes-or-no decisions. A process map adds what a business needs on top: who does each step, which tool it happens in, how long it waits and where it passes from one person or department to the next. Every process map contains a flowchart.

Most flowcharts are not process maps, and the difference shows up the moment something goes wrong. A flowchart tells you the next step is “send the welcome email”. A process map tells you that the account manager sends it from Gmail, but only after operations has created the client’s folder, and that nobody is told when the folder is late.

What are the different types of process maps?

The common types of process maps are the basic flowchart, the swimlane diagram, the SIPOC diagram, the value stream map and the data flow diagram. They answer different questions: what the steps are, who does each one, where a process starts and ends, where time is wasted, and how information moves between systems. A service business rarely needs all five.

For a service business the most useful map is usually a swimlane with the tool written on each step, which makes it part flowchart and part data flow diagram. That combination turns most directly into a system.

What is the purpose of a swimlane diagram?

A swimlane diagram gives each person, role or department its own horizontal or vertical lane and places every step in the lane of whoever does it. Its purpose is to make handoffs visible: each time the work crosses from one lane into another, someone has to notice it, and that crossing is where delays and dropped tasks tend to sit.

The format first appeared in the 1940s as a multi-column process chart, and Geary Rummler and Alan Brache gave it the swim lane name in 1990, as Wikipedia’s swimlane article describes. Most diagramming tools now include it. For a service business, the lanes are usually the client, sales, operations, delivery and finance. A map with five lanes and twenty crossings often says more about where the time goes than a time-tracking report does.

What is the easiest way to create a process map?

The easiest way to create a process map is to pick one process with a clear start and end, sit with the people who run each step, and write the steps in the order they really happen, on sticky notes or a whiteboard. Then mark who does each step, its tool and its handoffs. Draw the clean version last.

The method we use with clients follows that shape:

1. Start with the departments. List them, then go into each one and ask what its main processes are. Most service businesses have sales, marketing, operations, delivery and finance.
2. Talk to the people who do the work. We hold conversations with the key members of each team, because the owner’s version of a process and the version the team runs are rarely the same.
3. Write the as-is process, the way it runs today. Every step, including the workarounds, the copy-and-paste and the “I just remember to do it”. Map what happens most of the time, note the exceptions beside it, and resist fixing anything yet.
4. Connect the roles across departments. Mark every point where work passes from one role or department to another. These handoffs are where the map earns its keep.
5. Mark manual and automated steps. We record both, because a step that runs on its own still has to be known about. If nobody knows an automation exists, nobody notices when it stops.
6. Count the steps and question each one. Is this process 30 steps? Should it be 20, or 10, or two? Cutting steps comes before automating them.
7. Draw the to-be map and walk it with the team. The people who run the process check the new version against their real week, and the map changes until they agree it works.

Are visual SOPs better than written SOPs?

For most teams, yes. Written SOPs are helpful, but a visual SOP built from a process map is easier to follow, because it shows how each role connects to the others and where its work goes next. The same map also helps with planning new automations and with onboarding new clients and new employees, so it keeps being used.

That is how we build SOPs for clients. We map how each department works and how it connects to the rest of the business, and the map becomes the procedure. A written step-by-step document still has a place for tasks with exact settings or legal wording, and it can link from the step on the map where it applies. The map stays the thing people open first.

What are some examples of business process mapping?

Common examples of business process mapping in a service business are client onboarding, from signed contract to first delivery; lead handling, from enquiry to booked call; invoicing and collections; hiring and onboarding staff; and the delivery process itself. Client onboarding is usually the best one to map first, because it runs often, crosses several teams and touches every tool.

Here is a real one. Nomads Cast, an agency that produces social video for brands, brought every new client on through eight manual steps, all handled by one team member:

Mapped this way, the problem was plain to see. None of the eight steps connected to the next, so each one waited on a person. We rebuilt the sequence in Make, connecting Notion, Go High Level, Jotform, Google Drive, Gmail and Slack, and added a control panel where an operator can switch a single client’s onboarding on or off. Onboarding that took hours per client now finishes in under a minute, and the team saves about five hours per client.

Affinity Care is the larger version of the same exercise. Mapping every tool, spreadsheet and manual handoff between departments showed five disconnected systems, each owned by a different team. Once those flows were rebuilt in one Airtable base, caregiver onboarding dropped from 21 days to 8.

What is the best tool for mapping a business process?

The best tool for mapping a business process is the one your team will actually open. Lucidchart, Miro and Microsoft Visio are the common choices, and a whiteboard or sticky notes work well for the first draft. The quality of the map depends far more on talking to the right people than on the software you draw it in.

We do not sell a diagramming tool, so there is no reason to push one. What matters more is where the map ends up. A map that lives only in a drawing file goes out of date the day the process changes. A map that becomes the structure of the system, with each step a status, each handoff a trigger and each lane a role with its own view, stays current because the work runs through it.

How does a process map turn into automation?

A process map turns into automation in three passes. First, cut the steps that only exist to move information between tools. Second, automate the steps that follow a fixed rule, like sending a form, creating a folder or chasing a missing document. Third, keep people on the steps that need judgment, and tell them when it is their turn.

That order matters. A machine does exactly what it is told, including a broken process at scale, which is why we map before we automate a process. The map is also the first thing an operations audit produces, and it is part of what a client keeps when we hand the system over.

Frequently asked questions

What is business process mapping in simple terms?

It is drawing how a piece of work gets done in your business, step by step, with the name of the person or tool that does each step. The drawing shows the places where work stalls or depends on someone’s memory, and that is what makes it useful.

What is BPMN?

BPMN, Business Process Model and Notation, is a standard set of symbols for drawing process maps, maintained by the Object Management Group. It suits large organisations and software teams that need diagrams precise enough to execute. Most small businesses get more from a simple swimlane map that everyone on the team can read.

Who should be involved in process mapping?

The people who do each step, plus someone who can decide how the process should change. The owner alone will describe the official version. The team describes what really happens, workarounds included, and the gap between the two versions is usually where the biggest savings sit.

This is the first step of every operations consulting engagement we run.