The Kanban board is the most visible element of the Kanban Method. It is also the most commonly oversimplified. Walk into most offices where teams describe themselves as "using Kanban" and you will find a board divided into To Do, Doing, and Done, with cards moving from left to right. That is a good start. It is not, by itself, a Kanban board in the proper sense.

Understanding what makes a board actually functional — rather than just visually tidy — changes what you build and how you use it.

The basic structure

A Kanban board maps the steps in a workflow as vertical columns. Work items — represented by cards — move from left to right through these columns as they progress. The columns should represent the actual steps in your process, not a generic template. A software team's board will look different from a marketing team's board, which will look different from a legal team's board. If your columns are "To Do, Doing, Done," you have probably adopted someone else's workflow rather than mapping your own.

Cards carry information about each work item — typically a description, ownership, and relevant context on the front, with more detail accessible behind (or in the digital equivalent). The goal is that anyone looking at the board should be able to understand the current state of work at a glance — not after a ten-minute briefing.

Physical versus digital

Physical boards — walls, whiteboards, sticky notes — have genuine advantages in co-located teams. They are always visible, they cannot be hidden behind a menu, and they create a shared focal point for daily stand-ups. Walking up to a physical board together and talking about what is on it is a different experience from scrolling through items in a tool.

Digital boards are more practical for distributed teams and have obvious advantages in terms of searchability, data capture, and integration with other tools. Jira, Trello, and their equivalents offer varying levels of sophistication depending on what you need. The risk with digital boards is that they become a data management exercise rather than a communication tool — teams update the tool but do not actually use it to have conversations.

Neither is inherently better. The best choice depends on how your team works and what the board is primarily meant to do.

What makes a Kanban board actually Kanban

The feature that distinguishes a genuine Kanban board from a simple task tracker is Work-in-Progress (WIP) limits — explicit caps on how many items can be in any given column at any one time. These limits are what create the pull system. When a column is full, new work cannot enter it. The team must finish before they start.

WIP limits make bottlenecks visible in real time. If the "In Review" column regularly hits its limit while the "Development" column has empty slots, that tells you something actionable about where your process is constrained. Without limits, these bottlenecks exist but remain invisible until a deadline approaches.

Teams new to Kanban often resist WIP limits because they feel counterintuitive. "Limiting work means doing less work" is the concern. In practice, the opposite tends to be true: limiting work in progress increases throughput by reducing the overhead of context-switching and unfinished work.

Getting started

The Kanban Method's instruction for getting started is refreshingly simple: start with what you do now. Map your current process as it actually works — not as it is supposed to work. Visualise it. Then observe. The board will quickly show you where work is piling up, where it is waiting, and where the process is failing the people doing it.

From that observation, improvement follows naturally. You do not need to redesign your process before you start. You need to make it visible enough to have honest conversations about it.