How to Map a Business Process Without Complicated Software
Every business has processes. They are the ways work moves from a first message to a finished job and a paid invoice.
However, most are never written down. They live in habits, inboxes and people's heads.
Mapping a process simply means drawing it, so you can see it. You do not need complicated software to do that. Instead, paper, sticky notes and the people who do the work are enough.
This article starts with the business. First, it explains what a process map is. Then it gives seven steps to draw one. Finally, it shows what to do with it.
What a process map is, and is not
A process map is a picture of the steps in a piece of work. It shows who does each step, where the information goes and where things wait.
It is not a policy manual. Nor is it a perfect diagram. Instead, it is a working tool for seeing what really happens.
The GOV.UK Services in government blog makes a helpful point in its step-by-step guide to service mapping. It says there is no single required map, correct method or best template. It also says that trying is inexpensive. So you can discard a map that is not useful.
That is reassuring for a small business. Because trying costs so little, a rough map is better than none.
What you need
You need very little. In fact, the guidance suggests much the same kit.
- Paper, ideally a long roll, or large sheets taped together.
- Sticky notes, so each step can be moved.
- Marker pens and tape.
- A wall or a large table.
- The people who do the work.
For example, NHS England's Service Improvement Guide suggests paper on a wall, coloured sticky notes and marker pens. It says to write each step on its own note, so steps can be moved or added. It also suggests taping the notes down, because they can fall off in a warm room.
The same guide also keeps a flip chart labelled 'Car Park' for issues that cannot be settled in the session. That is a handy idea for any team.
Seven steps to map a business process
These steps adapt the guidance for a small business. However, they are our own practical suggestions, not research findings.
1. Pick one process and set a start and an end
Choose one process that matters. For example, you might choose everything from the first enquiry to the first invoice. The NHS guide advises agreeing the start and end before you begin.
2. Say what the map is for
The GOV.UK guide begins with purpose. For most businesses, the purpose is simple: to see what happens today. So leave redesign for later.
3. Gather the people who do the work
Include everyone who touches the process, not only managers. The NHS guide suggests people who support, deliver and manage the whole process. It also recommends ground rules that focus on the process, not on individuals.
4. Map the big steps first
Start high. Improvement Cymru suggests a first map of no more than six to ten steps. Then write each one on a note and put them in order.
5. Add detail where it helps
Next, go through each big step. Add who does it, what information they use and where it is kept. Also note any waiting time. The NHS guide advises mapping what happens most of the time, because rare exceptions can distract.
6. Mark the friction
Now use a different colour of note, or a pen, to mark where things go wrong. For example, mark hand-offs, waits, retyping and any step that depends on one person's memory. These are the gaps between people, information, systems and processes.
7. Check it, then choose what to change first
Show the map to people who were not in the room. Ask whether it is true. Then pick one or two changes to try first. After all, the NHS guide says a map is a tool for finding change, not an end in itself.
Three simple ways to lay it out
You do not need a special format. However, a few layouts work well on paper.
- A line of notes. Put the steps in a row, from left to right. This is the easiest start.
- A table. Use columns for the step, who does it, where the information lives and how long it waits.
- Swim lanes. Draw a row for each person or team. Place each step in the row of whoever does it.
Improvement Cymru lists swim lanes as one common type of map. Pick the layout that makes the process easiest to see. Then, if it stops helping, change it.
Common mistakes
Improvement Cymru's guide warns against several habits. However, we would add one more.
- Mapping what should happen, instead of what actually happens.
- Focusing on individuals, instead of the process.
- Recording one-off events, instead of what usually happens.
- Stopping where one team ends, instead of mapping end to end.
- Changing things before understanding how the current process works.
- Spending too long polishing the map. The GOV.UK guide warns about this too.
The first mistake is the most common. People describe the process as it is written, or as they wish it ran. So ask for a real example, and trace what really happened.
What to do with your map
A map on its own changes nothing. So use it to ask better questions.
The NHS guide suggests four ways to improve a mapped process: eliminate, combine, simplify and sequence. In other words, ask whether a step can stop, merge with another, become easier or move earlier.
After that, three more decisions follow naturally.
- Which record is the agreed home for each kind of information?
- Which steps suit technology, and which need a person?
- Is the process now clear enough to automate?
Each question has its own article. The reading list below shows where to go next.
When software starts to help
Software is not the enemy. However, it works best after the map is clear.
It may help when many people need to see and edit the map. It may also help when the process is stable, or when you need to share it beyond one room. Even then, a simple digital whiteboard is often enough.
However, the thinking still comes first. A tool can draw a confused process neatly. Yet it cannot make it clear.
An illustration: mapping a process in a morning
This example is invented to show the idea. It is not a client story.
Imagine a small services firm. The owner and three colleagues map the journey from accepted quote to paid invoice. For this, they use a roll of paper and sticky notes.
First, they agree six big steps. Then they add who does each one. Next, they mark the friction in pink pen.
They find two things. First, details are retyped into the invoice by hand. Second, nobody owns the chase when payment is late.
So they make two changes. They enter the details once, and they name an owner for payment chasing. As a result, no new software is needed.
That is a small result. However, it comes from seeing the work clearly.
Where to go next
Mapping is the first step in a connected business. The articles below follow on in the order most readers need them.
- What Happens After a Customer Enquiry? Map the Process Before You Automate It applies this method to one process.
- What Is a Single Source of Truth, and Does Your Business Need One? helps you choose the agreed record.
- Why Your CRM Data Is Out of Date Before the Week Ends explains why records fall behind.
- How Many Business Tools Does a Small Business Actually Need? helps you count jobs, not apps.
- Where AI Should and Should Not Sit in a Small Business Process shows where AI belongs on your map.
- Does Your Business Need a New CRM or a Clearer Process? helps you decide whether to replace or reconnect.
You can also see how a connected process works in practice in the Bridging Loans Broker case study.
Frequently asked questions
What is a business process map?
It is a picture of the steps in a piece of work. It shows who does each step, where information goes and where things wait.
Do I need software to map a business process?
No. Paper, sticky notes and the people who do the work are enough. However, software can help later, once the process is clear.
How long does mapping take?
The NHS guide allows half a day to draw a health-service pathway and half a day to analyse it. A smaller process may take less time. However, the scope and the people involved will decide.
How detailed should the map be?
Start with six to ten big steps. Then add detail only where it helps. After all, you can always go deeper later.
Who should be in the room?
Include the people who do the work across the whole process. Also include those at the start and the end, not only managers.
What should I do once I have a map?
Look for hand-offs, waits and retyping. Then choose one or two changes to try first. Finally, review the map again after a few weeks.
Start with the business
Before you buy, connect or automate anything, it helps to see how the work actually flows. Often, a rough map on a wall is the clearest starting point.
The Davina Connect Business Review looks at people, information, systems and processes together. The recommendation never starts with a tool.
Explore the Business Review →