What is Kanban? Principles, Boards, and Best Practices
Kanban is a visual workflow management method that helps teams see their work, limit work in progress, and continuously improve. Here's everything you need to know.
What is Kanban? Principles, Boards, and Best Practices
Kanban is a visual method for managing work as it moves through a process. Originally developed at Toyota in the 1940s to improve manufacturing efficiency, Kanban has become one of the most widely used approaches in modern knowledge work. Its simplicity is its strength: see your work, limit what's in progress, and improve continuously.
The Origins of Kanban
The word kanban is Japanese for "visual signal" or "card." Toyota engineer Taiichi Ohno developed the system in the late 1940s, inspired by how supermarkets restocked shelves — only when inventory ran low, not on a fixed schedule. This pull-based approach reduced waste and improved flow.
David Anderson adapted Kanban for software development in the mid-2000s, introducing it at Microsoft and later Corbis. His 2010 book Kanban: Successful Evolutionary Change for Your Technology Business formalized the method and sparked widespread adoption.
The Core Principles of Kanban
Anderson's Kanban method rests on four foundational principles:
- 1Start with what you do now — Kanban doesn't require a process overhaul. You map your current workflow and improve it incrementally.
- 2Agree to pursue incremental, evolutionary change — Small, continuous improvements are safer than large transformations.
- 3Respect the current process, roles, and responsibilities — Kanban doesn't prescribe titles or ceremonies. Existing roles remain intact.
- 4Encourage acts of leadership at all levels — Everyone on the team participates in improvement, not just managers.
The Kanban Board
The Kanban board is the central artifact of the method. At its simplest, it has three columns:
- To Do — Work that has been identified but not started
- In Progress — Work actively being done
- Done — Completed work
Teams customize the board to reflect their actual workflow. A software team might add columns like "Ready for Review," "In Testing," and "Deployed." A marketing team might use "Briefing," "Draft," "Approval," and "Published."
Cards
Each piece of work is represented by a card on the board. Cards typically show the title, owner, due date, and any blockers. In digital tools, cards link to detailed descriptions, attachments, and comments.
Work in Progress (WIP) Limits
The most powerful Kanban practice is limiting work in progress. Each column has a maximum number of cards allowed at once. When a column is full, the team stops pulling new work and focuses on completing what's there.
WIP limits expose bottlenecks. If the "In Testing" column is always at its limit while "In Progress" is empty, testing is the constraint — and the team can address it directly.
Key Kanban Metrics
Kanban teams use two primary metrics:
- Lead time: The total time from when a request is received to when it's delivered. This is what customers experience.
- Cycle time: The time from when work actively starts to when it's done. This is what the team controls.
Tracking these over time reveals trends: is the team getting faster? Are certain work types consistently slow? Where are the bottlenecks?
Kanban vs. Scrum
Kanban and Scrum are both Agile frameworks, but they differ in important ways:
| Kanban | Scrum | |
|---|---|---|
| Cadence | Continuous flow | Fixed sprints (1–4 weeks) |
| Roles | No prescribed roles | Scrum Master, Product Owner, Dev Team |
| Changes | Any time | Only between sprints |
| WIP limits | Yes — core practice | Optional |
| Metrics | Lead time, cycle time | Velocity |
Many teams use Scrumban — a hybrid that combines Scrum's ceremonies with Kanban's flow-based approach.
Kanban in Enterprise Environments
In large organizations, Kanban scales through portfolio boards that show work across multiple teams and products. Portfolio Kanban helps executives and program managers see the big picture without micromanaging individual team boards.
For matrix organizations, where individuals contribute to multiple projects simultaneously, Kanban is particularly useful because it makes cross-team dependencies visible and helps prevent individuals from being overloaded.
Getting Started with Kanban
Starting Kanban is straightforward:
- 1Map your current workflow — list every stage work passes through
- 2Create a physical or digital board with those stages as columns
- 3Add a card for every piece of active work
- 4Set WIP limits based on your team size (a common starting point: 1–2x the number of people per column)
- 5Hold a weekly review to discuss flow, blockers, and improvements
Kanban rewards patience. The improvements compound over time as the team develops better habits and the board reflects the real workflow with increasing accuracy.