BPMN in one sentence
BPMN (Business Process Model and Notation) is a standardized way to draw business processes so that everyone - from business analysts to developers to executives - can understand them.
Think of it as the blueprint language for how work flows through an organization. Just like architects use floor plans and electrical engineers use circuit diagrams, process professionals use BPMN to describe how tasks, decisions, and handoffs connect.
What does a BPMN diagram look like?
Here is a hiring process modeled in BPMN. An application arrives, HR reviews it, and the process branches: qualified candidates get interviews and offers, unqualified ones get a rejection email.
Even without knowing BPMN, you can probably follow the flow. That is the point. BPMN uses a small set of intuitive symbols that make processes readable at a glance.
The five building blocks
Every BPMN diagram is built from just five types of elements:
Events
Circles. Something that happens - a process starts, a message arrives, a timer fires, the process ends. Thin border = start, thick border = end.
Activities
Rounded rectangles. Work that needs to be done - "Review application", "Ship order", "Approve request". The core of every process.
Gateways
Diamonds. Decision points and synchronization. "Is the candidate qualified?" splits the flow into two paths. Only one is taken (exclusive gateway) or both run in parallel (parallel gateway).
Sequence Flows
Arrows connecting elements. They define the order: first this, then that. The simplest element, but the one that makes a diagram readable.
Pools and Lanes
Rectangles that organize who does what. A pool represents an organization or participant. Lanes divide the pool into roles - HR, IT, Management.
That is it. Five element types, and you can model most business processes. The full BPMN specification has more (timers, messages, sub-processes, error handling), but these five cover the fundamentals.
Why not just use a flowchart?
Flowcharts work for simple sequences. But they break down when processes involve multiple departments, parallel work, exceptions, or messages between systems.
BPMN handles all of that with a standard vocabulary. When you draw a diamond in a flowchart, it could mean anything. In BPMN, an exclusive gateway (X) means exactly one path is taken. A parallel gateway (+) means all paths run simultaneously. No ambiguity.
Here is an onboarding process where three tasks run in parallel - something a simple flowchart cannot express clearly:
Who uses BPMN?
BPMN is used across industries and roles:
- -Business analysts document how processes work today and design how they should work tomorrow.
- -Process consultants use BPMN as a common language when working with clients across different industries.
- -Developers implement processes in workflow engines like Camunda that execute BPMN directly.
- -Compliance teams document regulated processes in a format auditors can verify.
- -Organizations going through digital transformation map their processes before automating them.
Companies like IBM, Siemens, DHL, and thousands of others use BPMN daily. It is maintained by the Object Management Group (OMG), the same organization behind UML. The current version is BPMN 2.0.
A brief history of BPMN
BPMN was created in 2004 by the Business Process Management Initiative (BPMI), led by Stephen White at IBM. The goal was to create a notation that both business people and technical people could understand - bridging the gap between process design and implementation.
In 2006, BPMN was adopted by the Object Management Group (OMG), the same organization that maintains UML. The major revision, BPMN 2.0, was released in 2011 and is the current standard. It added formal execution semantics - meaning BPMN diagrams could now be directly executed by process engines, not just used for documentation.
BPMN 2.0 is an ISO standard (ISO/IEC 19510:2013). When someone says "BPMN" today, they almost always mean BPMN 2.0.
The four types of BPMN diagrams
BPMN 2.0 defines four diagram types. In practice, most people only use the first two:
Process diagrams
The most common type. Shows the internal workflow of a single organization or department. The hiring process above is a process diagram. This is what most people mean when they say "BPMN diagram".
Collaboration diagrams
Shows how multiple organizations or participants interact. Each participant gets their own pool, and message flows connect them. Used for B2B processes, customer-supplier interactions, or cross-department workflows.
Choreography diagrams
Focuses on the message exchange between participants rather than the internal process of any one participant. Rarely used in practice.
Conversation diagrams
A high-level overview of which participants communicate with each other, without showing the details. Think of it as the executive summary of a collaboration.
BPMN vs other notations
BPMN is not the only process notation. Here is how it compares:
| Notation | Best for | Limitation |
|---|---|---|
| BPMN | Detailed business processes with decisions, parallel work, exceptions | Steeper learning curve than simple flowcharts |
| Flowcharts | Simple sequential procedures, quick sketches | No standard for parallel work, roles, messages, or exceptions |
| UML Activity | Software system behavior, developer-focused workflows | Too technical for business stakeholders |
| EPC | Enterprise architecture (especially SAP environments) | Declining adoption, mostly legacy in ARIS/SAP tooling |
| Value Stream Mapping | Lean manufacturing, identifying waste in production | Not suited for decision logic or exception handling |
BPMN has the broadest adoption because it works for both documentation and execution. A business analyst can draw a BPMN diagram that a developer can implement directly in a process engine - no translation needed.
When not to use BPMN
BPMN is powerful, but not everything needs it:
- -Simple checklists - if the process is purely sequential with no decisions or parallel steps, a numbered list is fine.
- -Brainstorming sessions - use sticky notes or Miro first. Formalize into BPMN later when the process is understood.
- -One-time explanations - if you just need to explain something once in a meeting, a quick whiteboard sketch works. BPMN is for processes that need to be documented, shared, and maintained.
- -Software architecture - use UML or C4 diagrams. BPMN models business processes, not system architecture.
The rule of thumb: if the process involves decisions, multiple roles, exceptions, or needs to be understood by people who were not in the room when it was designed - BPMN is the right tool.
How to learn BPMN
The fastest way to learn BPMN is to model real processes. Reading about symbols is useful, but the notation clicks when you apply it to actual problems.
We built a set of free exercises for exactly this. Each one is a real company with a real problem - a shoe shop, a racing pit crew, a spacecraft manufacturer. You learn the elements by seeing them solve actual business challenges.
Quick reference
Once you start modeling, you will want to look up specific elements. These resources help:
Frequently asked questions
What does BPMN stand for?▼
BPMN stands for Business Process Model and Notation. It is a graphical standard maintained by the Object Management Group (OMG) for specifying business processes in a visual format.
Is BPMN hard to learn?▼
The basics are straightforward - you can read a simple BPMN diagram within minutes. The five core elements (events, activities, gateways, flows, and pools) cover most real-world processes. Advanced features like error handling and compensation take more practice.
What is the difference between BPMN and a flowchart?▼
Flowcharts use informal shapes with no standard meaning. BPMN has a precise vocabulary: an exclusive gateway (X) means exactly one path, a parallel gateway (+) means all paths. BPMN also supports pools, lanes, message flows, and events - concepts flowcharts cannot express.
What is the difference between BPMN 1.0 and BPMN 2.0?▼
BPMN 2.0 (released 2011) added formal execution semantics, meaning diagrams can be directly executed by process engines. It also introduced choreography diagrams, conversation diagrams, and a standardized XML interchange format. BPMN 1.0 was documentation-only.
Can BPMN diagrams be executed?▼
Yes. BPMN 2.0 defines an XML format that process engines like Camunda, Flowable, and jBPM can execute directly. This means the same diagram used for documentation can drive automated workflows.
What tools can I use to create BPMN diagrams?▼
Options range from free tools like Crismo and bpmn.io to enterprise platforms like ARIS and SAP Signavio. General diagramming tools like draw.io offer BPMN shapes but do not validate your diagram against the specification.