Teaching lean through interactive digital visual tools

Lean concepts are easy to name and difficult to feel. A class may correctly define value-stream mapping, Kanban, standard work and work-in-process, yet learners still struggle when they must decide which job to release next. Teaching lean concepts through interactive digital visual tools closes that gap. Instead of looking at a static diagram, participants move cards, change capacity, test a policy and watch the consequences appear on a shared board.

That immediacy matters because lean is a way of coordinating work, not simply a collection of techniques. A digital Kanban board can make a pull system visible: a limit becomes a queue, a blocked card becomes a conversation, and a change in cycle time becomes evidence for reflection. The exercise works best when the screen supports a real decision and a facilitator asks learners to explain it. This is the central concern of Celean, the Chalmers Electronic Lean Research Team, a collaboration between Chalmers University and industry partners that studies visual planning, enterprise systems and lean processes.

For Australian learners, the exercise can be grounded in familiar operating conditions. Melbourne’s automotive, manufacturing and logistics networks, Sydney’s construction and professional-services projects, and Perth’s mining operations all involve handoffs, interruptions and changing priorities. A board designed in a university seminar should therefore allow for dispersed teams, varying digital confidence and the practical constraints of shift-based work. The technology is valuable when it makes those realities easier to discuss, not when it pretends every workplace has unlimited connectivity.

Seeing the system instead of memorising the rule

Visual management turns an invisible coordination problem into an object that a group can inspect. Cards reveal queues; swimlanes expose handoffs; colour coding can distinguish status, risk or ownership. In a lecture, these elements are symbols. In an interactive session, a facilitator can place a card in a lane and ask what happens next. The question shifts from what does the symbol mean to how should the team respond now.

Digital tools add a time dimension. Learners can advance a scenario, inject an absent worker, reduce capacity or deliberately create a batch, then compare the outcome with the baseline. The evidence supports discussion of flow, utilisation, starvation and prioritisation without requiring a production line in the room. It also allows teams to test a policy across several conditions rather than defending one preferred answer.

Research into digital visual planning at Celean connects these teaching designs with studies of enterprise systems and lean processes. Collaboration with industry partners, including Volvo, provides a way to compare an academic model with operational constraints. The prototype is not a slick software demonstration; it is a thinking environment in which assumptions about work can be made explicit, challenged and revised.

Designing an interactive learning sequence

A strong session moves from diagnosis to decision to reflection. Participants first map the current value stream, identifying delays, rework and information gaps. They then work with a simple digital board whose rules represent the process being studied. Finally, they compare proposed changes with the original map and explain which measure or signal changed. This keeps the activity anchored in lean thinking rather than turning it into a contest to operate the interface.

The learning design can include:

• Use a value-stream map to expose delays and unsupported assumptions.
• Give each role a Kanban board with explicit WIP limits and pull signals.
• Prepare scenario cards for capacity loss, urgent work and blocked handoffs.
• Compare results through a shared view of cycle time, throughput and flow efficiency.

The facilitator should use open prompts rather than a single correct route: Why was this card released? Which constraint has priority? What would happen if the downstream stage failed? Recording answers creates an audit trail for comparison, while the live board keeps attention on the system. It also gives learners practice in respectful, evidence-based questioning, a skill that matters in a meeting room as much as on a shop floor. A resource such as visual planning examples can be used to prepare contrasting situations.

Kanban, flow and the visible workplace

Kanban is especially effective as a teaching system because it links a visible signal to a rule. Work-in-process limits show why starting more work can lengthen a queue. A pull policy shows why downstream need should influence upstream release. Cards can add context that a spreadsheet alone hides: customer priority, acceptance criteria, dependencies, age and the reason for a delay. In a classroom, participants can see how missing information becomes a source of variation.

The same logic applies to visual project management beyond manufacturing. A service team can use cards for cases, requests or intake activities, while a project team can represent approvals, design reviews and site handovers. The board should retain the vocabulary of the work; a generic task list makes it easier to teach click mechanics but harder to understand flow. Australian offices often combine physical whiteboards with Microsoft Teams, SharePoint and other enterprise systems, so the learning should address how a visual layer relates to existing records.

Metrics should remain subordinate to learning. Cycle time, lead time, throughput, WIP and flow efficiency can help a group notice effects, but a dashboard that rewards moving cards quickly teaches the wrong behaviour. The useful question is what changed, for whom and why. A card that remains blocked may reveal a broken handoff, whereas a fast-moving card may conceal rushed work or a temporary workaround. Facilitation should keep both possibilities open and turn them into subjects for continuous improvement rather than individual scores.

From simulation to everyday practice

An interactive exercise has value only when participants can carry its reasoning back to work. A pilot can use one real process slice, such as engineering changes, maintenance requests or project approvals, rather than modelling the entire organisation. The facilitator and a process owner can agree on a starting condition, a small set of rules and a period of observation. Learners test changes in the tool and compare the predicted effect with what actually happened.

Digital visual planning should connect with, rather than duplicate, enterprise systems. Where an ERP already stores status, the prototype can use a lightweight data layer or import so learners focus on flow rather than data entry. That distinction matters in Australian organisations with established Microsoft 365 and engineering software environments, as well as smaller suppliers with fewer integration resources. The tool can teach when a board is a source of truth, a coordination view, or a prompt for a meeting where ambiguity still needs human judgement.

Access is part of the pedagogy. Before a session, test a representative phone, tablet and shared display rather than assuming the seminar room is the only environment. Reviewing how the mobile access reference presents on a smaller screen can show what a learner sees before the session. In remote and regional settings, prepare screenshots, printable cards and an offline discussion so participation does not depend on a fast connection.

Making the exercise fit Australian work

Local context should shape the scenario, terminology and measures. Melbourne is a useful setting for discussions about automotive supply chains, port-linked logistics and mixed office-and-site coordination. Sydney adds construction, professional services and organisations juggling client approvals with distributed project teams. Perth and the Pilbara provide a contrasting case of shift-based, fly-in-fly-out work, where handovers and visibility across time zones are central. These workplaces are not interchangeable, but they offer distinct cases for the same lean questions.

A useful Australian adaptation might include:

• Set Melbourne scenarios around supplier delays, production and distribution priorities.
• Show Sydney project teams balancing approval queues, site information and client changes.
• Make Perth shift handovers and equipment constraints visible.
• Recognise AS/NZS practices, ISO management systems and mixed digital maturity across Australian sites.

Standards and work practices should be part of the scenario, not decorative background. Many Australian operations combine AS/NZS guidance with ISO management systems, while procurement, labour availability and project tempo can change the assumptions behind a policy. Give learners constraints that resemble local decisions: an approval waiting on a client, a technician travelling between sites, a supplier meeting a delivery window, or a handover at the end of a shift. The board can also model familiar workplace customs, including short stand-ups, visible escalation and decisions recorded where the next shift can find them.

A concrete first step for educators

Start with a narrow question rather than a large software project. Choose one workflow in which a learner can identify a queue, a handoff and a rule for releasing work. Build a small board around that workflow, include a card with missing information, and ask participants to make one change under a stated constraint. The learning objective should be observable: participants should explain how the change affects flow and identify the evidence they would monitor.

Invite an operations partner to co-design the scenario and review the artefacts after the session. The Project Visit research hub provides a starting point for exploring Celean’s research publications, prototype software and industry collaborations, including work connected with Volvo and other organisations. Comparing what the board suggests with a real operating pattern is more instructive than evaluating the elegance of the interface. Keep the first cycle small enough to revise the scenario, measures and facilitation prompts.

The next step is to schedule a 45-minute pilot with one cross-functional team, one real workflow and one digital Kanban board, and use it to capture three observations: where participants hesitated, which question improved understanding, and which measure changed after the intervention.