Business Process Modeling (BPMN & Flowcharts)

Business Process Modeling is the visual representation of how work flows through an organization — from trigger to outcome. As a Business Analyst, the ability to draw a clear process diagram is as important as the ability to write a clear requirement. Process models help stakeholders see the current state, identify inefficiencies, and agree on the future state before any solution is built.

This topic covers the three most common process modeling techniques: BPMN (Business Process Model and Notation), flowcharts, and swimlane diagrams. You will learn the standard notation, how to model AS-IS and TO-BE processes, and the basics of process improvement. You will also get hands-on with the tools BAs use: Visio, Lucidchart, and draw.io.

Complete Business Analysis Fundamentals and Requirements Elicitation before starting this topic.

You cannot improve a process you do not understand. Process modeling gives you a visual language to:

• Document the current state — capture how work actually happens (not how people think it happens)
• Identify inefficiencies — find bottlenecks, redundant steps, and unnecessary handoffs
• Align stakeholders — everyone sees the same picture, reducing miscommunication
• Define the future state — design the improved process before building the solution
• Support requirements — each process step maps to specific functional requirements

Process modeling is especially powerful because it makes invisible work visible. When you draw a process, stakeholders often realize for the first time how many steps, loops, and exceptions their daily work actually involves.

Flowcharts are the simplest and most universal process diagram. They use a handful of standard symbols:

Example: Employee Leave Request Process

1. Start (oval) → Employee submits request (rectangle)
2. Manager reviews (diamond): Approved? → Yes: HR processes → End; No: Rejected → End

Rules: Every flowchart must have exactly one start and one end (or a clear set of ends). Every decision diamond must have at least two outgoing arrows (Yes/No). Flows should go left-to-right or top-to-bottom when possible.

BPMN (Business Process Model and Notation) is the industry standard for professional process modeling. It is more detailed than a flowchart and supports complex scenarios like parallel activities, error handling, and sub-processes.

Core BPMN elements:

• Events (circles): Things that happen — start event, end event, intermediate events (e.g., "receive email," "timeout")
• Activities (rounded rectangles): Work that is performed — tasks and sub-processes
• Gateways (diamonds): Decision points — exclusive (XOR), parallel (AND), inclusive (OR)
• Sequence Flows (arrows): Order of activities
• Swimlanes (pools/lanes): Who does what — roles or departments as horizontal rows
• Data Objects (documents): Information flowing through the process

BPMN Gateway types:

Swimlane diagrams add a critical dimension to flowcharts: who is responsible for each step. Each swimlane represents a role, department, or system.

Example: Purchase Order Process

• Lane 1 — Requester: Submits PO request
• Lane 2 — Manager: Approves or rejects
• Lane 3 — Procurement: Creates PO and sends to vendor
• Lane 4 — Finance: Processes payment

Swimlane diagrams are invaluable because they make handoffs visible — the points where work moves from one role to another. Handoffs are where delays, miscommunication, and errors most commonly occur.

Key benefits of swimlanes:

• Clarify accountability — everyone knows what they own
• Reveal bottlenecks — if one lane has many tasks, that role is overloaded
• Identify unnecessary handoffs — can some steps be combined?
• Support requirements — each lane maps to a different user role in the requirements

The most common modeling exercise in BA work is the comparison between the current state and the desired future state:

AS-IS process: How work happens today. Document it honestly — include every step, exception, workaround, and manual process. This is often messy, but it is the baseline for improvement.

TO-BE process: How work will happen after the solution is implemented. This is the improved, optimized version. Every change in the TO-BE model must be justified by a specific business reason.

Gap Analysis: The difference between AS-IS and TO-BE reveals:

• Steps to eliminate — redundant approvals, duplicate data entry
• Steps to automate — manual tasks that a system can handle
• Steps to add — compliance checks, notifications, or analytics that were missing
• Handoffs to reduce — fewer department crossings means faster processing

Always present both models side-by-side so stakeholders can see exactly what changes and why.

Process modeling is not just documentation — it is the foundation for improvement. Common techniques:

Bottleneck Analysis: Find the step with the longest wait time or highest queue. Every process has at least one bottleneck — improving anything else does not speed up the overall process.

Lean Waste Elimination (TIMWOODS):

• Transport — unnecessary movement of data or materials
• Inventory — unprocessed work sitting in queues
• Motion — unnecessary human movement
• Waiting — idle time between steps
• Overproduction — doing more than needed
• Over-processing — doing work at a higher quality than required
• Defects — errors requiring rework
• Skills — underutilizing people’s abilities

Six Sigma DMAIC: Define → Measure → Analyze → Improve → Control. A structured approach to reducing process variation and defects.

Several tools make process modeling faster and more collaborative:

For learning and practice, draw.io is the best starting point — free, full-featured, and exports to all standard formats.

1. Draw a flowchart for a process you follow daily (e.g., making coffee, submitting an expense report). Use standard symbols.
2. Convert your flowchart into a BPMN diagram with at least one gateway and two lanes.
3. Model an AS-IS process for a real or hypothetical business process (e.g., employee onboarding) with at least 8 steps and 2 decision points.
4. Design the TO-BE version of that process, identifying at least 3 improvements.
5. Map at least 3 handoffs in your swimlane diagram and identify which ones could be eliminated.
6. Use draw.io or Lucidchart to create and export your diagrams professionally.

In a real job, process modeling is your most persuasive tool. When you present a messy AS-IS process with 23 steps and 5 manual handoffs, stakeholders immediately see the problem — no amount of text has the same impact. When you then present the TO-BE process with 9 steps and 2 automated handoffs, the business case makes itself. Process models also feed directly into requirements: every TO-BE step becomes a functional requirement, and every improvement becomes a business justification. BAs who can draw clear process models are the ones who get buy-in for their recommendations.

Business problem: A retail company processes customer returns manually. The process takes 10 days on average and has a 15% error rate.

Objective: Model the current process, identify inefficiencies, and design an improved process.