Kanban from Toyota to Swedish industry and Chalmers

Kanban began as a physical signal inside Toyota’s production system, but its development reveals a broader story about manufacturing, trade and organisational learning. The Japanese word refers to a signboard, yet the best-known form is a card that travels with material or authorises the next operation. Its importance lies not in the card itself, but in the disciplined flow of information that prevents factories from producing more than customers require. Learn more about Mrtinbeweging.net.

For Australian manufacturers, the history offers practical lessons without requiring a wholesale copy of the Toyota model. Swedish engineers transformed kanban for high-mix production, engineering projects and software-supported planning, while Chalmers researchers later examined how visual systems interact with enterprise technology. The result is a practice that has moved far beyond the factory floor while retaining its original focus on visibility, restraint and dependable flow.

Origins in Toyota’s production system

Taiichi Ohno developed Toyota’s production-control approach during the 1950s, when the company was expanding rapidly across many product lines. Limited resources and the difficulty of forecasting every customer order made large inventories risky. Toyota needed a method that would connect actual consumption in the workshop to permission to replenish materials, without waiting for managers to interpret a distant forecast.

Ohno later described a supermarket as an important analogy. Customers removed what they needed, and the store replenished those products through a visible information system. In Toyota’s version, downstream workers withdrew parts and generated the signal that authorised upstream production. The logic differed from simply putting materials wherever there was space: material movement carried information, while excess stock could hide both demand and defects.

Kanban therefore worked as part of just-in-time production and jidoka, the idea of stopping immediately when a problem appears. Cards, containers and standard quantities showed what could move next and when. Over time, the system was refined through a network of production and supplier loops, allowing small quantities to circulate through the entire supply chain. Its strength came from consistency, not from a particular card size or colour.

Adapting to Swedish industrial work

Japanese investment, export competition and visits by Toyota specialists helped spread production-system practices through Western manufacturing during the 1970s and 1980s. Swedish firms encountered ideas including just-in-time delivery, quality circles, total productive maintenance and kanban. Adoption was rarely a direct transfer from Japan. Engineers interpreted these methods through Sweden’s engineering culture, strong labour institutions and distinctive production environments.

Swedish factories often handled many product variants, customer-specific equipment and long-lived machinery. An authorised quantity that worked for repetitive automotive production could be unsuitable for a batch of pumps, robots or energy equipment. Local teams therefore adapted kanban by changing card quantities, route structures and withdrawal rules while preserving the principle that upstream work should respond to confirmed downstream demand.

The original production signals had several distinct functions:

• A withdrawal card authorised the removal of a standard container or batch.
• A production or conveyance card regulated work between successive operations.
• A supplier signal made an external replenishment requirement visible inside the factory.
• A warning or stop signal prevented defective material from moving onward.
• A controlled quantity linked the rhythm of one workstation with another.

Kanban adapted to Swedish work in a broader set of ways:

• It became part of visual production-control boards rather than a purely documentary system.
• It supported mixed-model manufacturing and engineer-to-order production.
• It linked suppliers, assembly teams and maintenance functions.
• It helped teams distinguish planned flow from urgent local problems.
• It became one source of evidence for continuous improvement.

Volvo is closely associated with lean production and close coordination between series production, suppliers and product development, although its history cannot be reduced to a single Japanese technique. Across Swedish industry, kanban increasingly sat beside teamwork, quality work and production planning. Its language changed too: what began as a physical production instruction could become a representation of constraints, risk and work commitments on a visual board.

Digital planning beyond the physical card

The move from paper to digital planning expanded both the possibilities and the risks of kanban. Physical cards remain valuable because people can see them beside the material they govern. Digital versions, however, can connect visual signals with enterprise resource planning, manufacturing execution and project-management systems. A constraint identified on a workshop board can then be linked to affected tasks, suppliers, equipment or delivery dates.

This development also weakened the distinction between kanban and visual project management. A software board may show dependencies, ownership and workflow status, but the labels alone do not guarantee control. If anyone can alter a quantity or authorisation without understanding the process rule, the board becomes decorative. Conversely, when field teams can update a signal while management receives reliable planning data, visual management becomes part of an operating system rather than a reporting layer.

Research into real shop-floor activity shows why context must remain central. The resource movement in manufacturing research illustrates how movement, time and spatial analysis can support the design of productive work. Such analysis complements kanban by revealing where waiting, travel or unnecessary handling occurs. A digital card can indicate that work is authorised, while systematic observation may show why the authorised work still takes too long.

Digital systems also require new controls around permissions, stale information and algorithmic decisions. Security, data quality and change history matter once thousands of signals circulate between organisations. The enduring value of Toyota’s idea is therefore procedural: people must know what each signal means, who may change it and what action follows. Technology can carry and interpret that rule, but it cannot create discipline where the rule is unclear.

Chalmers and the Project Visit research programme

Chalmers University of Technology in Gothenburg became an important setting for studying these changes because Celean brings academic researchers and industrial partners together around lean processes and digital planning. The team’s work covers kanban, visual planning, enterprise systems and the design of software that supports real work. This combination has placed the Swedish adaptation of kanban within a wider discussion about digital manufacturing and organisations.

The Project Visit programme presents research as a collaborative process rather than a one-way transfer from university to industry. Partners contribute operational problems, and prototypes allow assumptions to be examined before they become prescribed practice. Volvo is among the industrial organisations associated with this work, linking research to large-scale engineering and production environments in which thousands of people may need a consistent view of constraints.

Readers can examine the evidence through the Project Visit publications page, where research papers, project descriptions and prototype material connect theory with practical questions. The publications are significant because kanban in a digitally supported enterprise is not simply an older method represented on a screen. Its rules must be coordinated with system architecture, organisational roles, planning practices and the experience of people moving material or completing projects.

The Swedish contribution is consequently less about replacing Toyota’s production logic than about extending its use. Chalmers research has helped frame kanban as a sociotechnical design problem involving people, artefacts and information flows. That framing has travelled well beyond automotive plants, including into software-supported planning and collaborative visual management across complex organisations.

Lessons for Australian industrial teams

Australian industrial teams operate across a demanding geography. Manufacturing, maintenance and logistics activities in Melbourne, Sydney, Brisbane and regional industrial districts are often separated by long distances. Transport variation and the movement of specialised components between sites make visibility especially useful. A clear kanban policy can reveal whether a delay comes from an absent authorisation, unavailable equipment, a supplier problem or a mismatch between planned and actual demand.

Everyday work patterns also shape the design of a system. FIFO rosters, rotating shifts and informal handovers are familiar in mining and remote operations, while production teams in cities may rely on short stand-up meetings and whiteboards beside workstations. In these settings, a kanban card should have a precise purpose: releasing a maintenance kit, authorising a component transfer or identifying work blocked by a safety check. Digital displays can help distributed teams, but they should supplement direct communication rather than conceal uncertainty.

The Australian market provides several useful settings for this thinking. Automotive suppliers, food processors, defence contractors, advanced manufacturers and resource companies combine high-value engineering with operational urgency. Many businesses also work with imported parts or components subject to shipping variation and substantial lead times. Small batches and clear replenishment rules can reduce exposure, provided teams recognise when a stockout would stop an entire production line or create expensive downtime.

Regulation makes quality and safety inseparable from flow. Under the Fair Work Act and state and territory work health and safety laws, consultation, fatigue management and safe systems of work remain central responsibilities. A kanban system that pressures people to ignore defects or bypass rest requirements is plainly misaligned with those obligations. Visual controls are strongest when they make it easy to stop work, expose constraints and give employees a credible way to raise concerns.

The enduring lesson is that kanban works when a visible signal is backed by a clear rule, a timely response and respect for the people doing the work. Swedish research shows how this principle can travel from a workshop card to a digitally supported enterprise, while preserving the care and restraint that gave it value.