BPMN notation guide: top 6 dilemmas explained
Even experienced modellers hit moments of genuine uncertainty in BPMN. Should this be a Call Activity or a Subprocess? Is this step a User Task or a Manual Task? Does this boundary belong in a Pool or a Lane? These BPMN dilemmas are more common than most practitioners admit, and the element names alone don't always make the answer obvious.
This guide works through six of the most common BPMN "false friends": pairs of elements that are easy to confuse because they share a purpose but follow different rules.
For each pair of BPMN "false friends", you get:
- What the two elements have in common, so you understand why the confusion arises
- What makes them different: the specific rules and behaviors that distinguish them
- When to use each one: a clear, direct guidance you can apply in the moment.
The six dilemmas covered are:
- Call Activity vs Subprocess
- Message vs Signal
- Send/Receive Task vs Intermediate Message Events
- User Task vs Manual Task
- Script Task vs Service Task
- Pool vs Lane
Why these dilemmas persist
BPMN 2.0 is a rich standard, and part of its power is the precision it offers. But sometimes too much precision can make two elements seem interchangeable. Although the BPMN notation defines them specifically and differently, those differences are not always obvious from the element names or basic documentation.
Getting these BPMN “false friends” wrong can produce models where the execution logic is incorrect, the communication between processes is unreliable, or the responsibilities of stakeholders are misrepresented. Using the right element for the right purpose is what keeps a BPMN model readable, interoperable, and executable.
This guide clarifies the six most common BPMN dilemmas with practical, example-driven explanations based on how these elements behave in real process models.
BPMN best practices built in
Rather than just explaining what each element means, this guide gives you a decision framework. Each dilemma is resolved with clear criteria you can apply independently to help you build consistent habits, not just fix one-off problems. Over time, this kind of systematic understanding significantly reduces revision cycles and review feedback in your modeling work.
Who is this guide for
This guide is suited to BPMN practitioners at any level: beginners building their first models who want to avoid foundational mistakes, and experienced analysts who want a structured reference to resolve recurring uncertainties. It is also a useful onboarding resource for teams adopting BPMN as a shared modeling standard.
Download the guide
Whether you're building your first process model or refining years of practice, download this practical BPMN best practices reference to execute your models correctly.