Volvo’s shift from physical to electronic Kanban boards

Volvo’s move from physical Kanban cards to electronic boards changed how production information travelled, not merely how it was displayed. A card once moved between a supplier point and an assembly line; electronically, the same event could become a signal within a wider production system. The change affected sequencing, replenishment, exception handling and the attention of people working under time pressure.

Celean is the collaboration between Chalmers University and industry partners studying digital visual planning, Kanban and lean processes. Its team background explains the research setting in which Volvo’s work sits. This case study examines the operational shift behind the electronic board: which decisions became quicker, which became harder, and why the physical and digital forms of visual management can serve different purposes.

Australian readers need a local boundary. Volvo Cars has no vehicle assembly plant in Australia, so its model arrives through imported vehicles, dealerships, parts networks and suppliers rather than a local car factory. Melbourne’s automotive history around Dandenong and Broadmeadows nevertheless provides a useful comparison. The regional distribution of Australian production makes shared visibility valuable, while smaller scale makes expensive systems harder to justify.

The evidence should be read carefully. An electronic Kanban board does not by itself prove shorter lead times or lower inventory. Performance depends on the product mix, integration with enterprise systems, management routines and local conditions. The most defensible conclusions concern work design: who raises a signal, who confirms it, how exceptions travel and how people use the information.

The board before the screen

Physical Kanban made material flow visible through cards, containers and agreed positions. When a component was withdrawn, a signal travelled back to the supplying point; the receiving side could then replenish against a defined quantity. In this pull logic, downstream use authorised replenishment rather than a forecast pushing materials toward the line. People could see outstanding demand, identify a delayed movement and discuss the next action beside the board.

Volvo’s manufacturing environment added complexity. Different variants, model changes and tightly timed line-side deliveries meant that exceptions could matter as much as standard replenishment. A physical board often showed the intended sequence well, but it did not automatically provide a consolidated view across lines, stores or suppliers. Updates could lag behind events, and a signal travelling through several handovers could become detached from the operation that needed it.

Nor was the old arrangement free of weaknesses. Paper movement consumed time, information was difficult to aggregate and retrospective analysis required transcription. The electronic transition addressed some of those costs, yet it also exposed questions about data quality and system access. Celean’s work treats digital visual planning as a redesign of information and authority, rather than a simple conversion of artefacts.

What changed when the cards moved

The Volvo case centres on the signal that authorised material movement. A physical card was carried, sorted and returned; the electronic equivalent allowed an event at the point of use to create a request visible to the supplying and planning functions. Its state could show what was due, where it was, who was responsible and which rule triggered the next movement. The interface could retain familiar cues—lanes, quantities and priorities—while carrying information that paper could not easily hold.

Enterprise-system integration determines how much of that promise survives. When the signal reaches planning, purchasing or the shop-floor execution system, teams can work from the same demand signal rather than reconciling separate spreadsheets and status calls. When integration is partial, a screen may display information entered by hand. That creates two records of reality unless confirmation rules, identifiers and escalation paths are designed carefully.

Researchers must also distinguish speed from reliability. An apparently live dashboard may still rely on batch updates, manual confirmation or a scanner that operators cannot use at the point of work. Volvo-related work is available alongside the wider evidence on digital visual planning and lean enterprise systems in Celean’s research publications. These sources support the operational reading of the case without requiring a universal performance claim.

Visibility, exceptions and local limits

A well-populated board can still produce poor decisions. People scan what is visible, while the task requiring attention may sit outside the normal workflow. During a machine changeover, a quality quarantine or a staffing gap, a priority field matters less than a clear route to resolution. The digital board succeeds when it highlights exceptions and supports the next responsible action; otherwise, it can become a cleaner version of a cluttered wall.

Australian shopfloor language illustrates that gap. A team in Melbourne may call for a “material call” and describe an unresolved quality item as being “in quarantine”, while a colleague reading the same screen may look for “replenishment” and “hold”. These expressions need not become software requirements, but designers should test the words used during handovers. At a supplier in regional Victoria, a simpler interface may matter more than a richer dashboard.

The local system landscape adds another constraint. Many Australian manufacturers run SAP or Oracle systems alongside production software, spreadsheets and supplier portals built for a particular plant or customer. A new board may need to translate between them instead of replacing them. Data ownership then becomes operational: purchasing may know why an order moved, while production knows why a line stopped and a planner knows why a signal was deferred.

Adoption was an operating change

The transition worked as a change in work, not an installation. Operators needed to know what happened after a signal, when a physical card still had authority and how to challenge a status without creating a parallel record. Team leaders had to adjust daily meetings that had been organised around walking to the board. Supervisors needed reliable access to the same view, including when a screen failed or a device became unavailable.

That last point explains why hybrid arrangements can be sensible. A physical conversation may still be the fastest way to resolve uncertainty, while the electronic record supplies shared context and a trace of the decision. Sharing improvements with users also matters. Regular audio briefings can reach shift workers without recreating a formal meeting; the Ubuntu Podcast offers an example of specialist software discussion presented in an accessible, conversational format.

Training in Australia must account for distance, rosters and variable connectivity. A supervisor in regional Queensland may receive the same system as a colleague in Melbourne, but have fewer opportunities for informal support. Pilot sessions should include the people who enter data, not only those who design workflows. Where employees are represented, consultation on monitoring, performance measurement and device use can prevent the electronic board from being perceived as a tool for surveillance.

A practical adoption sequence

Australian teams should copy the operating principles rather than the screen layout. A small pilot can test whether the electronic signal improves decisions while preserving a clear path for exceptions.

• Choose a decision-led pilot: limit the scope to sequencing, replenishment signals or exception escalation rather than displaying every enterprise-system field.
• Establish a baseline: record current lead times, stock buffers, manual touches and unresolved signals before changing the workflow.
• Define event ownership: state who raises, confirms, queries and closes each Kanban movement, with authority to reject inaccurate data.
• Design a credible exception path: make missing material, quarantine and machine downtime visible outside the routine board, with named escalation roles.
• Test the data exchange: document identifiers, update frequency and failure handling between the board, ERP, stores and suppliers.
• Include adoption in the pilot: fund operator training, device access, agreed safety expectations and measures of practical usefulness alongside speed.

These steps make the pilot assessable and reversible. They also separate a useful digital signal from a system that merely moves the waiting to another queue. The physical board, where retained, should have a defined role rather than become an unofficial duplicate.

The next operating test

Volvo’s case is strongest when read as a lesson in coordination. Electronic Kanban can shorten the route between an event on the line and the response required elsewhere, while preserving the lean discipline of limiting work in progress. It cannot decide which exception deserves attention, repair an unreliable supplier process or replace local knowledge. Those responsibilities remain part of the operating system.

The case also cautions against generalising from a well-supported manufacturer to every workshop. Australian firms may have fewer resources for system integration and more variation between sites. Their advantage can be a shorter distance between decision-makers, provided the chosen signal and the governance around it are precise.

For an Australian pilot, the concrete next step is a scheduled ninety-minute review with production, materials and maintenance, using three weeks of records to compare signal response, manual handovers and unresolved exceptions against the baseline.