Map the workflow before you pick the AI.
The AI Workflow Mapping Template is a fillable canvas for documenting one workflow end to end: triggers, steps, decisions, handoffs, waits, and rework. Then a seven-mark overlay tells you, step by step, where AI helps, where ordinary automation wins, and where judgment stays human.
Automation amplifies the process it is given.
A process you don't fully understand still runs on quiet human judgment: people fix bad inputs, route weird cases to whoever knows, and delay things that look wrong. Automate around that hidden judgment and the corrections disappear while the volume goes up. And modern AI raises the stakes, because it produces fluent, confident output even when it's wrong.
So this template makes you map first: what actually happens, with numbers, workarounds and all. It's built on the methods that serious operators already trust: NIST's AI Risk Management Framework treats mapping as the go/no-go gate, lean value-stream practice supplies the per-step numbers, and the peer-reviewed task-suitability research supplies the step-by-step verdict.
Five parts, filled in order.
| Part | Name | What it captures | Time |
|---|---|---|---|
| A | Frame | Scope, boundaries, trigger, outcome, volume, constraints | 15 min |
| B | Flow | The step table: actors, systems, decisions, handoffs, waits, rework | 30–45 min |
| C | Surroundings | Systems inventory, data inventory, risks and existing controls | 15 min |
| D | Friction | Review the map against the twelve-problem checklist, rank the top 3–5 | 15 min |
| E | AI overlay | Per-step involvement mark, review design, prerequisite, metric | 20–30 min |
The order is the method: current state with real numbers first, problems second, AI last. Run Part E in a separate later session, after the map has been validated by the people who do the work. A first pass that leaves fields marked "?" is a legitimate result; unknowns tell you exactly what to verify.
Ten questions that frame the workflow.
One row per step. Fourteen things to record.
A step is one unit of work by one actor with a recognizable start and finish. Aim for 5–15 rows; exceptions and rework loops get suffixed numbers (4a, 4b) pointing back at the step they branch from.
| Column | What to record | Watch for |
|---|---|---|
| Step name | One verb phrase per action | Bundled steps hide the handoffs between them |
| Actor | The role or system that really does it | Ask who covers absences; that finds unowned steps |
| Systems | Every tool, inbox, and spreadsheet touched | The personal spreadsheet is usually the real system |
| Inputs | What the step needs, and where it comes from | Ask how often it arrives incomplete |
| Outputs | What it produces, and who consumes it | Outputs nobody reads are deletion candidates |
| Decision | The rule actually used, not the official one | The single most important field for the AI overlay |
| Handoff | Who is next, via what channel | "I mention it in standup" explains the missing days |
| Wait | Idle time before and after the step | In office workflows, waiting usually dwarfs working |
| Touch time | Hands-on minutes, clean case vs messy case | Averages hide the expensive cases |
| %C&A | Share of incoming items clean enough to process | Ask "out of the last 10, how many?" |
| Exceptions | Top failure paths, how often, where they go | Anything over ~10% is a standard path in denial |
| Workarounds | What people really do, and what it compensates for | Treat as evidence, never as confession |
| Data | What gets captured, what evaporates | Uncaptured judgments leave nothing to evaluate AI against |
| Pain | The operators’ own words, unsanitized | Predicts adoption better than any ROI estimate |
Three of these numbers do most of the diagnostic work. Wait exposes where items sit idle, which usually dwarfs the working time. Touch time, clean versus messy, prices the step and its exceptions. And %C&A (the share of incoming work that's complete and accurate enough to process without chasing or fixing) tells you whether any automation here would run on clean fuel or amplify the dirt.
Twelve problems to hunt before anyone says "AI".
| # | Problem | What it looks like |
|---|---|---|
| 01 | Unclear steps | Described differently by everyone you ask |
| 02 | Bottlenecks | Items pile up at one desk or queue |
| 03 | Sources of delay | Batching, absences, approval queues, external waits |
| 04 | Error and rework | Low %C&A, send-backs, silent corrections |
| 05 | Authority gaps | Only one person can do it, or approve it |
| 06 | Duplication | Same data keyed twice, same check done twice |
| 07 | Excessive handoffs | More desks than the work requires |
| 08 | Unnecessary steps | Approvals that never reject, reports nobody reads |
| 09 | Time imbalance | Days of elapsed time wrapped around minutes of work |
| 10 | Undocumented judgment | Consistent decisions that exist only in one head |
| 11 | Data dead ends | Judgments and outcomes never captured anywhere |
| 12 | Workaround load | The unofficial method has replaced the official one |
Items 01–09 adapt ASQ's classic guidance for reviewing a finished flowchart; 10–12 are ours for the AI context. The output is a ranked top 3–5 problem list with step numbers and evidence attached. Those problems, not "we should use AI", are what the overlay responds to.
Seven marks. One per step. Mixed is normal.
| Mark | Class | Use it when | People still |
|---|---|---|---|
| [H] | Human-only | High stakes with no stable pattern, or the step runs on relationships and accountability | Everything, as today |
| [R] | Rules, no AI | The rule is written, stable, and inputs are structured. Prefer this over AI whenever it qualifies | Own the rules, handle the else-path |
| [A] | AI-assisted | The human still performs the step; AI retrieves, summarizes, drafts fragments, suggests | Perform the step |
| [G] | AI drafts, human approves | AI produces the whole work product and checking it is faster than doing it | Approve or edit every item |
| [X] | AI runs, humans get exceptions | Accuracy proven on your own data, errors cheap and reversible, and a working exception queue | Work the queue, audit samples |
| [F] | Fully automated | Failure is low-cost and self-evident, reversal is cheap, monitoring exists | Own the monitoring |
| [N] | Not yet | Data, rule clarity, or input quality fails today. Record the reason and the fix that reopens it | Fix the blocker, then reassess |
Before marking a step, name which of its functions you'd change: gather
(collect information), interpret (summarize, categorize, score),
decide (select the action), or act (execute it). They
don't have to share one mark: "AI gathers and interprets, a person decides, the system
acts" is a complete and often ideal design. Write it like [G: interpret]
right on the map.
Before a step earns an AI mark, it passes five gates.
Record the verdict as one line that cites its evidence: "Step 4: [G: interpret]. Rule consistent but unwritten. Outcomes recorded. Errors reversible before send. Saves ~4 h/week. Prerequisite: write the criteria down." A mark that can't fill in its gates is a guess, and gets [N] until it can.
Inbound lead qualification, mapped and marked.
A 12-person services firm, ~45 leads a week, 25 minutes of touch time hiding inside 2–4 days of elapsed time. Every number here is illustrative; yours will differ, which is exactly why you map.
| Step | Today | Mark | Future state |
|---|---|---|---|
| Lead arrives | Sits in a shared inbox 4–24 hours | [R] | Parsed into the CRM within minutes |
| Research the company | 10 minutes of googling per lead | [G] | AI compiles the brief; manager spot-checks a weekly sample |
| Fit decision | Unwritten rule in one person’s head | [G] | AI scores against the written criteria; manager approves every lead |
| Route to a rep | Slack DM to whoever seems free | [R] | Round-robin with a load cap |
| First reply | 4–48 hours later, research redone | [A] | Rep gets the brief with the lead; the reply stays human |
Notice what the mapping session itself surfaced: the fit rule lived in one person's head, so writing it down was the prerequisite for everything else, and the "later" folder where a quarter of leads quietly died became an explicit queue with a day-14 review rule. No model fixed those. The map did.
That's the review design in four moves. Wherever an AI mark lands, the map must also show who checks, when, against what bar, and what happens on failure. Oversight nobody designed becomes either a rubber stamp or the new bottleneck.
Common questions
Why map a workflow before choosing an AI tool? ›
Because a process you do not understand still runs on hidden human judgment, and automating around it removes the corrections while the volume goes up. Mapping first finds fixes that need no AI, produces baseline numbers a pilot can be judged against, and lets you describe the AI opportunity precisely enough to test it cheaply.
How long does workflow mapping take? ›
About 60 to 90 minutes solo for a first-pass map of one workflow, or a half-day workshop with 4 to 6 people for a validated version with real numbers. Run the AI overlay in a separate, later session: mixing "what happens" with "what could AI do" reliably contaminates the map with aspiration.
What if the map says most steps should stay human? ›
That is the normal result. The research on task-level AI suitability finds most roles contain some AI-suitable tasks while very few are fully automatable, so a healthy map mixes marks: several [H] and [R], a few [A] and [G], one or two [X] candidates, and at least one honest [N]. A map that comes back all-automated was scored by optimism, not evidence.
Do I need special software to use this? ›
No. The canvas works in a doc, a spreadsheet, a Notion page, a Miro board, or on a wall of sticky notes. The template is deliberately vendor-neutral and tool-independent; nothing in it requires buying anything.
When is ordinary automation better than AI? ›
Whenever the decision rule is explicit and stable and the inputs are structured. Rules are cheaper, deterministic, explainable, and testable. AI earns its place where judgment is real but patterned, and where checking the output is faster than producing it.
The blank canvas, step table, and overlay sheet as a printable pack is in progress, and the Human-in-the-Loop Checklist is next. Join the list and each one lands in your inbox as it ships.
One useful email at a time. Unsubscribe whenever.