The Kanban system is a way to manage work as a flow: you make every task visible on a board, limit how much is in progress at once, and improve the flow step by step. It comes from Toyota’s production system and was adapted to knowledge work in the 2000s; today it runs software, marketing, support and operations teams. If you are new to it, start with what Kanban is; this page goes deeper into how to run it.
The 4 Kanban principles
- Start with what you do now. No reorganisation needed: map your current process on the board.
- Agree to pursue improvement through evolutionary change. Small changes, one at a time.
- Respect current roles and responsibilities. Kanban adds no new job titles.
- Encourage leadership at every level. Anyone can spot a bottleneck and propose a fix.
The 6 core practices
- Visualise the workflow: one column per stage, one card per item.
- Limit work in progress (WIP): a maximum number of cards per column.
- Manage flow: watch where cards wait, not where people are busy.
- Make policies explicit: write down what “Done” means for each column.
- Implement feedback loops: a short daily stand-up and a regular review.
- Improve collaboratively: change one rule, measure, keep or revert.
WIP limits, with an example
A team of four sets a limit of five cards in “In progress”. When the column is full, nobody starts a new card; they help finish or unblock one instead. The result is counter-intuitive: less work started, more work finished. A good starting point is one to two cards per person.
Swimlanes and classes of service
Swimlanes are horizontal rows across the board: one per team, per client or per type of work. Classes of service set priority rules, for example an “Expedite” lane for urgent fixes with a limit of one card. Use them only when the board gets crowded.
Kanban metrics
| Metric | What it measures | What it tells you |
|---|---|---|
| Lead time | Request → done | What the customer experiences |
| Cycle time | Started → done | How fast the team works an item |
| Throughput | Items done per week | Capacity, for forecasts |
| WIP | Items in progress now | Overload, multitasking |
| Cumulative flow diagram | Cards per column over time | Bottlenecks (a widening band) |
Cadences: the Kanban meetings
- Daily stand-up (15 min): walk the board right to left, focus on blocked cards.
- Replenishment (weekly): choose what goes into “To do”.
- Service delivery review (every 2–4 weeks): look at the metrics, decide one improvement.
Kanban and agile
Kanban is an agile method: it delivers continuously and adapts to change. Unlike Scrum, it has no sprints and no fixed roles. See Kanban vs Scrum for a full comparison.
Start a Kanban system in one hour
- Draw your current stages as columns on a free Kanban board.
- Put every open task on a card.
- Set a WIP limit on the busiest column.
- Hold a 15-minute stand-up every day for two weeks, then review.
Need dates too? In Ganttmint the same cards open as a Gantt chart. Prefer paper or spreadsheets? Use the Kanban board templates or printable Kanban cards.
Questions
What is a Kanban system?
A way to manage work as a visual flow on a board, with limits on work in progress and continuous improvement.
What are the principles of Kanban?
Start with what you do now, improve through small changes, respect current roles, and encourage leadership at every level.
What are Kanban metrics?
Lead time, cycle time, throughput, work in progress and the cumulative flow diagram.
What is a Kanban swimlane?
A horizontal row across the board that separates work by team, client or type, such as an expedite lane for urgent items.
Is Kanban agile?
Yes. It is one of the main agile methods, with continuous delivery instead of fixed sprints.