Mid-market manufacturers don't fail at ERP because they're careless. They fail because the same structural mistakes are baked in early, when everyone is still optimistic. Here are the five I see most often — and what to do instead.
Mistake 1: Designing for the demo, not the shop floor
It's easy to design a system that looks great in a workshop and falls apart the first time a real order goes through it. The antidote is to pressure-test every process against your messiest reality — the rush job, the engineering change mid-build, the part that's always short — before you sign it off.
Mistake 2: Customising away your best chance to improve
Every time you bend the software to match an old process, you spend money to preserve a habit. Sometimes that's justified. Often it's just fear of change wearing a business-case costume. Challenge every customisation: is this a genuine competitive difference, or are we paying to avoid a conversation?
Mistake 3: Under-resourcing your own team
The implementation partner can configure the system, but they can't make the decisions only your people can make. When key staff are expected to run the project 'on top of the day job', decisions slow and quality drops. Backfill your best people onto the project properly — it's cheaper than the alternative.
The organisations that succeed treat ERP as a business change programme that happens to involve software — not a software project that happens to involve the business.
Mistake 4: Skimping on data
Item masters, BOMs, routings, suppliers, customers — if this data is wrong, the system is wrong, no matter how well it's configured. Data cleansing is tedious and under-appreciated, and it deserves a dedicated owner and a head start.
Mistake 5: Treating go-live as the finish line
The weeks after go-live are when value is won or lost. Plan for hypercare, expect a dip in productivity, and keep experienced help on hand while people find their feet. The projects that budget for the landing, not just the launch, are the ones that stick.
The common thread
Every one of these mistakes comes from treating ERP as a technology purchase rather than an operational change. Get the framing right — senior ownership, honest scope, real data, and a plan for the human side — and the software does what it's supposed to.
Written from hands-on IFS Cloud delivery experience. Every engagement is confidential — this article contains no client names or project specifics.