For three years, a high-tech, fully digital paper converting machine had been producing roughly 50% of what it was designed to deliver. Running hours averaged just 53%. Downtime was absorbing nearly half of every operating day.
The investment had been significant. The expectation was that this machine would become the flagship asset. Instead, it had become the one that leadership could not explain at board meetings. The people closest to the machine could see the potential, but every attempt to close the gap ran into the same wall: inconsistent routines, unclear priorities, and a planning process that could not keep up with the complexity of the operation.
The Machine Was Not the Problem
When we started working with this team, most of the internal conversation was centred on the machine itself: its settings, its maintenance schedule, its technical specifications. But when we looked at the operation as a whole, we saw something different. The machine was capable. The system around it was not.
There was no integrated schedule connecting the converting line to upstream and downstream processes. Performance measures meant different things to different people. The real constraint was not mechanical. It was operational: the absence of a coherent operating rhythm connecting planning, execution, and review.
That reframe changed the scope of the engagement. This was not a machine improvement project. It was an operating model redesign.
We worked across three connected workstreams. The first was a rapid improvement sprint: four weeks to baseline performance, map constraints, and implement the highest-impact interventions. This gave the team early momentum and gave leadership visible proof that the approach was working.
The second was the full operating model. We redesigned how work was validated, planned, scheduled, resourced, and executed. We defined levels of work for each role, built an integrated scheduling workflow, and introduced structured management routines to surface issues early and keep the schedule on track.
The third was skills and capability development. Using an experiential simulation, we put the team through a compressed version of the same operating challenges they faced on the floor. When people could see how their individual decisions rippled through the value chain, the resistance to changing old habits dropped. They were not being told to work differently. They were discovering for themselves why it mattered.
We did not design any of this in isolation. The team was in every workshop, every design session, every review.
The rapid improvement sprint reduced operational delays on the highest contributing downtime categories by more than 50% within the first month. The shift structure was redesigned to eliminate overtime, reducing labour costs per hour by approximately 47% and cutting production cost per unit by roughly 33%.
The operating model drove the deeper shift. Saleable tonnes approximately doubled. Variability dropped dramatically. The machine moved from erratic output to consistent daily performance at a level the plant had never previously achieved.
The most significant change was in the team. Operators who had been working around a broken system were now working within one they understood and had helped design. When we stepped back, the system did not revert. The routines held. The line continued to perform.
When a high-value asset is underperforming, the instinct is to look at the asset. But in most cases, the asset is not the constraint. The operating system around it is.
This machine was always capable of delivering what was asked of it. What it needed was an organisation that could plan, schedule, resource, and execute with enough clarity and discipline to let it perform. The question for any manufacturing leader whose most important asset is not delivering: have you looked at the machine, or have you looked at the system around it?
