Kanban guide · Kanban basics
Kanban Swimlanes: Types, Uses and Best Practices
Swimlanes are horizontal rows on a Kanban board that separate different kinds of work. Used well, they make priorities and policies obvious at a glance.
Key takeaways
- Swimlanes separate work by urgency, type, team or customer.
- Classes of service define how different items are treated.
- Keep lanes few and policies clear.
Common swimlane types
| Swimlane by | Example | Useful when |
|---|---|---|
| Class of service | Expedite, Fixed date, Standard, Intangible | Work has different urgency and risk |
| Work type | Features, Defects, Maintenance | You need a balanced mix of work |
| Team or person | Design, Content, Development | Several groups share one board |
| Customer or project | Client A, Client B | Agencies and shared services |
Classes of service
Classes of service, described in the Kanban Method, define how different items are treated:
- Expedite: urgent, high cost of delay; pulled immediately, usually limited to one at a time.
- Fixed date: must be done by a specific date; started early enough to meet it.
- Standard: most work; pulled in priority order.
- Intangible: important but not urgent, such as reducing technical debt; reserved capacity.
Best practices
- Use as few swimlanes as possible; two to four is plenty.
- Give each lane a clear policy.
- Limit the expedite lane strictly, or it becomes the normal lane.
- Consider WIP limits per lane as well as per column.
- Review lanes in retrospectives and remove those nobody uses.
Free templates for this topic
Frequently asked questions
What is an expedite Kanban swimlane?
A swimlane for urgent items that bypass the normal queue. It should have a strict limit, usually one item.
Should Kanban swimlanes have WIP limits?
They can. Limits per lane help ensure a healthy mix, for example reserving capacity for improvement work.
What is a Kanban swimlane?
A swimlane is a horizontal row across the board that groups cards of a certain kind, such as urgent work, a work type or a team. Cards move left to right within their lane.
What are common types of Kanban swimlanes?
Common lanes are by class of service (expedite, fixed date, standard, intangible), by work type, by team or person, and by customer or project.
What are classes of service, and how do they map to Kanban swimlanes?
Classes of service are policies for how different kinds of items are treated, based on their urgency and cost of delay. Typical classes are expedite, fixed date, standard and intangible, and many teams give each class its own swimlane.
How many Kanban swimlanes should a board have?
As few as possible, usually two to four. Too many lanes clutter the board and hide the overall flow.
Should I use Kanban swimlanes for each team member?
Lanes per person can help small teams see who is overloaded, but they can encourage individual silos. Many teams prefer lanes by work type or class of service.
Why give intangible work its own Kanban swimlane?
Intangible items, such as technical debt or process improvements, have no immediate deadline but cost more the longer they are ignored. A dedicated lane makes sure some capacity goes to them.
Can you have Kanban swimlanes in Trello or Jira?
Jira boards support swimlanes natively, for example by epic or assignee. In Trello, teams often imitate swimlanes with labels or separate lists; see the tools comparison.
What is the difference between a Kanban swimlane and a column?
Columns show the stages of the workflow, so cards move through them. Swimlanes group cards by category, so a card normally stays in the same lane.
When should you not use Kanban swimlanes?
Skip them when all work is treated the same way or the board is small. Add a lane only when it changes how the team acts on the work.