The process side of mechanisation

This article is the third instalment in our series on mechanisation. In the previous parts we explained why technology alone isn’t enough. Here we share our observations from clients where mechanisation initially failed to deliver on its promises — with the focus on the process side.

More and more companies are investing millions in mechanising their production or distribution. Expectations are clear: lower costs, higher quality and scalability. The technology itself is promising. Yet the promised returns often fail to materialise. At many companies where we were involved, we saw expectations go unmet, despite substantial investment.

Instead of calm and predictability, unrest takes hold on the floor. Processes stall, output falls short and confidence in the new way of working evaporates. One of the causes: the processes were not adapted enough along with the technology.

What changes in the process after mechanisation

In the old situation, departments operated largely independently. Physical handovers, printed lists and visual control provided guidance. Operators could literally see what was coming and act on it themselves. The work rhythm was driven by visual signals, personal experience and informal coordination.

In the mechanised setting, those familiar reference points disappear. Semi-finished products arrive automatically, interdependencies between departments increase, and progress is visible only on digital screens. This demands new skills from employees, but also a different kind of collaboration and information exchange.

Scanning becomes the new language of the process. But too many scan points overload the system: in the quest to make everything measurable, the work actually slows down. A single missed scan can block an entire production flow. That makes the system fragile and the work frustrating for operators.

Process control in a mechanised environment

Mechanisation radically shifts the demands on control. Where the operation used to be controlled locally, central coordination is now required. Planning departments used to long-term planning are often not equipped for the real-time steering that is now needed. This creates a vacuum in operational control.

In that vacuum, teams revert to familiar patterns: ad hoc decision-making, firefighting and improvisation. Without clear KPIs and central orchestration, the overview fades. Departments revert to optimising their own part, resulting in sub-optimisation across the chain.

Escalations become unstructured. Who makes decisions when there is a disruption? What happens if a system glitches or a buffer overflows? Often there are no procedures and no clear overview. Control slips away, and employees lose trust in the system.

Processes under pressure: the non-happy flow

Designing for the ideal situation is understandable — but risky. Every operation has deviations: products that fail to meet specifications, systems that freeze, tasks that do not go as planned. That non-happy flow is often not sufficiently accounted for in the process design. At several clients we have seen how precisely these exceptions put the entire system under pressure when they were not included in the design.

Mechanisation makes this even more painful. Deviations that used to be solved with a minor fix now clog up the entire system. Buffers fill, processes block, and output drops faster than expected.

The cause often lies in poor data validation at system entry. Incorrect labels, incomplete information or misclassified flows trigger errors that cannot easily be corrected downstream. Without clear routing between main and secondary flows, contamination and loss of control follow.

Process design that does work: rhythm, orchestration and realism

Embed orchestration in new control processes. Set up a control room that interprets real-time data, spots deviations and intervenes. Not remotely, but embedded in the operation. The control room monitors the rhythm of the factory and acts as the central brain for planning, escalation and performance.

Design processes for end-to-end flow, not departmental optimisation. Use shared KPIs such as flow speed, and create clear handover points between departments. Think in terms of flow and availability, not just capacity per line.

Automate behaviour through process rules. Replace implicit knowledge on the floor with defined scenarios and automated triggers. Prioritise system hygiene: robust data checks at intake prevent contamination at the source. Define how exceptions are identified, handled and fed back.

Treat collaboration and escalation as a system process. Define who takes action for each type of incident, keep the tools simple, and establish recurring coordination with external service providers. Be ready for the unexpected by rehearsing disruption scenarios.

Monitor what really matters. Choose KPIs that link process and outcome, and make sure dashboards drive action. Use scanning for transparency, but avoid overkill: too many scans make the system slow and error-prone. Measure to steer, not to document.

Our approach in practice

Organisations often call on us when mechanisation does not deliver the desired result. Despite large investments, performance lags, unrest grows on the floor and the awareness sets in that more is needed than technology alone.

Our approach begins with understanding the full picture. We identify precisely where things are stuck — in systems and processes as well as in the collaboration between teams. Not through lengthy analyses, but with direct observation and data analysis on the floor. This becomes the starting point for a clear, phased improvement plan.

Next, we work with and within the organisation. We form an improvement team, help redefine roles and responsibilities, and make sure progress stays visible and open to discussion. We begin where the biggest difference can be made and expand from there.

Implementation is practical and focused. Together with the people involved, we improve tangible processes, make dashboards usable, bring structure to steering and make sure people take ownership. In parallel, we build in sustainability — through training, standards and a culture of learning and improvement.

Conclusion: process improvement as the key

Mechanisation is not the end point — it is a new beginning. The real challenge lies in redesigning processes, installing the right orchestration and building a culture in which technology, people and control come together. Companies that approach this as an integrated transformation don’t just achieve the promised return — they build an agile operation ready for growth and change.

In the end, it’s not the technology that makes the difference — it’s how you work with it.