Creating a process map: an example and choosing process no. 1
Creating a process map, for us, means putting every recurring process in your business on one list: who does it, how often, how long, where the work comes in, which system it's done in, and whether it needs thinking or just doing. Process map is our word for exactly this list. Business process automation with AI agents, or AI employees as we call them, starts here: the map answers which processes you can automate, for your business rather than in general. The short answer: those that run the same way each time, whose rules someone on your team can demonstrate, and where you only want to know at the end that they're done. In a business with a team, several usually qualify. The real question is which one goes first. This article shows how the map comes together, what it looks like in an example, how to sort each process and how process no. 1 comes out of it.
Why the question sounds different in a business with a team
If you work alone, you know your processes, because you do them yourself. In a business with a team, the people who handle a process every day know it best. They know which cases come up, where things get stuck and what gets left undone. The owner often knows the version from a few years ago, or how it's supposed to work.
That leads to a typical mistake. Without an overview, you start with the process that annoys you most right now. That feels right. But it's rarely the one that saves the most time or money, and sometimes it's the hardest, because it's full of exceptions.
So we turn the order around: collect, sort, score, choose. That's how the first month of Owner Autonomy starts: with a map of all your recurring processes, made with your team.
The process map: everything that recurs, on one list
The map is a table: one row per process, one question per column. In our template, the worksheet is called "Process Inventory".
It has these columns:
- Process: a short name with an action word, such as "Match delivery notes".
- Area: marketing, sales, fulfillment, customer service, bookkeeping and finance, HR, admin and back office, leadership and management.
- Who does it today? A role or a name. "Me" counts too, and often reveals the most.
- Trigger: A fixed time, an event such as an incoming email, or a nudge, where somebody says "go".
- Start, work, end: What's on the table, what gets done, how can you tell it's finished?
- Handoff and report: Who gets the result, and who learns it's done?
- How often and how long: Times per month and minutes per run, honestly estimated, with rework and follow-up questions. That gives hours and cost per month.
- Input and systems: Email, mail, portal or phone, and the software used.
- Thinking or doing? More on this in a moment.
- Irreversible? Is there a step that can't be undone?
- Pain today: What annoys, where do mistakes happen, what gets left undone?
Two columns deserve a closer look.
The "nudge" trigger. If a process only starts because somebody says "go", that somebody is needed, and very often that's you. Nudge processes are a good indication of where your business depends on you. For each one, ask: could this be a fixed time or an event?
Start and end. This is the real test of a process. "Customer service" has no start and no end; it's a whole area of work. "Take a complaint by email and pass it on to the warehouse" has both. If you can't name start and end for an entry, split it into two or three processes.
How the map comes together with your team
You don't collect alone. First, go through area by area and write down what comes to mind. Then talk to everyone on your team who does recurring work. A short conversation each is enough, with six questions:
- What do you do again and again, daily, weekly, monthly?
- What starts it: a time of day, an email, a call, somebody saying "go"?
- What's in front of you then, and what's finished at the end?
- Who do you pass it on to, and who finds out it's done?
- How long does it take once, with follow-up questions?
- What annoys you, what gets left undone, where do mistakes happen?
Say openly what it's for: finding work an AI employee can take on. People who know why they're asked answer more precisely.
One trap when estimating: people list only what takes "a lot" of time, and the small tasks slip through. Yet they add up: 5 minutes, 20 times a day, comes to 35 hours a month.
Without a map, you overlook exactly those processes.
Thinking or doing: the most important column
Not all work should run on its own. Some work you don't want to give away, because it's about ideas, judgment and decisions. For that, there are AI employees you work with in conversation, as thinking partners. Other work simply has to get done, and you just want to know it's done, with a report. For that, there are AI employees that take over processes.
Our home page says: the levels apply to AI employees that take over processes. AI employees you develop ideas and concepts with keep working with you in conversation.
Doing goes onto the four autonomy levels, described in our main article The four autonomy levels: how a process in your business runs on its own.
Here's how to sort:
Doing, if most of these are true:
- The steps are similar every time, even if there are variants.
- Someone on your team could write down or show the rules.
- At the end, you can check whether it's right.
- Afterwards, you want a report, not a conversation.
Thinking, if these fit better:
- The result depends on your judgment or your taste.
- There's no "right", only "better".
- You'd rewrite the result yourself every time.
Unclear usually means two processes in one. Our template's sample sheet, which shows a tax advisory firm, has an example: "Prepare a client meeting" is thinking. "Gather and file the client's documents" beforehand can be doing. Split such entries.
Many variants are fine. A process stays doing if every distinction can be written as a rule and demonstrated. And don't mark everything as doing because it feels like bigger savings. A thinking topic built as a process is back on your desk within two weeks.
Example of a process map
Kevin's own business could have a process map like this, sketched from the roles on our home page. He runs it with 14 AI employees: content, SEO, video editing, bookkeeping prep, leads and email. Input, system and "thinking or doing" are our assessment, not a measurement. The table is an excerpt.
| Process | Who does it | How often | Duration | Input | System | Thinking or doing |
|---|---|---|---|---|---|---|
| Deciding what's next, signing off | Kevin | … | … | the AI employees' reports | thinking | |
| Reviewing the AI employees' work | an AI manager, on trial | … | … | reports and logs | … | doing |
| Content: set topic and message, then write | content AI employee, with Kevin | … | … | Kevin's idea or brief | text files | both, so two processes |
| Videos: set selection and storyline, then edit | video AI employee, with Kevin | … | … | raw footage | video files | both: selecting is thinking, editing to a brief is doing |
| Website care for Google Search | an AI SEO employee, with Kevin | … | … | data from Google Search | website | both: deciding measures is thinking, analyzing and implementing by rules is doing |
| Bookkeeping prep | bookkeeping AI employee | … | … | receipts | bookkeeping | doing |
| Handling leads | leads AI employee | … | … | inquiries | contact list | doing |
| Handling email | email AI employee | … | … | inbox | doing | |
| 1:1 in the Owner Autonomy program | Kevin | weekly per business, per our home page | 60 minutes | appointment | … | thinking |
The example shows three things. First, "How often" and "Duration" are almost all gaps: without measured values, we write no numbers. In your map, these columns matter most, because they give the hours per month. Second, content, videos and SEO are mixed cases, two processes in one: judgment and taste are thinking, work to a brief is doing. Third, what needs judgment stays with Kevin: deciding, signing off, the 1:1. The column doesn't say whether a process already runs on its own; the levels do.
Choosing process no. 1: time, money, risk, feasibility
Only "doing" processes get scored, 1 to 5 points per criterion. Our template has six criteria; four are the focus here.
Time. How many hours a month go away? The basis is the hours from the map. A process that takes only a few minutes per run can still come out on top if it happens often.
Money. What does it cost per month, hours times hourly rate? What do its mistakes cost: rework, follow-up questions, late fees? The other direction counts too: some processes save little time but bring money in, such as checking open invoices. So our template scores the revenue lever separately.
Feasibility. Can an AI employee learn this today? Three questions decide:
- Digital or paper? Paper has to become digital first. That works, but it's one more step.
- Can it get to the data? Is read-only access enough?
- Are there clear rules? "It depends" is fine if someone can say on what. If nobody can, it's closer to thinking.
Note: feasibility is measured by the rules more than the technology. Access to a system can usually be sorted out. Whether your team can explain the rules decides whether the process runs soon.
Risk. What happens if there's a mistake? What counts most is whether a step is irreversible: a payment, a submission to a public authority, an email to a client. Such processes don't go first. When they come up, the irreversible step gets an approval point: the AI employee stops until a person explicitly says yes, every single time. So a lot of risk earns few points.
The worksheet also scores the revenue lever and team pain. Pain carries the least weight. It's no reason to go first, but it's a good tiebreaker.
From points to a decision
Each criterion has an adjustable weight. Points and weights produce a ranking, and the ranking is a proposal. You decide together, and for process no. 1, we check three questions:
- Can it run on its own by the end of month one?
- Does it have no step that can't be undone?
- Can someone on your team demonstrate it?
Three yeses make a good candidate. Nos. 2 and 3 get noted alongside. In Owner Autonomy, we lock in your process in writing by day 14 at the latest.
One warning: don't keep tweaking the weights until your favorite process comes out on top. Then you're only justifying what you wanted anyway. If your gut disagrees with the points, that's exactly what to talk about.
What comes after the choice
Once process no. 1 is chosen, the real work begins. First, it's written down so an AI employee can take it over: trigger, start, work per variant, end and report, plus the escalation path. How that works is covered in How to document business processes: the template for handing a process to an AI employee.
Then the AI employee is trained, and the process is at the first level: someone starts it, and your team checks every run. More on this in Autonomy Level 1, Assisted: when your team checks every run.
The map doesn't get put away. Only once a process is running does the next one come up, again from the map.
So a one-time overview becomes a plan for the coming months.
How this differs from a process map in quality management
In ISO 9001 quality management, a "process map" usually means a three-layer picture of the whole business, management, core and support, that organizes the major areas. Our map goes one level deeper and lists who does what, and how often. The purpose is different, and neither is wrong. We call the three-layer picture a process landscape. How it looks for a small business, and how it relates to the standard, is covered in Process landscape of a small business: core, management and support processes, with an example.
What this looks like for us
At a tax advisory firm, process no. 1 was filing digital tax assessment notices. On the map, you can see the lever: up to 30 to 40 notices arrive there per day, and the office team used to need about 2 minutes per notice. That sounds like little. On a full day, it's up to 60 to 80 minutes. How much of that goes away today, we haven't measured.
It also scored well on feasibility. The notices arrive digitally, and the rules can be demonstrated, even though the notice process as a whole, digital and paper, distinguishes around 45 of them.
Process no. 2 is the notices that arrive on paper: a very similar process with a different start, because they reach the firm's inbox by email. Filing them used to take the office team up to 2 hours, depending on volume.
The different start made it two processes. For it, a second AI employee came on board: it checks the inbox every 30 minutes, spots the emails with paper notices and hands them to the first AI employee, which files them. Both processes are at Autonomy Level 2, Autopilot (as of September 2026).
The map and scoring described here are templates from Owner Autonomy.
Their sample sheet shows a sample tax advisory firm with eight processes. Only two use the real numbers above; the rest are example values.
Runs without me
Every two weeks, one process that runs without the owner: what came in, what the AI did, where a person decided. Two minutes to read.
Worksheet
Process Potential Check
With five questions and a first process list to fill in, you find the process that could run on its own first. Comes as a PDF by email once you confirm your sign-up.
Strategy session
In a 20-minute strategy session, you tell us where things get stuck. We'll tell you honestly whether an AI employee is a good fit for you.
Book a strategy sessionFrequently asked questions
What is a process map?
For us, it's the list of every recurring process in a business, one row each, with the columns who, how often, duration, input, system and "thinking or doing". In quality management, the term often means the three-layer picture we call a process landscape.
Should I start with the process that annoys me most?
Only if it also comes out on top in the scoring. Annoyance is an honest signal, but a poor selection criterion. The most annoying process often has the most exceptions, which makes it the hardest start.
What about processes that arrive on paper?
They can be taken over, but they need one more step: the paper has to become digital first, for example as a scan that arrives by email. Such a process gets fewer points for feasibility. For process no. 1, one that already arrives digitally is usually the better choice.
Is a process that only takes a few minutes worth it?
If it happens often, yes. Hours per month matter, not minutes per run. The map has both, and the hours follow from them.
Who fills in the map?
You and your team together. You collect first, your team adds what you can't see. Without them, the processes that never cross your desk are missing, and you know those least.
Examples from everyday work
For ideas on which kinds of tasks suit AI at all, Kevin has eight examples of individual tasks, each with effort and limits: Automating Processes With AI: 8 Examples. This article is about something else: which process goes first in a business with a team, and why.
Your next step
No list from the internet answers which processes you can automate. The answer is in your own process map. If you want to know which process would be no. 1 for you, we'll look at it together on a call.