Kanban History: From Toyota’s Factory Floor to Modern Project Management

Introduction

Kanban is one of the most widely used visual project management systems in the world today, but its origins have nothing to do with software or knowledge work at all. Understanding where Kanban came from, and how it made the leap from a Japanese car factory to modern Agile teams, gives practitioners a far deeper appreciation of why its core principles, visualising work and limiting work in progress, remain so effective decades later.

Origins: Toyota and the Birth of Kanban

Kanban originated at Toyota in Japan in the late 1940s, developed by industrial engineer Taiichi Ohno as part of what became known as the Toyota Production System. Ohno was tasked with closing a significant productivity gap between Toyota and its American competitors, and he found inspiration in an unlikely place: the supermarket. He observed that supermarkets only restocked shelves once customers had bought nearly all available stock, a simple pull-based replenishment principle he believed could transform Toyota’s production line.

The word “kanban” itself is Japanese for “signboard” or “card”, referring to the physical cards Ohno introduced to signal when a preceding stage of production needed to supply more material. By the 1960s, Toyota had extended the kanban system across most of its manufacturing operations, and in 1978 Ohno published Toyota Production System: Beyond Large-Scale Production, formally documenting the principles of lean manufacturing that kanban was built on.

From Factory Floor to Knowledge Work

Kanban remained largely confined to manufacturing for decades until David J. Anderson, then working at Microsoft, applied a pull-based system incorporating theory-of-constraints thinking to an IT sustaining engineering project in 2004¹. Over the following years, Anderson refined the approach into what became known as the Kanban Method, introducing the now-familiar Kanban board, work-in-progress limits, and swimlanes that knowledge workers use today. By 2007, the method closely resembled its modern form, and it began spreading rapidly through management conferences and software teams eager for a lighter-weight alternative to rigid Scrum ceremonies.

Kanban Today in Project Management

Modern Kanban retains Ohno’s original insight almost unchanged: visualise work, limit how much is in progress at any one time, and let completed work pull new work into the system rather than pushing it based on a fixed schedule. Project teams now apply this thinking well beyond software, using Kanban boards for marketing campaigns, HR processes, construction coordination, and general project management, anywhere a visual, flow-based view of work in progress adds clarity over a traditional task list.

Core Kanban Principles That Emerged From This History

Several principles trace directly back to Kanban’s manufacturing roots. Visualising work on a board mirrors Toyota’s physical card system. Limiting work in progress echoes Ohno’s insistence that nothing should be produced until it was actually needed downstream. Managing flow rather than managing people reflects the system’s original focus on the movement of materials through a process, not the performance of individual workers. Understanding this lineage helps practitioners resist the temptation to treat a Kanban board as a simple to-do list, when its real power lies in the flow discipline behind it.

Why Understanding Kanban’s History Matters for Practitioners

Knowing where Kanban came from helps project professionals apply it with the right mindset rather than as a superficial visual layer over existing habits. The discipline of limiting work in progress, the principle that made Toyota’s production line dramatically more efficient, is frequently the first thing teams abandon when adopting Kanban boards, precisely because they adopt the board without understanding the history and reasoning behind the constraint. For UK project teams working across hybrid Agile environments, that historical grounding is often the difference between a Kanban board that changes how work actually flows and one that simply digitises an existing task list.

IPM Agile Project Professional

Advance your career with our Agile Project Management dual certification programme, offering practical skills to meet modern project demands.

Download Brochure View Course

Kanban and Scrum: A Historical Divergence

Kanban and Scrum both emerged from the same broader Agile movement of the early-to-mid 2000s, but they took genuinely different paths from their origins. Scrum was designed from the outset for iterative software development, built around fixed-length sprints, defined roles, and a prescriptive set of ceremonies. Kanban, by contrast, inherited its DNA directly from Toyota’s continuous manufacturing flow, with no fixed iterations and no prescribed roles, focused instead on visualising and limiting work in progress within whatever cadence a team already operates on. This history explains why Kanban has always been the more flexible, lower-ceremony option of the two: it was never designed around software sprints in the first place, but adapted from a continuous production system where work simply flows as capacity allows.

Modern Kanban Standards and Certifications

As Kanban matured through the 2010s, the community formalised its practices into recognisable standards, including the Kanban Method’s six core practices: visualise the workflow, limit work in progress, manage flow, make process policies explicit, implement feedback loops, and improve collaboratively, and later the Kanban Maturity Model, which gives organisations a structured way to assess how deeply Kanban thinking has been embedded beyond a simple visual board. Professional certifications through bodies such as the Kanban University now allow practitioners to formally validate this knowledge, mirroring the certification pathways that have long existed for Scrum, and giving UK project professionals a recognised way to demonstrate genuine Kanban competence rather than informal board familiarity.

Applying Kanban History Lessons to Team Adoption Today

Ohno’s own approach to rolling out Kanban at Toyota offers a lesson many modern teams overlook when adopting Kanban boards: he did not implement it company-wide overnight, but began experimenting within his own machining operations and expanded gradually only once the approach proved itself in practice. Teams adopting Kanban today often make the opposite mistake, rolling a board out across an entire department in a single week without first establishing sensible work-in-progress limits or testing how the visual system fits their actual workflow. Following Ohno’s original, patient, iterative approach, piloting Kanban with a single team, refining the board and WIP limits based on what is actually observed, and only then expanding, tends to produce far more durable adoption than a top-down mandate imposed all at once.

Key Milestones in Kanban History

Lean Manufacturing Principles That Shaped Kanban

Kanban did not emerge in isolation; it was one part of a broader lean manufacturing philosophy Ohno developed at Toyota, and understanding that wider context explains much of Kanban’s underlying logic. Central to this philosophy was Ohno’s identification of seven forms of waste: overproduction, waiting, unnecessary transport, over-processing, excess inventory, unnecessary motion, and defects, all of which the kanban pull system was specifically designed to reduce by ensuring nothing was produced before it was actually needed downstream. The related concept of jidoka, building quality checks directly into a process so problems are caught immediately rather than discovered later, also shaped how kanban systems evolved to include explicit process policies and visible signals when something goes wrong. Modern project teams applying Kanban boards without this broader lean context often use the visual board correctly but miss the deeper waste-reduction discipline that made the original system so effective at Toyota.

Kanban’s Influence on Modern Project Management Tools

Kanban’s history is written directly into the interfaces of the project management software most teams use today. Tools such as Trello popularised the simple column-and-card Kanban board for general audiences well beyond software teams, while platforms like Jira, Asana, and Monday.com built native Kanban board views alongside their other project tracking features specifically because the visual, flow-based model proved so intuitive across such a wide range of work types. Even project management approaches that are not formally Kanban, including many hybrid PRINCE2 and Agile blends now common in UK organisations, routinely borrow the visual board and work-in-progress limiting concepts that trace directly back to Ohno’s original factory-floor cards, a testament to how thoroughly this seven-decade-old manufacturing innovation has reshaped how modern teams visualise their work.

Conclusion

Kanban’s journey from a Toyota factory floor to the modern project management board is a reminder that some of the most effective project tools are built on decades of tested, real-world discipline rather than new invention. Understanding that history gives project professionals a far stronger foundation for applying Kanban’s principles properly, rather than treating the board as decoration on top of business as usual.

Frequently Asked Questions (FAQs) About Kanban History

Who invented Kanban?

Kanban was developed by Taiichi Ohno, a Toyota industrial engineer, in the late 1940s as part of the Toyota Production System.

What does the word Kanban mean?

Kanban is a Japanese word that translates roughly as “signboard” or “card”, referring to the physical cards originally used to signal replenishment needs on Toyota’s production line.

When did Kanban move into software and project management?

David J. Anderson first applied kanban thinking to a knowledge-work environment at Microsoft in 2004, and the modern Kanban Method for software and project teams took shape between 2004 and 2007.

Is Kanban the same today as it was at Toyota?

The core principles, visualising work and limiting work in progress, remain the same, but modern Kanban has been adapted from physical manufacturing cards into digital boards used across software, marketing, HR, and general project management.

Is Kanban older than Scrum?

Yes, considerably. Kanban’s manufacturing origins date to the late 1940s at Toyota, decades before Scrum was formalised for software development in the mid-1990s, though both were adapted for knowledge work within a similar period in the early-to-mid 2000s.

References

1. Agile Alliance. (2023). What is Kanban? ↩︎