If you’ve used draw.io at all (and even if you haven’t) chances are you’ve made a flowchart or two in your life. They’re one of the most common use cases for draw.io. They’re ideal for visualizing the individual steps of a complete process. And when that process involves multiple teams or other entities, it becomes necessary to divide your chart into lanes representing each of those entities. We call them swimlanes. And here’s what you need to know about the ease of working with swimlanes in draw.io.
When to use swimlanes
It’s actually not very often that a flowchart process is limited to just one person or one team. This is why we use cross-functional flowcharts and swimlane diagrams to show the flow of data or activity relationships between multiple groups.
The act of separating the steps in a process visually identifies the parties responsible for each step. It makes the information easier to understand. And the result is decreased confusion between teams.
Specific examples of use cases that make use of swimlanes and cross-functional flowcharts include UML activity diagrams, interaction diagrams, sequence diagrams, use case diagrams, data flows, and more.
We cover the overall mechanics of swimlanes as well as some useful pro tips here. But for a look at a specific use case, take a look at our post: Using draw.io for BPMN Diagrams.
When you imbed a draw.io diagram in Confluence, the easiest way to open a swimlane template is to select it from the initial splash screen: