Mapping before automating
Process mapping is the first step in any automation project. Without it, you are writing code for a process you do not fully understand - including its exceptions, edge cases, and manual workarounds that make it actually work.
The mapping phase answers three questions: What exactly happens? What should happen? And what parts are worth automating?
The automation mapping workflow
1. Map the as-is process
Document every step, decision, handoff, and exception. Include the manual workarounds. Use BPMN with generic tasks - do not specify task types yet.
2. Identify automation candidates
For each task, ask: Is it rule-based? Is it repetitive? Is the volume high enough? Does it have a clear input and output? Tasks that score yes on all four are automation candidates.
3. Design the to-be process
Replace generic tasks with typed BPMN tasks: service tasks (system does it), user tasks (human with a form), send/receive tasks (messages). Add error handling that the as-is lacked.
4. Implement and execute
Deploy the BPMN diagram to a process engine (Camunda, Flowable). The diagram IS the automation - no translation from documentation to code needed.
What not to automate
- -Processes that change weekly - automation maintenance will cost more than manual work.
- -Low-volume processes - if it runs 5 times a month, the ROI is probably negative.
- -Processes requiring judgment - keep humans in the loop for decisions that need context, empathy, or creativity.
- -Broken processes - fix the process first. Automation amplifies both efficiency and dysfunction.
Why BPMN for automation
BPMN 2.0 is the only notation that works for both documentation and execution. The same diagram a business analyst draws can be deployed to a process engine. This eliminates the gap between requirements and implementation - the diagram IS the code.
Related guides
Process Automation
Types and when to use each.
As-Is vs To-Be
Map before you automate.
Task Types
User vs service vs script tasks.
AI and BPMN
AI-powered automation.
Keep learning
Practice
Space Ship Inc.
Boundary events and error handling.
Practice
Bankovia
Compensation for failed transactions.
Frequently asked questions
Should I map before automating?▼
Always. Automating without understanding the process means automating waste, exceptions, and workarounds. The mapping phase typically saves 3-5x its cost in avoided rework during implementation.
Can I automate a BPMN diagram directly?▼
Yes. BPMN 2.0 defines an XML format that process engines like Camunda and Flowable execute directly. The diagram becomes the running workflow.
What is the difference between RPA and BPMN automation?▼
RPA automates individual tasks by mimicking human clicks. BPMN automation orchestrates entire end-to-end processes. RPA is tactical; BPMN automation is strategic. They complement each other.
Top comments (0)