BPMN Lanes vs Pools: Who Does What in a Workflow Diagram

Are your lanes swimming in the wrong pool? Misusing pools and lanes isn't just a diagramming slip—it can cause misaligned teams, brittle automation, and BPMN diagrams that confuse more than they clarify. Even seasoned modelers stumble here, especially when switching between business and technical perspectives. This guide shows how to choose pools and lanes correctly so your workflow diagram reflects reality and can be implemented with confidence. First: Know What You're Modelling BPMN Pool A pool represents a participant in a collaboration—an independent actor with its own process logic (an organization, external customer/vendor, or an autonomous system). BPMN Lane A lane subdivides a single participant by roles, teams, or departments. It clarifies who does what inside that participant. Key distinction: Pools define boundaries ; lanes define responsibilities . Use pools to show between-participant interactions (messages). Use lanes to organize within-participant work (sequence flows).