.png){kind=logo}
There is a dangerous moment in any manufacturing transformation project.
It is the moment everyone starts celebrating.
The new MRP system has gone live. The automation is installed. The new process has been launched. Training has been completed. The project plan says everything has been delivered.
It feels like the finish line.
But it isn't.
One of the easiest mistakes to make in transformation is to confuse delivering the project with changing the business.
A useful way to think about it is:
Delivery → Adoption → Outcome
All three matter. But they are not the same thing.
Delivery tells you whether the project happened
Most businesses are relatively good at measuring delivery.
Did the system go live on time? Was the new equipment installed? Did people complete the training? Were the milestones achieved?
These are sensible questions. If you are spending significant amounts of money on a transformation programme, you need to know whether it is being delivered properly.
The problem comes when those measures are also used as evidence that the transformation has succeeded.
A system being live tells you that a system is live.
It doesn't tell you whether people are using it properly, whether the new process is working or whether the business is performing any better.
That's where adoption comes in.
Adoption is about what people actually do
Forget the project dashboard for a moment and look at what is happening inside the business.
Are people using the new system without being chased?
Are managers making decisions using the information it provides?
Or have they quietly returned to their own spreadsheets?
Are operators following the new process, or have unofficial workarounds started to appear?
Perhaps most importantly, are people starting to suggest ways the new system or process could be improved?
One of the most encouraging questions you can hear after a transformation is:
“Could we get it to do this too?”
That's a subtle but important shift. People are moving beyond simply complying with the change and starting to take ownership of it.
The real test comes after the project team leaves
Go-live often comes with plenty of support.
There are workshops, training sessions and project meetings. Problems are quickly escalated. Senior leaders are paying attention.
Then everyone moves on.
That's when the real test begins.
Several weeks or months later, people encounter situations that weren't covered in training. The novelty disappears. Old habits start creeping back. Someone discovers that the old spreadsheet seems quicker. Another person finds a workaround.
Before long, you can have a new system sitting on top of the old way of working.
This is precisely when ongoing support, coaching and continuous improvement matter most.
If all the planning and resource stopped at go-live, the business may have planned the implementation without really planning the change.
Then ask the question that really matters
Has the business actually become better?
That's the outcome.
The answer will depend on why you started the transformation in the first place.
Perhaps you wanted to increase capacity, improve quality or shorten lead times. Maybe the objective was better traceability, improved customer service, higher productivity or faster decision-making.
Perhaps success is simply that managers spend less time firefighting, and people can find the information they need to do their jobs.
Those are very different measures from whether the software was delivered on time.
And sometimes the evidence isn't found in a dashboard.
Listen to the conversations happening around the business.
“We don't have those delivery problems anymore.”
“The certificates are going out on time.”
“I can finally see the stock.”
Small comments like these can tell you a lot about whether a new way of working has genuinely become embedded.
Don't just plan the change. Plan how it will stick.
This changes the questions manufacturing leaders need to ask before a transformation begins.
Don't only ask:
When will we go live?
Also ask:
What will successful adoption look like?
How will we know people are working differently?
Who will support them after implementation?
What will we do when workarounds start appearing?
What business outcomes should we expect to see if the transformation is working?
And perhaps:
At what point will we be confident that the new way of working has become normal?
That last question matters because transformation doesn't happen simply because somebody changes the process.
People have to change with it.
Go-live is the beginning, not the end
None of this means delivery doesn't matter. It does.
But it is only the first part of the story.
A transformation must move from something that has been delivered, to something people have adopted, to something that produces a meaningful outcome for the business.
Or, as Angela Fumpson puts it in The Manufacturing Playbook:
Implementation is an event. Adoption is a behaviour. Transformation is an outcome.
That's a much tougher test of success than hitting a go-live date.
But it's also the one that matters.
