What is Kanban?
Kanban is an agile working method in which you visualise tasks on a board, limit work in progress and deliver continuously instead of working in fixed sprints.
DEFINITION
Kanban makes work visible. You have a board with columns that show the status of a task — for example “To Do”, “In Progress” and “Done”. Each task is a card on this board. Kanban has one decisive rule: limit how many tasks may be in progress at the same time. This limit is called a work in progress limit (WIP limit). It forces the team to finish tasks before starting new ones. The result: less multitasking, faster throughput, earlier visibility of bottlenecks. Kanban has no fixed roles, no sprints, no retrospectives. It is more flexible than Scrum and suits teams that handle continuous requests, such as support, marketing or operations. Kanban originally comes from Japanese manufacturing and became known through Toyota in the 1950s.
CONNECTIONS
Leadership
Kanban makes delegation visible: when tasks are handed over, the Kanban board immediately shows where overload arises and where capacity is free. Leaders can make steering decisions on a data basis.
Artificial Intelligence
Autonomous AI agents can update Kanban boards automatically, assign tickets or report bottlenecks. Kanban thus becomes more than a visualisation tool — a self-regulating system.
Project Management
Kanban visualises bottlenecks in the workflow, similar to how critical path analysis exposes bottlenecks in project schedules. Both methods help make blockers visible early.
KEY POINTS
- Kanban visualises tasks and workflow on a board.
- WIP limits restrict parallel work and reduce multitasking.
- Kanban has no fixed sprints; it works as a continuous flow.
- There are no prescribed roles as in Scrum.
- Kanban comes from the Toyota production system of the 1950s.
EXAMPLE
A marketing team has a Kanban board with the columns: Ideas, Briefing, In Production, Review, Published. The WIP limit for “In Production” is three. When three pieces of content are being produced at once, no new one may start until one is finished. The team quickly notices that “Review” is the bottleneck because everything waits there. It solves the problem by having a second team member take on reviews. Throughput time drops by 40 percent.
MISCONCEPTIONS
Is Kanban only suitable for software teams?
No. Kanban suits any kind of knowledge work: marketing, HR, operations, legal. Wherever tasks have a clearly definable flow process, Kanban works well.
Do I need a digital tool for Kanban?
No. A physical board with sticky notes is often just as effective as a digital tool. The method works regardless of the medium.