What is a swimlane?
A swimlane is a horizontal row on a kanban board that groups cards by a shared attribute such as team, priority, workstream, or card type. While columns represent the stages of a workflow (To Do, In Progress, Done), swimlanes add a second dimension by slicing the board horizontally. This lets teams see work from multiple perspectives without needing separate boards for each category.
The term comes from the horizontal lanes in a swimming pool. On a board, each lane spans all columns, creating a grid where every cell shows the cards for one category at one workflow stage. Common swimlane groupings include team (frontend, backend, design), priority (urgent, normal, low), work type (feature, bug, chore), and individual assignee.
When to use swimlanes
Swimlanes are most useful when a single board serves multiple workstreams or when you need to compare progress across categories. A board shared between frontend and backend teams, for example, becomes much easier to read when each team's cards are in their own lane. Without swimlanes, cards from different workstreams interleave within each column, making it hard to see the balance of work or spot bottlenecks that affect only one team.
Swimlanes also help during planning sessions. A board with priority-based swimlanes immediately shows whether urgent work is dominating the pipeline or if the team has capacity for lower-priority improvements. This visual structure replaces the mental sorting that managers do when scanning a flat list of cards.
Swimlanes vs. separate boards
The alternative to swimlanes is creating separate boards for each category. Both approaches work, and the choice depends on whether you need cross-category visibility. Swimlanes keep everything on one board so you can compare lanes side by side. Separate boards provide cleaner, focused views but require switching between boards to get the full picture. For cross-board visibility, a multi-board view can bridge the gap.
How Flux handles grouping
Flux provides several tools for organizing cards by category on a board. Labels let you tag cards by any dimension - priority, type, team, or custom categories - and then filter the board to show only the cards that match. For teams that need cross-project visibility without swimlanes, the multi-board view consolidates cards from multiple boards into one screen with filtering by label, assignee, and due date. Combined with the board's real-time sync, any grouping or filter reflects the current state across all team members instantly.
Related terms
See also: Kanban Board, Workflow, WIP Limit.