What the Kanban Method is and why it matters
In this body of knowledge, Kanban means the Kanban Method: an approach to managing and improving knowledge work services, organized by David J. Anderson starting in the mid-2000s. The core idea fits in one sentence. You make work visible, limit how much work is in progress at the same time and use what you observe to change the system in small, safe steps.
The method starts from the process the team already uses, with no ready-made roles, artifacts or events to replace what exists. That is why it is described as an evolutionary change method and not as a process framework. A change that does not threaten people’s job titles or identity meets less resistance and lasts longer.
What Kanban is not
Three misconceptions are common:
- Kanban is not just the board. A board with “To do, Doing, Done” is a visualization. Without WIP limits, explicit policies and feedback cadences, it shows the work but does not change how the system behaves.
- Kanban is not a lack of commitment. A well-designed Kanban system has a clear commitment point, data-based delivery expectations and explicit agreements with the people who request the work.
- Kanban is not “Scrum without sprints”. The method does not define iterations or mandatory roles. A team that uses Scrum can apply the Kanban Method on top of what it already does, and many do.
Key concepts
Change management principles
The first group of principles deals with how change happens:
- Start with what you do now. Understand the real process, as it actually happens, and respect current roles and responsibilities.
- Agree to pursue evolutionary improvement. People agree to change through incremental, observable and reversible adjustments.
- Encourage leadership at every level. Anyone who sees a problem in the flow can propose an experiment, without waiting for management to take the initiative.
Service delivery principles
The second group looks at the service the team provides:
- Understand what the customer needs and expects, including delivery time, quality and predictability, and not just the list of requests.
- Manage the work, not the people. When the flow is visible and the rules are clear, people self-organize around it.
- Regularly review the network of services and its policies, because the outcome depends on the system’s rules more than on individual effort.
General practices
The general practices are what you actually do day to day:
- Visualize the work and the flow, including queues and blockers.
- Limit work in progress, to create the pull system.
- Manage flow, watching time, accumulation and the aging of items.
- Make policies explicit, such as entry and exit criteria for each step.
- Implement feedback loops, through cadences.
- Improve collaboratively and evolve experimentally, using models (queuing theory, theory of constraints, Cost of Delay) to form hypotheses.
Nobody adopts all six in depth at once. A support team can start by visualizing tickets and blockers and only introduce WIP limits in the second month.
Pull system
In a push system, work enters because someone decided it should: the manager hands out twelve tickets to each analyst on Monday. In a pull system, work enters when there is free capacity, and the signal for that capacity is the WIP limit. When the “In analysis” step has a limit of 3 and holds 2 items, there is a slot, and someone pulls the next item from the queue. In knowledge work, the limit itself plays the role of the signal card: that is why people speak of a virtual kanban system.
The practical effect is that the team stops starting and starts finishing: less context switching, smaller queues and shorter, more stable delivery times. You can feel this effect in a few minutes in the WIP limit experience.
From Toyota to knowledge work
The word kanban comes from the Toyota Production System, where cards signaled the need to replenish parts, limiting inventory between steps. The Kanban Method inherits two elements from that origin: the pull signal and the limit on intermediate inventory. It does not inherit the assumption that items are alike. In knowledge work, each item is different, much of the work is discovery and variability is high. That is why the method prefers probabilistic expectations, such as “85% of items are done within 9 days”, over point estimates for each item.
Common mistakes
- Copying another team’s board. The board needs to reflect your flow, not the flow of an example from the internet.
- Restructuring roles on day one. This goes against the principle of starting with what exists and creates needless resistance.
- Treating the WIP limit as a utilization target. The limit is a ceiling that exposes problems, not a number to fill.
- Measuring people instead of the flow. Comparing individual productivity encourages starting many items and hiding blockers.
How this shows up on the exam
Questions in this domain ask you to recognize which principle is at stake in a concrete situation. For example: a manager wants to roll out Kanban and proposes, in the same week, creating new job titles and switching tools. You need to identify what conflicts with evolutionary change and what a coherent first step would be. You will also see situations that ask you to tell a visualization apart from a Kanban system and to distinguish a pull system from a push system based on a description of how work enters.
Frequently asked questions
Is the Kanban Method an agile methodology?
It is compatible with agile values and widely used by agile teams, but it does not depend on them. The Kanban Method is a method for change management and service improvement. It works in software development, operations, marketing, legal and any area where work arrives as requests and must be delivered predictably.
Do I need to drop Scrum to use the Kanban Method?
No. Because the method starts with what you do now, it can be applied on top of a Scrum process. In practice, Scrum teams often add WIP limits to the sprint steps, measure cycle time and use probabilistic forecasts in planning.
What is the difference between a Kanban board and a Kanban system?
The board is the visualization. The Kanban system includes the board, the WIP limits that create pull flow, the explicit policies, the metrics and the review cadences. A board without limits shows the work; a system changes how the flow behaves.
