How to Prioritize Work with Kanban Columns?
Usually every Kanban board starts with a column called “backlog”. This is the place where you put all future work and ideas.
Next is the “requested” or “ready to start” column that serves as the entry point of work items to your workflow. All Kanban tasks that the team committed to start are positioned there depending on their priority.
However, there can be different types of waiting Kanban columns further in the workflow on your board depending on the functionalities of your team.
For each of them, your team needs to follow the rule of pulling top cards first. This way the tasks of highest importance will be completed as fast as possible.
Some examples of waiting Kanban columns may be:
- Waiting for Approval – This type of Kanban queue column is appropriate for tasks which require approval to be processed (e.g. payments, promotional sales, etc.)
- Waiting for Review – This Kanban queue is a relevant stage of the workflow where work items wait to be evaluated. It is like a filter before tasks receive feedback and move forward to completion stage or go back for improvements. It plays a crucial role in product/service’s quality (e.g. product development, content writing, design, etc.)
- Waiting for External Activity – This kind of Kanban column is applicable for tasks waiting for third party actions in order to be completed. It happens often when a team communicates with other units outside of the company. (e.g. partnerships, affiliate programs, etc.)
Generally, by using Kanban, you create a pull system where team members pull their next task after finishing their current one. However, before pulling the next work item, you need to know one basic rule:
When you place future tasks in a waiting Kanban column you need to make sure that the top ones will be of the highest importance.
So every time one of your team members decides to pull a new Kanban task, it will be the one with the highest priority. This doesn’t mean that high priority tasks will constantly overpass tasks with low priority. You have to expedite only urgent work items.
Prioritizing Tasks with Kanban Swimlanes
Apart from improving transparency, swimlanes can also serve as a tool for prioritizing work tasks on your Kanban board. While columns divide your workflow into different stages (such as development, review, ready for delivery and etc.), swimlanes may be used in various ways like:
- Grouping tasks depending on the type of work, for example: web development, technical features, content and etc.
- Grouping tasks based on product development: Working on product X, product Y or product Z.
- Grouping tasks depending on their priority: low priority, average priority, high priority.
In the first two cases, you can easily apply work prioritization. You just need to add an “expedite” swimlane on the top of your Kanban board. After this, every time when there is an urgent issue, you simply have to move it to the top swimlane. Furthermore, make sure that the team member related to this exact issue is working only on it. Until its completion.
By using Kanban swimlanes for task prioritization, you can be sure that valuable work items will be completed prior to others. Furthermore, the visualization of the whole process will help you notice weak spots in your workflow and continuously improve it.
The Kanban Backlog
The backlog is the space where you place work items or ideas that will be done in the near or distant future. However, there is no guarantee that all tasks in the Kanban backlog will be delivered. The items in this column are more like an option the team has for the future work rather than a commitment point.
Prioritizing the Kanban backlog
The backlog may be the place where your team plan all future work, but it can easily become a messy place with tons of ideas.
This is why, your team needs to review all items on the backlog to ensure that it contains the appropriate items and prioritize them. This should be an ongoing activity or even better, an activity that occurs on a regular basis.
Some of the things your team can do during this refinement process are:
- removing irrelevant tasks
- new tasks that cover newly discovered requirements
- merging tasks
- breaking down items that are too big and others
Additionally, you can create sub-columns in your backlog in order to separate tasks planned for different periods, for example, each quarter of the year.
Prioritizing Tasks With Color Indicators
Using color indicators is one of the most common ways to prioritize work. Contemporary Kanban software solutions usually allow you to use customized colors in order to mark levels of priority.
For example, a red card may signify it has critical priority, while a green one has a normal priority. You can also add color codes for tasks such as: bug, change required, etc. As visual signals, color marks can be easily spotted by any team member.