What is a process map?
A process map is a visual diagram that shows the steps, decisions, actors, and flow of a business process from start to finish. It uses standardised shapes — rectangles for tasks, diamonds for decisions, arrows for flow, and cylinders for data stores — to make a process explicit, legible, and shareable. Unlike written procedures, a process map shows the sequence, branch points, and handoffs between actors in a way that is immediately scannable.
Process maps are used to document how work actually happens (AS-IS mapping), design how it should happen after improvement (TO-BE mapping), identify bottlenecks and waste, onboard new team members, support automation initiatives, and provide evidence for compliance and audit requirements. They are the foundational tool of business process management, operational excellence programmes, and digital transformation projects.
Process map vs flowchart vs BPMN
| Dimension | Process Map | Flowchart | BPMN |
|---|---|---|---|
| Formality | Semi-formal: consistent shapes, business context | Informal to semi-formal: varies by author | Formal: ISO/IEC 19510 standard notation |
| Actors shown | Yes — roles, departments, systems | Sometimes | Yes — pools and lanes with strict semantics |
| Audience | Business stakeholders, analysts, team leads | Any — depends on diagram type | Business analysts, process architects, engineers |
| Machine-executable | No | No | Yes — BPMN diagrams can drive BPM engines |
| Best for | Process documentation, improvement, communication | Quick logic or decision diagrams | Formal process specification for automation |
Use a process map for stakeholder communication, operational documentation, and improvement analysis. Use BPMN when the process will be automated, integrated with a BPM platform, or formally specified for handover to an engineering team.
Swimlane process maps: showing who does what
A swimlane process map divides the diagram into horizontal or vertical lanes, with each lane representing a different role, department, team, or system. Each step in the process is placed in the lane belonging to the actor who performs it. Steps that cross a lane boundary are handoffs — points where ownership transfers from one actor to another.
Swimlane maps are particularly valuable for cross-functional processes like order fulfilment, employee onboarding, customer complaint resolution, and procurement — processes where work passes between multiple teams or systems before completion. Handoffs are where most delays, errors, and miscommunications occur; making them visible is the first step to reducing them.
Swimlane process map for employee onboarding. Lanes: HR, IT, Manager, New Employee. Process starts when offer is accepted. HR: send welcome email, create employee record, initiate background check. IT: provision laptop, create accounts (email, Slack, Jira), set up VPN access. Manager: prepare 30-day plan, schedule intro meetings, assign buddy. New Employee: complete paperwork, attend orientation, complete training modules, confirm system access. Show decision: if background check fails, terminate process and notify manager. End state: new employee active and productive.
AS-IS vs TO-BE process mapping
AS-IS process mapping documents how a process actually works today — capturing every step, decision, workaround, manual intervention, and inefficiency in the real current state, not the idealised version described in the procedure manual. AS-IS maps reveal where value is lost: unnecessary handoffs, approval queues with no clear owner, manual re-entry of data between systems, or steps that exist only because "we've always done it that way".
TO-BE process mapping designs how the process should work after improvement — removing waste, eliminating unnecessary handoffs, automating manual steps, and resolving the pain points identified in the AS-IS map. The gap between the AS-IS and TO-BE maps defines the improvement work required: the steps to be automated, the systems to be integrated, the approvals to be streamlined.
- Always complete the AS-IS map before designing the TO-BE. Designing improvements without understanding the current state produces solutions that miss the real bottlenecks.
- Involve the people who actually do the work in the AS-IS session. The procedure manual describes the intended process, not the real one.
- Annotate the AS-IS map with pain points, average step durations, and error rates before designing the TO-BE. Data-driven improvement beats assumption-driven improvement.
- Show both maps side by side when presenting the improvement case — the contrast makes the value of the TO-BE design immediately visible to stakeholders.
How to map a business process in 5 steps
- Define the scope. Name the process, its trigger (what starts it), and its end state (what a successful completion looks like). Scope creep is the most common reason process mapping sessions fail.
- Identify the actors. List every role, team, or system that participates in the process. These become your swimlane labels.
- Walk the process end to end. With the people who do the work, trace every step from trigger to completion — including exceptions, workarounds, and the "what if" branches.
- Draw the map. Use flow-chart.io to generate the process map from your notes. Place each step in the correct swimlane, connect steps with arrows, and mark decisions with diamond shapes.
- Validate and iterate. Review the draft map with process participants. Check for missing steps, incorrect sequences, or actors who were overlooked. The first draft is always incomplete.
Frequently asked questions
- What is a process map?
- A process map is a visual diagram showing the steps, decision points, actors, and flow of a business process from start to finish. It uses standard shapes (rectangles for tasks, diamonds for decisions, arrows for flow) to make a process explicit and readable. Process maps are used to document current workflows, design improved workflows, identify bottlenecks, onboard staff, support automation, and provide audit evidence.
- How is a process map different from a flowchart?
- A flowchart is a general term for any diagram showing a sequence of steps and decisions. A process map is a type of flowchart focused specifically on a business process — it typically includes actors (who does each step), systems (what tools are used), and handoffs between roles or departments. In practice the terms are often used interchangeably, but "process map" implies business context with roles, while "flowchart" is broader and includes algorithm diagrams and decision trees.
- How is a process map different from BPMN?
- BPMN (Business Process Model and Notation) is a formal, standardised notation with specific symbols for events, gateways, tasks, and pools — designed for machine-executable process models that can drive BPM and workflow automation engines. A process map is more informal and accessible, designed for human communication. Use a process map for stakeholder communication and improvement analysis; use BPMN when the process will be automated or formally specified for an engineering team.
- What is a swimlane process map?
- A swimlane process map divides the diagram into lanes (horizontal or vertical), with each lane representing a different role, department, team, or system. Each step is placed in the lane of the actor who performs it. Steps crossing lane boundaries are handoffs — points where ownership transfers and where most delays and errors occur. Swimlane maps are essential for cross-functional processes like order fulfilment, onboarding, or complaint resolution.
- What is AS-IS vs TO-BE process mapping?
- AS-IS mapping documents how a process actually works today, capturing all steps, workarounds, and inefficiencies in the real current state. TO-BE mapping designs how the process should work after improvement — removing waste, automating steps, and eliminating unnecessary handoffs. The gap between AS-IS and TO-BE defines the improvement work required. Always complete the AS-IS map before designing the TO-BE, and involve the people who actually do the work in the AS-IS session.
- What export formats are available for process maps?
- flow-chart.io exports process maps as SVG (scalable vector, for Confluence, Notion, or SharePoint documentation), PNG at 2× and 4× resolution (for slide decks and reports), PDF (print-ready for process documentation libraries and audit files), and JSON (re-importable scene graph for future editing). All exports come from the editable scene graph — not screen captures — so they stay sharp at any size.