Kanban guide · Kanban basics
Kanban Principles and Practices Explained
Kanban is built on a small set of principles and practices. Together they explain why Kanban works without imposing a new process, and they give teams a clear path to improve.
Key takeaways
- Kanban starts from your current process and improves it gradually.
- Six core practices: visualise, limit WIP, manage flow, explicit policies, feedback loops, improve.
- Leadership and improvement can come from anyone.
Foundational principles
- Start with what you do now. Map your current process; don't reorganise first.
- Agree to pursue improvement through evolutionary change. Make small, safe, incremental changes rather than one big transformation.
- Encourage acts of leadership at all levels. Anyone can spot a problem and propose an improvement.
Service delivery principles
- Understand and focus on customers' needs and expectations.
- Manage the work, and let people self-organise around it.
- Regularly review the network of services and the policies that govern them.
The six core practices
| Practice | What it means | How to apply it |
|---|---|---|
| Visualise | Make work and workflow visible | A Kanban board with every item on it |
| Limit work in progress | Cap how much is started but not finished | WIP limits per column |
| Manage flow | Optimise how smoothly work moves | Track cycle time and throughput |
| Make policies explicit | Agree and display the rules | Entry and exit criteria per column; classes of service |
| Implement feedback loops | Regular reviews at several levels | Kanban cadences |
| Improve collaboratively, evolve experimentally | Use models and data to guide change | Little's Law, Theory of Constraints, experiments |
Applying the principles
A support team might start by putting every open ticket on a board (visualise), then notice that half sit in "waiting for engineering". They agree a WIP limit, add a policy that blocked tickets are reviewed daily, and track cycle time. After a month, they review the data and try another change. That is Kanban in practice: small, visible, evidence-based improvements.
Free templates for this topic
Frequently asked questions
How many Kanban practices are there?
The Kanban Method describes six core practices: visualise, limit WIP, manage flow, make policies explicit, implement feedback loops, and improve collaboratively.
What is the most important Kanban principle?
Many practitioners consider limiting work in progress the most powerful, because it drives faster flow and exposes problems.
What are the Kanban principles?
The Kanban Method's change management principles are to start with what you do now, agree to pursue improvement through evolutionary change, and encourage acts of leadership at every level. Service delivery principles focus on understanding customer needs and managing the work, not the people.
What does the Kanban principle "start with what you do now" mean?
It means you do not throw out your current process, roles or titles. You visualise how work really flows today and improve it step by step, which reduces resistance to change.
What does the Kanban practice "make policies explicit" mean?
It means writing down the rules the team works by, such as definitions of done for each column, WIP limits and how urgent items are handled. Visible policies make decisions consistent and easy to improve.
What does the Kanban practice "manage flow" mean?
Managing flow means watching how smoothly items move across the board and acting on queues, blockers and bottlenecks. Teams use measures such as cycle time and throughput to guide this.
Why do Kanban practices limit work in progress?
Limiting WIP reduces multitasking and context switching, shortens cycle time and makes bottlenecks visible. By Little's Law, less WIP at the same throughput means faster delivery.
What is the Kanban practice of implementing feedback loops?
Feedback loops are the regular meetings, or cadences, where the team reviews its work and process, from the daily Kanban meeting to service delivery and strategy reviews. See Kanban cadences.
Do Kanban principles require changing job titles?
No. Kanban respects current roles, responsibilities and titles, and it only changes them when the team agrees that doing so would help.
How are Kanban principles different from Scrum values?
Scrum values (commitment, focus, openness, respect, courage) describe team behaviour inside a defined framework. Kanban principles describe how to evolve an existing process gradually without imposing a new one.
Can you apply Kanban principles without a board?
Visualisation is a core practice, so some form of board is expected. It can be very simple, a list split into to do, doing and done, as long as it shows the real state of work.