Business Process Modeling Tools and Techniques: Choose the Technique Before the Software
Teams often start process modeling by picking software, then discover the diagram answers the wrong question. The better order is to decide what you need to learn, choose the technique that shows it, and only then choose a tool. This guide compares six common techniques, runs one made-up process through them, sorts tools into five types without naming a favorite vendor, and gives a short checklist for diagrams people will actually read. If you need the basics first, start with what is a business process.
Technique first, tool second
A process model is a picture of how work moves. Different pictures answer different questions. A one-page overview answers “what are we talking about?” A detailed diagram answers “who does what, in what order?” A timing map answers “where does the time go?” No single diagram answers all three well.
That is why tool shopping goes wrong. Most tools can draw boxes and arrows. What differs is the notation they support, how many people can edit, and whether the diagram can feed other systems. Decide your question first, and the tool list gets shorter.
Six techniques compared
The table below is our summary. ASQ (the American Society for Quality) provides the definitions for the first two rows. The rest are common practice descriptions.
| Technique | What it shows | Best question it answers | Watch out for |
|---|---|---|---|
| SIPOC | Suppliers, inputs, process, outputs, customers on one page | What is in and out of scope? | Too high-level to find root causes |
| Flowchart | The steps and decisions in order | How is this process performed? | Gets messy beyond a page or two |
| Swimlane diagram | A flowchart with lanes for each person, team or system | Who hands work to whom? | Many lanes make hand-off problems obvious but the picture crowded |
| Value stream map | Steps with work time and waiting time | Where does the time go? | Needs measured data, not guesses |
| BPMN diagram | A standard notation with events, activities and gateways | How do we share one precise model across business and technical teams? | Readers must learn the symbols |
| Process mining | The process as it really ran, rebuilt from system event logs | What really happens, including the exceptions? | Needs good data in your systems |
SIPOC
According to ASQ’s SIPOC description, SIPOC stands for suppliers, inputs, process, outputs and customers, with optional constraints and measures. ASQ calls it a data collection tool for improvement teams that gives a high-level view of a process’s current state, and suggests using it when first investigating a process and before building a flowchart. For the process block it recommends listing the key five to seven core activities. Use it at the start of any project to agree on the boundaries.
Flowchart
ASQ defines a flowchart as a common type of process map that visually represents the steps of a process. Its listed uses include understanding how a process is performed, studying it for improvement and defining its boundaries. Standard symbols include a rectangle for a step, a diamond for a decision based on a question, an arrow for direction of flow, and a semicircle for a delay or wait.
Swimlane diagram
A swimlane diagram is a flowchart divided into lanes, one for each person, department or system. Steps sit in the lane of whoever performs them, and arrows that cross lanes show hand-offs. It is the most useful single diagram when the problem is “things fall between teams.”
Value stream map
A value stream map adds timing to the steps: how long work takes and how long it waits. It comes from lean practice. ASQ describes value stream mapping as a product process analysis and improvement tool. Our guides to Six Sigma vs. Lean Six Sigma and DMAIC show where such maps fit.
BPMN
BPMN, the Business Process Model and Notation, is a standard from the Object Management Group, also published as ISO/IEC 19510. Its core symbols are events, activities, gateways and the flows that connect them. Choose it when many people, including technical staff, must read and maintain the same diagram, or when the model may later become an automated workflow.
Process mining
Process mining works backward from data. Instead of asking people how the process works, it reads timestamps and case IDs from systems and reconstructs the actual paths. It can show variants nobody drew, such as rework loops and skipped steps. Its limit is data quality: if the system does not record the step, mining cannot see it.
One process, several views
This is our made-up example: a retailer’s online return process. It shows how each technique picks out something different.
| Technique | What you would draw or write for this process |
|---|---|
| SIPOC | Supplier: customer. Input: return request, order number. Process: request, review, approve, label, receive, refund. Output: refund and updated stock. Customer: the shopper. |
| Flowchart | Start, request submitted, review, decision “within return window?” (no: decline), approval, label, item received, inspection, refund, end. |
| Swimlane | Lanes for Customer, Support, Manager, Warehouse and Finance. Every hand-off between teams shows up as an arrow that crosses a lane. |
| Value stream map | Timing per step, in the table below. |
| BPMN | The same flow with a start event, tasks, an exclusive gateway for the return-window decision and an end event, with the lanes kept inside one pool. |
Timing for the value stream view (assumed numbers):
| Step | Work time (hours) | Waiting time (hours) |
|---|---|---|
| Customer submits request | 0.10 | 0 |
| Support reviews | 0.25 | 24 |
| Manager approves | 0.10 | 48 |
| Warehouse issues label | 0.20 | 24 |
| Item received and inspected | 0.50 | 72 |
| Finance issues refund | 0.20 | 24 |
| Total | 1.35 | 192 (8 days) |
People work about 1.35 hours in a process that takes about 193 hours, so work time is roughly 0.7 percent of the total. The map shows that speed depends on waiting, not on how fast people work. Only the value stream view makes that obvious. The flowchart alone would have hidden it. Real figures will differ; measure your own.
Five types of tools
Tools change quickly, so we describe categories rather than products. Check current features and prices with each vendor.
| Tool type | Good for | Typical limits |
|---|---|---|
| Whiteboard, paper, sticky notes | Workshops; first drafts with the people who do the work | Not easy to store, version or share later |
| General diagramming tools | Flowcharts and swimlanes that people can edit together | Notation is not enforced; models do not connect to systems |
| Dedicated BPMN modelers | Standard models, shared repositories, consistency across teams | Learning curve; more setup |
| BPM and workflow platforms | Turning a model into running, automated workflow | Higher cost; takes technical skills and change management |
| Process mining software | Finding real paths and bottlenecks from system data | Needs clean event logs; best on large volumes |
How to choose
| If you need to… | Start with this technique | And this tool type |
|---|---|---|
| Agree scope with a new team | SIPOC | Whiteboard |
| Document how a small process works | Flowchart or swimlane | General diagramming tool |
| Fix hand-off problems between departments | Swimlane | General diagramming tool |
| Cut lead time | Value stream map | Whiteboard first, then a diagramming tool |
| Share one precise model across business and IT | BPMN | BPMN modeler |
| Automate a process | BPMN | BPM or workflow platform |
| Find out what really happens at scale | Process mining | Process mining software |
Most small teams need only the first three rows. Try a pilot on one process before buying anything. If you later improve the process, see what is BPM for the management side.
Rules for diagrams people read
- One page per view. If it needs more, break out sub-processes.
- Start and end clearly. Name the trigger and the result.
- Label steps with verb and object. “Approve return,” not “Approval.”
- Label every decision outcome. “Yes” and “No” at least.
- Show how work really happens. Check the draft with the people who do it.
- Add time where you can. Even rough waiting times help.
- Date and version it. Old diagrams cause arguments.
Common mistakes
- Modeling the manual instead of the work. Observe and ask; do not copy policy documents.
- Over-modeling. A diagram nobody uses is waste.
- Buying a platform for a one-off fix. Start with the lightest tool that answers the question.
- Skipping the “to-be” model. Mapping the current state is only half the job. Draw what you will change.
- Ignoring exceptions. The unusual cases often cause the most delay.
- Letting models go stale. Assign an owner and a review date.
Learn more
If you want structured learning, online providers such as Coursera and Udemy list business process management and modeling courses. We may earn a commission if you sign up, at no cost to you. We are not affiliated with any university. Check the syllabus, including which notation and tools it teaches, before you pay. For study options and credentials, see our business process management certificate guide, or browse all BPM guides.
Frequently asked questions
What is business process modeling?
Drawing or describing a business process so people can understand, analyze and improve it. The model can be a simple flowchart or a formal diagram in a standard notation.
What are the main business process modeling techniques?
Common ones include SIPOC, flowcharts, swimlane diagrams, value stream maps, BPMN and process mining. Each answers a different question.
What is the difference between a flowchart and a swimlane diagram?
A flowchart shows steps and decisions in order. A swimlane diagram adds lanes for each person, team or system, so you can see who does each step and where hand-offs occur.
What is BPMN?
The Business Process Model and Notation, a standard from the Object Management Group that is also published as ISO/IEC 19510. It uses events, activities, gateways and flows.
Do I need BPMN?
Not for a simple process or a small team. It becomes useful when many people must share one precise model, or when you plan to automate the workflow.
What is SIPOC used for?
For a one-page view of a process’s suppliers, inputs, process, outputs and customers. ASQ suggests using it at the start of an investigation and before drawing a flowchart.
Which business process modeling tool is best?
It depends on your question, team size and budget. Pick the technique first, then the lightest tool that supports it. Test with a real process before committing.
How is process mining different from process modeling?
Modeling draws the process as people describe or design it. Process mining reconstructs it from system data, so it shows what actually happened, including exceptions.
Browse certificate, course and degree programs side by side.