Kanban as a Lean Tool - Lean Software Development

1The Original Kanban

The word "kanban" (看板) means "signboard" in Japanese. In Toyota's factories, kanban were physical cards attached to bins of parts.

When a worker used the last part from a bin, they'd return the kanban card to the upstream station. This signaled: "I need more parts." Only then would upstream produce more.

This simple mechanism created:

Pull: Nothing produced without a signal
Visibility: Cards showed system state at a glance
WIP limits: Number of cards constrained inventory
Flow: Work moved based on actual demand

The card itself wasn't magic. What mattered was the signal, the constraint, and the visibility.

2Kanban for Knowledge Work

David Anderson adapted Toyota's kanban system for software development, creating the Kanban Method.

The translation:

Cards → Work items: Digital cards on a board represent features, bugs, tasks
Stations → Columns: Board columns represent stages (To Do, Dev, Review, Done)
Card limits → WIP limits: Each column has a maximum number of cards
Card movement → Pull: When space opens in a column, work is pulled forward

The Kanban Method adds practices for knowledge work:

Visualize the workflow: Make all work visible on the board
Limit WIP: Constrain each stage (and/or the whole system)
Manage flow: Measure lead time, cycle time, throughput
Make policies explicit: Document rules for how work moves
Implement feedback loops: Regular cadences for review and improvement
Improve collaboratively: Use data to drive experiments

Kanban is Lean's operational answer to the challenge of invisible knowledge work.

Kanban is Lean made visible for knowledge work. The board shows what Lean principles describe: flow, pull, constraints, continuous improvement. If you understand Lean, Kanban practices make obvious sense.

3Why Kanban Works

Kanban works because it implements core Lean concepts:

Visibility: Work that's invisible can't be managed. The board makes work visible. Queues become obvious. Blockers stand out.

WIP limits implement pull: You can't push work in when the limit is hit. Downstream must pull when ready. This creates pull without complex scheduling.

Flow focus: By measuring and optimizing flow (not utilization), Kanban prioritizes what customers care about: lead time.

Evolutionary change: Kanban says "start where you are." You don't need to reorganize or adopt a framework. Just visualize your current process and improve from there.

Explicit policies reduce friction: When everyone knows the rules, handoffs become smoother. No debates about "is this ready for review?"

Kanban isn't just a board. It's a system for managing and improving knowledge work—a direct descendant of Toyota's production system, translated for intangible products.

Kanban Done Right

Team visualizes their full workflow, sets WIP limits per column, measures lead time, reviews flow weekly, and experiments with policy changes. The board is a living tool, not a static display.

Kanban in Name Only

Team has a Trello board with columns. No WIP limits. No flow metrics. No policies. Cards pile up indefinitely. The board is just a prettier to-do list. They call it Kanban but get no benefits.