Swimlane Diagram in draw.io (Cross-Functional Flowchart)
A swimlane diagram shows what happens and who does each step. Learn how to build a cross-functional flowchart in the free draw.io web app: add a pool with lanes, name the lanes, and drop each step into the lane of the team that does it, using an online shop refund process.
Step by step
Who does what
- Swimlane diagrams. A flowchart shows what happens. A swimlane diagram also shows who does each step. The example is the refund process for an online shop, with one lane for each team.
- Blank diagram. Start a blank diagram in draw.io. It's free in the browser and needs no account.
Add the lanes
- Pool and lanes. Open the Advanced shapes and drag in a horizontal pool with 3 lanes. Drag its right edge to make it wider. Name the pool Refund process, then name the lanes Customer, Support and Finance.
Steps go in lanes
- Steps in lanes. Each step goes in the lane of whoever does it. The process starts with the customer, so drop an ellipse labelled Refund requested into the Customer lane. Support checks the returned item, so drop a rectangle labelled Check returned item into the Support lane.
- Handoffs. Connect Refund requested to Check returned item. A line that crosses from one lane to another is a handoff. Work often waits there, so business analysts look at handoffs first.
- Decision. Support decides if the item is OK, so add a diamond labelled Item OK? in the Support lane. Then connect Check returned item to the diamond.
- Yes path. If the item is OK, Finance pays the money back. Drop a rectangle labelled Issue refund into the Finance lane. Connect the diamond down to Issue refund and label the line Yes. The process ends back with the customer, so add an ellipse labelled Refund received in the Customer lane. Connect Issue refund to Refund received. That's another handoff, from Finance back to the customer.
- No path. If the item is not OK, the customer gets it back. Add an ellipse labelled Item sent back in the Customer lane too. Connect the diamond up to Item sent back and label the line No.
- The finished swimlanes. Click an empty spot to see the whole diagram: 3 lanes, with every handoff between teams in plain sight.
Recap
- The rules. The rules: one lane per role or team, every step in the lane of whoever does it, and a label on each path out of a decision. Then check the handoffs, because that's where work tends to wait.
Common mistakes
- Unlabelled lines out of a decision. A diamond like Item OK? has 2 lines going out, and without labels nobody knows which is which. Label each one, here Yes and No.
- A lane for each person instead of each role. Name lanes after the role or team that does the work, like Support or Finance. People change jobs, but the role stays, so the diagram stays correct.
- A step put in the wrong lane. The lane says who does the step, so a step in the wrong lane gives the wrong owner. Ask "who does this?" and drop the step fully inside that lane, not across the line between 2 lanes.
When a business analyst uses this
In a process mapping workshop, a business analyst draws the current refund process with one lane per team while people talk it through. The lines that cross lanes show where work changes hands, so the group can see where delays and missing owners are before designing the new process.
Questions people ask
What is a swimlane diagram?
It's a flowchart split into lanes, one for each role or team. Each step sits in the lane of whoever does it, so the diagram shows both what happens and who does it.
When should you use a swimlane diagram?
Use one when a process passes between several people or teams, like a refund that goes from Customer to Support to Finance. It makes every handoff between teams easy to see.
How do you add swimlanes in draw.io?
Open the Advanced shapes and drag a horizontal pool onto the page. It comes with lanes that you can rename, and you drop each step shape into the right lane.
