What is Kanban?
Discover the Kanban method—a lean workflow management approach born in Toyota factories that helps teams visualize work, manage flow, and continuously deliver value without the rigid structure of fixed iterations.
Understanding Kanban
Kanban is a workflow management method that originated from lean manufacturing principles at Toyota. The term "Kanban" comes from Japanese and literally means "visual card" or "billboard." The method focuses on visualizing work, limiting work-in-progress (WIP), and optimizing the flow of work through a system. Unlike Scrum, which organizes work into fixed time-boxed sprints, Kanban operates on a continuous flow model where work moves through stages as capacity becomes available. This makes Kanban particularly well-suited for environments where work arrives unpredictably or where maintaining a steady flow is more important than completing a fixed set of work in a specific timeframe.
The modern Kanban method for knowledge work was developed and formalized by David J. Anderson in the 2000s, adapting the manufacturing principles from Toyota to software development and other service-oriented work. Today, Kanban has evolved into a complete approach to workflow management that many teams use either standalone or combined with other agile practices. What makes Kanban particularly appealing is its gentleness—it doesn't require major organizational upheaval or strict adherence to ceremonies. Teams can adopt Kanban gradually, starting with simple visualization and building from there.
Kanban is about making the work visible and managing the flow of that work systematically, enabling teams to be more responsive and efficient without the overhead of sprint planning and time-boxing.
The Historical Origins of Kanban
The roots of Kanban trace back to the Toyota Production System (TPS) in post-World War II Japan. Taiichi Ohno, a visionary engineer at Toyota, observed American supermarkets and noticed how they managed inventory—products were stocked based on actual customer demand, and shelves were replenished only when items were sold. This sparked the idea of applying similar principles to manufacturing. In the 1940s and 1950s, Ohno developed the concept of Kanban cards as a way to signal when parts were needed in a production line, creating a "pull" system rather than a "push" system.
In a pull system, work is only started when there's capacity to handle it and downstream processes need the output. This was revolutionary because it reduced overproduction, decreased inventory holding costs, minimized waste, and improved overall efficiency. Toyota's remarkable success using these principles inspired companies worldwide to adopt lean manufacturing. When software development teams began exploring agile methods in the early 2000s, they recognized that Kanban's principles could apply to knowledge work just as effectively as to manufacturing. David J. Anderson's formalization of the Kanban Method for IT and knowledge work has since become a cornerstone of modern agile practice.
Core Principles of Kanban
The Kanban method is built on several core principles that guide how teams should organize their work and thinking about continuous improvement.
Visualize the Workflow
The first principle is to make the work visible. A Kanban board typically displays columns representing stages in the workflow—such as "To Do," "In Progress," "In Review," and "Done." Each piece of work is represented as a card that moves across the board from left to right as it progresses. This visualization makes it immediately obvious what's being worked on, who's working on what, where bottlenecks exist, and what's stuck. Teams gain clarity about the state of work at any moment, which is impossible when work is tracked only in spreadsheets or meetings.
Limit Work-in-Progress (WIP)
Each column on the Kanban board has a maximum WIP limit. This limit represents the maximum number of items that can be in that stage at any given time. For example, a team might limit "In Progress" to 5 items and "In Review" to 3 items. By restricting WIP, teams avoid overloading team members, reduce context switching, and create pull signals—when an item is completed and moves out of a stage, new work can pull in. WIP limits are fundamental to preventing chaos and ensuring that the system doesn't become overwhelmed with half-finished work.
Manage Flow
Kanban focuses on optimizing the flow of work through the system. Flow refers to how quickly work moves from request to completion. By monitoring flow metrics—such as cycle time (time from start to finish), lead time (time from request to start), and throughput (items completed per week)—teams can identify where work gets stuck and make targeted improvements. Rather than focusing on resource utilization, Kanban emphasizes flow efficiency. A team member might appear idle between tasks, but this actually enables faster overall flow because work isn't queued waiting for attention.
Make Policies Explicit
Kanban teams should clearly define and display the rules and policies that govern how work flows. This includes criteria for what items can enter the system, when work should be pulled from one stage to the next, when items are considered "done," and how priorities are determined. Explicit policies reduce ambiguity, enable consistent decision-making, and make it easier to onboard new team members. These policies are often captured in writing and posted near the Kanban board so everyone understands the rules of engagement.
Implement Feedback Loops
Kanban teams gather data about their workflow and use that data to drive improvements. This might involve metrics dashboards showing cycle time trends, cumulative flow diagrams visualizing bottlenecks, or regular reviews of flow metrics. Feedback loops also include customer feedback and stakeholder input, which inform prioritization decisions. By continuously studying how work flows and what customers need, teams identify where to focus improvement efforts next.
Improve Collaboratively
Continuous improvement in Kanban is a shared responsibility of the entire team. Rather than having a separate management layer impose changes, teams collectively identify improvement opportunities through their own observation and data. Regular retrospectives or flow reviews allow the team to discuss bottlenecks and collaboratively develop solutions. This distributed approach to improvement fosters ownership and ensures that changes are grounded in the team's real experience.
Understanding the Kanban Board
The Kanban board is the most visible and iconic aspect of the method. A basic Kanban board has columns representing the stages of work and rows representing different work items or projects. Each item is represented as a card that contains key information—the title, assignee, priority, and any other relevant details. Cards flow from left to right as work progresses, and when they reach the rightmost "Done" column, that work is complete and delivered. The beauty of the Kanban board is its simplicity—it requires no sophisticated tools and can be implemented with a whiteboard and sticky notes, or with digital tools for distributed teams.
Different types of work might be distinguished by colors or symbols on cards. For example, a team might use red cards for bugs, blue for features, and yellow for technical improvements. This visual distinction helps the team at a glance understand the composition of their work. WIP limits are often written at the top of each column to serve as a visual reminder and enforcement mechanism. When a column reaches its limit, no new work can be pulled into that stage until something moves out, creating a natural throttle that prevents overloading any part of the system.
Kanban vs. Traditional Project Management
Kanban differs significantly from traditional project management approaches that rely on comprehensive upfront planning, fixed timelines, and sequential phases. Traditional approaches attempt to predict the entire project scope before beginning work, establish a fixed schedule, and often use a waterfall model where each phase must be completed before the next begins. This can lead to delayed delivery, resistance to change, and situations where stakeholder feedback comes too late to be incorporated.
Kanban, by contrast, assumes work will continuously arrive and evolve. Rather than planning a massive project with hundreds of tasks upfront, Kanban maintains a prioritized list of work and pulls items into the workflow as capacity allows. This approach is far more responsive to changing business needs, customer feedback, and emerging priorities. Teams can deliver value continuously rather than waiting for a final "big bang" release. Additionally, Kanban's focus on flow metrics provides better visibility into productivity and predictability than traditional project management, which often tracks percent complete rather than actual throughput.
When to Use Kanban
Kanban is ideal for several scenarios and team structures. It works exceptionally well for maintenance and support work where requests arrive unpredictably throughout the day—a support team can't schedule support tickets into two-week sprints when they don't know what will arrive. Kanban is also excellent for teams that have highly variable work—some days might bring complex tasks requiring deep focus, while other days bring quick wins. Teams working on continuous delivery or deployment pipelines often use Kanban because work is continuously flowing through stages of development, testing, and release. Kanban also suits distributed teams where asynchronous work is important because there's no dependency on synchronous sprint ceremonies.
Additionally, Kanban works well as teams transition to agile practices. Rather than requiring a wholesale shift to Scrum with all its ceremonies and roles, teams can start with Kanban's simple visualization and WIP limits, gradually building agility without overwhelming change. Many teams ultimately use a hybrid approach, combining Scrum's sprint structure with Kanban's continuous flow principles—this is often called Scrumban.
The Power of Continuous Improvement
What makes Kanban uniquely powerful is its commitment to continuous incremental improvement rather than periodic big changes. By constantly studying how work flows, identifying constraints, and testing small improvements, Kanban teams compound their productivity gains over time. A team might spend a week analyzing why the "In Review" column consistently has work piling up, then implement a new code review process or add a team member with specialized skills. These targeted improvements directly address real bottlenecks discovered through the team's own observations. Over months and years, this relentless focus on flow improvements transforms teams from chaotic to highly efficient, delivering more value with less stress and waste.
Written by PV
© 2026 All Rights Reserved