Why process maps matter
A process map makes invisible work visible: handoffs, approvals, rework, queues, decisions and system boundaries. It is especially useful when a project is described as a “website problem” but the real issue sits across operations.
Start with the simplest useful level
Begin with a high-level flow. Do not create a 200-box diagram before the team agrees on the basic journey. Expand only where detail changes a decision.
Look for friction
- Repeated data entry
- Manual approvals
- Unclear ownership
- Waiting between teams
- Rework caused by missing information
- Decisions made without reliable data
Current state vs future state
Map the current process first. Then design the future process. The gap between them becomes a useful source of requirements, transition work, risks and training needs.
| Question | Practical answer |
|---|---|
| Current state | Order received → manual check → email confirmation → fulfillment |
| Future state | Order received → automated validation → confirmation → fulfillment queue |
| Gap | Automation, exception handling, ownership, monitoring, training |
Tool choice
A simple flowchart is often enough for a project discussion. BPMN can be useful when the process is complex and the team needs a more formal notation. The right diagram is the one the audience can understand and use.
Portfolio exercise
Take an eCommerce order from checkout to delivery. Draw the customer actions, system actions, operations handoffs and exception paths. Then highlight three places where automation could reduce friction.
Map the work before you automate it
Process maps are powerful because they expose work that software screens hide. A customer order may look like a single transaction in the storefront but involve marketing, finance, warehouse, support, shipping and payment systems behind the scenes.
Look for queues and handoffs
If a task moves from an online form to a spreadsheet and then to email, ask why. The issue may be a missing integration, unclear ownership, poor data structure, or a control deliberately introduced by finance. Automating the spreadsheet without understanding its purpose can simply move the problem elsewhere.
From map to improvement hypothesis
After mapping, mark wait time, rework, duplication, manual entry, approval loops and unclear ownership. Then choose one area to investigate. Do not redesign the entire process just because you can draw it. A small, evidence-backed change is often easier to validate.
When the To-Be process is ready, compare it against As-Is step by step. Every difference should have a reason: remove, automate, combine, reassign or add a control.
Map an eCommerce cancellation process with Customer, Support, Operations and Finance swimlanes. Identify one waiting point, one duplicate data-entry step and one decision that lacks an explicit rule. Propose a To-Be change for each.