What business process mapping is
Business process mapping is drawing how work actually flows through an organisation — the steps, the decisions, the handoffs — so that anyone can understand it at a glance. Done well, a map captures the real process, not the policy theory of how it's supposed to work.
Pick the right level of detail
The most common mistake is mixing levels. Decide up front whether you're mapping the high level (a five-to-seven-step SIPOC overview), the mid level (a swimlane diagram showing who does what), or the detailed level (every click and keystroke). Each has its place; combining them in one diagram is what makes maps unreadable.
The symbols that actually matter
You need far fewer symbols than most notations suggest. For 90% of maps: a rounded rectangle for a step (one action, verb + outcome), a diamond for a decision (with labelled exits), and an arrow for flow. A circle marks the single start and the single end. That's enough to map almost anything clearly.
A simple method
Agree the scope with a SIPOC. Map the happy path first — what happens when everything goes right — as one clean line. Add decisions only where the path genuinely splits. Then add exceptions and rework as secondary paths, clearly labelled, so the normal flow stays dominant. Finish with one clear end that represents a real outcome, not an administrative full-stop.
That's the entire method. LeanBean runs it for you: describe the process in plain words and it produces the mapped, structured result.
Skip the drawing. Describe it in plain English.
LeanBean turns a plain-language description of any process into a professional map — with waste, efficiency and AI-readiness analysis built in. Free to start.
Build your first map free →Common questions
What is business process mapping?
Business process mapping is drawing how work actually flows through an organisation — steps, decisions and handoffs — so anyone can understand it quickly. It captures the real process, not just the intended one.
What symbols are used in process mapping?
Most maps need only a few: a rounded rectangle for a step, a diamond for a decision with labelled exits, arrows for flow, and a circle for the single start and end point.
What is the first step in mapping a process?
Agree the scope first — often with a SIPOC diagram — then map the happy path (what happens when everything goes right) before adding decisions and exceptions.
Related guides: SIPOC explained · How to make a swimlane diagram · The 8 wastes of Lean