Every organisation runs on processes. Some are documented. Most are not. The ones that are documented are frequently out of date, reflecting how work was done two years ago rather than how it is done today. And the ones that exist only in people's heads — the tribal knowledge that walks out the door when key employees leave — represent one of the biggest operational risks any business faces.
Business process mapping is the discipline of making the invisible visible. It transforms informal, undocumented workflows into structured, visual representations that can be analysed, improved, automated, and shared. At Pepla, process mapping is where most of our consulting and software development engagements begin, because you cannot improve what you have not documented, and you cannot automate what you do not understand.
Why Map Processes?
The immediate value of process mapping is clarity. When you put a process on paper (or screen), everyone involved can see the same picture. Disagreements about how work actually flows — which are surprisingly common — surface immediately. "I thought you sent the approval to finance before procurement" becomes a visible fork in the diagram rather than a misunderstanding discovered three weeks into a project.
When you put a process on paper, disagreements about how work actually flows surface immediately -- not three weeks into a project.
Beyond clarity, process maps enable:
- Bottleneck identification. When you can see the entire flow, the steps where work queues up become obvious. That approval step that takes five days? It is visible as a single box in the diagram with a five-day annotation.
- Redundancy elimination. Processes that evolved organically often contain duplicate checks, unnecessary handoffs, and steps that made sense once but no longer serve a purpose.
- Automation opportunity assessment. You cannot evaluate which steps to automate until you know what all the steps are. Process maps provide the inventory.
- Training and onboarding. New team members can understand their role in a larger process by reading a diagram, rather than relying on word-of-mouth knowledge transfer.
- Compliance and auditing. Regulated industries require documented processes. Maps provide the evidence that processes exist, are followed, and are reviewed.
BPMN: The Standard Notation
Business Process Model and Notation (BPMN) is the internationally recognised standard for process mapping, maintained by the Object Management Group (OMG). It provides a consistent set of symbols and rules that make process diagrams readable by anyone familiar with the notation — regardless of the specific process being described.
The core BPMN elements you need to know:
- Events (circles) — represent something that happens. A thin circle is a start event (the process begins). A thick circle is an end event (the process concludes). An intermediate event (double-bordered circle) represents something that happens during the process, like a timer or a message received.
- Activities (rounded rectangles) — represent work that is performed. A task is a single unit of work. A sub-process is a compound activity that can be expanded to show its internal detail.
- Gateways (diamonds) — represent decision points and path divergence. An exclusive gateway (X) is an either/or decision. A parallel gateway (+) means all outgoing paths are followed simultaneously. An inclusive gateway (O) means one or more paths may be followed.
- Sequence flows (solid arrows) — show the order of activities within a process.
- Message flows (dashed arrows) — show communication between different participants or organisations.
- Data objects (page icons) — represent information used or produced by activities.
You do not need to master the entire BPMN specification to be effective. The elements above cover 90% of what you will encounter in practice. The full specification includes dozens of additional symbols for specialised scenarios, but starting with the basics and adding complexity as needed is the pragmatic approach.
You cannot improve what you have not documented -- make invisible workflows visible before trying to optimise them.
Swimlane Diagrams
Swimlane diagrams (also called cross-functional flowcharts) add a critical dimension to process maps: responsibility. The diagram is divided into horizontal or vertical lanes, each representing a role, department, or system. Activities are placed within the lane of the responsible party, and sequence flows crossing lane boundaries represent handoffs.
Swimlane diagrams are exceptionally effective at revealing handoff problems. When a process crosses six department boundaries and involves twelve handoffs, the inefficiency is visually obvious. Each handoff is a potential delay point, a communication failure point, and a data integrity risk. Reducing handoffs is one of the most reliable ways to improve process efficiency.
At Pepla, we default to swimlane format for any process involving more than one role. The visual clarity is worth the extra space, and the handoff visibility is invaluable for identifying improvement opportunities.
Value Stream Maps
Value stream mapping (VSM), borrowed from Lean manufacturing, takes process mapping further by adding time and value analysis. Each step in the process is categorised as value-adding (the customer would pay for this), necessary non-value-adding (required by regulation or supporting infrastructure), or waste (neither the customer nor the business benefits).
The power of VSM is in the timeline at the bottom of the diagram, which shows two numbers for each step: processing time (how long the work actually takes) and lead time (how long the step takes including waiting, queuing, and handoff time). The ratio between total processing time and total lead time — the process efficiency ratio — is often shockingly low. A process with 4 hours of actual work and 3 weeks of total lead time has an efficiency ratio of 2.4%. The other 97.6% is waiting.
VSM is most valuable for end-to-end processes that cross multiple departments, particularly those with long lead times relative to actual work content. It is the tool of choice when the question is "why does this take so long?" rather than "what are the steps?"
Most processes have under 3% efficiency -- the rest is waiting. Value stream mapping exposes where your time actually goes.
Current State vs Future State
Process mapping is not an end in itself. The value comes from comparing where you are to where you could be. This is the current state / future state framework:
Current state mapping documents how the process actually works today — not how it should work according to the policy manual, but how it actually works, including workarounds, informal steps, and undocumented exceptions. This requires talking to the people who actually do the work, not just their managers.
Future state mapping designs how the process should work after improvements. This might include eliminating waste steps, automating manual activities, reducing handoffs, parallelising sequential steps, or introducing technology to support decision-making.
The gap between current state and future state defines your improvement roadmap. Each change can be assessed for cost, effort, risk, and expected benefit. This makes the business case for process improvement concrete rather than aspirational.
Tools for Process Mapping
The tool matters less than the technique, but the right tool does make the work faster and the output more professional.
- Microsoft Visio — the traditional standard for process mapping in enterprise environments. Full BPMN stencil support, integration with the Microsoft ecosystem, and wide familiarity among business analysts.
- Lucidchart — a cloud-based alternative to Visio with strong collaboration features. Multiple users can edit simultaneously, making it excellent for facilitated mapping sessions.
- Miro — primarily a whiteboard tool, but its flexibility makes it ideal for workshop-style mapping where the process is being discovered rather than documented. Start in Miro for exploration, move to Lucidchart or Visio for the formal diagram.
- draw.io (diagrams.net) — free, open-source, and surprisingly capable. It supports BPMN notation, swimlanes, and exports to multiple formats. For teams without a tool budget, it is an excellent choice.
- Camunda Modeler — if your process maps will eventually be used for process automation (BPMN execution), Camunda's free modeler produces BPMN XML that can be directly executed by the Camunda platform.
Common Pitfalls
Process mapping projects fail in predictable ways. Here are the pitfalls we see most often:
- Mapping the ideal process instead of the actual process. If your current state map looks clean and efficient, you probably mapped the policy rather than the reality. Talk to the people doing the work. The exceptions, workarounds, and informal steps are where the real improvement opportunities live.
- Too much detail too early. Start at a high level (5-10 steps for the end-to-end process) and drill into detail only where the high-level map reveals problems. A 200-step process map is unreadable and unmaintainable.
- Mapping without a purpose. "Let's map all our processes" is a project that never ends and rarely delivers value. Map the processes that are causing problems — the ones with long lead times, high error rates, frequent complaints, or pending automation decisions.
- Skipping validation. A process map created by one person reflects one perspective. It must be reviewed and validated by the people who actually perform the process, the people who manage it, and the people who depend on its outputs.
- Creating maps that are never maintained. A process map is a living document. When the process changes, the map must change. Assign ownership of process maps just as you assign ownership of the processes themselves.
Map the actual process, not the policy manual. The exceptions and workarounds are where the real improvement opportunities live.
Workshop Facilitation Tips
The most effective process maps are created collaboratively, in facilitated workshops with the people who own and operate the process. Facilitation is a skill, and here are the techniques we use at Pepla:
- Start with the trigger and the outcome. "What starts this process?" and "What does done look like?" anchor the boundaries before anyone starts listing steps.
- Use sticky notes before software. Physical or digital sticky notes (one step per note) allow participants to rearrange, add, and remove steps without the friction of editing a diagram in real time.
- Ask "and then what happens?" repeatedly. This simple prompt keeps the conversation moving forward through the process and prevents participants from getting stuck on edge cases too early.
- Timebox ruthlessly. A 2-hour workshop with a clear agenda produces better results than an open-ended session. Map the happy path first (1 hour), then identify exceptions and edge cases (30 minutes), then identify improvement opportunities (30 minutes).
- Capture decisions and parking lot items. Questions that cannot be answered in the room, disagreements about how the process works, and improvement ideas that are out of scope should all be captured visibly so participants know they have been heard without derailing the session.
The goal of process mapping is not to produce a beautiful diagram. It is to produce shared understanding — a common picture that everyone involved can point to and say "yes, that is how it works." From that shared understanding, improvement becomes possible.
Pepla's consulting team runs process mapping workshops for clients across industries -- from financial services to agriculture. If your processes need documenting or re-engineering, our business analysts can help.
Start with one process. The one that causes the most pain, takes the longest, or is about to be automated. Map it honestly, validate it with the people who do the work, and use the map to identify concrete improvements. That is the discipline of business process mapping, and it is one of the highest-value activities any organisation can undertake.
