The Origins of Kanban

Kanban didn't start in software. It started in a Toyota factory in the 1940s, created by Taiichi Ohno to solve a specific problem: how do you produce only what's needed, when it's needed?

The word "kanban" literally means "signboard" or "visual card" in Japanese. In Toyota's factories, these were physical cards attached to bins of parts. When a worker used the last part from a bin, they'd send the kanban card back upstream—signaling that more parts were needed.

This simple mechanism had profound effects:

• No overproduction — You only make what's been consumed
• Visible flow — Anyone could see what was happening
• Pull-based work — Downstream demand drives upstream production
• Built-in limits — The number of cards constrained work-in-progress

The genius wasn't complexity. It was elegant simplicity.

In 2004, David J. Anderson was working at Microsoft when he began adapting Toyota's ideas for software development. His key insight: knowledge work has similar flow problems to manufacturing, even though the "product" is intangible.

Software teams were struggling with:

• Too much work-in-progress (WIP) causing context switching
• Unpredictable delivery times
• No visibility into bottlenecks
• Resistance to process change

Anderson's innovation wasn't just translating factory concepts. He added something crucial: start with what you do now. Unlike Scrum, which prescribes a framework, Kanban begins by visualizing your existing process.

The first software Kanban system at Microsoft's XIT team showed immediate results:

• Lead time dropped from 5+ months to 5 weeks
• Throughput increased 155%
• No layoffs, no reorganization—just better flow

Here's where people get confused. There are two things called "Kanban":

kanban (lowercase) — The visual signaling tool. Cards on a board. This is what most people think of when they hear "Kanban."

The Kanban Method (uppercase) — A complete approach to managing and improving knowledge work, created by David J. Anderson. It includes principles, practices, and a philosophy of evolutionary change.

You can use kanban boards without following the Kanban Method. Many teams do—they put cards on a board and call it "doing Kanban." But they miss the deeper practices: WIP limits, flow metrics, continuous improvement cadences.

This curriculum teaches the Kanban Method, not just how to set up a board.