Process to Agent Intent Mapping

Intent Mapping Levels

Intent Mapping Guidelines (L1 - L3)

Methods to Compile Initial Process Catalogue

Here are the widely used methods and tools architects use to compile that initial L1-L3 Process Catalog before Discovery begins.

Industry Reference Models (The Cheat Codes)

You don't need to guess what an event management, manufacturing, or software company does. Industry consortiums have already mapped every business process on earth. You download their map, highlight what you think applies, and use that as your baseline.

• APQC (American Productivity & Quality Center): This is the gold standard. APQC provides free, downloadable "Process Classification Frameworks" (PCFs) for almost every industry. It gives you the exact L1 to L4 taxonomy for a business.

• TM Forum (eTOM): If you are working in Telecommunications or Media, this is the mandatory standard for process mapping.

• ITIL: For IT service management processes.

Artifact Harvesting (The Paper Trail)

Before you schedule a single workshop, you ask the client's IT or Project Management Office (PMO) for existing documentation. You mine these documents strictly for nouns and verbs to add to your catalog.

• The SOW / RFP: The Statement of Work or Request for Proposal that initiated your project is a goldmine. If the SOW says "Must support split-billing," you immediately add L3: Split-Billing to your catalog.

• Standard Operating Procedures (SOPs) & Training Manuals: HR and onboarding teams often have step-by-step guides for new hires. You aren't reading them for the pain points; you are just extracting the titles of the processes.

• Existing Org Charts: If you see a team called "Deal Desk," you know you have to add L3: Non-Standard Pricing Approvals to your catalog.

System Snooping

If the organization is already using Salesforce (or another ERP/CRM) and you are coming in to implement Revenue Cloud Advanced, their current system configuration will tell you exactly what processes they run today.

• Custom Objects & Fields: If you look at their Salesforce schema and see a custom object called Vendor_Rebate__c, you immediately add L3: Vendor Rebate Management to your map.

• Approval Processes & Flows: Looking at the names of active workflows gives you a literal list of automated business processes.

The Tools of the Trade

When compiling and presenting this catalog, architects use a mix of high-tech visualization and low-tech organization tools.

Process Mining Tools (The High-Tech Approach)

In highly mature enterprise environments, organizations use software that connects to their ERP/CRM and reads the system logs to automatically draw the process maps based on what users are actually clicking.

• Celonis: The heavyweight champion of process mining.

• UiPath Process Mining: Often used if the company is already heavy into robotic process automation (RPA).

Enterprise Architecture (EA) & Mapping Tools

These are used to visually draw the L1-L3 taxonomy boxes so executives can agree on the boundaries.

• Lucidchart / Visio: The standard for drawing the high-level Value Streams (L1) and Process Areas (L2).

• Signavio (SAP) / ARIS / LeanIX: Heavy-duty Enterprise Architecture tools that link processes to IT systems and business capabilities.

• Elements.cloud: Specifically built for Salesforce. It allows you to map business processes and tie them directly to Salesforce metadata (like fields and objects).

Spreadsheets in Use

Despite all the fancy tools, 90% of architects compile their final Process Catalog in Excel or Smartsheet.

• Why? Because a spreadsheet allows you to add columns for "In Scope / Out of Scope", "Process Owner", and "Priority." It is the easiest format to present to a steering committee for sign-off before Discovery begins.

Alignment Workshop

Once Data and Artifact Harvesting to build a draft hold alignment workshops.
This may cross out, add, and change things frequnetly. Now, you are ready for Discovery.