Kanban swimlanes are horizontal rows that run across every column of a board, so cards are sorted twice: by stage (left to right) and by something else (top to bottom). The row can be a person, a client, a type of work or a priority. Columns still say where a card is in the process; the lane says what kind of card it is. Most small boards do not need them, and the ones that do usually need only two.
What is a swimlane on a kanban board?
Picture a board with three columns, To do, Doing and Done. Without lanes, every card sits in one of those three stacks. With lanes, the board gains rows, say "Client A" and "Client B", and each column is cut into one cell per row. A card for Client A that is in progress lives where the Doing column meets the Client A row.
The name comes from a swimming pool: work moves left to right along its own lane without crossing into the next one. The point is visual separation. Two streams of work that have nothing to do with each other stop sharing a stack, so you can read each stream's state at a glance.
That is the whole mechanism. A lane does not change how cards move between columns, and it does not add a rule by itself.
What are the common types of swimlanes?
Four splits cover nearly every board you will meet.
By person or team. One row per assignee. This is the default in many tools and the one people reach for first. It shows who is carrying what, which is useful on a team and mostly redundant when you are the only person on the board. Jira, for example, can group a board by assignee, epic, query or parent work item, among others, according to Atlassian's swimlane documentation. By client or project. One row per client, product or project, so a freelancer or small agency sees every account on one board without the accounts mixing. This is the version that earns its place most often on small boards. By work type. One row for recurring routine work (invoicing, weekly reports, maintenance) and one for one-off projects. The routine row stays full of small repeating cards and stops drowning the work that is actually moving. By class of service. One row per urgency policy. Businessmap's guide lists four classes: expedite, fixed delivery date, standard and intangible. Expedite is the row for work that jumps the queue, fixed date is anything with a hard deadline, standard is everything else, and intangible is the useful-but-not-urgent work that never gets scheduled on its own. It is the most formal of the four and makes sense once a team has agreed what each class promises.Some boards add a fifth, a row for time frames such as this week, next month and later, and tools like KanbanTool also list goals and products as lane options. Those are variations on the same idea: pick one dimension, give each value a row.
How do swimlanes work with WIP limits?
A work-in-progress limit caps how many cards may sit in a column at once. With lanes you have a choice: cap the whole column, or cap each cell.
Capping the whole column is the safer default. The limit describes how much you can really carry at one time, and that does not change because the cards are drawn in two rows. If Doing allows three cards, three is the number whether they belong to one client or two.
Capping each cell gets complicated fast. Four lanes with a limit of two each means a column that can hold eight, which is usually far past what one person can actually finish. If you do set limits per lane, set one for the lane that must not be starved, such as expedite, and leave the rest alone. Our guide to WIP limits covers where to set the number in the first place.
Do you need swimlanes at all?
Probably not at first. Lanes cost you vertical space, and every row you add pushes cards off the screen. A board with four lanes and four columns has sixteen cells to scan, and a board with a dozen cards spread over sixteen cells looks emptier and harder to read than the same cards in four stacks.
Three signs say a board has outgrown a single stack:
- Two kinds of work never mix. Client work and internal admin, or product work and support requests, with different people or different rules.
- One kind of card keeps burying another. Routine tasks swamp the project cards, or a priority class gets lost under the standard queue.
- You keep asking the same filtering question. If you filter to one client every morning, that client wants a row.
If none of these applies, adding lanes makes the board look more organised without making it work better.
What can you use instead of swimlanes?
A tag does most of what a lane does, for less. Give every card a colour for its client, type or priority, and the board shows the separation without a permanent layout change. When you want to look at one stream, filter to that tag, and when you are done, clear the filter. Nothing about the board's structure moved.
EasyKanban takes this one step further. It can group every column by tag as a temporary view, so each column splits into sections for each tag. It is a lens on the board, not a fixed layout: a card still sits in exactly one column, dragging works as it always did, and you switch the grouping off again when you are done. A card with several tags appears once, under its first. That makes it a stand-in for lanes rather than a copy of them, and it only offers tags as the dimension. If you need person or class of service as a real row, with limits attached, a tool built around lanes will serve you better. We say so plainly because it is true.
For the free plan, that covers a lot. You can start a board without signing up, tag a few cards and see whether the grouped view answers the question before you commit to a more complex layout.
How do you set up swimlanes without making a mess?
If you decide you do need lanes, a few rules keep them readable.
Pick one dimension. A board split by client and by priority and by person is a spreadsheet. Choose the single split that answers your most frequent question and let tags handle the rest. Keep it to three or four rows. More than that and each cell is too small to hold a card comfortably. If you find yourself wanting a seventh row, the dimension is wrong, or the work belongs on two boards. Add a catch-all row. Cards that fit no lane need somewhere to go, or they stop being added. A row called "Other" costs nothing and stops the board from dictating what counts as work. Review the lanes monthly. A client who left, a project that ended, a lane that has been empty for weeks: remove it. An empty row is dead space and a quiet signal that the board has stopped being tended.For examples of full column layouts to put lanes on top of, see kanban board examples. If you are still deciding how many columns you need, start there before adding a second dimension.
Frequently asked questions
What is a swimlane in kanban?
A swimlane is a horizontal row that crosses all the columns of a kanban board and groups cards by a second dimension, such as person, client, work type or priority. Columns show the stage of the work and lanes show which stream it belongs to.
What are the types of kanban swimlanes?
The common ones are by person or team, by client or project, by work type (routine versus one-off) and by class of service (expedite, fixed delivery date, standard, intangible). Pick one dimension per board, since combining several makes the board unreadable.
Do swimlanes need their own WIP limits?
Not necessarily. A limit on the whole column keeps your total load honest regardless of how many lanes you draw. Per-lane limits multiply the total capacity, so use them only for a lane that must be protected, such as urgent work.
When should you not use swimlanes?
When the board is small or the work is one stream. Lanes take vertical space, and a few cards spread across many cells are harder to read than the same cards in a single stack. A colour tag plus a filter covers most small boards.
Does EasyKanban have swimlanes?
Not as fixed rows. It groups every column by tag as a temporary view, which splits each column into sections without changing the board layout or how drag and drop works. Rows by person or class of service are not supported.
Related reading
A lane is worth its row only while the two kinds of work it separates still behave differently.