Map one workflow at a time. Fill these in with the people who do the work, not from memory. Where a step is unclear, write that down: gaps in the map are often the first thing worth fixing.
1. Name it
- Workflow name, in plain words (for example, 'Customer refund requests').
- Owner: the person accountable for how it runs.
- Team or teams involved.
2. Trigger and inputs
- What starts the workflow? (An email, a form, a ticket, a schedule, a phone call.)
- What information arrives with it?
- Where does that information come from, and in what format?
3. The steps
- List each step in order, with who or what does it.
- For each step, note the system used and roughly how long it takes.
- Mark steps where work waits for someone else.
- Mark steps that are the same every time, and steps that need judgment.
4. Decisions and exceptions
- What decisions are made along the way, and by whom?
- What rules do people follow to make them?
- What are the common exceptions, and what happens to them?
- What happens when something goes wrong?
5. Volume and time
- How many times does this run per month?
- How many minutes of people's time does one run take, start to finish?
- What does that time cost? (Use a rough hourly figure.)
- How often are there mistakes or rework?
6. Where AI could help
For each step, ask which of these it would be:
- Reading and extracting information from emails, forms or documents.
- Sorting or classifying requests.
- Drafting a reply or document for a person to approve.
- Finding the right information in your own knowledge sources.
- Helping with a decision by pulling the facts together.
- Not a good fit: rare, high-stakes or purely relational steps stay with people.
7. Review and risk
- Which steps need a person to approve the AI's work?
- What is the worst result if the AI is wrong at each step?
- What must be logged so the work can be audited?
- How will you tell if the new version is better than the old one?
Common questions
Why map a workflow before using AI?
Because AI works inside a process. Mapping shows where time is lost, which steps are repetitive and which need judgment, so you can choose where AI helps and where a person should stay in charge.
How detailed should the map be?
Detailed enough that someone who doesn't do the work could follow it. Capture the steps, systems, decisions and exceptions, but you don't need a formal diagram. A written list is fine.
Should we map every workflow first?
No. Start with one workflow that is frequent, measurable and painful. A single well-mapped workflow teaches you more than a shallow map of everything.
Want a second pair of eyes on your own workflow?
Book a Discovery Call