Why do teams struggle to map a process they run every day?
Teams struggle because the process lives in people's heads as habits, not as a sequence, so the first description you get is the happy path with the awkward parts left out. The exceptions, the waiting and the 'whoever is free' steps are exactly where delays and errors come from.
Take a fictional 25-person accounting practice, Lindqvist & Rao. The office manager, Priya, has been asked to map client onboarding before the firm hires two new staff. Her notes read: 'new client - Sam does engagement letter, sends by email, client signs (sometimes not for weeks). then ID docs - photo ID + proof of address, Jo checks. if missing chase twice then partner phones. once ok set up in practice software - Jo or Sam whoever is free. partner approves fee. if it's a company, Companies House check. welcome email.'
How do you build a process map step by step?
Build a process map by fixing the start and end points first, then listing each step as a verb and an object with one owner, and only then adding handoffs, decisions and exceptions. AI is good at turning notes into that structure quickly; it cannot know what really happens, so every gap it finds becomes a question for the team.
1. Set the boundaries
Name the trigger that starts the process (a client accepts a quote) and the outcome that ends it (the welcome email is sent).
2. List steps as verb plus object
'Send engagement letter', 'Check ID documents'. One action per step. If a step needs 'and', split it.
3. Give every step one owner
Use a role, not a name where possible. Owners become the lanes of a swimlane map. 'Whoever is free' is recorded as an open question, not an owner.
4. Mark handoffs
A handoff is where work moves to a different owner. Handoffs are where things wait, so note what is passed on.
5. Write decisions as yes or no questions
'Are all ID documents received?' Each answer needs its own next step.
6. List exceptions separately
Exceptions are the cases that leave the normal route: a client who never signs, a document that is out of date. Ask what happens and who decides.
7. Ask AI for a table before a picture
A table of step, owner, input, output and next step is easy to check line by line. Draw the diagram afterwards.
What does a weak and an improved AI process map look like?
Weak prompt: 'Make a process map of our client onboarding from these notes.' Typical result: a neat list of nine steps in a single line, starting with 'Client enquiry received' and including 'Add client to CRM', a step nobody mentioned. Every step happens in order, there is no owner, the chasing and the partner phone call have disappeared and the Companies House check applies to everyone.
Improved prompt: 'From the notes below, draft a process map as a table with columns: step number, step (verb plus object), owner role, input, output, next step. Start when the client accepts the quote and end when the welcome email is sent. Write decisions as yes or no questions with both outcomes. List exceptions separately. Do not add any step that is not in the notes. Where the notes are unclear, write the question I need to ask instead of guessing.'
The improved result shows six owned steps, two decisions ('Engagement letter signed?' and 'Is the client a company?'), one exception route for missing documents, and four questions for Priya: who sets up the software account when both Jo and Sam are free, when the partner approves the fee, how long the firm waits before the first chase, and what happens if the client never signs. Those questions are the most valuable part of the output.
How do you check a process map with the people who do the work?
Check a process map by walking through it with the people who perform each step, using one real recent case from start to finish, and recording every point where they say 'actually, we usually...'. Their corrections replace the draft, not the other way round.
Walk a real case
Ask Jo and Sam to trace the last client they onboarded. Where the case left the map, the map is wrong or incomplete.
Check each owner agrees
An owner who did not know they owned a step is a finding, not a typo.
Separate 'is' from 'should'
Map how the process runs today first. Improvements belong in a second version, clearly labelled.
Do process maps need a formal notation such as BPMN?
Most internal process maps need no formal notation; a swimlane diagram with boxes for steps and diamonds for decisions is enough. When maps feed automation or audits, Business Process Model and Notation (BPMN), maintained by the Object Management Group and published as ISO/IEC 19510, is the shared standard.
What are the common mistakes when mapping processes with AI?
The biggest mistake is accepting the AI draft as the process, which hides the exceptions and unclear ownership the map was meant to expose. Others: mapping the ideal process instead of the real one, letting the tool add steps from a generic template, and drawing a polished diagram before anyone has checked the table behind it. Keep personal client details out of the notes you paste; the structure is all the tool needs.
Where does this lesson sit in the Tosheo.ai catalogue?
Process maps is a Practitioner lesson in the AI for Operations category, alongside SOPs from notes, supplier comparisons, status reports and checklists and audits. You can see the full set on the AI training for operations teams page. The hands-on task gives you a fictional process description, and the rubric checks owners, decisions, exceptions and the questions you raise. A clear map is also the first step before you automate anything, which is where the AI automation course picks up.