How to choose a kanban tool for a digital board

To choose a kanban tool, check its WIP limits, flow metrics and history against how your team already works. The kanban software category compares the options.

A whiteboard and sticky notes are still a good place to start with kanban. Teams move online when they work across sites, need history, or want the metrics a physical board cannot give them.

This guide covers when to switch, what to look for and how to test a tool before you commit.

Signs it is time to switch

The board is out of date because people work remotely or on different shifts. Nobody can say how long items took last month, because the history was wiped. Several teams share work, and nobody can see the whole picture.

If none of these apply, keep the physical board. It is cheap, visible and easy to change.

WIP limits in a digital kanban tool

Look for column and swimlane WIP limits that are visible and that warn the team when they are exceeded. Without them, a digital board quickly becomes a long to-do list.

The guide on why limiting WIP makes teams faster explains the effect behind the feature.

Board design: columns, policies and classes of service

Columns should match the real steps work goes through, including waiting states such as "ready for review". Each column needs a short policy that says when an item may enter or leave it.

Classes of service handle urgent work. An expedite lane lets a true emergency jump the queue, with a limit of one item so it stays rare.

Flow metrics out of the box

Cycle time, throughput and a cumulative flow diagram should come from the board without exports. If the tool cannot show them, pair it with a flow metrics tool. The Little's Law calculator shows how the numbers relate.

Integrations, hosting and your data

Check which tools the board must connect to, such as code repositories, chat or a help desk. Ask whether the tool is hosted only by the vendor or can also run on your own servers.

Make sure you can export the full history, including dates, so you are not locked in if you switch later.

Room to grow

Check whether boards can connect upward into a portfolio view. Teams often want to link their boards to strategic themes later. See lean portfolio management software.

Run a two-week pilot

Move one team's real work onto the new board for two weeks. Agree in advance what success looks like, such as an up-to-date board at every standup and cycle time data you trust.

If the pilot works, write down how the team uses the tool before other teams adopt it. The lean stack guide covers how to keep tools to the minimum you need.

Frequently asked questions