Process Mapping & Analysis
Topic 4 of 12 · In Process Improvement · September 9, 2026
Master flowcharting, swimlane diagrams, BPMN 2.0, value-added analysis, bottleneck identification, Theory of Constraints basics and process mining.
Overview
You cannot improve what you cannot see. Process mapping is the practice of creating visual representations of how work actually flows — from trigger to completion. A good process map reveals handoffs, delays, loops, decision points and redundancies that are invisible in verbal descriptions.
This topic goes beyond basic flowcharting. You will learn swimlane diagrams that show who does what, BPMN 2.0 — the industry standard for professional process notation — and analytical techniques like value-added analysis, bottleneck detection and Theory of Constraints. By the end you will be able to draw any process accurately, analyze it for inefficiencies, and identify exactly where to focus improvement efforts.
Before You Start
- Complete Lean Methodology and Six Sigma Basics first, since mapping supplies the visual backbone for VSM and DMAIC work.
- Choose a process involving at least three roles or departments — employee onboarding, course registration or order fulfilment — to map across lanes.
- Have timed data for each step before the lesson so the bottleneck analysis can use real numbers rather than guesses.
- Review the standard flowchart symbols (terminator, process, decision, connector, data, delay) before starting the lesson.
- Be ready to compare your map of how the process actually works against the way it is officially supposed to work.
Learning Objectives
- Draw flowcharts using standard symbols (terminator, process, decision, connector, data)
- Create swimlane diagrams that clarify roles and handoffs
- Read and create BPMN 2.0 diagrams for complex processes
- Perform value-added analysis on each step of a process map
- Identify bottlenecks using time and capacity data
- Apply the five focusing steps of the Theory of Constraints
- Understand the basics of process mining from event logs
Prerequisites
Complete Lean Methodology and Six Sigma Basics (DMAIC). You should be familiar with value stream mapping and the DMAIC framework before diving into detailed mapping techniques.
Flowcharting — Standard Symbols
A flowchart is the simplest and most universal process map. It uses a small set of standardized symbols:
| Symbol | Shape | Represents |
|---|---|---|
| Terminator | Rounded rectangle / oval | Start or end of the process |
| Process | Rectangle | A task or activity step |
| Decision | Diamond | A yes/no or multiple-choice question that splits the flow |
| Connector | Arrow | Direction of flow between steps |
| Data / Document | Parallelogram / rectangle with wave bottom | Input or output of data/materials |
| Delay | D-shape | A wait or queue in the process |
Rules: flow top-to-bottom or left-to-right; every connector must lead somewhere; every decision must have at least two outgoing arrows; avoid crossing lines.
Swimlane Diagrams
A swimlane diagram adds a critical dimension to flowcharting: who performs each step. The diagram is divided into horizontal or vertical lanes, one per role, department or system. Steps are placed in the lane of the person or team responsible.
Swimlane diagrams excel at revealing:
- Handoff waste — every time the flow crosses a lane, a handoff occurs, and handoffs are the #1 source of delays and errors
- Accountability gaps — if no lane owns a step, no one is responsible
- Parallel vs sequential work — steps in different lanes can sometimes happen simultaneously
BPMN 2.0 — Professional Process Notation
Business Process Model and Notation (BPMN) 2.0 is the international standard (ISO/IEC 19510) for process modeling. It provides a rich, precise visual language that goes far beyond basic flowcharts:
- Events — circles with icons representing triggers (message received, timer, error) and outcomes (message sent, termination)
- Activities — rounded rectangles; sub-processes are expandable boxes
- Gateways — diamonds with symbols distinguishing parallel (AND), exclusive (XOR) and inclusive (OR) splits and joins
- Sequence flows — solid arrows showing the order of activities
- Message flows — dashed arrows showing communication between pools (organizations or systems)
- Artifacts — data objects, annotations and groups for additional context
BPMN is essential when processes span multiple systems or organizations, because it can model inter-system communication explicitly.
Value-Added vs. Non-Value-Added Analysis
Once a process is mapped, classify every step using the Lean value framework:
- Value-Added (VA) — the customer would pay for this step if they knew it existed. It changes the form, fit or function of the output in a way the customer values.
- Business-Value-Added (BVA) or Necessary Non-Value-Added (NNVA) — required by regulation, compliance, safety or internal policy, but the customer would not pay for it if they could avoid it.
- Non-Value-Added (NVA) — pure waste. The customer would refuse to pay for it and would not notice if it disappeared.
Example in an insurance claim: Assessing the claim (VA), filing regulatory reports (BVA), re-entering data from one system into another because the systems don't integrate (NVA).
The goal: maximize VA, minimize BVA where possible, and ruthlessly eliminate NVA.
Bottleneck Analysis
A bottleneck is the step in a process with the lowest capacity — the step that limits the throughput of the entire process. No matter how fast the other steps work, the process cannot go faster than the bottleneck.
How to find bottlenecks:
- Measure the cycle time (or capacity) of each step.
- The step with the longest cycle time or lowest capacity is the bottleneck.
- Calculate utilization for each step: actual output ÷ maximum capacity. A step running at 100 % utilization is likely the bottleneck or very close to it.
Impact: Improving any step other than the bottleneck does not improve overall throughput — it just creates more inventory or waiting before or after the bottleneck. This is a critical insight from the Theory of Constraints.
Theory of Constraints — The Five Focusing Steps
The Theory of Constraints (TOC), developed by Eliyahu Goldratt in The Goal, provides a systematic method for improving any constrained system:
- Identify the constraint — which step limits throughput?
- Exploit the constraint — make sure the bottleneck is working on the highest-value items with zero idle time. No lunch breaks at the bottleneck without coverage.
- Subordinate everything else — align all non-bottleneck steps to the pace of the bottleneck. Slowing down non-bottlenecks to match the bottleneck eliminates excess inventory.
- Elevate the constraint — if exploiting is not enough, invest in more capacity (hire, automate, outsource the bottleneck step).
- Repeat — once the bottleneck is resolved, a new constraint will appear elsewhere. Return to step 1.
TOC is powerful because it prevents the common trap of improving everything equally. Concentrated effort on the single biggest constraint yields disproportionate results.
Process Mining Introduction
Process mining is a data-driven technique that automatically generates process maps from event logs in IT systems (ERP, CRM, ticketing systems). Instead of interviewing people and drawing maps by hand, process mining tools analyze the digital trace of every case and produce an actual process map showing how work really flows — including deviations, rework loops and bottlenecks.
Popular tools: Celonis, Disco (Fluxicon), ProM, UiPath Process Mining. Common event log fields: Case ID, Activity, Timestamp (and optionally Resource, Cost).
Process mining is especially valuable for large, complex processes with thousands of cases where manual mapping is impractical.
Hands-On Practice
Choose a process you are involved in at work or school:
- Draw a detailed flowchart using standard symbols. Include every decision point and loop.
- Convert it into a swimlane diagram identifying all roles involved.
- Classify each step as VA, BVA or NVA. Calculate the value-added ratio.
- Measure or estimate cycle time for each step and identify the bottleneck.
- Apply the five focusing steps of TOC to the bottleneck: what would you exploit, subordinate and elevate?
- If you have access to event log data, try importing it into a free process mining tool (Disco offers a free trial) and compare the discovered map to your manual map.
Deeper Worked Examples
Swimlane map and bottleneck of a purchase requisition
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Five focusing steps on a packaging line
Step 1
Step 2
Step 3
Step 4
Step 5
Common Mistakes
- Drawing the process as it should work instead of how it actually works — always map reality first
- Skipping decision points — they are the most common source of process variation
- Ignoring handoffs between roles — handoffs are where delays and errors concentrate
- Mapping too large a scope in one diagram — break complex processes into sub-processes
- Failing to label the time and data requirements for each step — a map without data is just a picture
- Confusing the bottleneck with the most expensive step — the bottleneck is defined by capacity, not cost
Real-World Usage
A logistics company mapped its shipment processing using swimlane diagrams and discovered that 40 % of lead time was spent in a single handoff: the warehouse team physically walking signed paper forms to the dispatch office. By digitizing the form and integrating it into the existing system, they eliminated the handoff and reduced lead time by 35 %. The process map made this invisible waste visible for the first time.
Mini Project
Business problem: A university's course registration process takes students an average of 45 minutes online, with 20 % of students needing to visit the registrar's office in person to resolve issues.
Objective: Map the registration process, identify bottlenecks and waste, and design an improved process flow.
Task 1
Task 2
Task 3
Task 4
Task 5
Task 6
Task 7
Task 8
| Deliverable | What it proves |
|---|---|
| Current-state flowchart | You can use standard flowchart symbols accurately |
| Swimlane diagram | You can identify roles and handoffs |
| Value-added classification | You can distinguish VA, BVA and NVA steps |
| Bottleneck identification | You can find the process constraint |
| TOC analysis | You can apply the five focusing steps |
| Future-state process map | You can design an improved flow |
| Registrar recommendation | You can communicate improvements clearly |
Key Takeaways
- Flowcharts use standard symbols (terminator, process, decision, connector) to map any process
- Swimlane diagrams add role accountability and expose handoff waste
- BPMN 2.0 is the international standard for professional process modeling
- Value-added analysis classifies steps as VA, BVA or NVA to prioritize improvement
- Bottleneck analysis finds the capacity-constrained step that limits total throughput
- Theory of Constraints provides five focusing steps: Identify, Exploit, Subordinate, Elevate, Repeat
- Process mining automatically discovers actual process flows from event log data
Key Terms & Glossary
| Term | Meaning |
|---|---|
| Flowchart | The simplest process map, using standard shapes such as the rounded terminator, rectangle for a task, diamond for a decision and arrow for flow direction. |
| Swimlane diagram | A flowchart divided into lanes, one per role, department or system, which makes handoffs and accountability gaps visible. |
| BPMN | Business Process Model and Notation 2.0, the international standard (ISO/IEC 19510) whose circles, rounded rectangles, gateways and message flows model complex multi-system processes precisely. |
| Bottleneck | The step with the lowest capacity that limits the throughput of the entire process, regardless of how fast the other steps run. |
| Theory of Constraints | Goldratt's five focusing steps — Identify, Exploit, Subordinate, Elevate, Repeat — for improving a constrained system by concentrating effort on its single biggest constraint. |
| Process mining | Automatically generating a real process map from IT event logs (case ID, activity, timestamp) to reveal how work actually flows rather than how it is intended to flow. |
Learning Resources
BPMN 2.0 Specification (Object Management Group)
The official BPMN standard documentation.
The Goal — Eliyahu Goldratt
The classic novel that introduces the Theory of Constraints through a compelling story.
Process Mapping and Analysis (LinkedIn Learning)
Practical course on flowcharting, swimlanes and BPMN for business professionals.
Celonis Process Mining Academy
Free courses on process mining concepts and hands-on exercises with the Celonis tool.
Understanding the Theory of Constraints — Eliyahu Goldratt
A concise explanation of TOC principles and the five focusing steps.
Chapter Quiz
Chapter Quiz — Process Mapping & Analysis
Flowchart symbols, swimlanes, BPMN, value-added analysis, bottleneck detection, TOC and process mining.
Question 1 of 5
In a flowchart, a diamond shape represents:
Knowledge Check
End-of-Topic Exam
Hint: Three roles nearly always demands a swimlane; then list what every handoff can lose.
Model answer: I would draw a swimlane diagram with one lane each for HR, IT, the manager and the new employee, because a simple flowchart would hide who does what at each boundary. I would use a terminato for start and end, rectangles for concrete steps, diamonds for decisions (e.g. does the hire need a laptop?), and delay symbols for queues. The three handoff risks are: waiting, because every time work crosses a lane it sits in someone's inbox; miscommunication, because instructions are lost between departments (for example, access requested with the wrong role); and accountability gaps, because a task that belongs to no lane is simply never done. I would annotate each handoff with a target turnaround, then use value-added analysis to decide which steps are genuinely necessary.
Hint: The slowest daily capacity is the constraint; the other steps must match it.
Model answer: Step B at 30 units/day is the constraint; total output cannot exceed 30 units/day whatever you do to A and C, so the team would be 30 units short of the 100-unit demand. Exploit B by keeping it fully loaded — running it without idle breaks, on the highest-value or most urgent units, with all its inputs pre-positioned. Subordinate A and C by pacing them to B, producing only what B can consume so inventory does not grow ahead of the constraint. Elevate B by adding capacity — a second machine, overtime or moving part of the work — until its capability exceeds demand; then measure again, because a new constraint (likely C at 70 units/day) will appear and the five focusing steps must repeat.
Hint: One captures intention by observing people; the other captures reality from data.
Model answer: Manual process mapping (flowcharts and swimlanes) captures the intended process — what people believe happens — built through interviews and observation, and is ideal for small or improvement-focused scopes. Process mining reconstructs the actual process from event logs (case ID, activity, timestamp) in the ERP, CRM or ticketing system, which makes it the right choice for large, data-rich processes with thousands of cases where manual mapping is impractical. The gap between the two is diagnostic gold: deviations, rework loops and bottlenecks that appear in the mined map but nowhere in the manual map reveal undocumented shortcuts, bypassed approvals and handoff delays — precisely the waste the improvement project should attack.
Hint: Ask who would actually pay for each step if they could avoid it.
Model answer: Assessing the damage is value-added: it changes the claim in a way the customer pays for and depends on. Filing the regulator's mandatory report is business-value-added (necessary non-value-added): the customer would not pay for it, but regulation requires it, so it should be minimised but not removed. Re-typing the customer's address is pure non-value-added waste: the customer would refuse to pay for it, would never notice if it vanished, and it sits squarely under the 'extra-processing' waste since the address already exists in the email. The improvement target is to eliminate the re-typing by integrating email capture into the claims system, not to touch the compliance step.