3.1Process mapping & BPMN
The essentials in 30 seconds
- PROCESS MAPPING: for multi-actor processes, lanes (swimlanes) — strips each representing an ACTOR/service — show WHO is doing WHAT and the transmissions (passages between lanes).
- BPMN (Business Process Model and Notation) is the STANDARDIZED and international NOTATION of BPM: a rigorous language (events, activities, gateways, flows, corridors) to model processes WITHOUT AMBIGUITY.
- Corridors = frequent need (understand a multi-actor process). BPMN = more FORMAL/rigorous (official documentation, quality/BPM, exchange with experts); a lane flowchart is sufficient for simple needs.
Ongoing mini-case — Nadia applies “Process mapping & BPMN”
Nadia, quality and organization manager in a service SME in Algiers, must map business processes (corridors: who does what) and know BPMN (standardized notation) to understand, document, analyze and improve. She starts from “Process mapping & BPMN” and follows the approach: Create a cross-functional flow diagram (corridors): define the corridors (one per actor/department: Customer, Sales, Logistics, etc.). Place each step in the lane of the actor carrying it out; the passages from one corridor to another show the transmissions between actors (WHO is doing WHAT). Discover BPMN: the standardized BPMN model and templates (events, activities, gateways, flows) for rigorous and standardized modeling. Use these diagrams to ANALYZE the process (bottlenecks, redundancies, unclear responsibilities) as well as to document it. Expected result: You map business processes (lanes: who does what) and know BPMN (rigorous standardized notation) — key tools for understanding, documenting, analyzing and improving an organization.
Ongoing case from section 3.1: it comes back in the script and the 48 hour challenge.
1. Swimlanes
Level 3 covers specialized BUSINESS diagrams, starting with process mapping and BPMN — key topics for management, quality and organization. A simple flowchart (level 2) is sufficient to represent a basic process; but to model RIGOROUS business processes, INVOLVING SEVERAL ACTORS, we use more structured techniques. swimlanes: we organize a process into “lanes” (horizontal or vertical strips), each representing an ACTOR, a SERVICE or a ROLE (“Customer”, “Sales service”, “Logistics”, “Accounting”). Each step of the process is placed in the lane of the actor who carries it out. We then see not only the FLOW of the stages, but WHO is doing WHAT — essential for understanding a process involving several participants and their interactions (the passages from one corridor to another show the transmissions between actors). Visio provides the cross-functional flowchart template with swimlanes ready to use.
2. BPMN
The BPMN (Business Process Model and Notation) is a STANDARDIZED and international NOTATION for modeling business processes in a rigorous and standardized way. It is more than a flowchart: it is a complete language with precise symbols for events (start, end, intermediates), activities (tasks, sub-processes), gateways (decisions/branches, with different types: exclusive, parallel, etc.), flows (sequence, message), corridors and artifacts. BPMN makes it possible to model complex processes in an UNAMBIGUOUS way, understood by process professionals around the world — it is the standard for business process modeling (used in process management, quality, transformation, information systems). Visio provides a BPMN template and templates with standardized symbols, and can VALIDATE a BPMN diagram (verify that it follows the notation rules — section 4-5). Important points. (1) Process mapping (with corridors) responds to a frequent need: understanding and documenting WHO does WHAT in a multi-actor process — very useful in organization, quality, continuous improvement. (2) BPMN is more FORMAL and RIGOROUS (a true standardized notation) — to be used when rigor and standardization count (official process documentation, quality/BPM contexts, exchange with experts); for simpler needs, a lane flowchart is sufficient. (3) These diagrams are used to ANALYZE and IMPROVE processes (identify bottlenecks, redundancies, unclear responsibilities) as well as to document them. Mastering process mapping (corridors) and knowing BPMN is very rewarding in the management, organization, quality and IS professions: they are key tools for understanding, documenting, analyzing and improving the functioning of an organization — one of the most important professional uses of Visio.
🔎 Concrete example — View transmissions
Multi-actor.
Corridors: Customer | Commercial | Logistics | Accounting.
Every step in the hallway of who makes it.
→ the passages between corridors show the transmissions.Result: key tools to understand and improve an organization.
Reflex: corridors for most cases; BPMN if rigor required.
Section vocabulary
- Process mapping
- Represent a business process in a structured, often multi-actor way; is used to understand, document, analyze and improve the functioning of an organization.
Simple example: In “Process mapping & BPMN”, Nadia applies it as follows: create a cross-functional flow diagram (corridors): define the corridors (one per actor/department: Customer, Sales, Logistics, etc.).
What it is not: It is not a simple decorative element: without this reference, the diagram loses clarity or rigor.
Reflex: Process mapping → represent a business process in a structured, often multi-actor way
- Swimlanes
- Bands (horizontal/vertical) each representing an ACTOR/department/role; each step is placed in the corridor of who carries it out — we see WHO is doing WHAT and the transmissions.
Simple example: In “Process mapping & BPMN”, Nadia applies it as follows: create a cross-functional flow diagram (corridors): define the corridors (one per actor/department: Customer, Sales, Logistics, etc.).
What it is not: It is not a simple decorative element: without this reference, the diagram loses clarity or rigor.
Reflex: Swimlanes → strips (horizontal/vertical) each representing an ACTOR/department/role
- BPMN
- Business Process Model and Notation: STANDARDIZED and international notation to rigorously model business processes (events, activities, gateways, flows, corridors); the BPM standard.
Simple example: In “Process mapping & BPMN”, Nadia applies it as follows: create a cross-functional flow diagram (corridors): define the corridors (one per actor/department: Customer, Sales, Logistics, etc.).
What it is not: It is not a simple decorative element: without this reference, the diagram loses clarity or rigor.
Reflex: BPMN → business Process Model and Notation: STANDARDIZED and international notation to rigorously model business processes (events, activities, gateways, flows, corridors)
- BPMN symbols
- Precise language: events (start/end/intermediates), activities (tasks, sub-processes), gateways (decisions/branches), flows (sequence, message), artifacts.
Simple example: In “Process mapping & BPMN”, Nadia applies it as follows: create a cross-functional flow diagram (corridors): define the corridors (one per actor/department: Customer, Sales, Logistics, etc.).
What it is not: It is not a simple decorative element: without this reference, the diagram loses clarity or rigor.
Reflex: BPMN symbols → precise language: events (start/end/intermediates), activities (tasks, sub-processes), gateways (gateways: decisions/branches), flows (sequence, message), artifacts
- Analyze & improve
- These diagrams are used as much to ANALYZE and IMPROVE processes (bottlenecks, redundancies, unclear responsibilities) as to document them.
Simple example: In “Process mapping & BPMN”, Nadia applies it as follows: create a cross-functional flow diagram (corridors): define the corridors (one per actor/department: Customer, Sales, Logistics, etc.).
What it is not: It is not a simple decorative element: without this reference, the diagram loses clarity or rigor.
Reflex: Analyze & improve → these diagrams are used as much to ANALYZE and IMPROVE processes (bottlenecks, redundancies, unclear responsibilities) as to document them
In practice — Map a business process
- Create a cross-functional flow diagram (corridors): define the corridors (one per actor/department: Customer, Sales, Logistics, etc.).
- Place each step in the lane of the actor carrying it out; the passages from one corridor to another show the transmissions between actors (WHO is doing WHAT).
- Discover BPMN: the standardized BPMN model and templates (events, activities, gateways, flows) for rigorous and standardized modeling.
- Use these diagrams to ANALYZE the process (bottlenecks, redundancies, unclear responsibilities) as well as to document it.
Script to say — Process mapping & BPMN
1) Create a cross-functional flow diagram (corridors): define the corridors (one per actor/department: Customer, Sales, Logistics, etc.). 2) Place each step in the lane of the actor who carries it out; the passages from one corridor to another show the transmissions between actors (WHO is doing WHAT). 3) Discover BPMN: the standardized BPMN model and templates (events, activities, gateways, flows) for rigorous and standardized modeling. 4) Use these diagrams to ANALYZE the process (bottlenecks, redundancies, unclear responsibilities) as well as to document it. Then I check: You map business processes (lanes: who does what) and know BPMN (rigorous standardized notation) — key tools for understanding, documenting, analyzing and improving an organization
Adapt the names, forms and distribution format to your context.
Copy and paste model — Card 3.1
Card 3.1 — Process mapping & BPMN
Objective: map business processes (corridors: who does what) and know BPMN (standardized notation) to understand, document, analyze and improve
1. Create a cross-functional flow diagram (corridors): define the corridors (one per actor/department: Customer, Sales, Logistics, etc.).
2. Place each step in the lane of the actor carrying it out; the passages from one corridor to another show the transmissions between actors (WHO is doing WHAT).
3. Discover BPMN: the standardized BPMN model and templates (events, activities, gateways, flows) for rigorous and standardized modeling.
4. Use these diagrams to ANALYZE the process (bottlenecks, redundancies, unclear responsibilities) as well as to document it.
Expected result: You map business processes (lanes: who does what) and know BPMN (rigorous standardized notation) — key tools for understanding, documenting, analyzing and improving an organizationSME / low budget
Minimum version: PROCESS MAPPING: for multi-actor processes, lanes (swimlanes) — strips each representing an ACTOR/service — show WHO is doing WHAT and the transmissions (passages between lanes). We limit ourselves to a model, a diagram and a PDF export.
Algerian SME
Local context: BPMN (Business Process Model and Notation) is the STANDARDIZED and international NOTATION of BPM: a rigorous language (events, activities, gateways, flows, corridors) to model processes WITHOUT AMBIGUITY. We adapt the wording, examples and distribution formats to the team.
Remote work
Remote: corridors = frequent need (understand a multi-actor process). BPMN = more FORMAL/rigorous (official documentation, quality/BPM, exchange with experts); a lane flowchart is sufficient for simple needs. We favor cloud storage, sharing by link and comments.
Multidisciplinary team
For a mixed audience: these diagrams are used to ANALYZE and IMPROVE processes (bottlenecks, redundancies, unclear responsibilities) as well as to document them. Very rewarding in management, organization, quality, IS — a major professional use of Visio. We explain the symbols and keep the wording short.
✓ Best practices
- Use swimlanes for a multi-stakeholder process (who does what).
- Reserve BPMN for contexts requiring rigor and standardization.
- Use these diagrams to analyze, not just document.
✗ Common pitfalls
- A flat flowchart for a multi-actor process (we lose the “who”).
- Use full BPMN where simple lanes would suffice.
- Forgetting to show transmissions between actors.
Key takeaways
- PROCESS MAPPING: for multi-actor processes, lanes (swimlanes) — strips each representing an ACTOR/service — show WHO is doing WHAT and the transmissions (passages between lanes).
- BPMN (Business Process Model and Notation) is the STANDARDIZED and international NOTATION of BPM: a rigorous language (events, activities, gateways, flows, corridors) to model processes WITHOUT AMBIGUITY.
- Corridors = frequent need (understand a multi-actor process). BPMN = more FORMAL/rigorous (official documentation, quality/BPM, exchange with experts); a lane flowchart is sufficient for simple needs.
- These diagrams are used to ANALYZE and IMPROVE processes (bottlenecks, redundancies, unclear responsibilities) as well as to document them. Very rewarding in management, organization, quality, IS — a major professional use of Visio.
48h challenge — apply tomorrow
Within 48 hours, take an actual diagram and apply “Process Mapping & BPMN”: You map business processes (lanes: who does what) and know BPMN (rigorous standardized notation) — key tools for understanding, documenting, analyzing and improving an organization Deliver the .vsdx and a PDF export, with a sentence about what has changed.
- I know how to explain: PROCESS MAPPING: for multi-actor processes, the CORRIDORS (swimlanes) — bands each representing an ACTOR/service — show WHO is doing WHAT and the transmissions (passages between lanes).
- BPMN (Business Process Model and Notation) is the STANDARDIZED and international NOTATION of BPM: a rigorous language (events, activities, gateways, flows, corridors) to model processes WITHOUT AMBIGUITY.
- Corridors = frequent need (understand a multi-actor process). BPMN = more FORMAL/rigorous (official documentation, quality/BPM, exchange with experts); a lane flowchart is sufficient for simple needs.
Frequently asked questions
Swimlanes or BPMN: which approach to choose to map a process?
The choice between a simple swimlane diagram and formal BPMN depends on the NEED for rigor and CONTEXT — both are used to map processes, but at different levels of formality. Let's see how to decide. The SWIMLANES diagram / cross functional flow: (1) What it is: a flowchart organized in CORRIDORS, each representing an ACTOR (department, role, person). Each step is placed in the lane of whoever performs it. We see the FLOW of the process AND WHO does WHAT, as well as the TRANSMISSIONS between actors (when the flow passes from one corridor to another). (2) Advantages: SIMPLE to understand and create, very READABLE (you can see the responsibilities and interactions at once), sufficient for most of the understanding and communication needs of a multi-actor process. (3) FOR: understanding/documenting/communicating a process involving several actors, identifying who does what and the transmissions, analyzing a process (bottlenecks, unclear responsibilities) — in a framework where the rigor of a formal notation is not required. It is the accessible and versatile tool for mapping processes. BPMN (Business Process Model and Notation): (1) What it is: a STANDARDIZED and international NOTATION, more RIGOROUS and COMPLETE, with precise symbols (start/end/intermediate events, activities/tasks/sub-processes, gateways of different types, sequence/message flows, corridors, artifacts). It is a real LANGUAGE of process modeling, standardized worldwide. (2) Advantages: RIGOR and PRECISION (models complex processes without ambiguity, with precise semantics), STANDARDIZATION (understood by process professionals around the world — a common language), adapted to DEMANDING contexts (process management/BPM, quality, transformation, information systems, process automation). Visio can VALIDATE a BPMN (check compliance with the rules). (3) FOR: OFFICIAL and rigorous process documentation, BPM (Business Process Management)/quality contexts, exchange with process experts, complex processes requiring unambiguous modeling, process automation (BPMN can power process engines). (4) Disadvantage: more COMPLEX to learn and read (full notation has lots of symbols and rules) — oversized for simple needs. How to choose: (1) Need to UNDERSTAND/COMMUNICATE a multi-actor process, without formal notation requirements → CORRIDORS (swimlanes). Simple, readable, sufficient for most cases (document a process, show who does what, analyze). This is the default choice for common process mapping. (2) Need for RIGOR, STANDARDIZATION, BPM/quality/IS context, complex process, exchange with experts → BPMN. When precision and compliance with a standardized notation count (official documentation, rigorous modeling, automation), BPMN is the right choice — it is the professional standard in the field. (3) Consider the PUBLIC: for a general public (understanding a process), the corridors are sufficient and are more accessible; for process experts / a BPM context, BPMN is expected and meaningful. (4) Consider COMPLEXITY: a simple to medium process → corridors; a complex process requiring precise modeling → BPMN. (5) Consider your SKILLS/those of the public: the BPMN requires knowing the rating; the corridors are intuitive. A step-by-step approach: (1) For most process mapping needs, START with the swimlanes (accessible, readable, sufficient). (2) Learn and use BPMN when your context requires it (BPM, quality, IS, rigor) or to improve your skills in process modeling (a skill valued in these professions). (3) The two are not opposed: the corridors are also present in the BPMN; mastering the corridors prepares you for BPMN. In summary: choose SWIMLANES to map a multi-actor process in a SIMPLE and READABLE way (understand/communicate who does what, analyze) — the default choice, accessible and sufficient for most needs; choose BPMN for RIGOROUS and STANDARDIZED modeling (BPM/quality/IS contexts, complex processes, official documentation, exchange with experts, automation) — the professional standard, more formal but more demanding. The criterion: the need for rigor/standardization and the context. To understand and communicate a process, corridors are often enough; for rigorous professional modeling of BPM, BPMN is essential. Both are rewarding skills in management, organization, quality and IS — start with the (accessible) corridors, move up to the BPMN according to your needs. In both cases, these tools are used as much to ANALYZE and IMPROVE processes as to document them — one of the most valuable contributions of Visio for the organization's businesses.
What are swimlanes used for in a process map?