AI Process Mapping for Business Analysts

Why a plain description isn't a process map

"Someone submits a request, it gets approved, then it happens" is how most people describe a process out loud — and it hides every handoff, rework loop and wait state that's actually causing the pain. A real process map surfaces those explicitly, which is what makes the pain-point analysis possible.

What it does

Process summary. Trigger, end state, actors, systems, volume and cycle time.
As-is process. Numbered steps in the form "[Actor] does X in [System] → produces Y", with every handoff, decision and wait state explicitly marked.
Pain-point analysis. Each step's problem type — delay, rework, manual, duplication, control gap — and its effect.
To-be process. Same numbered format, with each change annotated [CHANGED], [NEW] or [REMOVED].
Delta summary. Steps and handoffs removed, controls added, and what would have to be true for the to-be to actually work.

Example

A made-up example, not an actual client.

Input

Invoice approval: AP clerk enters
invoice in system, emails manager for
approval, manager replies "approved",
clerk manually updates status and
pays.

Output (excerpt)

AS-IS PROCESS
1. [AP Clerk] enters invoice in Finance
   System → creates invoice record
2. ⇄ HANDOFF [AP Clerk] emails Manager
   for approval
3. WAIT: manager response (email)
4. [Manager] replies "approved" (outside
   system — no audit trail)
5. [AP Clerk] manually updates status
   in Finance System

PAIN POINTS
Step 2-4 | Approval happens outside the
system of record | control gap | no
audit trail of who approved

How it works with Claude

Add it to Claude. One-off setup, roughly 10 minutes.

Describe the workflow, or paste notes from a walkthrough.

Out comes the as-is map, the pain points, and the to-be version.

FAQs

Can AI do process mapping without a diagramming tool?

Yes, as a numbered text narrative — trigger, steps, handoffs, decisions, wait states and end state — which many BAs use as-is or as the basis for a diagram in Visio, Miro or Lucidchart.

What's the difference between as-is and to-be process mapping?

As-is maps the process as it happens today, including its inefficiencies. To-be maps the target process after improvements, with each change annotated against the as-is version.