The Kanban board: a complete guide

What is Kanban?

Kanban is a workflow management method built around a simple visual metaphor: work as physical cards moving through stages on a board. It was developed in the 1950s by Taiichi Ohno, an engineer at Toyota, who adapted an observation about how American supermarkets managed their shelves.

Supermarkets didn't try to predict exactly how much of each product they'd sell. They stocked the shelves, watched what customers took, and replenished based on what was actually consumed. Supply followed demand rather than anticipated demand. Ohno applied this principle to manufacturing: instead of producing to forecast, Toyota would produce in response to actual pull from downstream. This became part of what's now known as Just-in-Time manufacturing.

The core principle, that work flows in response to actual capacity, not planned capacity, transferred well to software development in the 2000s and has since spread to knowledge work, marketing, creative teams, and personal task management.

The core ideas

Visualise the work. Kanban starts by making work visible. Every task is a card. Every stage of your workflow is a column. At a glance, anyone can see what's being worked on, where it is, and what's queued. This transparency is the foundation of everything else.

Limit work in progress. Each column (other than the initial queue and the done column) has a maximum number of cards it can hold at once. When a column is full, no new work enters it until something completes and moves forward. This is the WIP limit, and it's the mechanism that prevents teams from taking on more than they can handle.

Pull, don't push. Work moves forward when there's capacity to take it, not when someone decides to assign it. The person doing the work pulls the next card when they're ready, rather than being handed tasks by someone else. This keeps quality higher and keeps the system honest about actual throughput.

Improve continuously. Kanban treats the current workflow as a starting point, not a final state. Regular reviews, observation of where work slows down, and deliberate adjustment are built into how the system operates.

Setting up a board

Choose your columns

Columns represent stages of your workflow. The simplest possible Kanban board has three columns: To Do, Doing, Done. This works for individual personal use or for very simple team workflows.

For more complex work, columns should reflect the actual stages tasks move through. A web design team might use: Backlog, Design, Development, Testing, Done. A content team might use: Ideas, Writing, Editing, Publishing, Live. A freelancer managing client work might use: Briefing, In Progress, Review, Delivered.

The principle is that each column should represent a distinct stage where meaningful work happens and where a task actually changes state. Avoid adding columns that are just ways of feeling organised without corresponding to real workflow transitions.

Create your cards

Each card represents a task. The right level of granularity is important and takes some calibration. Cards that are too small (every individual step) generate overhead without insight. Cards that are too large (multi-week projects) move so slowly that the board stops reflecting what's actually happening day to day.

A useful starting point is tasks that take roughly a day to complete. That keeps the board moving at a cadence where you can see flow, notice bottlenecks, and understand how the work is progressing.

Each card should include: a short, clear title; any context the person picking it up will need to get started; a due date if there is one; and who owns it (for team boards).

Set WIP limits

For each working column (everything except the initial backlog and the done column), decide on a maximum number of cards. When that limit is reached, no new cards enter the column until one moves out.

Choosing the right limit involves some trial and error. Too low and work stalls because people can't take on the next thing. Too high and you lose the constraint that keeps the system honest. A common starting point for small teams is a WIP limit of one to two per person per column, then adjust based on what you observe.

The discomfort of enforcing WIP limits is part of the design. When a column is full, the team has to focus on finishing what's there rather than starting something new. This is where Kanban diverges most sharply from a standard task list, where the natural impulse is always to add more rather than finish what's running.

Using the board

The pull mechanism

When someone finishes a task and the next column has available capacity (hasn't hit its WIP limit), they pull the card forward. They then look at the queue column and pull the next card into their in-progress column.

Nobody assigns tasks. The person doing the work decides when they have capacity and pulls accordingly. This matters because it means commitments are based on actual capacity rather than optimistic planning, which makes the system more honest and delivery more consistent.

Review cadence

Getting the team together regularly to look at the board together is where Kanban pays off at scale. A daily check, especially when first getting started, helps identify cards that are stuck, columns that are consistently full, and adjustments that need making.

The questions to ask at any review: Where is work slowing down? Why is that column consistently hitting its limit? Are any cards blocked? What's the average time a card takes to move from start to finish?

That last measure, cycle time, is one of the most useful metrics Kanban produces. Once you know how long work typically takes to move through the board, you can make more reliable commitments about when things will be done, and you can see when something in the process is breaking down.

When cards get stuck

It happens: a card reaches a point where it can't move forward because something is blocking it. An external dependency hasn't resolved, a decision hasn't been made, a piece of information is missing.

The instinct is to move the card backwards. Resist this. Moving cards backwards makes the board less honest about where things actually are and can lead to cards bouncing back and forth indefinitely. Instead, create a new card representing the blocking task and tag both. The original card stays in its current column, taking a WIP slot, which creates pressure to resolve the blockage rather than hiding it. If your tool allows it, tag the blocked card clearly so everyone can see its status.

This might seem rigid, but the point of Kanban is to surface reality rather than paper over it. A card that can't move represents a problem in the workflow. Making that problem visible is how you solve it.

Personal vs team Kanban

Kanban originated as a team system, but a simplified version works well for personal task management too.

A personal Kanban board with three columns (Backlog, Doing, Done) and a WIP limit of two or three on the Doing column provides a lightweight visual alternative to a flat task list. The WIP limit is the key element: it prevents the scattered feeling of having twenty things nominally "in progress" and forces a commitment to finishing before starting.

The key difference from a to-do list is the visual representation of work in flight. A to-do list tells you what to do. A Kanban board also shows you what state your work is currently in, which is more useful for anything with multiple stages.

Kanban vs Scrum

Both are methods for managing team workflows, and they're often confused. The main differences:

Scrum works in fixed time periods called sprints, typically one to two weeks. Work is committed to at the start of a sprint and delivered at the end. Kanban has no fixed periods; work flows continuously.

Scrum defines specific roles (Scrum Master, Product Owner, Development Team). Kanban has no prescribed roles.

Scrum breaks work into sprints with defined scope. Kanban limits work in progress but doesn't batch it into iterations.

Scrum suits teams where the work is highly interdependent and benefits from synchronised delivery. Kanban suits teams where work is continuous and varying in complexity, or where the work type doesn't map naturally onto fixed iterations.

Many teams use a hybrid: Kanban's visual board and WIP limits within a Scrum-like cadence. This is sometimes called Scrumban.

Kanban and other systems

GTD: GTD processes tasks into next actions and projects. A Kanban board can serve as the visual layer where those next actions and project tasks live, making status visible in a way a flat list doesn't.

PARA: PARA organises information; Kanban manages workflow. Active project tasks in PARA can be managed on a Kanban board, with the PARA structure providing the context for what each card belongs to.

MoSCoW Method: MoSCoW prioritises what should and shouldn't be in a project's scope. A Kanban board then manages the execution of the Must Have and Should Have items, with WIP limits ensuring the most important work moves first.

Time blocking: Time blocking schedules when you'll work; Kanban visualises what you're working on and where it is. Used together, time blocking can protect focused time for pulling and completing Kanban cards.

Task management basics: Kanban is one approach to task management. If you're new to managing tasks at all, the task management basics guide covers the foundations before Kanban adds its specific constraints and visual layer.

Frequently asked questions

Do I need special software for Kanban? No. Kanban was originally done with physical sticky notes on a whiteboard. Any tool that lets you create columns and move cards works: sticky notes, a shared spreadsheet, a whiteboard photo, or dedicated software like Trello, Linear, or Notion. The method is entirely tool-agnostic. Use whatever your team will actually look at.

What's a good WIP limit to start with?

There's no universal answer. A common starting point is one to two per person per active column. Start there, observe what happens, and adjust. If columns fill up and work stalls, increase the limit slightly. If people are constantly taking new work before finishing old work, reduce it. The right limit is one that keeps things moving without becoming overwhelming.

Should cards ever move backwards?

Rarely and reluctantly. When they do, it usually signals a gap in the process rather than a one-off exception. If a card regularly needs to move back to the same earlier stage, that's a sign a new column might be needed in the workflow, or that something is missing from cards when they first get created.

How is a Kanban board different from a to-do list?

A to-do list is a collection of tasks. A Kanban board shows tasks in the context of a workflow, with status visible, work in progress limited, and bottlenecks visible. The core difference is the WIP limit: a to-do list lets you start as many things as you want; Kanban forces you to finish before starting.

How many columns should I have?

As many as you have meaningful stages in your workflow, and no more. Most teams find three to six works well. More than that and the board becomes hard to read and the transitions between columns stop representing real state changes.

Is Kanban good for solo work?

Yes, with some simplification. The visual board and WIP limits are the most valuable elements for solo use. The team-oriented features (pull-based assignment, daily standups) are less relevant. A personal Kanban with three columns and a strict limit on simultaneous in-progress work is a lightweight and effective personal productivity tool.

Kanban was developed by Taiichi Ohno at Toyota in the 1950s and adapted for knowledge work by David J. Anderson and others in the 2000s. Related guides: Task management basics, MoSCoW Method, GTD.