Software is usually bought to fix a problem that somebody described in a meeting, and the description is rarely how the work really moves. A map made before you buy shows where the time goes, where information is typed twice and which problems software can solve at all. It needs no special tools, only a few days, somewhere to write and the people who do the work.
What You Need Before You Start
One journey
A single thing to follow from start to finish, such as an order, a job, a booking or a purchase.
The people who do it
Time with the staff who handle that journey every day, in addition to the manager who oversees it.
Real examples
The last five or ten that went through, including one that went wrong, so that you map what happened.
Step 1: Pick One Journey
Mapping the whole business at once produces a diagram nobody can read. Choose the journey that carries the most money or attracts the most complaints, and follow it from the first contact with the customer to the money arriving in the bank. For a contractor that might be a job from enquiry to final invoice, and for a wholesaler it might be an order from the buyer's first message to delivery.
Step 2: Walk It With the People Who Do It
Sit beside each person who touches the journey and ask them to show you the last real one they handled. Watching somebody do the work tells you more than asking them to describe it, because people leave out the steps they no longer notice, such as the spreadsheet they keep on the side or the message they always send to check a figure. Those unofficial steps are often where the system on paper and the system in use have drifted apart.
Step 3: Write Down Every Handover
Each time the work passes from one person or system to another, record three things: who hands it over, how they do it and what the next person has to enter again. The "how" matters, because a handover by email, by a shared spreadsheet, by a messaging group or by word of mouth each fails in its own way. By the end you should have a simple line of boxes and arrows that anyone in the business would recognise.
Step 4: Mark the Four Kinds of Trouble
Go back along the line and mark each place where one of these happens.
| Mark | What it means | A typical example |
|---|---|---|
| Waiting | The work stops until someone acts | A quote sits in an inbox until a director approves it |
| Typed twice | The same information is entered again | An order is keyed into the stock system and then into accounts |
| Checked by hand | A person compares two things to catch mistakes | Delivery notes are ticked off against a printed order |
| In one head | Only one person knows the rule | One planner knows which crews can work on which sites |
Step 5: Count, Roughly
For each mark, estimate how often it happens in a week and how long it takes. The figures do not need to be precise, since the aim is to tell a nuisance that costs ten minutes a week from one that costs two people a day each. Counting also settles arguments, because the problem the business talks about most is not always the one costing it the most.
Step 6: Read What the Map Is Telling You
| What the map shows | What it usually calls for |
|---|---|
| Information retyped between two tools you want to keep | A connection between them, which is far smaller than a new system |
| A step that exists only to catch another step's mistakes | A system that prevents the mistake at the point it is made |
| Rules that live in one person's head | The rule written into the system, so that the business no longer depends on one person being in |
| Trouble at almost every handover | One system for the whole journey, shaped around how you work |
Some of what you find will have nothing to do with software
A map often shows an approval nobody needs any more, or a decision that no one owns. Fix those first, because they cost nothing to change and any software you add afterwards will be simpler for it.
What to Take to a Supplier
Take the map, the counts and the three marks that cost you the most, and ask every supplier to show how their product or their proposal handles your real journey from end to end. A demonstration built around your own order or job is far harder to dress up than a standard one, and it makes the quotes you receive much easier to compare. If a supplier cannot follow your map, that tells you something useful before any money has been spent.
Common Questions
A few days for most businesses, spread over a week so that it does not take people away from their work for long. Journeys that cross several departments or sites take longer, mainly because of the time needed with each team.
You can make a first map yourselves, and it is worth doing even if you later bring someone in. Outside help earns its place when a journey crosses departments that do not agree on how it works, or when the people closest to the process can no longer see its workarounds.
No. Start with the journey that carries the most money or causes the most complaints. One good map is enough to make a sound first decision, and each later one takes less time because the method is already familiar.
Mapping an operation is how BY BANKS gets to know a business before designing anything for it, and it is often where our consultancy work begins, before anyone decides what to build, buy or leave alone. If you would like it done with you, or want a second opinion on a map you have made, get in touch, or read how the map becomes bespoke business software.
Ready to Build Something?
If this resonated, let's talk about how we can apply these ideas to your business.
Start a Conversation