Kanban: Definition, Meaning, and Application
Kanban is a visual workflow management system that originated at Toyota and is now used worldwide in manufacturing, software development, and service operations to control work in progress, improve flow, and make process problems immediately visible. This guide explains what kanban is, how kanban systems and boards work, the difference between physical and digital kanban, and how kanban connects to lean management.
Kanban Definition
Kanban is a visual pull-based scheduling system that uses cards or signals to authorise and control the production and movement of materials through a process, ensuring nothing is produced without downstream demand.
- Visual pull system using cards or signals to authorise production
- Limits work in progress (WIP) to improve flow and quality
- Originated at Toyota in the 1940s; now used globally
- Applied in manufacturing (physical kanban) and software (digital boards)
- Prevents overproduction — one of the eight lean wastes
Explanation of Kanban
Kanban (看板) is a Japanese word meaning 'signboard' or 'visual card'. The kanban system was developed at Toyota in the late 1940s by industrial engineer Taiichi Ohno, who was inspired by the way American supermarkets managed inventory: shelves were replenished only when items were purchased, and only in the quantities that had been consumed. Ohno adapted this concept to Toyota's factory floor, using physical cards to signal when a process step needed to produce or move material — creating the first industrial pull system.
In a traditional two-bin kanban system, each production stage has two bins of parts. When the first bin is emptied (consumed by the downstream process), the empty bin is sent back to the upstream process as a replenishment signal (the kanban card), while production continues using the second bin. When the upstream process refills the bin, it is returned to downstream. This simple mechanism ensures that production is always driven by actual consumption, not by forecasts — eliminating overproduction and reducing inventory.
Modern kanban boards — both physical and digital — extend this concept to knowledge work and service processes. A kanban board displays work items as cards moving through columns representing process stages (typically To Do, In Progress, and Done). The critical mechanism is the WIP limit: each In Progress column has a maximum number of work items allowed simultaneously. When a column is full, upstream work must wait until capacity is available. This constraint makes bottlenecks immediately visible and drives teams to solve them rather than accumulate queues.
How to Implement a Kanban System
-
1Visualise the workflow
Map all stages of the process on a board (physical or digital) with columns representing each stage from request to delivery.
-
2Set WIP limits
Define the maximum number of work items allowed in each In Progress stage based on capacity, aiming to prevent overload and expose bottlenecks.
-
3Create kanban cards
Represent each work item as a card carrying relevant information (description, owner, due date, priority) that moves through the workflow columns.
-
4Manage flow
Monitor the board daily, actively resolving blocked items and addressing columns that consistently reach their WIP limit.
-
5Make policies explicit
Document the criteria for moving cards between stages, how blocked items are handled, and how priorities are determined.
-
6Improve collaboratively
Regularly review cycle times, throughput, and bottleneck patterns and adjust WIP limits and process design to continuously improve flow.
Kanban for Software Development at a SaaS Company
A software development team at a SaaS company was struggling with context switching, missed deadlines, and developers working on 10 or more tasks simultaneously with nothing completing. They implemented a digital kanban board with columns for Backlog, Development, Code Review, Testing, and Done, with WIP limits of 3 items for Development, 2 for Code Review, and 2 for Testing.
Within one month, average cycle time (the time from starting a task to completing it) dropped from 18 days to 7 days, and the number of items completing per week (throughput) increased by 40%. The WIP limits forced developers to finish work before starting new tasks, and the visible bottleneck at Code Review prompted the team to implement pair reviews that halved review turnaround time. The board made the team's true capacity and problems visible in a way that previous status meetings had never achieved.
Importance of Kanban in Quality Management
Kanban addresses one of the most universal sources of inefficiency in modern work: multitasking. Research consistently shows that context switching between multiple tasks reduces productivity, increases errors, and lengthens the time to complete any individual item. By limiting work in progress, kanban forces teams to finish what they start before beginning something new — which counterintuitively results in more being completed, faster, with fewer errors.
For organisations, kanban provides real-time visibility into process performance that enables active, evidence-based management rather than reactive firefighting. Managers who can see where work is flowing and where it is stuck can direct resources and remove impediments proactively. This visibility, combined with the discipline of WIP limits, systematically builds the flow efficiency and quality awareness that are hallmarks of high-performing operational teams.
- Limits work in progress to improve focus and quality
- Makes process bottlenecks immediately visible
- Reduces lead time and improves delivery predictability
- Prevents overproduction and excess inventory
- Applicable to physical manufacturing and knowledge work
- Simple to implement with minimal overhead
Toyota-style manufacturing pull systems, Agile software development, IT service management, healthcare patient flow management, HR recruitment pipelines, marketing campaign management, and any process where work moves through sequential stages.
Kanban in ASQ Certification
Professionals working in quality, process improvement, operations, and organisational excellence often encounter this concept in real-world applications. Many ASQ certifications cover related principles,
tools, and methods as part of the Body of Knowledge.
Frequently Asked Questions
The concept of Kanban is rigorously covered in the following ASQ certifications: Six Sigma Green Belt.
Scrum organises work into fixed-length sprints with defined ceremonies (sprint planning, daily standup, sprint review, retrospective) and roles (Product Owner, Scrum Master, Development Team). Kanban has no fixed iterations or roles — it simply manages continuous flow with WIP limits. Scrum is more prescriptive; kanban is more flexible.
A WIP (Work in Progress) limit is the maximum number of items that can be in a given stage of the process simultaneously. WIP limits prevent bottlenecks from being hidden by accumulating queues, force teams to resolve blockages before starting new work, and improve overall flow speed and quality.
No. Kanban originated in manufacturing at Toyota and is equally applicable to any process involving sequential stages of work. It is used in healthcare for patient flow management, in HR for recruitment pipelines, in manufacturing for production scheduling, and in any service environment where work moves through defined stages.
A task list shows what needs to be done. A kanban board shows the current state of all work in progress, making flow, bottlenecks, and WIP visible at a glance. The WIP limits on a kanban board actively constrain behaviour to improve flow; a task list has no such mechanism.