Leading an ERP Rollout: The People Side Managers Can’t Afford to Skip
16 November 2026
The software went live on a Monday. By the end of the quarter, the finance team was still exporting ledgers to Excel to prepare board reports, and the warehouse had quietly gone back to its old stock sheet. The software was not the problem. The problem was how the people side of the transition had been managed. A failed ERP rollout often goes unnoticed in vendor demonstrations, because the build process is fairly predictable whichever system you choose. Managers have the most influence over the part that is not.
Why an ERP Rollout Is a Management Challenge
The research is consistent on this. A 2023 EDUCAUSE and CampusWorks study of ERP implementations in higher education concluded that these projects are often more about people than technology, and that they cannot be treated as IT projects. It called for continued, meaningful involvement from executives, staff and functional leaders. Panorama Consulting’s 2023 ERP Report points the same way. In its survey, roughly 14% of organisations put very little or no focus on change management, about 61% a moderate focus and about 25% an intense one.
That makes your role in an ERP rollout plain. You are not there to configure the system. You decide how decisions get made, who has time to work on the project and whether people feel ready when the new system arrives. Our article on the secret to successful change explains why structured change models, and individual support for the people affected, make the difference.
A Note on the Examples Used
The platform example in this partnered article, MYOB Acumatica, is sold in Australia and New Zealand. The research comes mainly from US surveys, and the EDUCAUSE study covers higher education institutions. Treat the details as illustrations of the approach, and check what is available and relevant in your own market and sector.
Map How Work Really Happens Before Anything Is Configured
Every organisation has two sets of processes: the one in the procedures manual and the one people actually use. The second includes the spreadsheet an accounts payable clerk built years ago, the approvals made by email because the old system could not handle them, and the customer whose invoices have always looked slightly different. If you configure the new system around the first set, staff will rebuild the second within weeks to make it fit. Mapping both is the first real task of any ERP rollout.
So talk to the people who do the work, and ask what they do when something does not fit. Acas, the UK’s employment advice service, notes that consulting employees helps employers hear opinions across the organisation and identify problems with a proposed change before they escalate. The workarounds you uncover are your real requirements, and they show where the new system could save effort. This is also where scope is set. Panorama found that around 35% of the organisations that went over budget cited an expanded project scope.
Get Finance and Operations Agreeing Before Go-Live
An ERP links finance, operations, sales and usually HR through shared data. That is its purpose, and it forces answers to questions that separate systems let you avoid. What counts as a completed job? When do we recognise project revenue? Who owns the customer record? If you leave these open, the person configuring the system ends up deciding them, and they are the last person who should.
Bring the heads of each department together early, reach agreement and write the conclusions down. It can feel slow in week three, but it pays back within months. Senior support matters too. In the EDUCAUSE study, 77% of institutions that had completed an implementation named leadership support as the most critical success factor, and 60% named effective communication with stakeholders as the most important skill. The figures come from universities, but the lesson applies wherever the sponsor goes quiet after the kick-off.
Choose a Platform That Fits Your Processes
Good process mapping makes selection much easier, because you compare each system with how your business works instead of ticking off features. MYOB Acumatica illustrates the sort of criteria to use. It is a cloud ERP based on the Acumatica platform and localised for Australian and New Zealand tax and compliance. It offers industry editions for construction, manufacturing and professional services, and it covers payroll and workforce management. Its modular design lets you switch on the processes you need now and add others later.
No platform suits everyone. MYOB describes this one as designed for larger, more complex organisations, so small businesses with simple processes may be better served by lighter software. Apply the same test to every option on your list. If a vendor cannot tell you who their software is not suited to, note that. Our decision making knowledge hub offers a structured way to weigh options against criteria you set before the demonstrations begin.
Treat the Implementation Partner as Part of the Team
Most mid-market ERP rollouts involve an implementation partner, and the partnership matters almost as much as the software. A good partner will challenge unnecessary customisation, ask hard questions about your data and be clear about where the project will end up. For each shortlisted partner, ask about their approach to data migration, how many hours a week they expect from your people, and what support they give after go-live.
Resourcing is where many projects come unstuck. In Panorama’s 2023 survey, 38% of organisations that overran their budgets said they had underestimated staffing, making it the most common reason. A plan that expects your finance manager to run month-end and the project at the same time is optimistic. Agree who backfills their regular work before you sign anything.
Plan Training and Adoption as a Phase of Its Own
Training squeezed into the two weeks before go-live is one of the most common reasons ERP projects stumble. Treat adoption as its own phase of the ERP rollout, and begin it during implementation, not at the end. Three choices shape how well it goes.
Role-Based Training
Train people for the work they will do, not for the whole system. Someone in accounts receivable needs to rehearse the new Tuesday process and the screens that go with it, not tour the inventory module. Build short, role-specific sessions around real tasks and real data. Repeat them after go-live, when people have genuine questions, and keep recorded versions for new starters.
Department Champions
Choose a champion in each department. Pick someone experienced and respected, give them early access to information and the time to help colleagues. They become the first stop for questions, and they tell the project team what is really happening on the floor. Recognise the extra load in their workload, or the role will quietly fall to whoever has the least to do.
A Phased or Big-Bang Go-Live
Panorama found that only about 21% of organisations used a big-bang approach, going live with everything at once. The rest used phased or hybrid approaches, by module, location or business unit. Phasing can look inefficient on paper, but it gives users time to adapt. Whichever route you take, expect productivity to dip after go-live, and avoid scheduling go-live during year-end reporting.
Final Thoughts
A successful ERP rollout depends on people as much as software. Map how work really happens, get departments to agree on definitions and choose a platform by fit, not features. Treat your implementation partner as part of the team and give training and adoption a phase of their own. Before the next demonstration, ask each head of department for their team’s top three workarounds. That list will tell you more about your readiness, and what you need from the system and its partner, than any feature list. The software is the part you can buy. Preparing your team is your job.
Disclosure and Disclaimer
This is a partnered post. See our disclosure policy for details. The content on this site is provided for general information and educational purposes only. It is not intended as professional IT, financial, legal or project management advice. Software capabilities, availability and pricing vary by supplier and market and change over time, and the statistics quoted come from third-party surveys of varying age, sector and scope. UK readers should refer to current guidance from Acas on consulting employees about change. US readers should note that federal and state employment rules differ and should consult a qualified adviser. Readers should seek qualified professional advice for their specific situation. The Happy Manager and Apex Leadership Ltd accept no liability for actions taken in reliance on the content of this article.
Further Reading
- Consultation and Change — Acas (UK): Guidance for employers on why, when and how to consult employees about changes, including when consultation is a legal duty. Read the guidance
- More Than “Going Live”: Key Findings — EDUCAUSE (US): The key findings of the 2023 EDUCAUSE and CampusWorks study of ERP implementations, with its conclusions on people, culture and leadership. Read the findings
- 60 Critical ERP Statistics — NetSuite: A vendor’s compilation of ERP implementation statistics, with links to the underlying studies. Treat vendor-selected figures with care and check the sources. Read the statistics
References
- Panorama Consulting Group (2023), The 2023 ERP Report (underestimating staffing the most common reason for budget overruns; fewer than a quarter of organisations used a big-bang approach; median project cost $625,000). https://4439340.fs1.hubspotusercontent-na1.net/hubfs/4439340/Reports/ERP%20Report/2023-ERP-Report-Panorama-Consulting.pdf
- ECI Solutions (2024), 39 ERP Facts and Statistics Every SMB Executive Should Know, summarising the Panorama 2023 ERP Report (38.4% of over-budget projects underestimated staffing; 34.9% expanded scope; 20.8% big bang; 60.7% moderate, 25.1% intense and 14.2% little or no focus on change management). https://www.ecisolutions.com/blog/39-erp-statistics-smb-2024/
- EDUCAUSE and CampusWorks (2023), More than “Going Live”: Achieving Institutional Transformation through ERP Implementation (ERP implementations are often more about people than technology and cannot just be IT projects; 77% of completed implementations cited institutional leadership support as the most critical success factor; 60% cited effective communication with stakeholders as a key skill). https://www.educause.edu/ecar/research-publications/2023/more-than-going-live-achieving-institutional-transformation-through-erp-implementation/institutional-culture-and-readiness-for-change
- Acas (n.d.), What consultation is (consulting employees helps employers hear opinions across the organisation, explore support for a change and identify issues with it). https://www.acas.org.uk/consulting-employees
- Kilimanjaro Consulting (n.d.), MYOB Acumatica (formerly MYOB Advanced) Cloud-Based ERP (based on the Acumatica platform and localised for Australia and New Zealand; modular design; industry editions; designed for larger, more complex organisations). https://kilimanjaro-consulting.com/myob-software/myob-acumatica/
Header image by DTSoft Official from Pexels
Leadership Resources

We’ve bundled together these five e-guides at half the normal price! Read the guides in this order, and use the tools in each, and you’ll be well on your way to achieving your personal development plan. (6 guides, 167 pages, 27 tools and 22 insights, for half price!)
- Leadership Essentials
- Defining Leadership
- Leading Insights
- Leading with Style and Focus
- Transformational Change
- Making Change Personal