Lessons from Chalmers University’s Collaboration with Industry on Lean Tools

Lean management is often presented as a set of techniques: Kanban boards, daily meetings, workflow limits, standard work and performance dashboards. Chalmers University’s collaboration with industry offers a more useful interpretation. The value of a lean tool depends on how well it fits the work, the people using it and the decisions that need to be made. A board can improve flow, or it can become another reporting burden.

The work associated with the Chalmers Electronic Lean Research Team, known as Celean, sits at the meeting point between academic research and operational practice. Its focus on digital visual planning, project management, enterprise systems and lean processes is especially relevant to Australian organisations, where manufacturers, construction firms, hospitals, logistics operators and public agencies are managing dispersed teams and complex supply networks.

Treat tools as part of a working system

The first lesson is that a tool should support a management system rather than stand in for one. A digital Kanban board may display tasks clearly, yet it cannot decide which work has priority, identify why jobs are blocked or create agreement between engineering, procurement and production. Those decisions require shared rules and regular conversations.

This distinction matters when an organisation moves from a physical board to software. A paper board in a Melbourne workshop may make unfinished work visible to everyone passing through the area. A cloud platform can extend that visibility to a design office in Sydney, a supplier in Geelong and a project manager working from home. The digital version is useful only if the underlying workflow, ownership and escalation practices remain clear.

Research-led industry collaboration helps expose these assumptions. Instead of asking whether a particular application is modern enough, teams can ask what information workers need, when they need it and which decisions the information should support. That approach prevents the common mistake of digitising an unclear process.

For Australian businesses, the choice also has practical consequences. Many small and medium-sized manufacturers operate with limited improvement staff, while larger organisations may have several enterprise systems acquired by different departments. A lean visual tool has to connect with existing systems without forcing every employee to become a data administrator.

Make work visible without creating surveillance

Visual management works because it turns invisible work into something a group can discuss. It shows queues, dependencies, bottlenecks and completed tasks. It can also reveal that a team is overloaded long before a missed delivery becomes a customer complaint. In this sense, visibility is a basis for learning rather than simply a way to measure effort.

The risk is that visibility becomes surveillance. If every card is interpreted as evidence of an individual’s productivity, people may split tasks into artificial pieces, hide problems or avoid taking on uncertain work. A sound system concentrates on flow, quality and obstacles. It asks why work is waiting, not which person can be blamed for the delay.

That principle is important in Australian workplaces shaped by consultation requirements and health and safety obligations. Under state and territory work health and safety laws, employers must manage risks and consult workers about matters that affect their health and safety. A new digital workflow that changes workloads, screen time or job control should therefore be discussed with employees and health and safety representatives, not imposed as a neutral software upgrade.

A useful visual board includes a small amount of information that people trust. It might show the customer need, responsible team, current stage, ageing work and next decision. Colour coding should have an agreed meaning, and blocked work should trigger assistance rather than embarrassment.

Combine academic evidence with operational judgement

A university–industry partnership creates a productive tension. Researchers can examine patterns across projects, test concepts and challenge assumptions. Industry partners bring constraints that cannot be reproduced in a classroom: customer deadlines, machine availability, industrial agreements, supplier delays and the pressure of a live order book.

The best collaboration treats the workplace as a source of evidence. Prototypes are tried in real settings, users explain where they struggle and the design is adjusted. This cycle is more valuable than selecting a fashionable framework and declaring a transformation complete. The aim is to learn which behaviours help work move and which features merely decorate the system.

Organisations studying the background to these methods can explore the team’s research publications, where academic and applied work provides a stronger foundation than isolated case-study claims. The important question is not whether a tool worked somewhere else, but which conditions made it useful and which elements can be adapted.

Australian firms should allow for local variation. A high-volume automotive supplier in Melbourne may need detailed production control, while a resources contractor in Perth may coordinate maintenance across fly-in fly-out rosters. A Brisbane construction project may depend on weather, subcontractor availability and safety permits. The same visual principle can serve each setting, but the board structure and meeting rhythm will differ.

Design for the rhythm of Australian work

Lean tools become credible when they fit everyday habits. A short stand-up before the first shift can work well in a warehouse, while a distributed engineering team may need an online review that accommodates flexible hours. Australian organisations commonly span multiple time zones, particularly when head offices, mines, ports and suppliers are spread across the country. A meeting schedule that works in Sydney may be inconvenient for Perth.

Local market conditions also influence the design. Australian manufacturers often manage long replenishment lead times, imported components, small production runs and exposure to currency or freight changes. A Kanban signal must account for those realities. Reducing stock blindly can create expensive shortages when replacement parts take weeks to arrive. Visual controls should distinguish healthy buffers from excess inventory.

The same caution applies to service organisations. Hospitals, councils and utilities have variable demand and strict obligations around records, privacy and continuity. A digital planning system should collect only the information needed for the work and should apply appropriate access controls under the Privacy Act 1988 and relevant organisational policies. Integration with payroll, customer or patient systems needs careful governance.

Practical experimentation is easier when teams define a small operational question. They might test whether limiting active design jobs reduces engineering rework, whether a daily replenishment signal improves parts availability, or whether an ageing-work indicator helps supervisors intervene earlier. A short trial with agreed measures is usually more informative than a large software rollout with vague expectations.

Turn lessons into repeatable improvement

A collaboration with industry produces lasting value when the learning is captured in routines. Teams should record what changed, what evidence was collected and what decision followed. This does not require lengthy reports. A brief experiment log, annotated board history or review note can preserve the reasoning behind a process and help new staff understand it.

Improvement should also be connected to commercial and human outcomes. Delivery reliability, lead time and work-in-progress matter, but so do rework, safety, training time and employee control over difficult tasks. Australian employers must account for the Fair Work Act 2009, modern awards and consultation arrangements when changes affect roles, hours or responsibilities. Lean improvement is stronger when it respects those conditions from the beginning.

The following practices help translate research and pilot work into day-to-day management.

Practices that strengthen a lean visual system

• Define the decision each board, report or dashboard is meant to support.
• Limit work in progress according to capacity, risk and customer urgency.
• Give blocked work a clear escalation path and an owner for the next action.
• Review the system with the people who use it on the factory floor or job site.
• Measure flow, quality, safety and learning rather than individual busyness.

A mature organisation treats the tool itself as something that can be improved. Columns may change when the work changes. A metric may be removed if it produces gaming or no longer informs a decision. New software features should be judged by whether they reduce friction and improve understanding, not by how many functions they contain.

Build trust across organisations and disciplines

Industry collaboration often crosses boundaries between university researchers, software developers, managers, operators and external suppliers. Each group sees a different part of the process. Operators know where information becomes unreliable, managers understand commercial constraints, researchers can test explanations and developers translate requirements into usable interfaces.

Trust grows when these perspectives are recognised as complementary. A prototype should be explained in plain language, and feedback should be treated as data rather than resistance. Industry partners also need clarity about what can be shared publicly, how business information is protected and how research findings will be reported.

This approach is relevant to Australia’s project-based economy. A major infrastructure programme may involve a principal contractor, specialist subcontractors, government clients and communities. If each organisation uses a different definition of complete, priority or delay, a shared dashboard can create the appearance of coordination without the substance. Common terms and agreed review points are more valuable than a highly visual interface.

External examples can broaden the conversation. Materials such as movement-focused examples can prompt discussion about how visual information guides behaviour in settings beyond a conventional factory. The transferable lesson is to examine how people interpret signals and act on them, then adapt the idea to the operational context rather than copying its surface design.

A practical collaboration model can be organised around a small set of shared commitments:

Questions for an industry–university pilot

• Which operational problem is important enough to study and small enough to test?
• Who performs the work, and whose knowledge is missing from the design?
• What information can be shared safely under privacy, security and commercial rules?
• Which measures will show better flow without encouraging unsafe shortcuts?
• When will the partners review evidence and decide whether to adapt, stop or scale?

The most useful lesson from Chalmers University’s collaboration with industry is that lean tools are social and technical at the same time. Digital planning, Kanban and enterprise systems can make work easier to coordinate, but only when they are grounded in real workflows, respectful consultation and continuous learning. For an Australian organisation, the practical starting point is a small visible problem, a cross-functional group and a simple tool that helps people make a better decision every day.