Every ERP project that fails on adoption looked successful on paper. The software was configured correctly. The data was migrated. The training was delivered. Go-live happened on schedule. And three months later, the production team is back on Excel and the system is used only to generate the monthly finance report.
Change management is the discipline that prevents this outcome. For Singapore SMB manufacturers, where production teams are often sceptical of new systems and margins are tight enough that disruption is costly, it is the most important factor in implementation success.
Why Production Teams Resist ERP Systems
Resistance to new systems is rational, not obstinate. Production staff have found ways to make the existing workflow function — Excel, WhatsApp, physical job cards, informal handoffs — and those ways work well enough. A new system asks them to change their muscle memory, adds steps during a learning curve, and exposes their mistakes in a way that informal systems do not.
- The four most common resistance patterns:
- \'The old way is faster\' — true for the first few weeks; the speed advantage of the new system only appears after 3-4 weeks of consistent use
- \'The system does not match how we actually work\' — often legitimate; if the system does not match the real workflow, adoption will not happen
- \'Nobody told us why we are doing this\' — resistance driven by exclusion from the decision, not the system itself
- \'We can just use Excel when the system does not support this\' — the exception-as-escape-hatch that kills adoption if left open
The Change Management Timeline
Change management starts before implementation, not at go-live. The decisions made during vendor selection and scope definition determine whether adoption succeeds or fails. A system built around how the team actually works is adopted faster than a generic system configured to match a standard workflow that does not fit the operation.
- Change management by phase:
- Selection (before signing): involve the production manager and one senior operator in evaluation — their buy-in is worth more than any feature comparison
- Design (weeks 1-4): hold workflow mapping sessions with actual users, not just management — the gaps between documented workflow and real workflow are where adoption fails
- Training (weeks 8-12): train on daily workflow, not features; train in small groups; test with real scenarios from the last month of production
- Go-live (day 1-14): executive sponsor walks the floor; production manager is visible using the system; issues get resolved within hours, not days
- Stabilisation (weeks 2-12): remove the parallel system by week 3; weekly review of system usage metrics; public recognition of teams with high adoption
Making the Old Way Harder
The most effective change management intervention for Singapore manufacturers is removing access to the old system faster than feels comfortable. If the Excel file still exists and is up to date, staff will use it. If the whiteboard is still the official production schedule, the system is optional.
Cutting the old system requires confidence in the new one. This is why the parallel running phase exists — to validate that the new system produces accurate outputs before the old one is decommissioned. Once validated, the cut should be hard and fast. Two weeks, not two months.
Who Owns Change Management
Change management cannot be delegated to the implementation vendor. The vendor owns the system; the manufacturer owns the people. The internal change management owner is typically the production manager or operations director — the person whose team is adopting the system and who has the authority to require its use.
This person needs three things: air cover from the CEO (so that reverting to the old way has a cost), time allocated specifically to change management (not added to their existing workload), and a direct line to the vendor for issue resolution during the first 60 days.
Custom Build Advantage for Adoption
One reason custom-built systems tend to see higher adoption rates than off-the-shelf ERP packages in Singapore SMBs: the system is built around the actual workflow, not configured to approximate it. When the job card module matches exactly how the production team tracks jobs, training is shorter and the 'the old way is faster' objection disappears sooner.
The same applies to terminology. A custom system can use the exact words the team uses for job stages, materials, and processes. An off-the-shelf system uses vendor terminology that the team must learn alongside the workflow. Small friction points compound into adoption failure.
Measuring Adoption
- Adoption metrics to track weekly for the first 90 days:
- Active daily users vs expected users (are all production staff logging in?)
- Job cards created in system vs total jobs started (is production using the system for all jobs?)
- Quotes generated in system vs total quotes sent (is sales using the quoting module?)
- Invoices created in system vs total invoices issued (is the system the source of truth for billing?)
- Issues logged vs issues resolved (is the vendor responding fast enough to sustain adoption?)
These metrics are more useful than satisfaction surveys. Adoption is a behaviour, not a feeling. If all job cards are in the system at day 60, the implementation succeeded regardless of what staff say in a survey.