Map a business process before adding AI
Map triggers, decisions, handoffs and exceptions before choosing an automation tool or AI model.
A process map should explain what people actually do when a request arrives, including the awkward cases. For a small business, its main value is making the next implementation decision visible: which step needs a fixed rule, which needs interpretation, and which still needs an accountable person.
Follow a real item from arrival to completion
Choose one recent, ordinary request and reconstruct its path using the people who handled it. Record the arrival channel, documents opened, fields copied, decisions made and final destination. Separate hands-on work from waiting time. A request sitting in an inbox overnight is a different problem from slow data entry.
Then repeat the exercise for an incomplete request and a request that needed rework. Add those branches to the same map. Avoid drawing only the ideal sequence from a procedure document. If staff use a spreadsheet alongside the official system, include it and establish why the workaround exists.
Classify the decisions before selecting tools
Mark each step as a transfer, calculation, rule, interpretation or approval. Transfers and calculations usually need ordinary software. Interpretation may justify AI when the input is variable text, but the output still needs a defined format. An approval belongs to someone with authority to accept the proposed action.
For each connection, confirm that the destination supports the exact operation you need. A connector that reads contacts may not update the fields used by your team. Microsoft’s automation planning guidance distinguishes connector, API and interface automation options; evaluate the needed action before committing to a platform.
Turn the map into a bounded implementation brief
Define where the proposed automation starts and stops. Write one sentence describing an acceptable completed item, including where it is stored and who receives it. Add the conditions that must stop processing, such as a missing customer identifier, conflicting address, or attachment that cannot be read.
Use the map to select a narrow first change and collect a baseline for that segment. Track staff effort, elapsed time and rework separately. A map can reveal an unnecessary approval or unclear ownership; resolving that may be more useful than building an AI step around the existing confusion.
Practical checklist
- Name the trigger and the completion condition.
- Identify the authoritative record at every handoff.
- Include missing-information and rework branches.
- Choose one segment with a measurable baseline.
Illustrative setup: a maintenance request
A facilities team receives requests by email, copies the address into a spreadsheet, asks for missing access details and assigns a technician. Its first map separates address validation from urgency interpretation. A sensible pilot creates a reviewable job draft, while access confirmation and technician assignment remain with the coordinator.
Common questions
Do I need a specialist diagramming tool?
No. A shared document or simple flowchart is enough if staff can identify the trigger, decisions, owners and exceptions. The accuracy of the map matters more than its visual sophistication.
Should every branch be automated immediately?
No. Document the branches, then deliberately choose which ones the pilot supports. Unsupported cases should return to a named person with their original information intact.
Further reading
Start with your actual workflow.
Turn the useful parts of this guide into a focused project brief.
Shape your project