Change and training
The system will do what it was configured to do. Whether people use it as designed is the open question on every ERP programme. Our ERP change management work covers impact analysis, process ownership, communications, role based training, super users and adoption measures that run past go live.
Delivered for and alongside
































The evidence on this is consistent and old enough that nobody can claim surprise. McKinsey's 2015 article Changing change management put it bluntly: 70 per cent of change programmes fail to achieve their goals, largely due to employee resistance and lack of management support. Panorama Consulting's 2021 ERP Report, drawn from 112 organisations, found that organisational issues (governance, resistance to change and process redesign) were the leading reason for schedule overruns at 26.7 per cent, and had been the top reason every year since 2018. In the same survey 67 per cent found the organisational side of the change difficult, against 8 per cent who found the technical side difficult, yet only 23 per cent gave change management an intense focus. Prosci's research across more than 2,600 practitioners found that 88 per cent of projects with excellent change management met or exceeded their objectives, compared with 13 per cent of those with poor change management.
Read together, the pattern is plain. ERP programmes are planned as technology projects, costed as technology projects and governed as technology projects, then fail for reasons that have nothing to do with technology: approvers who keep approving by email, warehouse teams who keep a paper log beside the scanner, finance teams who export to spreadsheets because they do not trust the report. Our article on why ERP implementations fail goes through the mechanics.
ERP change management is the discipline that prevents this. It is not a communications team sending newsletters. It is structured work with analysis, decisions, owners and measures, and it starts at selection, not at training.
Impact analysis starts with a stakeholder map that names every group whose working day changes, from the board to the goods in desk, and then gets specific. For each role we record what they do today, what they will do in the new system, what they stop doing, which decisions move, and what data they now own. A buyer who raised orders from an email trail will raise a requisition that routes for approval and matches three ways on receipt. A credit controller who waited for an overnight report will see balances as they change. A plant manager who approved overtime on paper will approve it in a workflow with a deadline. Each of those is a change to someone's authority and habits, and each is a place where the old way quietly returns if nobody is watching.
Process ownership is the second pillar and the one most often fudged. Every end to end process, from order to cash and procure to pay through to record to report, needs a named business owner with the authority to take design decisions, to accept or reject configuration, and to be held to the benefits in the business case. Owners sit in design workshops, sign off test scenarios and chair the decisions about which local variations survive. Without them, design decisions default to the systems integrator, and the business inherits a system it never agreed to.
We run the impact analysis and establish ownership during planning, alongside the ERP readiness assessment, so the people work is in the plan and the budget from the start rather than bolted on when training is already late. The ERP implementation plan article shows where it sits in the sequence.
Communication starts earlier than most programmes think. Panorama found that the share of organisations communicating about the change before selection had risen to more than half, and that only 71 per cent of those had a communication plan. The plan is simple: who needs to know what, when, from whom, and what you will tell them honestly about the parts that get harder before they get easier. The sponsor speaks, repeatedly and in person. Line managers get the detail first so they are never surprised in front of their teams.
ERP training is designed by role, not by module. A credit controller does not need a course on the receivables module. She needs the dozen things she will do on Monday, in the system, with migrated data, and somewhere to ask questions on Tuesday. We build the curriculum from the same process scripts used in user acceptance testing, so training and testing reinforce each other, and we deliver it close to go live so it is still fresh. Training completion and role assignment are go live criteria, which is also what Microsoft's go live checklist demands: complete user training and assign the correct security roles before the date is confirmed.
Super users are the mechanism that makes this hold. One in each team, chosen for credibility rather than seniority, released for a real share of their time, trained first, involved in user acceptance testing, walking the floor in the first weeks and acting as first line for questions before anything reaches the help desk. They are also the people who tell you, early and truthfully, what is not working. How testing and training come together before the date is covered on ERP testing and go live.
Adoption is measured, not assumed. From the first week we track a short set of indicators and report them to the sponsor alongside the defect list.
Those measures feed the benefits case. A faster close or a cut in manual postings is only real when the measure says so, and that is how we connect change management to cost optimisation and benefits realisation.
We do this work either as independent assurance of your partner's change and training plan, or as the team that designs and runs it alongside your people. Across 19 years of delivering major systems and transformation programmes on five continents, the pattern has held: programmes with named process owners, trained super users and measured adoption keep their benefits, and the rest refight the same battles a year later. Fees are published on our pricing page.
ERP change management is the structured work that gets people to use a new system as designed. It covers stakeholder and impact analysis by role, naming business owners for each end to end process, a communications plan that starts at selection, role based training built on real scenarios and migrated data, a super user network, and measures of adoption after go live. It is a workstream with owners and a budget, not a newsletter.
Because the technology usually works and the habits around it do not. McKinsey found 70 per cent of change programmes fail to meet their goals, largely through employee resistance and lack of management support. Panorama's ERP research found organisational issues were the leading cause of schedule overruns every year from 2018 to 2021, and far more organisations found the organisational change difficult than the technical change. Approvals revert to email and reports to spreadsheets unless somebody owns the change.
Enough for each person to perform their own role on day one, in the live configuration, with data that looks like theirs. That means role based sessions built from the process scripts used in user acceptance testing, delivered close to go live, followed by floor support from super users. Training completion and security role assignment should be go live criteria. A general module overview delivered months early is the most common and least useful alternative.
A super user is a respected member of a team who is trained first, takes part in user acceptance testing, helps design training for colleagues, walks the floor in the first weeks after go live and handles first line questions before they reach the help desk. They also feed back early and honestly on what is not working. They need time released from their day job, and one per team is the usual minimum.
Track active users against assigned licences by role and site, the transactions that should be happening in the system but are not, workarounds such as spreadsheets and email approvals, cycle times like requisition to order and days to close compared with the pre programme baseline, data quality indicators such as duplicate records and rejected postings, and support ticket themes by role. Report them weekly to the sponsor alongside the defect list and tie them to the business case.
Where next
Tell us where your programme is and we will show you what the change and training plan is missing.