Resistance to change is guaranteed. Plan for it.

Companies invest millions in software, then wonder why adoption stalls.

They focus on features and functionality, and ignore the human element. But your MES/MOM is only as effective as your organisation's willingness to change.

Technology is the easy bit. I genuinely mean that. You can buy the best platform on the market, connect every machine, integrate it with ERP, and still fail.

Every project meets resistance

Every single one. If someone tells you their project met no resistance, they either weren't paying attention or they're not being honest.

People resist change not because they're difficult or don't care, but because change is uncomfortable. It disrupts routines. It challenges expertise. It brings uncertainty.

For someone who's done their job well for fifteen years, being told "we're changing how you work" can feel like being told they've been doing it wrong.

Why good projects collapse

I've seen technically brilliant implementations fall apart because:

• Leadership didn't communicate the vision clearly
• Shopfloor teams weren't brought along on the journey
• Change management was an afterthought
• Internal expertise wasn't developed or kept

What leadership has to do

Successful transformation is impossible without strong leadership buy-in. Leaders need to:

1. Set the vision. Where we're heading, and why. Communicated clearly and often.
2. Back the change management. Resistance is the status quo. Get this wrong and the project fails.
3. Build a strong team. The right people at every level, cross-functional and properly supported. More in Building the right team.
4. Invest in resources. Find the knowledge and skills gaps. Upskill where you can, and hire where you can't.

If digital transformation is a business priority, give it the support and attention a business priority deserves.

Involve people early

Bring operators, supervisors, quality and maintenance into the design, not just the training.

They know the process better than anyone, including the workarounds. Their input makes the system better. And people support what they helped create.

Explain the why

People need to understand not just how to use the new system, but why it's better for them. Less paperwork. Fewer arguments about numbers. Clearer instructions. Less time chasing information.

If the only message is "management wants more data", expect resistance. If the message is "this makes your shift easier", you'll get help.

Invest in adoption, not just implementation

Implementation ends at go-live. Adoption starts there.

• Super users on every shift, trained early and given time to support others
• Quick wins made visible, like an operator seeing their own downtime data for the first time
• Feedback channels that actually lead to changes
• Leaders on the shopfloor, using the system themselves

Ask yourself honestly: do we have the internal capability to make this work? Have we prepared our people? Are we ready to invest in adoption, not just implementation?

The difference between success and failure is the culture you build around the system.

What's been your experience of change on the shopfloor?