Process Mapping Techniques
Methods for documenting, analysing, and redesigning business processes as a prerequisite to workflow automation implementation.
Purpose of Process Mapping
Process mapping creates a shared, explicit representation of how work actually flows through an organization — who does what, in what sequence, using which systems, and under what conditions. Before automating a process, mapping the current state reveals hidden steps, undocumented exceptions, system dependencies, and handoff delays that a purely verbal description would omit.
Attempting to automate a poorly understood process produces automated versions of broken workflows. Thorough process mapping before automation design reduces the risk of encoding existing inefficiencies into automated systems.
Current State vs Future State Mapping
Process mapping for automation projects typically produces two maps: a current-state map that documents how the process works today (including manual steps, workarounds, and unofficial handoffs), and a future-state map that describes the redesigned process after automation is applied.
Current-state maps are built through process observation, stakeholder interviews, and review of existing procedure documentation. They should capture the actual process as performed, not the process as documented in procedure manuals — these often diverge significantly. Note every decision point, every waiting period, every system involved, and every person who touches the process.
Future-state maps redesign the process to remove steps that can be eliminated, automate steps that can be systematized, and clarify responsibilities for steps that require human judgement. The gap between current state and future state defines the automation scope.
BPMN Notation Overview
Business Process Model and Notation (BPMN) is an internationally standardized graphical language for representing business processes. BPMN diagrams are readable by both business stakeholders and technical implementers, making them effective for process design collaboration.
Core BPMN Elements
BPMN diagrams use a small set of core symbols. Events (circles) mark process start, end, and intermediate points. Activities (rectangles with rounded corners) represent tasks or sub-processes. Gateways (diamonds) represent decision points and branching logic. Sequence flows (solid arrows) connect elements in execution order. Message flows (dashed arrows) represent communication between separate process participants.
Gateway types encode different routing behaviours: exclusive gateways (X) route to exactly one of several paths. Parallel gateways (+) activate all outgoing paths simultaneously. Inclusive gateways (O) activate one or more paths based on conditions.
Pools and Lanes
Pools represent separate organizational entities (companies, departments, or systems). Lanes subdivide a pool to show different roles or teams within an organization. Swimlane diagrams using pools and lanes make responsibility boundaries explicit — every activity sits in the lane of the team or system responsible for executing it, making handoffs visible as flows crossing lane boundaries.
Swimlane Diagram Best Practices
Swimlane diagrams are effective for communicating process flow to non-technical stakeholders. Practical design guidelines include: keep each lane to one clearly defined role or system; place activities in temporal order left to right; show handoffs as horizontal flows crossing lane boundaries; mark decision points explicitly with gateways rather than branching arrows; and limit diagram scope to a single process or subprocess — deeply nested processes are better represented as separate child diagrams.
Avoid creating swimlane diagrams with more than five or six lanes in a single view. Diagrams with many lanes become difficult to read and often indicate a process that should be decomposed into separately mapped subprocesses.
Identifying Automation Candidates
Not all process steps are equally suitable for automation. Evaluate each step against five criteria to identify strong automation candidates:
- Rule-based: The step applies consistent rules to data and produces a deterministic output. Exceptions requiring human judgement reduce automation suitability.
- High frequency: The step occurs many times per day, week, or month. Low-frequency steps produce limited efficiency gains from automation.
- Digital inputs: The step receives structured electronic data. Steps involving paper documents, phone calls, or unstructured data require additional pre-processing before automation.
- Stable process: The underlying business rules change infrequently. Frequently changing processes generate ongoing automation maintenance costs.
- Measurable outcome: The step produces a clear, verifiable output that can be validated automatically.
Steps meeting all five criteria are strong automation candidates. Steps meeting three or four criteria may be automatable with workarounds. Steps meeting fewer than three criteria are better candidates for process simplification before automation investment.
Process Mapping Documentation Outputs
A complete process mapping engagement produces several artefacts: the current-state BPMN or swimlane diagram, the future-state diagram with automation scope annotated, a process inventory table listing all steps with owner, system, frequency, and automation suitability rating, a data flow map showing what data enters and exits each step, and a list of assumptions and open questions that require clarification before automation design begins. These artefacts become the basis for workflow specification documents that guide technical implementation.