How to Map a Business Process When Nobody Follows the Same Process
When different people handle the same task in different ways, it becomes difficult to see where work gets stuck. Learn how to map the process as it really happens and identify what needs to change.
The process on paper is not always the process people follow
A business may have a documented process for handling a customer enquiry, preparing a quote or completing a service request.
But ask three people how they do the work, and you may get three different answers.
One person updates the CRM immediately. Another keeps notes and updates it later. A third uses a spreadsheet because it is easier to track what is waiting.
Everyone may be trying to get the job done properly. Yet the work moves differently depending on who handles it.
This makes it difficult to understand why things get delayed, why information goes missing or why customers receive different experiences.
Before changing the process or introducing new software, you need to understand what people actually do.
That starts with mapping the work as it happens, not just how it is supposed to happen.
Start with one piece of work
Trying to document every process in a business at once can quickly become a large project.
Start with one instead.
Choose a process that regularly causes confusion, delays or extra work. For example:
- An enquiry coming in and becoming a confirmed job.
- A quote being prepared, sent and followed up.
- A customer request passing from one team to another.
- A completed job being checked and reported.
Then follow one real example from beginning to end.
Do not start by asking everyone to describe the ideal process. Ask them to walk you through a recent piece of work.
What happened first? Who handled it? What information did they need? Where did they record it? Who picked it up next?
A real example often reveals details that people forget when describing a process from memory.
Speak to the people doing the work
A manager may understand the intended process, but the people doing the work often know where it becomes difficult.
Speak to the people involved at different stages. If possible, ask each person to explain their part separately before comparing their answers.
You are looking for differences, not trying to decide who is doing things incorrectly.
One person may believe that updating the CRM is the next person's responsibility. That person may believe the update should already have been completed.
Someone else may be maintaining a separate tracker because they cannot easily see what is waiting in the main system.
These details matter.
If people are using different methods, ask why. There may be a practical reason behind the workaround, even if it creates problems elsewhere.
The aim is to understand what the process requires from people and where the current way of working makes that difficult.
Map the steps simply
You do not need specialist software or a complicated diagram to begin.
Start by writing down each step in order. For every step, note who handles it, what information they need and what happens next.
For example, imagine a business handling a new customer enquiry.
Step 1: The enquiry arrives
A customer sends an enquiry by email or through the website. Someone needs to make sure it is received and recorded.
Step 2: The details are recorded
A team member enters the customer's information into the CRM. If important details are missing, someone may need to contact the customer again.
Step 3: The quote is prepared
The person preparing the quote uses the customer details. If the information is stored elsewhere, they may have to copy it manually.
Step 4: The quote is sent
The customer receives the quote, but the next action is not always clear. Should someone follow up? When? Who is responsible?
Step 5: The next action is recorded
If nobody records what needs to happen next, the enquiry may sit untouched until someone remembers to check it.
This is an illustrative example. Your own process may look different.
The purpose is not to create a perfect diagram. It is to make the work visible, from the first step to the last.
As you map the process, note who is responsible at each stage, what information they need and where work can wait or become unclear.
Pay particular attention to handovers. Work often becomes difficult to track when responsibility passes from one person to another.
Look for the gaps, not just the steps
Once you have mapped the process, look for the places where work slows down or becomes harder than it needs to be.
Ask a few questions:
Where does work wait?
Is a task sitting in an inbox because nobody knows who should handle it? Does someone need to chase another person before moving forward?
Where is information repeated?
Are details copied between systems, re-entered into spreadsheets or requested again because they are difficult to find?
Where does the process depend on memory?
Does someone need to remember to follow up, update a record or notify another team member without a clear reminder or agreed routine?
Where is ownership unclear?
Can you identify who is responsible for the next action at every important stage?
Where do people use workarounds?
A separate spreadsheet, private task list or repeated WhatsApp message may be a clue that the normal process does not give someone what they need.
Do not assume every workaround is unnecessary. First understand what problem it solves.
Do not force everyone to work identically
Finding differences between people does not mean every step needs to be standardised.
Some variation is reasonable. Different customers may require different handling, and experienced team members may need flexibility in how they complete certain tasks.
The question is whether those differences create avoidable problems.
For example, team members may prepare quotes in different ways, but the business may still need a consistent place to record the final amount, the date sent and the next follow-up action.
You can standardise the information and responsibilities that matter without prescribing every detail of how someone works.
A useful process should make the important things clear while allowing reasonable flexibility.
Fix the most important gap first
After mapping the process, you may identify several problems. Resist the temptation to fix all of them at once.
Choose the gap that causes the most meaningful difficulty and start there.
The answer may be as simple as assigning one owner to each enquiry, agreeing when a record must be updated or making the next action visible to the team.
In other cases, the business may need to change how an existing CRM is configured, clean up its data or connect two systems.
Automation can help when a task is repetitive and the underlying process is clear. But automating an unclear process can make confusion happen faster.
Start with the problem. Choose the simplest change that addresses it. Then test that change on real work before rolling it out more widely.
A simple exercise to try this week
Choose one recent piece of work that took longer than expected or required unnecessary chasing.
Write down:
- Every step from the beginning to the end.
- The person responsible at each step.
- The information or tool needed to move forward.
- Where the work waited, was repeated or became unclear.
- One change that could prevent the same problem next time.
Then check your map with the people involved. Ask whether it reflects what really happened, including the workarounds.
You do not need a perfect diagram. You need a clear enough picture to see what is getting in the way.
Understand the work before changing the system
When a process is inconsistent, buying another tool or writing a new procedure may seem like the quickest response.
But neither will necessarily solve the underlying problem.
A simple process map gives you a better starting point. It shows how work moves between people and systems, where responsibility becomes unclear and which steps deserve attention first.
That is often enough to identify a practical first improvement without turning the exercise into a large transformation project.
At Opriva, the starting point is understanding where work gets stuck, then fixing the simplest thing that needs fixing.
If a process in your business works differently depending on who handles it, tell us where work is getting stuck.