What Is Kanban? Meaning, Principles and a First Board

Kanban is a way of managing work by making it visible and only starting something new when there is room for it. The word is Japanese for “sign” or “signboard”. At Toyota, a kanban card told an earlier process to make or deliver exactly the parts a later process had used, so nothing was produced before it was needed. Teams outside factories took the same idea and turned it into a board: columns for the stages work goes through, a card for each piece of work, and an agreed limit on how much can be in progress at once. That limit is what makes it kanban rather than a to-do list with columns.

This page is the definition. If you already know what kanban is and want the rollout, read how to implement kanban. If you only need the board itself explained, see what is a kanban board.

Kanban meaning: where the word comes from

The Lean Enterprise Institute’s lexicon defines a kanban↗ (opens in a new tab) as a signaling device that authorizes and instructs the production or withdrawal of items in a pull system, and notes that the term is Japanese for “sign” or “signboard”. The best-known form is a card, but the lexicon lists triangular metal plates, colored balls and electronic signals as kanban too. What matters is the job it does: it tells a process to make something, or a material handler to move something.

Two kinds follow from that job. A production kanban tells an upstream process what to make and how many. A withdrawal kanban authorizes moving parts downstream to where they will be used. In both cases the number of cards in circulation caps the inventory: no card, no production.

The Toyota origin

Kanban grew out of the Toyota Production System and its Just-in-Time pillar: make only what is needed, when it is needed, in the amount needed. Toyota’s own production system tour↗ (opens in a new tab) describes the pull system behind it, in which the following process goes back to the preceding process to collect the parts it has used, “facilitated by Kanban card”. The same page says the idea came in part from supermarkets, which only refill goods that have been sold.

It took years to spread. Toyota’s company history records that the kanban management system was adopted at all plants in 1963↗ (opens in a new tab), and that through 1965 kanban were also adopted for retrieving parts from suppliers. Taiichi Ohno, backed by Eiji Toyoda, is the name most associated with building that framework.

What is kanban outside the factory?

Software and other knowledge work borrowed the pull signal and the capped queue, not the card mechanics. There is no physical part to run out of. Instead, a column on a board holds a limited number of cards, and a free slot is the signal to pull the next piece of work. Two definitions are widely cited, and they agree more than they differ.

The Kanban Guide: a kanban system in three practices

The May 2025 edition of The Kanban Guide↗ (opens in a new tab), by John Coleman and Daniel Vacanti, defines kanban as “a strategy for optimizing the flow of value through a process”. It names three practices working together, and calls them, once implemented, a kanban system:

1. Defining and visualizing a workflow. The team writes a Definition of Workflow: what a work item is, when it counts as started and finished, the states between, how work in progress is controlled, explicit policies for how items move, and a service level expectation, a forecast of how long an item should take.
2. Actively managing items in a workflow. Controlling work in progress, keeping items from aging unnecessarily, and unblocking blocked work. Controlling work in progress should create a pull system: start something only when there is a clear signal of capacity.
3. Improving a workflow. Changing the Definition of Workflow as the team learns, whenever the context calls for it, not only at a scheduled meeting.

The guide also asks for four flow metrics: work in progress, throughput, work item age and cycle time. Its history section traces today’s kanban for knowledge work to a team at Corbis in 2006, and before that to the Toyota Production System. The difference between cycle time and the customer’s wait is covered in cycle time vs lead time.

The Kanban Method: David Anderson’s version

Kanban University says its Kanban Method↗ (opens in a new tab) is based on David J. Anderson’s 2010 book, Kanban: Successful Evolutionary Change for Your Technology Business. It adds change-management principles to the practices. The first is “Start with what you do now”: you put your existing process on a board and improve it gradually, rather than replacing it.

• Change management principles: start with what you do now; agree to pursue improvement through evolutionary change; encourage acts of leadership at all levels.
• Service delivery principles: understand and focus on customer needs and expectations; manage the work and let people self-organize around it; regularly review the network of services and its policies.
• Six general practices: visualize; limit work in progress; manage flow; make policies explicit; implement feedback loops; improve collaboratively, evolve experimentally.

If you want one sentence that covers both: kanban is a visible workflow, a limit on work in progress, the habit of managing flow, and written rules that the team changes as it learns.

A first kanban board in ten minutes

Here is a worked example. A three-person web team in Columbus, Ohio, keeps its work in an inbox and a spreadsheet. A sticky-note wall, a whiteboard or any board tool will do. Set a timer.

1. Minutes 0 to 2: list every piece of work anyone is doing or has promised. One line each, written so a stranger could understand it. The team gets fourteen.
2. Minutes 2 to 4: draw the columns. Keep them to the states work really passes through. For this team: Backlog, Next, Doing, Done.
3. Minutes 4 to 6: place every item. Half-finished work goes in Doing even if nobody touched it this week. The team finds seven cards in Doing, which surprises everyone.
4. Minutes 6 to 8: set a work in progress limit on Doing. One per person is a common first number, so three. The four extra cards go back to Next, each with a note saying why.
5. Minutes 8 to 10: write the rules on the board itself: what counts as started and finished, who refills Next and when, and what to do with a blocked card.

BACKLOG (6)              NEXT (max 4)            DOING (max 3)           DONE
- Accessibility audit    - Fix checkout tax      - Contact form spam     - Update SSL cert
- Blog redesign          - Sales tax for Texas   - New pricing page
- Migrate image CDN      - Refund email copy     - Mobile nav bug
- Newsletter template    - ZIP code lookup
- 404 page copy
- Analytics cleanup

Started  = card moves into Doing.     Finished = deployed and checked by someone else.
Next     = refilled Mondays by the lead, at most 4 cards.
Blocked  = a comment says why and who is chasing it, the same day.

That is a working kanban system: a visible workflow, a limit, and explicit policies. What it does not have yet is history. Start noting when each card enters Doing and when it reaches Done, and after a few weeks you have cycle times to base a forecast on. The week-long version of this, with a review cadence and the backlog cleanup, is in how to implement kanban.

Kanban principles in practice

• Stop starting, start finishing. When Doing is full, help finish a card rather than pulling a new one. Choosing and defending the number is covered in kanban WIP limits.
• Read the board right to left. In a daily look, ask what is nearly done and what it needs before asking what to start.
• Make waiting visible. A card that has not moved in a week is information, not clutter.
• Split by class of work when one board gets crowded. Rows for expedite, standard and fixed-date work are kanban swimlanes.
• Change one thing at a time, and write the change into the policies.

Kanban, Scrum and agile

Kanban is not a project plan and not a set of meetings. It has no sprints, no fixed roles and no required ceremonies; work flows continuously and the limit controls how much is in flight. Scrum plans work in fixed-length sprints with defined roles and events; see what is Scrum, and kanban vs Scrum for choosing between them. Both sit under the wider idea in what is agile. Kanban works for one person too: personal kanban shrinks the same rules to a single to-do board, and kanban board examples shows boards other teams run.

A kanban-style board on fenbs, and its limits

fenbs is a kanban-style board with four fixed lanes: To Do, Next Up, In Progress and Completed. The ten-minute board above maps onto them directly, with Backlog as To Do. Each task is a feature, an enhancement or a bug, with a priority from 1 (most urgent) to 10, and Add many pastes a list in as tasks, which covers the first two minutes. History records every move with who made it, a person or an AI assistant, which is the raw material for cycle time.

Be clear about what it lacks. fenbs has no WIP limit setting, no swimlanes, no custom columns, no sprints, no due dates and no settable assignee. The limit is an agreement you keep yourselves; each lane shows its count beside its name. Board policies go in AI context notes that people and every connected AI assistant read, and a policy that must always hold goes on the Decisions and rules page as a rule, decided by a person. If your board needs six columns and enforced limits, a configurable kanban tool will suit you better.