Learn what Kanban swimlanes are and how they can help teams improve their work organization and prioritization.
Kanban swimlanes are horizontal lines that split a Kanban board into sections. Teams usually use them to visually separate different work types on the same board and organize homogenous tasks together.
A simple example of a Kanban swimlane would be the separation of different product types (“Hardware” and “Services”) of your procurement team. In this case, separate swimlanes give you a better overview of the workload per product type and help you achieve a better flow.
Kanban board with two Swimlanes
When talking about flow, we should mention the topic of limiting work-in-progress (WIP) too. As you are probably familiar with, your workflow's different stages should have limits, so your team members focus on finishing rather than constantly starting new work.
The same thing applies to the Kanban swimlanes. If we take the procurement example from above, you should set separate WIP limits for the Hardware and Service lanes that conform with the overall limit of the “In Progress” work stage on the Kanban board.
Generally speaking, Kanban swimlanes are used to separate different types of work. How you should apply them depends on the specifics of your workflow. However, there are some major types of lanes that you should be familiar with, so keep reading below.
The most common types of swimlanes on a Kanban board are:
– Repetitive tasks
– Classes of Service (Expedite, Fixed Delivery Date, Standard, Intangible)
– Company-level lanes
– Discarded Options
Let’s briefly go over each one of them.
You can create dedicated Kanban swimlanes to visualize the work of different teams or individuals. Here you see the three units of “Application & Assembly” (Fly Engine Subsidiary, Flow Air, and Wings LTD Subsidiary) have dedicated swimlanes. Although they all share the same workflow, this gives a better overview of which unit tasks are piling up or additional capacity is needed.
Kanban board with multiple Swimlanes
Furthermore, you can use Kanban swimlanes to separate work for different clients to visualize better what you are preparing for them. This scenario is not very common, but it is very effective for long-term clients.
For example, let's say you are a project delivery firm for engineering and construction, working with different clients on their new corporate headquarters or a new production facility. Separating the different projects' tasks in dedicated swimlanes on your team-boards will make the management of such large, long-term projects much easier. This way, you will ensure the project status and workload are easy to monitor and track.
Sometimes, teams have many recurring tasks. For example, an IT operations team might have maintenance tasks that require the regular backup of important business files within a network system.
Those are work items that provide the organization with higher security. Due to their repetitive nature, it’s a good practice to use Kanban swimlanes to visualize and separate them from the rest. This way, you will be able to further de-clutter your Kanban board, especially if you have a larger volume of both one-time and recurring tasks.
Kanban board with a "Recurring Tasks" Swimlane
Visualizing different classes of service is one of the most widely used options for Kanban swimlanes. The purpose of these lanes is to provide teams with a solution to prioritize work effectively to reduce risk.
As you can imagine, different types of work items will not have the same type of “urgency” attached to them. That’s why there are 4 classes of service for priority management in Kanban, which you can separate and visualize with the help of Kanban swimlanes. We are listing them below.
10 Years Kanban Experience In 1 Free Book:
This class of service is reserved for work items that have the highest priority, which means that they require your team’s full devotion. You can create a separate Expedite swimlane on your Kanban board for that class of service and process items through it that are critical, have high risk and might be blocking your other tasks from moving forward.
Kanban board with an Expedite Lane
Fixed Delivery Date is reserved for work items that need to get done by a certain point in time. You can use a dedicated Kanban swimlane to visualize and separate items that might accumulate a high cost of delay (CoD) if not finished within a given timeframe.
The standard class of service represents the normal activities in your workflow that don’t come with much risk or cost of delay attached to them. That’s why, in case the work items in your project are not homogenous, a good practice is to use a Kanban swimlane to separate the standard tasks from those with higher priority.
The last class of service in Kanban is Intangible. It is reserved for the tasks that are non-urgent in the given moment and thus bear the lowest risk and cost of delay. As you’ve probably guessed, you can visualize and separate those work items from the rest, too, with the help of a dedicated Kanban swimlane.
Learn more about Kanban classes of service.
When working on projects, teams often come up with many different ideas on what approach to take with the work's execution and how to develop specific things. However, a lot of those ideas never come to pass and are abandoned during the refinement process. A problem here comes when those options are just thrown away and never looked up again because it might turn out that their alternatives were not the better choice.
In Kanban, a good practice is to keep discarded options for a while in a dedicated swimlane before completely rejecting them. This will give you greater flexibility to reflect on your decision to choose a certain option over another and determine whether something has been properly discarded.
Apart from separating and visualizing different types of work on the team-level, there are also company-level Kanban swimlanes that you can apply. This is part of Portfolio Kanban and works best when you are scaling Kanban across the entire organization.
Portfolio Kanban board
For example, you can use a dedicated lane to visualize your wider company objectives on a Portfolio Kanban board. After that, you can break down those bigger strategic objectives into smaller key results that are visualized and separated with their own Kanban swimlanes. Those key results can be further broken down into epics/projects allocated to the respective teams and live both on the Master Kanban board and the separate team boards within the company.
Hopefully, by now, you have a good grasp of what Kanban swimlanes are and how they can be used. While they are a great solution for better work organization and prioritization, we at Kanbanize always follow the mantra of “continuous improvement”, which we have now applied to our swimlanes too.
So far, the standard approach has been to use one Kanban board per workflow and apply different lanes within it. However, when we identify more than one unique flow of work items in our teams, our best practice is to use Multiple Workflows on one Kanban board and then apply swimlanes within them. The concept is simple. For example, a Customer Success team can use two workflows on their Kanban board – Requests from Existing Clients and Internal Activities.
Kanban board with multiple Workflows and several Swimlanes
In the former – Existing Clients’ Requests, they can have different Kanban swimlanes to separate tickets from hot customers (highest priority), small and medium-sized businesses, enterprises, customers interested in a specific integration, etc. The latter workflow – Internal activities, can serve as a place where they visualize tasks, unrelated to clients’ work, that they have to do internally for the company.
This will allow the team to organize their activities better, keep everything in one place, further reduce context switching, and increase their productivity levels.
Kanban swimlanes represent lines that divide a board horizontally. They have various use cases, with the main types summarized below. You can create swimlanes for:
During the 30-day trial period you can invite your team and test the application in a production-like enviroment.