Why good systems still get pushback
After go-live, resistance usually comes from routine disruption. People who have worked a certain way for years may feel slower at first, especially when they must capture the same job in a new format. In a Centurion office or a warehouse in the East Rand, that hesitation often sounds like, “the old way was quicker”. It is not always stubbornness, it can be fear of making mistakes in front of others.
One of the most common user adoption hurdles is poor fit between the process and the person. If staff have to click through too many screens or wait for approval steps that do not match the real workflow, they will find shortcuts. That is when data quality drops and managers lose confidence in reports.
- Slow screens and confusing menus make people avoid the system.
- Too many manual steps encourage workarounds and duplicate entries.
- Unclear roles cause staff to assume someone else has updated the record.
Start with the reasons people use the system, not just the features
Before training starts, explain what the ERP is meant to fix in plain language. Staff do better when they know why stock counts must be accurate, why invoices need to be captured the same day, and why managers want a cleaner audit trail. If the business has branches in Johannesburg and Pretoria, explain how one shared record prevents one office from selling stock that another office has already allocated.
Keep the message practical. People do not need a lecture about digital transformation, they need to know what changes in their workday and what stays the same. A short meeting with each department often helps uncover the real worries, such as overtime approvals, month-end pressure, or whether the system will cope during load shedding when teams are switching between devices and power backups.
Train by role, not in one big room
Generic training is one of the fastest ways to lose attention. A sales coordinator, warehouse clerk and finance user do not need the same depth of detail. Role-based sessions shorten the learning curve and stop people from sitting through features they will never use. It also helps to train supervisors separately, because they need to know how to support the team when mistakes happen.
- Use short sessions of 45 to 90 minutes instead of one long workshop.
- Show the exact screens users will see on day one.
- Give each role a simple checklist for daily tasks.
- Repeat the critical steps, such as posting, approving and reconciling.
A good training plan also includes practice data. Staff should be able to enter a test order, correct an error and reprint a document before they work with live information. That small confidence boost can save a lot of time once the pressure is on.
Make support easy to reach in the first 30 days
The first month after go-live is where confidence is won or lost. If users have to wait days for help, they will start keeping parallel records in spreadsheets and notebooks. That creates confusion for management and increases the risk of errors. Fast support matters even more for SMEs with lean teams, because one unhappy user can slow down a whole department.
Set clear support rules from the start. Tell people who to contact, what to send, and how quickly they can expect a response. It helps to nominate one internal champion in each branch, whether that is in Durban, Cape Town or Gqeberha. That person can handle basic questions and escalate only the issues that need specialist attention.
- Use a simple support log with issue, owner, priority and status.
- Review common questions weekly and update the training notes.
- Keep approvals and fixes visible so users know their call was not forgotten.
Use early wins to prove the change was worth it
People support a new system when they can see something better happening quickly. Early wins might be a faster month-end report, a cleaner stock count, or fewer invoice errors. These examples matter because they show the new process is not just different, it is useful. In one Pretoria distributer, for example, managers were able to cut manual stock checks by using one shared transaction record and a tighter receiving workflow. Staff were sceptical at first but after two weeks they could see fewer mismatches on high-value items.
Share those wins in the language of the business. Mention saved hours, fewer corrections and less rework rather than abstract system benefits. Small successes build trust and reduce the feeling that the change is being forced on people for no reason.
Keep improving after go-live instead of freezing the process
User adoption is not finished on launch day. Once the team is using the system, review what still feels awkward and adjust where possible. Sometimes a report needs changing, sometimes a workflow needs fewer approval steps, and sometimes the issue is simply that a form label is unclear. A good support retainer should include regular check-ins, usage reviews and practical guidance for upgrades or policy changes.
Change management works best when it is steady and factual. Ask what users are struggling with, what they are doing around the system, and where the business is still losing time. That ongoing feedback is what keeps adoption alive, especially in SMEs that are balancing growth, staff turnover and tight month-end deadlines.
When teams feel heard and supported, they stop seeing the ERP as extra admin and start using it as part of the normal day. That shift is what turns implementation into real value.
