How-to
How to map a business process before you automate it
Most of the gain from automation comes from mapping and fixing the process first. Here is how to draw a real workflow on paper, from the trigger to the last step, and fix it before you spend anything on AI.
Founder and lead engineer
- Published
- Updated
- Reading time
- 10 min read
Why map a process before automating it?
Because automating a broken process just makes it break faster. A map shows where work really stalls, repeats and changes hands, so you can delete and simplify first. Most of the payoff comes from fixing the process; only what is left after that is a real candidate for AI.
A tool inherits whatever process you point it at. Aim AI at a messy workflow and you get the same mess, running faster and harder to see. That is a big reason MIT’s Project NANDA found 95% of enterprise generative AI pilots delivered no measurable return, with the main cause traced to mismanaged adoption (Fortune). The firms that get results do the unglamorous work first. McKinsey found AI high performers were about three times more likely to fundamentally redesign their processes than everyone else (McKinsey).
Mapping is the front half of how we work, the Map step in Map, Redesign, Match, Embed. You do not need us, or any software, to start. A pen, an hour and an honest account of what really happens are enough.
If you cannot draw the process, you cannot automate it.
How do you map a business process? (6 steps)
Pick one painful, frequent process. Write every step as it really happens, including the unofficial parts. Mark who does each one, how long it takes and the tools used. Find the stalls, rework loops and handoffs. Delete, simplify and standardise, and only then flag what is left for AI.
The whole method fits on one page. Work through the six steps in order. The first five involve no technology at all.
- 01
Pick one painful, frequent process
Choose a single workflow that hurts and happens often: handling an inbound lead, processing an invoice, onboarding a client. Do not try to map everything. One finished map of a process with a clear start and a clear end is worth more than ten half-finished diagrams. - 02
Capture every step as it really happens
Write each step in the order it actually occurs, including the parts the official SOP leaves out. Sit with the people who do the work and record the shortcuts and workarounds. The honest map is messier than the documented one, and that gap is where most of the waste hides. - 03
Mark owner, time and tools for each step
For every step, note who does it, roughly how long it takes and which tools or systems they touch. A flat list becomes a picture of cost and effort: the time-eaters and the jumps between people and apps appear straight away. - 04
Find the stalls, rework loops and handoffs
Mark where work waits, where it loops back for corrections, and every point it changes hands. Flag the “it depends” decision points too, because those judgement branches shape what you can and cannot standardise. - 05
Delete, simplify, standardise
Fix the map before any tool. Cut steps that exist only by habit, simplify what is overcomplicated, and standardise decisions that do not truly need judgement. Most of the gain usually comes from this step, and it costs nothing in technology. Never automate the broken original. - 06
Mark what is left that AI could do
On the cleaned-up map, flag the remaining steps that are repetitive, rule-based and checkable, such as drafting a reply, classifying a request or pulling data into a form. Those are your AI candidates. Judgement, empathy and true edge cases stay human. Only now do you match a tool.
What does a finished process map look like?
A finished map is a numbered list of every real step from the trigger to the last step, each tagged with who does it, how long it takes, the tools used and whether it stalls. The bottlenecks and rework loops stand out, the “it depends” branches are flagged, and a handful of steps are marked as honest AI candidates.
Take an illustrative example: handling an inbound lead. The trigger is a form submission. The official process is three steps. The real one looks more like this: a salesperson sees the email whenever they next check their inbox, copies the details into the CRM by hand, looks the company up, drafts a reply from memory, waits on a manager to approve pricing, then chases the lead three days later because the first reply sat in drafts. That is seven steps, two stalls, one rework loop and a handoff that depends on who is online.
Written down, the problems are obvious. The lead goes cold in the gap between “form submitted” and “someone notices”. The manual CRM entry is pure copy and paste. The pricing approval is a real it depends: sometimes standard, sometimes a judgement call. A good map makes all of that visible before anyone argues about which tool to buy. Use the template below to capture yours the same way.
The copy-paste template
No download needed. Copy these eight columns into a document or onto a whiteboard, one row per step, and work down your process.
| Column | What to write |
|---|---|
| Step name | What happens, in plain words (for example, “copy lead into CRM”) |
| Trigger | What kicks this step off: a form, an email, the previous step finishing |
| Who does it | The person or role who actually does it |
| How long | Rough time it takes, plus any waiting before it starts |
| Tools used | Every app, document or system the step touches |
| Decision points | Any “it depends” branch or judgement call here |
| Where it stalls | Waits, rework loops or handoffs that lose time |
| Automate? (Y/N) | Filled in last, only after you have fixed the process |
How do you know which steps AI should handle?
A step is a strong AI candidate when it is repetitive, rule-based and checkable: same input, predictable output, easy to verify. Keep people on anything that needs judgement, empathy or handling of messy edge cases. The test is simple: if you cannot write the rule down, AI cannot reliably follow it.
On the inbound lead map, the copy and paste into the CRM and the first-draft reply are textbook candidates: repetitive, rule-based and easy to check before they go out. The pricing decision is not. It carries judgement and risk, so a person stays in the loop. An agent can prepare the options, and a person signs them off. This is also where you may decide you need no tool at all. Sometimes the fix is a shared inbox rule, and we sometimes tell clients exactly that.
Strong AI candidates
- Repetitive, same-shape work: copy and paste, data entry, formatting
- Rule-based decisions you can write down as if this, then that
- First drafts a person still reviews before they go out
- Outputs that are quick and easy to check for correctness
Keep these human
- Judgement calls: pricing, exceptions, trade-offs
- Anything that needs empathy, trust or a real relationship
- True edge cases and one-offs with no clear rule
- Decisions where a wrong answer is costly and hard to undo
What do you do after you have mapped it?
After mapping, you redesign the process around the fixes you found, match the right tool to each remaining AI candidate, then embed it in the daily workflow and measure the result. The map is the input to every step that follows.
That is the back half of our method: Redesign, Match, Embed. If you mapped honestly, the most useful part of the work is already done. If you want help with the rest, there are two routes. The AI consulting and audit reviews your map, or builds it with your team, and hands you a ranked roadmap with a fixed quote. Once the candidates are clear, done-for-you agents on Qoren or custom AI agent development pick up the build.
You can also talk a workflow through on a free 30 minute call. The map comes first, and you can do most of it today with a pen.
Work with Magentic
What we offer
- Done-for-you AI agentsWe set up agents on Qoren and hand them over working.From $2,000
- Custom AI agent developmentAgents built on your own cloud or the stack you already use.Fixed-price quote
- Support and maintenanceMonitoring, fixes and updates for agents already in production.Flat monthly retainer
- AI consulting and auditA ranked list of what to automate, and what it would cost.€1,200 to €1,800
FAQ
Questions
What is business process mapping?
Business process mapping is writing down every step of a real workflow in order, from the trigger that starts it to the result that ends it, and marking who does each step, how long it takes and where it stalls. It turns a fuzzy process that lives in people's heads into something visible you can fix, standardise or automate.
Do I need special software to map a process?
No. Paper, a whiteboard, sticky notes or a plain document work for almost every small business. The value comes from the thinking. A clear list of steps in order is more useful than a fancy diagram nobody finishes. Reach for dedicated mapping software only once the process is genuinely large or branching.
How detailed should a process map be?
Detailed enough that someone new could follow it and do the job, but no more. Capture every real step, decision point and handoff, including the rework and the “it depends” branches, but do not drown it in sub-steps. If a step never changes the result or who acts next, you can usually fold it in.
How long does it take to map a process?
A single, well-bounded process usually takes a couple of hours to map honestly, longer if several people have to compare how they each do it. Most of that time goes into surfacing the unofficial version and the exceptions. Do not map ten processes at once; one clear map beats ten half-finished ones.
Can AI map my process for me?
AI can help draft and tidy a map once you feed it the steps, but it cannot see how work really happens in your business: the workarounds, the bottleneck, the unwritten rules. The accurate first version has to come from the people who do the job. Use AI to tidy the map after that.
Can someone map our processes for us?
Yes. The Magentic AI consulting and audit interviews the people who do the work, maps how it really flows, and hands you a written roadmap with the opportunities ranked by return and a fixed quote to build them, for €1,200 to €1,800. The roadmap is yours to keep, whoever builds it.
Sources
Written by David Silva
David has shipped production software for more than ten years, including enterprise work for Bentley Motors and L'Oréal. He designed and wrote every layer of Qoren, and runs every Magentic project himself.
More about David