Swimlane

Swimlane is the umbrella term for the horizontal bands on a BPMN diagram that group activities by performer. In BPMN 2.0 vocabulary, a pool and a lane are both swimlanes; informally the whole pattern — horizontal bands across the diagram — is called "swimlane notation" or "swimlane diagram".

Swimlane diagrams are the shape that makes "who does what" readable at a glance. The process flows left to right; the bands split vertically by actor; at each handover the flow visibly moves from one band to another. This is the single most impactful readability pattern in process modelling — the same diagram drawn without swimlanes forces the reader to read every label to reconstruct the role assignment.

• The process clearly has multiple distinct performers — three or more roles, or two roles with frequent handovers.
• Handovers are interesting — the pain points are at boundaries, not inside single-role segments.
• The audience includes non-specialists who need to see "where does my team fit into this" without learning BPMN syntax.
• Avoid swimlanes when a single performer does 90% of the process — the diagram becomes a single band with other lanes sitting empty.

LucidFlow supports two layouts for the same underlying process: flow view (no lanes, compact) and swimlane view (one lane per detected role). The toolbar switches between them with no data loss — the roles and handovers are always stored, the view just decides whether to render them as lanes. The cost dashboard breaks down costs per lane in either view, which is the fastest way to spot a role that is disproportionately expensive.