A map without lanes shows what happens. Lanes add who does it: each horizontal band is a role or a team, and each task sits in the lane of whoever performs it. A diagram like this is often called a swimlane diagram.
Lanes make two things visible at once:
- Ownership. Arguments about who does a step end when the step sits in one lane.
- Hand-offs. Every time a flow crosses from one lane to another, work changes hands. Hand-offs are where things wait and get lost, so a map with many crossings is often a map with delays.
Name lanes after roles, not people ("Store staff", not "Maria"): people change jobs, roles stay. Keep the customer in a lane of their own when they take part in the process.
In the editor, choose the lane when you add a task, or select a task and change In lane to move it.