Kanban guide · Kanban basics
What Is Kanban? A Complete Guide to the Kanban Method
Kanban is a method for managing work by making it visible, limiting how much is in progress at once, and continuously improving the flow of work from request to delivery. It started on Toyota's factory floors and is now used by software, marketing, operations and support teams worldwide.
Key takeaways
- Kanban visualises work, limits WIP and improves flow.
- It began at Toyota and was adapted to knowledge work in the 2000s.
- Start with your current process and improve it step by step.
Where Kanban comes from
"Kanban" is Japanese for "signboard" or "visual card". In the Toyota Production System, developed from the late 1940s under Taiichi Ohno, kanban cards signalled when a process needed more parts, so production was pulled by real demand instead of pushed by forecasts. See Just-in-Time and pull vs push systems.
In the 2000s, David J. Anderson and others adapted these ideas for knowledge work. The resulting Kanban Method is now one of the most widely used Agile approaches.
How a Kanban system works
- Visualise the work on a Kanban board, with one card per work item and one column per stage.
- Limit work in progress with WIP limits on each active column.
- Pull, don't push: people start new work only when there is capacity.
- Manage flow: watch how work moves and remove what slows it down.
- Make policies explicit: agree and display the rules for each stage.
- Improve continuously using metrics and regular reviews.
Kanban's principles
The Kanban Method starts from where you are rather than imposing a new process. Its foundational principles are to start with what you do now, agree to pursue improvement through evolutionary change, and encourage acts of leadership at every level. See Kanban principles for the full set.
Benefits of Kanban
- Visibility: everyone sees what is being worked on and where it is stuck.
- Faster delivery: limiting WIP shortens cycle time.
- Flexibility: priorities can change at any time without disrupting work in progress.
- Less overload: teams pull work at a sustainable pace.
- Predictability: flow metrics support reliable forecasts.
- Easy to start: no new roles or ceremonies are required.
When to use Kanban
- Work arrives continuously and unpredictably: support, operations, maintenance.
- Items vary widely in size and urgency.
- The team wants to improve gradually without a big reorganisation.
- Several teams or individuals share a service and need to see demand.
For product development in fixed cycles, compare Kanban vs Scrum.
How to start in one week
- Map the stages your work actually goes through.
- Draw a board with those stages and put every current item on it.
- Agree a WIP limit for each active column, roughly one or two items per person.
- Hold a short daily Kanban meeting at the board.
- After two weeks, look at cycle time and where cards wait, and make one improvement.
Free templates for this topic
Frequently asked questions
Is Kanban Agile?
Yes. Kanban is widely considered an Agile approach, focused on flow and continuous improvement rather than fixed iterations.
Does Kanban have roles?
The Kanban Method does not require new roles. Some teams add a Service Delivery Manager or Service Request Manager as they mature.
Do you need software to use Kanban?
No. A whiteboard and sticky notes are enough to start. Digital tools help for remote teams and metrics.
What does Kanban mean?
Kanban is Japanese for "signboard" or "visual card". At Toyota, kanban cards signalled when a process needed more parts, so production was pulled by real demand.
What is Kanban in simple terms?
Kanban is a way of managing work by putting every item on a visual board, limiting how much is in progress at once and steadily improving how work flows to completion. You start with the process you already have and change it gradually.
Who created the Kanban Method?
The Kanban Method for knowledge work was developed in the 2000s by David J. Anderson and others, building on the kanban system from the Toyota Production System led by Taiichi Ohno.
What are the core practices of Kanban?
Visualise the work, limit work in progress, manage flow, make policies explicit, implement feedback loops, and improve collaboratively and experimentally. See Kanban principles.
Does Kanban use sprints?
No. Kanban manages a continuous flow of work, with items pulled in as capacity frees up rather than planned in fixed-length iterations. Teams that want a time-boxed rhythm often look at Scrumban.
What types of teams use Kanban?
Software, IT operations and support, marketing, HR, legal, design and many other teams use Kanban. It suits work that arrives continuously or varies in size and urgency.
What is a WIP limit in Kanban?
A WIP limit caps how many items can be in a stage or on the board at one time. It stops the team starting too much and shortens the time each item takes; see WIP limits.
Is Kanban good for project management?
Yes, especially for projects with changing priorities or a steady stream of tasks. Many teams combine a Kanban board with milestones or a high-level plan when they have fixed deadlines.
How do you start using Kanban?
Map your current workflow into columns, put all current work on cards, agree WIP limits and a few explicit policies, then hold a short daily meeting around the board. Improve the board as you learn.