Kanban Guide · New edition v2.1

The Official Guide to the Kanban Method.

New to Kanban? Your easy entry into the Kanban Method: its principles, practices and the Kanban visualization.

Consent
  • PDF download
  • 21 pages
  • Version 2.1, November 2026

Chapter 01

The Kanban Method

This guide is for you if you are new to Kanban and interested in learning about the basics of the method. That is why we included an introductory metaphor (Kan-Bahn) to help you connect to the concept. Our hope is that this guide provides an easy entry into the vast Kanban body of knowledge.

If you have taken Kanban University classes and want to review certain aspects, we recommend Kanban+ as a reference – you can sign in with your Kanban University account.

What is Kanban?

Maybe the simplest way to put it is: with Kanban, you can manage work. It is a method to manage all types of professional services, also referred to as knowledge work. Using the Kanban Method means applying a holistic way of thinking about your services with a focus on improving them from your customers’ perspective.

With the Kanban Method, you visualize invisible knowledge work and how it moves through a workflow. This helps to effectively operate your business, including understanding and managing risks in delivering your services to the customers. With Kanban, you and your business will develop an adaptive capability over time to respond better and faster to changes in your customers’ needs and expectations or within your business environment.

Kanban is widely known for usage within teams, to relieve overburdening and to (re-)gain control over the work done by the team. While this usually brings quick benefits, applying the Kanban Method at a greater scale, e.g., for a line of service usually encompassing the work of multiple teams or different parts of organizations, brings even greater opportunities. Used with a service focus in mind, Kanban is an effective organizational development tool.

Kanban University is “Home” of the method and the global community of Kanban trainers, coaches and consultants who continue to evolve the method and develop its related body of knowledge.

The Kanban Method at a glance: change management principles, service delivery principles and the six general practices – visualize, limit work in progress, manage flow, make policies explicit, establish feedback loops, improve collaboratively and evolve experimentally
Method, Methodology, or Framework?

Kanban is often confused with a methodology or framework. In software engineering a methodology is a process definition approach to software development and project management (a bit of a misnomer, as “methodology” should mean “the study of methods”). Methodologies contain prescriptive, defined workflows and processes, including roles and responsibilities. This means that they are usually specific to a domain, such as software development.

A process framework on the other hand is an incomplete methodology – a set of scaffolding that is intended to have broader applicability but requires customization for each context in order to fill in the missing gaps.

Kanban is not a methodology nor a process framework. Rather, it is a management method or approach that should be applied to an existing process or way of working. There is never a question of using Kanban versus a given methodology or framework. Rather, it is always adding Kanban using an existing methodology, framework, or way of working. Kanban is intended to help you manage work better and to improve service delivery to the point where you consistently meet customer expectations. Kanban is a means to improve what and how you already do things. It is not a replacement for what you already do.

The roots of the method are found in Lean Manufacturing. However, Kanban is meant to be used to manage knowledge work resulting in intangible and virtual goods and services. When compared to manufacturing, the Kanban Method views inventory as usually intangible or invisible and has much lower direct costs attached, variability in the delivery of work is accepted as inherent, the workflow is usually less strict, and the focus on waste reduction is of lower concern. Improving the value and flow of goods and services delivered are the initial focus when using the Kanban Method.

In many aspects, Kanban is strongly founded on Lean: the focus on the flow of work, limiting work in progress to establish pull systems, focus on the optimization of the system as a whole rather than managing individuals’ performance, making decisions based on data, and continually improving in an evolutionary way.

Origins

The Kanban Method as described here is based on Kanban: Successful Evolutionary Change for Your Technology Business, by David J Anderson, 2010. The motivation to create the method was mainly to find a way to manage and improve professional service businesses as well as a way to provide a humane change method.

Comic: a team in front of a Kanban board with columns Analyze, Implement, Test and Deliver. Team members say: I’m stuck. I’m too busy. I’m idle. Let’s do something about it!
Areas of Application

Kanban is a rather abstract “method without methodology” and has a wide area of possible applications.

It is important to understand that the Kanban Method is applied with its principles and practices on top of an existing flow of work and way of working. The work can be of very different kinds. After being introduced in 2010, there were several examples of Kanban being applied to services in the IT sector. Today, there is an ever increasing amount of examples of Kanban being utilized by marketing agencies, human resources, media and design services, customer support, product development, and education.

Chapter 02

Principles and Practices of the Kanban Method

When using Kanban, the scope of application (e.g., single team, multiple teams, departments, divisions, etc.) can influence the way the method’s principles and practices are applied.

If you have a look at a basic scope within a team for instance, you might find a relatively simple Kanban board with maybe 5 columns indicating the workflow, a few simple metrics and diagrams, a daily held coordination meeting and regular reviews of the team’s work and performance.

Now imagine a whole internal services department within an enterprise, which is managed by a set of Kanban boards relating to each other, placed at different levels of granularity, covering different workflows. The amount of work in progress is limited at different levels.

Both instances are proper usage of the Kanban Method. There is no “right or wrong” in Kanban, rather more or less appropriate adoption of practices given the business context and cultural environment.

The following two sections describe the general Kanban principles and practices.

Kanban Principles

Change Management Principles

These Change Management Principles are common to all Kanban implementations:

  • Start with what you do now
  • Agree to pursue improvement through evolutionary change
  • Encourage acts of leadership at all levels

Kanban is not a big bang transformation going from a current state to some future state. We know from history that those rarely work. Instead, Kanban uses an evolutionary change approach, building on the way of working already in place, seeking to improve it using many forms of feedback and collaboration. The Kanban Method engenders evolutionary change through insights gained by the people working with the Kanban board and taking acts of leadership to continuously improve their way of working. These acts of leadership may not be what are thought of as traditional leadership. They may be small observations and suggestions for improvement by individuals without organizational leadership roles.

Service Delivery Principles

Kanban encourages you to take a service-oriented approach to understanding your organization and how work flows through it. This service-oriented organizational paradigm is based on the idea that your organization is an organic entity consisting of a network of services, each of them living and breathing, and evolving. Customer requests flow through this network of services. If we are to improve service delivery, improvements should be guided by a set of principles. These principles may not be utilized early on by organizations as they may not have developed or evolved a service-oriented or customer service mindset as part of their culture.

The service-oriented principles are:

  • Understand and focus on customer needs and expectations
  • Manage the work; let people self-organize around it
  • Regularly review the network of services and its policies in order to improve outcomes

Manage with Competence.

Lead with Confidence.

Alba, a knowledge worker, at her laptop in a bright office; colleagues gather around a Kanban board in the background
#KanbanWorks
Kanban General Practices

As mentioned earlier, the breadth and depth of Kanban practices applied varies greatly. In this section, the six general Kanban practices are described. Later in the guide we go into more details on some of the core specific practices that fall within these 6 general practices. Please refer to the Kanban Maturity Model (KMM) for more details on specific implementation by maturity level.

Visualize

Visualize: show work and its flow; visualize risks; build a visual model that reflects how you actually work. No skinny mirrors!

A good visualization is the key to effective collaboration and to identify improvement opportunities. Many times, work in the organization is hidden. Visualizing that work and the flow of that work greatly improves transparency. The human sense of vision is very old from an evolutionary point of view. It allows us to absorb and process a great deal of information in a short time. In addition, visualization supports cooperation, as everyone involved literally has the same picture. More details on visualization are presented in the guide’s section on Kanban boards.

Limit Work in Progress (WIP)

WIP (Work in Progress) states the number of work items in progress at a certain time. Through Kanban we have discovered that effective systems focus more on flow of work and less on worker utilization. When resources are fully utilized there is no slack in the system and the result is very poor flow, just as in rush hour on the freeway. In knowledge work we also have the issue of context switching that can drastically reduce the effectiveness of workers.

In Kanban, we limit the WIP to balance utilization and still ensure the flow of work. The guide later describes WIP limits and how they are used in a “pull system”.

Manage Flow

The goal of managing the flow of work is to complete work as smoothly and predictably as possible, while maintaining a sustainable pace. As mentioned before, limiting WIP is one of the key ways that helps us ensure smooth and predictable flow. The monitoring or measuring of the workflow results in important information that is very useful for managing expectations with customers, for forecasting, and for improvements. This is discussed in the guide’s section on core Kanban metrics.

Make Policies Explicit

Every day, countless decisions are made about the organization of work, either by individuals or between groups of people.

Imagine a new employee starting in your area. Ideally, she will quickly understand how work is organized through explicit policies. These include:

  • Policies such as replenishing the board (when, how much, by whom)
  • Definition of when a work activity is completed, and the work item can move on (“pull criteria”)
  • WIP limits
  • Policies for handling work items of different classes of service
  • Meeting times and content
  • Other principles and collaboration agreements

All of these policies should be agreed to jointly between all parties involved including customers, stakeholders, and employees responsible for work on the board. The policies should be placed in a clearly noticeable area, preferably right next to the board. At team level, a team agreement is a good way to introduce policies. Like all other building blocks of the system, it is necessary to check and adapt these regularly.

Please note that policies are not like work instructions freeing people from the burden to make meaningful decisions. Rather, policies should enable self-organization within the group of people running a Kanban system.

Policies should be:

  • sparse
  • simple
  • well-defined
  • visible
  • always applied
  • readily changeable by those providing the service

Implement Feedback Loops

Feedback loops are required for a coordinated delivery and for improving the delivery of your service. A functioning set of feedback loops appropriate for the given context strengthens the learning capabilities of the organization and its evolution by means of managed experiments.

Some commonly used means for feedback loops in Kanban systems are the board, metrics, and a set of regular meetings and reviews which are referred to as cadences.

Improve Collaboratively, Evolve Experimentally

Back to the Change Management Principles, in the Kanban Method we “Start with what you do now” and “Agree to pursue improvement through evolutionary change.” Kanban is a method for continuous change, and we make those changes collaboratively using designed experiments based on models and the scientific method. This is where feedback and metrics are so important to guide us in the evolutionary path. We design safe-to-fail experiments so that if our hypothesis is correct and the experiment gives good results, we keep the change, but if the results are not positive, we can easily roll back to the prior state.

Chapter 03

“Kan-Bahn” – An Introductory Metaphor

The basic concepts of Kanban will be introduced here by means of a metaphor. Before we start, please consider George E.P. Box’s famous quote “All models are approximations. Essentially, all models are wrong, but some are useful. However, the approximate nature of the model must always be borne in mind”. An international group of Kanban coaches and trainers created this metaphor in 2016 at a Kanban Leadership Retreat in Barcelona.

It is based on an “Autobahn”, a German form of highway, hence the name. Our board (or system) is represented by a highway. Traffic (the work) flows – divided into packages – in the form of different vehicles through our system, a defined section of the route.

Tap the numbers on the poster to explore. The full metaphor, with all 13 concepts, is in the complete guide.

Visualize the Kan-Bahn: a motorway illustration of the Kanban Method with sticky notes for blockers, metrics, explicit policies, expedite, class of service, limit WIP, feedback loops, manage flow, discard, work types and start where you are now

1 / 11

The welcome sign

Change management principleStart with what you do now

Kanban is not a big bang transformation going from a current state to some future state. We know from history that those rarely work. Instead, Kanban uses an evolutionary change approach, building on the way of working already in place, seeking to improve it using many forms of feedback and collaboration.

Chapter 04

Specific Practices

So how do you build your own Kanban system? Let’s learn about some of the Kanban Method’s specific practices.

STATIK

The Systems Thinking Approach to Introducing Kanban (STATIK) is a repeatable and humane way to design a Kanban system for a service. Rather than copying someone else's board, a representative group of the people involved works through six steps: identify sources of dissatisfaction, analyze demand, analyze system capabilities, model the workflow, identify classes of service, and design the Kanban system. The steps are applied iteratively, as a feedback loop rather than a one-pass sequence, and typically take between four hours and four days. The result is a shared view of how the work really flows, and a full system design: board, tickets, metrics, cadences and policies.

Get each of the six STATIK steps in detail in the complete guide

Kanban Boards

Kanban boards are the most common way to visualize a Kanban system. Work is pulled from left to right: new work items enter on the left, and value is delivered to customers when they exit on the right. Every board shows at least one clear commitment point and delivery point, and how much work in progress is permitted. The columns model the actual workflow, not a wished-for future one, because Kanban starts where you are now. Lanes and card colors can separate work types or clients. A useful board is rarely just To Do, Doing, Done: each Kanban system and board is unique.

See an example board layout in the complete guide

WIP Limits and Pull

A WIP limit is the maximum number of work items allowed at one time. It can be set per workflow state, per person, per lane, per work type or for the whole system. Limiting the work that enters the system reduces delay and context switching, and balances demand with capability over time. It also creates a pull system: new work is drawn in only when there is capacity, and pull signals travel upstream as work moves downstream. This is a key difference from traditional, push-based planning, and often a cultural change. A good mantra to start with: "Stop starting, start finishing."

See how WIP limits and pull signals work on a board in the complete guide

Core Kanban Metrics

Kanban uses three core metrics. Lead time is how long a single work item takes to pass through the system, from the commitment point to completion. Delivery rate is the number of work items completed per unit of time, such as features per week or new hires per month. WIP is the number of work items in the system at a given moment. These metrics feed charts such as the run chart, the lead time distribution and the cumulative flow diagram (CFD), which help you understand how your system behaves, make delivery more predictable and timely, and find opportunities to improve.

See the run chart, lead time distribution and CFD explained in the complete guide

Kanban Cadences

Cadences are the regular meetings and reviews that put Kanban's feedback loops into practice. They grow with maturity, so build them up gradually and fit them to your organizational context. Start by identifying existing meetings that already serve a similar purpose, and evolve them. Keep their names or use the standard cadence names: the purpose is what matters. Choose the frequency and duration to suit your context, as more frequent, shorter meetings often increase agility. A common side effect of Kanban initiatives is better-focused, more structured meetings with fewer attendees.

See example team-level and service-oriented cadences in the complete guide

The complete guide

Take the whole guide with you

All four chapters, the full Kan-Bahn metaphor and the glossary in one PDF. Edition 2.1 is available in English; earlier editions are available in Armenian, Bulgarian, Catalan, Chinese, Danish, Dutch, French, German, Italian, Korean, Polish, Portuguese, Russian, Spanish, Turkish and Ukrainian.

Get the guide

From the guide

Kanban glossary

66 key terms of the Kanban Method, as defined in the official guide.

Kanban Method

A method for the definition, management and improvement of services that deliver knowledge work.