Plants cannot be rolled back like a bad release, and the people who carry institutional knowledge cannot be rehired at speed. An essay on what makes industrial transformation different, and on the moment Central European industry is now in.
Industry does not transform like software
An industrial transformation is constrained by physics and by people long before it is constrained by software. A production line has a unit cost of downtime that no software company ever faces. Legacy systems are not technical debt in the abstract: they genuinely run the plant, today, and the institution's knowledge of why they are configured the way they are often lives in a handful of people approaching retirement. Replacing the system without first securing that knowledge does not modernise the operation so much as quietly remove its memory of itself.
This is why programmes designed at headquarters speed get rejected at plant speed. The boardroom experiences the transformation as a roadmap, while the floor experiences it as a request to abandon tools that work, mid-shift, on the word of people who have never stood next to the machine. Both experiences are rational, and a transformation that has no honest translation between them will only produce dashboards at the top and parallel spreadsheets at the bottom, which amounts to no transformation at all.
The Central European moment
Polish and Central European industrial groups are in a specific and demanding position. Decades of competitiveness built on operational excellence now have to carry multi-country platform modernisation, technology functions that are scaling faster than their governance, and tariff and supply-chain disruption that demands operational redesign on timelines the org chart was never built for. The pressure is real, and so is the opportunity: the groups that get the sequence right will consolidate their position while their competitors are still reconciling ERP instances.
A representative engagement from our practice: a legacy industrial group whose strategy had outrun its systems, re-platforming operations across seventeen countries, with new internal and external communications built alongside the technology rather than after it. The lesson worth generalising has little to do with the platform that was chosen. It is that the modernisation held because the operating model and the communication changed alongside the systems rather than after them.
Growth that is planned rather than suffered
Unplanned growth is indistinguishable from chaos, except that chaos is cheaper. Growth that is not built on a clear understanding of what the organisation can actually absorb, operationally, culturally and financially, simply creates fragility at scale. The ambition behind it is rarely the problem; the sequence in which it is pursued almost always is.
Planned growth means knowing what has to be true before you expand: which capabilities are genuinely load-bearing and which are decorative, who carries the institutional knowledge that cannot be replaced at speed, and what you will deliberately not do, because the constraint is always real, and pretending otherwise does nothing to remove it. In the current environment, securing the core is less an act of caution than a genuine strategic choice: an organisation that has protected its core people, its core capabilities, and its financial resilience keeps its options open, while one that chased growth without that foundation quietly runs out of them.
Where to begin is usually not a mystery. It is a transformation audit: the processes as actually performed, the stack as actually run, and the distance between the stated strategy and what the plants are doing on a Tuesday.
Q: What does digital transformation mean for a manufacturer?
Far less an IT project than the redesign of how the plant, the supply chain, and the boardroom come to share one version of reality: platforms and data, certainly, but held together by an operating model the workforce actually adopts. A manufacturer has transformed when the floor trusts the system enough to stop keeping the old spreadsheet running in parallel.
Q: Why do industrial programmes stall more often than others?
Because the distance between the boardroom and the plant floor is physical, not just organisational. Decisions travel through more layers, legacy systems genuinely run the production line, and downtime has a unit cost that software companies never face. A programme designed at headquarters speed will be rejected at plant speed.
Q: How should a group sequence a multi-country modernisation?
Ground truth first: the processes as actually performed, the stack as actually run, and the unofficial tools each country adopted because the official ones failed them. Then one real step at a time, knowing in advance what has to be true before the next country is brought on. Rolling out everywhere at once tends to be less a sign of ambition than of risk that has not yet been examined.
Q: How do tariffs and supply-chain disruption change the priority?
They compress the timeline for operational redesign below what most governance structures were ever designed to handle, which is what turns resilience of the core into the strategic choice rather than the merely cautious one. Protect the people, the capabilities, and the balance sheet that give you options, and then redesign from that position.
Q: How does Jigen work with industrial companies?
Engagements are led by a senior practitioner with direct operating experience in Polish and Central European industrial environments as well as Japanese and American ones. The work spans the boardroom and the plant floor in the same engagement, is scoped to a defined outcome, and is never delegated to junior analysts.