amer.catic@projectvisit.org dagb@projectvisit.org +46 31 322 7207
PV Project Visit

When lean research crosses borders

International collaboration in lean research projects asks researchers, suppliers and operators to learn across institutional and national borders. The work is technically demanding: visual management cards, Kanban policies, enterprise-system rules and lean experiments must be interpreted by people who may use the same words for different practices. A pull signal that appears routine in a Swedish production network can acquire a new meaning in an Australian worksite, where shift structures, outsourcing patterns and expectations about workplace voice differ.

Project Visit, the publication home of the Chalmers Electronic Lean Research Team, or Celean, provides a useful setting for this challenge. Its publications, prototype tools and industry collaborations—including work involving organisations such as Volvo—show how method development depends on people, place and organisational context. Cross-border teams benefit when they treat translation as a research capability rather than assuming that a board, standard or software licence already contains a universal practice.

Shared meanings travel more slowly than tools

Lean language compresses complicated judgements into memorable labels. “Lead time”, “flow” and “standard work” can sound self-explanatory until a researcher asks who owns the work, which exceptions are legitimate and how performance is recorded. A card that travels from a Swedish supplier to an Australian distributor may also travel from one enterprise system to another, carrying assumptions about identifiers, planning horizons and acceptable evidence. Shared vocabulary is therefore a negotiated artefact, not merely a glossary delivered at kickoff.

Culture influences what counts as a reasonable instruction. Swedish teams often rely on consultation, consensus and technically detailed discussion, while Australian workplaces may combine open informal conversation with strong expectations about pace and autonomy. Both settings include diverse teams; an Australian partner may also bring multilingual supervisors, remote workers and operators from several generations into the same improvement activity. The safe approach is to test meanings through shop-floor examples, ask people to demonstrate the process, and record where shared terms conceal different priorities.

Power differences can remain hidden even when language is shared. An international research team may be invited to improve a process while frontline staff carry the burden of the trial. Suppliers can also fear that efficiency data will become leverage in a commercial negotiation. Australian industrial settings add local complexity through enterprise agreements, site-based health and safety duties and the participation of workers’ representatives. These arrangements differ from Swedish joint consultation structures, so a project that looks consultative in one country can feel extractive in another.

Distance changes the rhythm of research

Sweden and Australia occupy opposite sides of the world, and the time difference shapes even simple research administration. A 9 a.m. meeting in Gothenburg falls at about 4 p.m. in Perth, 5:30 p.m. in Adelaide and 6 p.m. in Sydney during common offset periods, with daylight saving changing the equation. Melbourne workshops scheduled for late afternoon can exclude eastern states or place experienced operators at their limit. Meeting invitations must state the local time, rotate the burden of late attendance and protect time for informal discussion that does not fit a formal agenda.

Fieldwork makes geography more concrete. A delegation visiting northern Tasmania must plan transport, regional supplier networks, local contacts and evening debriefs. A directory of Launceston hospitality venues can support catering logistics, yet hospitality remains context rather than evidence: interviews belong in agreed settings, and an informal social venue should not be mistaken for a production site. For partners in Newcastle, Wollongong or Perth, reaching a host plant may also mean a full day of travel, turning a two-hour observation into a multi-day commitment.

Distance can nevertheless improve the research if it is designed for it. Short, recorded demonstrations can be paired with live workshops so that a visual issue is seen before it is debated. Shared digital boards can expose differences between the planned workflow and the actual one, while a rotating meeting time can prevent one region from becoming the default centre of the partnership. The key is to treat coordination as part of the method and budget for it, including facilitators, translation, travel, connection reliability and follow-up.

Digital systems must negotiate different realities

Kanban may look like coloured cards on a wall, but its rules carry an industrial history. The Project Visit account of Kanban’s Swedish history traces the adaptation of Toyota’s production method through Swedish industry and Chalmers research. For international teams, that history is a reminder to study the socio-technical system around a tool. A digital Kanban board should reveal queues, ownership and exceptions, rather than merely reproduce a tidy card layout imported from another organisation.

Enterprise systems add another layer. A host using an established ERP may need fields and permissions that differ from a university prototype, while a small Australian supplier may run on spreadsheets, paper travellers and accounts packages with limited integration. A visual planning concept must therefore be tested against actual master data, supplier records, shift calendars and audit requirements. Translating labels is not enough: identifiers, status definitions and decision rights must also agree. Otherwise, a visually elegant board can create two versions of operational truth.

Research data creates further obligations. Digital visual planning can include photographs of work areas, employee identifiers, performance measures and video used for time-and-motion analysis. Moving such material between Sweden, the European Economic Area and Australia raises questions about consent, storage location, retention, disclosure and research ethics. Swedish and Australian organisations may apply different privacy expectations and internal review practices, while industrial partners can impose stricter confidentiality rules than either legal regime. A shared data-governance plan should identify a lawful route for each dataset before fieldwork begins.

Markets, ownership and evidence need alignment

The business case for lean must also travel. Evidence on visual management economics can help partners assess time savings and return on investment, but those figures depend on labour costs, line balancing, inventory patterns and how interruption is priced. A two-minute retrieval saved on a high-volume automotive line in Sweden may matter less than a five-minute delay at a remote Australian mine maintenance bay. The relevant metric is therefore not the impressive average, but the effect within the host market and operation.

Australian supply chains provide a particularly clear example. The country combines large mining and resources operations with regional manufacturers, automotive suppliers and small firms that may lack enterprise support for complex pilots. Long travel distances, remote sites and a smaller pool of specialist consultants can change what an improvement team can implement and maintain. Imports add logistical friction: physical demonstration cards, sensors or prototype equipment may require commercial documents, customs clearance and Australian GST treatment. Partners should test the total operating consequence, not assume that a proven configuration remains cheap once it reaches a local market.

Commercial and research interests can diverge over publication, tooling and ownership. A supplier may want a visual system protected, an operator may want practical control, and a university team may need to publish findings that expose the wider method. Funders can also expect transfer between partner countries, while host companies may see the collaboration as market development rather than open research. Clear agreements on foreground intellectual property, confidential results, prototype licences and attribution reduce conflict. Consultation with unions, suppliers and works councils should be planned as data collection and governance work, not left until the end when findings are difficult to change.

A working protocol for international lean studies

A workable protocol begins with a shared purpose, local decision rights and named owners for research, industrial change and data. The team should document what must remain consistent across sites, such as the definition of a validated lead-time event, and what may be adapted, such as card layout, shift terminology and escalation routes. This protects comparison without pretending that a common metric makes two workplaces identical. It also gives local experts authority over how the method is enacted.

The following practices keep the collaboration inspectable and usable across borders:

These practices should be reviewed after each site visit. The team can compare whether the visual tool was used, whether participants understood the rule, whether they changed the work and whether they retained that change after the research team departed. That distinction matters for transfer: uptake proves adoption, while sustained behaviour and measurable flow gains provide stronger evidence that the intervention has become part of local lean practice.

International lean research is strongest when uncertainty is made visible. The method, the evidence and the divisions of responsibility should be clear enough for a partner in another country to challenge them, reproduce them and adapt them without erasing local practice. The lesson to remember is that a successful cross-border project does not export a finished idea; it builds the shared capability to interpret, test and refine an idea across industrial systems.