BPMN (Business Process Model and Notation) is the international standard for drawing business processes. If you have ever seen a diagram with boxes, diamonds, and arrows showing how work flows through an organization — that is probably BPMN.
BPMN in one sentence
BPMN is a visual language for describing how work gets done. It gives you a precise set of symbols that everyone — business analysts, developers, managers — interprets the same way.
The five building blocks
Every BPMN diagram uses just five types of elements:
- Events (circles) — things that happen. A start event triggers the process, an end event finishes it.
- Activities (rounded rectangles) — work that gets done. Tasks, sub-processes, call activities.
- Gateways (diamonds) — decision points. Exclusive (X) means one path, parallel (+) means all paths.
- Flows (arrows) — connect everything. Sequence flows show order, message flows show communication.
- Pools & Lanes — who does what. Pools represent organizations, lanes represent roles within them.
Why not just use a flowchart?
Flowcharts are informal. A diamond in one person's flowchart might mean something different in another's. BPMN standardizes this — an exclusive gateway (X) always means exactly one path, a parallel gateway (+) always means all paths.
BPMN also handles things flowcharts cannot: parallel work, role boundaries, message exchange between organizations, error handling, and timeouts.
Who uses BPMN?
- Business analysts document processes
- Process consultants use it as a common language across industries
- Developers implement processes in workflow engines like Camunda
- Compliance teams document regulated processes for auditors
- Organizations going through digital transformation map before automating
A brief history
BPMN was created in 2004 by the BPMI, adopted by the Object Management Group (OMG) in 2006, and reached version 2.0 in 2011. BPMN 2.0 is an ISO standard (ISO/IEC 19510:2013) and is what everyone means when they say "BPMN" today.
The four diagram types
- Process diagrams — the most common. Internal workflow of a single organization.
- Collaboration diagrams — multiple organizations interacting via message flows.
- Choreography diagrams — message exchange focus. Rarely used.
- Conversation diagrams — high-level overview. Also rarely used.
When NOT to use BPMN
- Simple checklists with no decisions
- Brainstorming sessions (use sticky notes first)
- One-time meeting explanations
- Software architecture (use UML or C4)
The rule of thumb: if the process involves decisions, multiple roles, or exceptions — BPMN is the right tool.
Start learning
The fastest way is to model real processes. We built free exercises for exactly this — real companies, real problems, BPMN solutions.
Read the full interactive guide with BPMN diagrams you can explore: What is BPMN?
Top comments (0)