When a process feels slow, the obvious fix is to buy software or automate it. Sometimes that works. Just as often, it makes a messy process run faster, with the same gaps, duplicate steps and waiting, now hidden inside a tool that is harder to change than a checklist.
Mapping the process first takes a few hours. It shows you where the time actually goes, which steps add nothing, and which parts are repetitive enough to hand to a machine. It also gives you a clear brief for any tool you do end up buying.
Here is the way we map a process, with a template you can copy into a document or a spreadsheet.
Pick one process and draw its edges
Start with a single process that matters and repeats often, such as handling a new enquiry, sending an invoice or processing a return.
Then write down its boundaries:
- Trigger: the event that starts it, for example "a customer submits the quote form".
- End point: the moment it is finished, for example "the signed quote is saved and the job is booked".
- Volume: roughly how many times it runs in a week or a month.
- Owner: the person who would be asked if it went wrong.
Without clear edges, a map tends to sprawl into neighbouring processes and never gets finished.
Write the steps as they really happen
Sit with the people who do the work and walk through a recent real example, not the version in the procedure manual. Write each step as a short verb phrase, such as "copy customer details into the CRM", "email the quote as a PDF" or "chase for signature".
For each step, note four things:
- Who does it (a role rather than a name, where possible).
- Which tool or document they use.
- How long the work itself takes.
- How long it waits before the next step starts.
The last one matters more than people expect. A quote that takes twenty minutes to prepare can still take a week to reach the customer if it sits in an inbox waiting for approval.
Cover the exceptions too. What happens when information is missing, the customer changes their mind, or the person who normally approves is on holiday? Exceptions are often where the manual work hides.
Spot hand-offs, waiting and rework
With the steps written down, go through the list and mark three things.
Hand-offs
Every time work passes from one person to another, information can get lost and the task can sit in a queue. Mark each hand-off. If a single process has six or seven of them, ask whether some steps could be done by the same person.
Waiting time
Highlight any step where the wait is longer than the work. Then look for the cause. It might be an approval only one person can give, a batch that only runs on Fridays, or a missing piece of information that has to be chased.
Rework
Mark any step that exists only because something earlier went wrong: correcting details, re-sending a document, asking the customer for information they already gave. Rework usually means the real problem sits upstream, often in how information is collected at the start.
Decide what to drop, simplify or automate
Now give each step one of four labels. We work through them in this order on purpose, because automation should come last.
| Label | Question to ask | Typical example |
|---|---|---|
| Drop | Would anyone notice if this step disappeared? | Printing a form only to scan it again |
| Simplify | Could it be done with fewer people, fields or approvals? | Two sign-offs on small purchases |
| Automate | Is it repetitive and done by the same rule every time? | Copying form answers into the CRM |
| Keep | Does it need judgement or a conversation? | Agreeing the scope of a job with a client |
A step is a good candidate for automation when the input is predictable and a mistake is easy to spot and fix. Steps that need judgement, or that only happen a few times a year, rarely justify the setup effort.
Once you have dropped and simplified, redraw the process. The new version is the one you automate, and it may well be several steps shorter than the original.
A template you can follow
Fill in one row per step, using the columns below. The example is a hypothetical plumbing firm handling quote requests, and all of the times are illustrative.
| Step | Who | Tool | Work | Wait after | Note | Label |
|---|---|---|---|---|---|---|
| Read the website enquiry | Office manager | Shared inbox | 5 min | Up to 1 day | Hand-off to engineer | Automate an alert |
| Phone for missing details | Office manager | Phone | 10 min | 1 to 2 days | Rework, form lacks fields | Simplify the form |
| Copy details to job sheet | Office manager | Spreadsheet | 10 min | Same day | Typed twice | Automate |
| Assess the job | Engineer | Phone or visit | 30 min | 2 to 3 days | Hand-off back to office | Keep |
| Write the quote | Engineer | Quote template | 20 min | 1 to 2 days | Waits for owner approval | Simplify approval rule |
| Print, sign and scan | Owner | Printer | 10 min | Same day | Adds nothing | Drop |
| Send and chase | Office manager | 10 min | Varies | Chased from memory | Automate a reminder |
In this example the work adds up to about an hour and a half, while the waiting can stretch past a week. That gap is the first thing to look at.
Under your own table, answer these questions:
- Where does the longest wait happen, and why?
- Which information is asked for more than once?
- Which steps exist only to fix an earlier mistake?
- What does the process look like with the dropped and simplified steps taken out?
- For each step labelled Automate, what exactly should happen, and what triggers it?
The answer to the last question becomes your brief for any tool. Hand it to a supplier and ask them to show how their product handles each of those steps.
Before you buy anything
A few checks we would run before spending money on a tool:
- Run the simplified process by hand for two or three weeks. If it still has problems, a tool won't fix them.
- Agree who owns the process after the change, including who updates the automation when something changes.
- Write down what happens when the automation fails. Someone should notice, and there should be a manual fallback.
- Measure the process before and after on two or three simple numbers, such as days from enquiry to quote sent and how often customers are chased for missing details.
Sometimes the map shows that the biggest improvement comes from removing steps, and the tool you were about to buy can wait. When automation does make sense, you will know exactly what you need it to do.
An automation map along these lines, covering your main processes, is one of the documents we write at Noovotic.
Examples in this article use hypothetical businesses and illustrative numbers. It is general information, not advice for your situation.
Automation Opportunity Map, $89 one-time
Five of your processes reviewed step by step, with what to automate, what to simplify and the type of tool for each.






