Skip to main content
Category: Methods
Type: Workflow Management System
Origin: Toyota, 1940s
Also known as: Kanban, Visual Workflow Management, Lean Management System
Quick Answer — The Kanban Method is a visual workflow management system that helps teams visualize work in progress, limit work in progress (WIP), and maximize efficiency. Originally developed by Toyota in the 1940s for manufacturing, Kanban uses a board with columns representing different stages of work—typically “To Do,” “In Progress,” and “Done”—with cards representing individual tasks. The method’s core principle is that visualizing work makes bottlenecks and inefficiencies visible, enabling teams to continuously improve their process.

​
What is the Kanban Method?

The Kanban Method is a lean management approach that visualizes work on a board, making the flow of tasks transparent and manageable. At its heart, Kanban is about making the invisible visible: by placing every task on a board where team members can see it, hidden bottlenecks, excessive workload, and stalled work become immediately apparent rather than lurking in inboxes or spreadsheets. A typical Kanban board consists of columns representing stages in a workflow. Tasks move from left to right as they’re worked on. The simplest boards have three columns—“To Do,” “In Progress,” and “Done”—but more complex workflows might include additional stages like “Review,” “Testing,” or “Deployment.” Each task is represented by a card that contains relevant information: description, assignee, priority, deadline, and any other metadata the team finds useful.
“The bottleneck determines the throughput of the entire system. By visualizing the workflow, Kanban helps identify these constraints so teams can address them systematically.” — David Anderson, author of “Kanban: Successful Evolutionary Change for Your Technology Business”
The true power of Kanban lies in its emphasis on flow optimization rather than strict scheduling. Unlike traditional project management methods that plan specific delivery dates, Kanban focuses on the smooth movement of work through the system. When a card stalls in a column, that’s a signal to investigate. When one column always has more cards than others, that’s a bottleneck to address. This continuous feedback loop enables teams to iteratively. improve their process### Kanban in 3 Depths
  • Beginner: Start with a simple three-column board (To Do, In Progress, Done). Create cards for every piece of work and move them through the columns as work progresses. Focus on making work visible to everyone on the team.
  • Practitioner: Add WIP limits to each column to prevent overloading. Use swimlanes to separate different types of work or team members. Implement policies for when cards can move between columns. Add columns for key process stages like review or testing.
  • Advanced: Use metrics like cycle time, throughput, and cumulative flow diagrams to identify trends. Run regular retrospectives focused on improving flow. Experiment with different board structures, WIP limits, and policies. Connect Kanban to other agile practices like Scrum or XP.

​
Origin

The Kanban Method originated at Toyota in the late 1940s, developed by industrial engineer Taiichi Ohno as part of the Toyota Production System (TPS). The word “Kanban” comes from Japanese, meaning “signboard” or “visual card.” Originally used in manufacturing, the system aimed to create a pull-based workflow where materials and components were only produced or delivered as needed, reducing waste and overproduction. In the early 2000s, software consultant David Anderson adapted Kanban for technology businesses. His 2010 book “Kanban: Successful Evolutionary Change for Your Technology Business” became the foundational text for applying Kanban to software development and IT operations. Anderson introduced key concepts like WIP limits, cumulative flow diagrams, and service delivery templates that expanded Kanban beyond its manufacturing roots. The agile community embraced Kanban for its flexibility. Unlike Scrum, which prescribes specific roles, ceremonies, and timeboxes, Kanban is simply a method for managing work flow—teams can adopt as much or as little as they need. This non-prescriptive nature made Kanban particularly attractive to teams in operations, support, and maintenance roles where Scrum’s fixed sprints didn’t fit well.

​
Key Points

1

Visualize Work

Create a board with columns representing workflow stages. Every task becomes a card on the board. This transparency reveals the true state of work across the entire team—no more hidden work stuck in personal inboxes or forgotten spreadsheets.
2

Limit Work in Progress (WIP)

Set maximum limits for each column. When a column reaches its limit, team members must finish existing work before pulling new tasks. This prevents multitasking, reduces context-switching, and surfaces bottlenecks that would otherwise remain hidden.
3

Manage Flow

Monitor how work moves through the system. Track metrics like cycle time (how long a task takes from start to finish) and throughput (how many tasks complete per time period). Use this data to identify delays and improve the process.
4

Make Policies Explicit

Define clear rules for how work moves through the board. When can a card move to “In Progress”? What criteria must be met before moving to “Done”? Explicit policies reduce confusion and create shared understanding.
5

Implement Feedback Loops

Hold regular standups at the board to discuss blockers and progress. Use retrospectives to identify improvement opportunities. The Kanban cadences—operations review, service delivery review, and risk review—provide structured opportunities for feedback.
6

Improve Collaboratively

Use data and team observations to evolve the process. Start with small experiments rather than large changes. Focus on improving flow rather than just moving more cards—the goal is sustainable pace and quality.

​
Applications

Software Development

Kanban is widely used in software development for managing feature work, bug fixes, and technical debt. Its visual nature helps development teams balance new development with maintenance work and quickly identify when too much work is in progress.

IT Operations & Support

Teams managing IT infrastructure, help desks, and customer support queues use Kanban to visualize incoming requests, track ongoing work, and ensure nothing falls through the cracks. WIP limits help prevent burnout by capping how many incidents can be worked on simultaneously.

Marketing & Creative Work

Creative teams use Kanban to manage content production, campaign planning, and design work. The visual board helps balance competing priorities and ensures all stakeholders can see the status of deliverables without constant status meetings.

Personal Productivity

Individuals use personal Kanban boards to manage projects, daily tasks, and goals. The method’s simplicity makes it accessible for personal use while still providing the benefits of visualization and flow management.

​
Case Study

Context: A 15-person customer support team at a SaaS company was struggling with escalating response times and agent burnout. Tickets were piling up, customers were complaining on social media, and the team felt constantly overwhelmed. Traditional approaches like adding more agents or working overtime weren’t sustainable. Question: How could the team gain visibility into their workflow and reduce the backlog without simply adding more hours? Evidence: The support lead implemented a Kanban board with columns for triage, in-progress, waiting for customer, and resolved. They introduced WIP limits for each agent (maximum 5 active tickets) and visual signals for blocked work. The team tracked metrics for 8 weeks and compared outcomes to the previous 8-week period. Result: Average first response time decreased from 4.2 hours to 1.8 hours—a 57% improvement. Customer satisfaction scores rose from 3.9 to 4.5 out of 5. Perhaps most importantly, agent burnout scores dropped by 40%—the WIP limits forced the team to focus on finishing work rather than starting more, which paradoxically allowed them to handle more total tickets with less stress. Lesson: Kanban revealed that the team’s real problem wasn’t volume—it was poor flow management. Agents were constantly context-switching between dozens of open tickets, never finishing anything. By limiting WIP and making work visible, the team discovered that doing less actually meant accomplishing more.

​
Boundaries and Failure Modes

Kanban works best when the workflow is relatively stable and predictable. It struggles in certain situations:
  • Highly variable priorities: If priorities change daily or hourly, the constant reprioritization can make a board chaotic. Consider whether your work actually has stable stages before adopting Kanban.
  • Very small teams: A two-person team may find Kanban overhead excessive for their needs. The method works best when there’s enough work to fill a board and enough people to benefit from shared visibility.
  • No commitment to WIP limits: Simply creating a board without enforcing WIP limits won’t produce results. The limits are what force difficult conversations about capacity and bottlenecks.
  • Static boards: A Kanban board should evolve with your process. If you never change columns, limits, or policies, you’re missing the improvement opportunity that Kanban enables.

​
Common Misconceptions

While Kanban is popular in software development, its origins are in manufacturing and it’s applicable to any knowledge work. Support teams, marketing departments, HR, finance, and individuals all use Kanban successfully. The core principle—visualizing work to improve flow—is universal.
Start simple. A three-column board (To Do, In Progress, Done) is perfectly valid Kanban. Additional columns can be added as you identify specific stages that need attention. The key is not the number of columns but the discipline of limiting WIP and making flow visible.
Many teams successfully combine Kanban and Scrum (often called “Scrumban”). Kanban provides the flow management while Scrum provides the cadence. These methods can complement each other rather than competing.
The Kanban Method connects to several other productivity and management approaches. Agile Methodology provides the philosophical foundation for iterative improvement. Lean Management, which also originated at Toyota, shares Kanban’s emphasis on eliminating waste and maximizing flow. For understanding how to limit work, consider Theory of Constraints—the idea that every system has a single constraint that limits throughput. The Eisenhower Matrix helps prioritize which tasks deserve attention on your board.

Scrum

Agile framework with sprints and roles

Lean Thinking

Eliminate waste, maximize value

Theory of Constraints

Identify and address system bottlenecks

​
One-Line Takeaway

Use Kanban to make work visible and limit work in progress—the visual feedback this provides is what enables continuous improvement and prevents burnout.