What is process mapping, and why is it worth doing?
Every team runs on processes, but most of them live only in people’s heads. A process map writes them down where everyone can read them, agree on them and improve them. This guide explains the practice, compares the two main notations, and shows how to keep a map light.
What a process map actually is
A process map is a picture of how a piece of work actually gets done: the steps, in order, and what passes between them. You read it left to right: an activity happens, it produces an outcome, and that outcome lets the next activity start. “Receive request” → details complete → “Check details” → approved → “Notify customer”.
That’s the whole idea. A map is not a flowchart of every conceivable branch, and it’s not a system diagram. It’s a shared, plain-language record of how the work flows, the kind of thing a new joiner could read in a meeting without a tutorial.
Why bother mapping it?
Because work that only lives in people’s heads is fragile. A map turns that knowledge into a record the whole team can read and keep. A healthy map pays off in four ways:
- Shared understanding. Everyone argues from the same picture instead of three private versions of “how it works”.
- Faster onboarding. A new hire follows the map instead of shadowing someone for a month.
- When someone leaves, the process stays.. The person who “just knows” goes on leave or moves on, and the work still runs. The map is the record of how things are meant to run, ready for an audit or a handover.
- Surfacing waste. Once the steps are visible, the rework loops, the dead handoffs and the duplicated effort are obvious, and fixable.
One expense claim. Two notations. Same facts.
The usual notation for process maps is BPMN, Business Process Model and Notation. It is a real standard and it is powerful, but it has well over a hundred symbols: pools, swimlanes, many types of gateway, and intermediate and boundary events. Drawing it well is a skill of its own, and reading it needs a legend.
The people who most need to read the map are the people who do the work, and they often cannot read BPMN without training. Then the notation becomes a barrier to the conversation, and the map goes out of date because it is too much effort to keep it correct. Below is the same expense claim in both notations. The facts are the same. Only one of the two can be checked in the meeting.
Two elements say what BPMN says in twenty
Universal Process Notation strips the vocabulary back to two things: activity boxes and flowlines. An activity is a verb plus an object, “Approve invoice”. A flowline names the outcome that lets the next step begin. That’s the entire vocabulary; there’s nothing to misuse.
Branching is shown by where the lines attach, not by decision diamonds. Detail lives in drill-downs: any box can open into its own child map, and a map can go up to 6 levels deep, the top level included. Each level uses the same two elements. You get depth without sprawl, and each activity carries its RASCI roles without extra symbols.
Verdin is a process-mapping tool built on that notation: a library of maps that people read at a glance and that a team keeps true as the work changes. To see if it fits your team, read who it’s for.