Kanban board design: columns, WIP limits, and card structure

A Kanban board is designed around three core elements: column structure, WIP limits, and card information. The standard column structure is: Backlog → Ready → In Progress → Review → Done. Each column represents a stage in the workflow. WIP limits define the maximum number of items allowed in each active column — typically set at the number of team members plus one for that stage. When a column hits its WIP limit, the team stops starting new work and focuses on completing what is already in progress. Each Kanban card should contain: work item title, owner, start date, priority, and any blocking dependencies. The board's primary purpose is not to track work — it is to make flow visible and surface bottlenecks before they cause delays. A board that nobody looks at is decoration, not Kanban.

Kanban is deceptively simple to start and surprisingly difficult to sustain. Most teams put columns on a board and call it Kanban. The boards that actually improve flow share three design principles that most initial implementations get wrong: meaningful column definitions, enforced WIP limits, and cards that contain the right information.

Column Structure: Define Your Workflow States

Columns represent distinct workflow states — not just stages in a timeline. The difference matters: a workflow state is a condition that requires specific work to complete before the item can move forward. A well-designed Kanban board has 4–7 columns. More than seven usually indicates that some states should be merged or that the workflow is too complex for a single board.

WIP Limits: The Most Important Kanban Rule

Work-in-progress limits are the mechanism that makes Kanban a flow management system rather than a task tracking system. Without WIP limits, a Kanban board is a visual to-do list. With enforced WIP limits, it becomes a constraint management tool that forces the team to finish work before starting new work.

Card Design: The Right Information at a Glance

Every Kanban card should answer five questions at a glance:

1. What is the work item? — Clear, specific title — not 'update website.'.
2. Who owns it? — Named individual — not 'team.'.
3. When did it start? — Start date in the current column — enables cycle time tracking.
4. What is the priority? — Color code or label (High / Medium / Low).
5. Is anything blocking it? — Red flag or blocker label with the dependency named.

Cards that lack owner names or start dates make cycle time measurement impossible — which means the board can show you work is stuck, but not how long it has been stuck or why.

Physical vs. Digital Kanban Boards