Kanban
A visual pull-based production scheduling system that signals upstream processes to replenish items only when consumed downstream, controlling work in progress and synchronizing production with actual demand.
Full Definition
Kanban (Japanese for "signboard" or "visual card") is the Toyota Production System's implementation mechanism for JIT pull production. In its traditional form, a kanban card attached to a physical container of parts circulates between consuming and producing process steps: when the container is emptied, the kanban card is sent upstream as a replenishment signal. The upstream process produces exactly the quantity the card authorizes and sends the replenishment downstream. The number of kanban cards in the system controls the maximum work in process (WIP) allowed at any point—when all cards are in circulation, no additional production is authorized, preventing overproduction. Physical kanban evolved into electronic kanban (e-Kanban) systems integrated with ERP platforms that transmit replenishment signals electronically when inventory thresholds are reached. Digital kanban boards—popularized by software development tools like Jira, Trello, and Azure DevOps—visualize work items moving through workflow stages (To Do, In Progress, In Review, Done) with explicit WIP limits at each stage to prevent bottleneck accumulation. This software development adaptation of manufacturing kanban has proven extraordinarily effective for knowledge work, where visual WIP management provides the same throughput benefits and bottleneck identification capabilities that physical kanban provides in manufacturing. The kanban system's power comes from its self-regulating nature: it automatically calibrates production pace to actual downstream consumption without requiring central planning or complex scheduling algorithms. When demand slows, kanban signals slow and production naturally decreases. When demand increases, consumption accelerates and more signals flow, increasing production. This self-regulating property eliminates the planning errors and forecast inaccuracies that cause inventory buildup and shortages in traditional push systems. The discipline of respecting WIP limits—not overriding the system during periods of pressure by allowing more work to start than the system can complete—is the most critical cultural challenge in kanban implementation.
FAQs
How is Kanban different from Scrum in software development?
Scrum organizes work in fixed-length time boxes (sprints) with defined ceremonies, specific roles (Scrum Master, Product Owner), and commitment to a sprint scope at the start. Kanban has no fixed time boxes—work flows continuously, with new items pulled into the workflow as capacity becomes available. Kanban is more appropriate for operations with unpredictable incoming work (support teams, maintenance teams); Scrum is more appropriate for product development with planned feature delivery cycles.
What is the right WIP limit for a kanban system?
WIP limits are set based on team capacity and the desired trade-off between responsiveness and context-switching. A common starting point: (number of team members) x 1.5-2 active items at any workflow stage. Tight WIP limits (1 per person) maximize focus and throughput but reduce flexibility. Looser limits (3+ per person) provide more flexibility but increase multitasking and reduce throughput. Teams should experiment with WIP limits and observe the effect on cycle time and team stress before settling on the right balance for their context.
Relevant Executive Roles
The Crimson Bench · Est. 2002 · Founded in New York City
Deploy an Executive in 48 Hours
Verified corporate accounts only. Ivy League-educated. Flat-rate pricing. 14-day no-cause cancellation.
25,000+ Ivy League Executives · 150,000+ Global Consultants · 48-Hour Deployment