BPMN

A standard notation for drawing business processes — events, tasks, gateways and flows. Its value is that a diagram means the same thing to everyone who reads it.

Also called: Business Process Model and Notation

What it is

Business Process Model and Notation is a standard set of shapes for describing a process: circles for events, rounded rectangles for tasks, diamonds for decisions, arrows for sequence. It is a notation rather than a tool, and its whole point is that a diamond means the same thing in your diagram as in someone else's.

The subset that does the work

  • Start and end events: where the process begins and what states it can finish in. Processes with no defined end are usually the ones nobody can measure.

  • Task: a unit of work with an owner.

  • Exclusive gateway: a decision, exactly one path taken. The most commonly misused symbol — parallel work is not an exclusive gateway.

  • Parallel gateway: paths that proceed simultaneously.

  • Sequence flow: the arrow. Direction matters and should be consistent.

Why bother with a standard

An ad-hoc diagram is faster to draw and slower to use. Six months later nobody can tell whether a box was a decision or a step, whether two arrows leaving a shape meant "and" or "or", or who owned which part. A notation removes that ambiguity at the cost of learning about eight symbols.

Where it stops helping

BPMN describes sequence, not data. A process diagram showing a clean handoff can coexist with an integration that drops half the fields. Pair it with a data model, or the diagram will be accurate and useless.

RELATED TERMS

COMMON QUESTIONS

Do I need the full BPMN specification?
No. Five or six symbols cover the overwhelming majority of revenue process work. The full specification exists for automation engines, not for aligning a go-to-market team.
What is the difference between an exclusive and a parallel gateway?
Exclusive means exactly one outgoing path is taken. Parallel means all of them are, at once. Using exclusive where work genuinely happens in parallel is the most frequent modelling error.
BPMN or a flowchart?
A flowchart is fine for something you will throw away. If the diagram is going to be referenced, handed over or built from, the shared meaning of BPMN pays for itself quickly.

WHERE THIS HAS BEEN APPLIED

Client work and research from RevOps HQ, our consulting practice.

Build the capability

Definitions are the vocabulary. The courses are where you learn to operate it, with the interactive audit tools.

See the courses