A new ERP only pays off when people use it well. Acclaim’s change management treats the people side of your MYOB Acumatica project as seriously as the data and the configuration. We plan for it, measure it and stay with it until the new way of working has stuck.
Go-live isn’t the finish line
Most ERP projects that disappoint don’t fail on the day the system goes live. They fade over the months that follow, as teams build workarounds, keep their spreadsheets and quietly go back to the old way. Modern change management is about preventing that. It’s practical, measured and built into the project from the start, not a binder of documents written once and never read again.
Our approach: prepare, manage, sustain
1. Prepare
- Case for change: a short, plain-English explanation of why you’re changing and what the business will look like afterwards, agreed with your leadership team
- Impact and risk: which teams and roles are affected, how much their day-to-day work changes, and the risks to adoption, each with a plan to reduce it
- Stakeholder map: who supports the change, who has doubts, and how we’ll work with each group (see below)
- Readiness baseline: where each team stands today, measured before any training begins
- Success measures: the adoption targets that will tell you the project has worked
2. Manage
- Communication plan: who hears what, from whom, through which channel and when, with messages ready to send
- Role-based training: people learn the processes they’ll actually run in MYOB Acumatica, using your own data where possible
- Change champions: respected people in each team who test early, answer questions and share feedback
- Readiness re-check: each team is measured again before go-live, and any gaps are closed first
- Go-live timing: a change calendar that avoids month-end, stocktakes, payroll runs, the 31 March year-end and the Christmas shutdown, and spots other projects landing on the same teams
3. Sustain
- Adoption tracking: actual use of the new system compared with the targets set at the start
- Reinforcement: recognising early wins, fixing friction quickly and retiring the old spreadsheets and workarounds
- Knowledge transfer: your people own the processes and can train new staff without us
- 90-day check: a review three months after go-live to confirm the change has stuck, with a plan for anything that hasn’t
Measuring readiness, team by team
Teams move through change at different speeds, so one organisation-wide score hides the problems. We assess each team across five areas:
| Area | The question it answers |
|---|---|
| Awareness | Do people understand why the business is changing? |
| Desire | Do they want to take part and support it? |
| Knowledge | Do they know what to do differently? |
| Ability | Can they actually do it in the new system, day to day? |
| Reinforcement | Is there enough in place to stop them slipping back? |
We also run short anonymous pulse surveys alongside quick comprehension checks, reported by group only. They show the gap between how prepared people feel and what they’ve actually understood. That gap is often the first sign that a team needs more support.
Knowing where people stand
Resistance is rarely about the software. It’s usually about trust, workload or not seeing what’s in it for them. Following Peter Block’s stakeholder model, we map people by how much they agree with the change and how much they trust the people leading it. Each group needs a different approach:
- Allies (high agreement, high trust): involve them as champions and early testers
- Opponents (low agreement, high trust): listen carefully, because their objections often improve the design
- Bedfellows (high agreement, low trust): agree clear commitments and follow through on them
- Fence-sitters (undecided): give them evidence and ask them to take a position
- Adversaries (low agreement, low trust): engage directly and honestly, and make sure the sponsor is involved
We log key conversations and update the map as people move, so the approach changes with them.
Sponsors who lead, not just sign
Visible, active sponsorship is one of the strongest predictors of a successful change. We keep your sponsor’s role clear and manageable:
- Gate decisions: a recorded go or no-go at each key point, such as approving the design, starting training and going live
- A short weekly update: wins, slips and the specific help we need from them, drawn from real project activity
- Clear asks: when a message needs to come from leadership, we draft it and they deliver it
Getting a stalled change back on track
Already live, but the system isn’t being used the way it should? Whether it’s MYOB Acumatica or another platform, we can help recover adoption in four steps:
- Assess: measure readiness and adoption by team, and find out what’s really getting in the way
- Stabilise: fix the urgent process, training and configuration problems that are driving workarounds
- Decide: your sponsor agrees the way forward, including what to change, pause or retire
- Sustain: reinforce the new way of working, then re-check after 90 days
Less paperwork, more buy-in
Change plans, communication schedules and training materials used to take weeks to produce. We use proven templates and modern tools, including AI, to draft them quickly, and our consultants review every plan and message before it goes anywhere. That leaves more time for what makes change work: talking with your people.
Change management is built into every Acclaim MYOB Acumatica implementation, and it’s also available on its own for other system and process changes. For more on why it matters, read Change management: the key to ERP success and the 10-step plan for a successful ERP implementation. The free ERP Toolkit includes a go-live checklist to help you plan.
Frequently asked questions
What is change management in an ERP project?
It’s the work that helps people adopt a new system: explaining why it’s changing, understanding who is affected, communicating, training, and measuring readiness and adoption until the new way of working sticks.
Why do ERP projects fail without change management?
Most don’t fail on go-live day. They fade afterwards, as teams build workarounds and go back to spreadsheets. Change management prevents that by preparing people early and tracking adoption after go-live.
When should change management start?
At the planning stage, before configuration begins. That leaves time to baseline readiness, map stakeholders and plan communication and training well before go-live.
How do you measure change readiness?
We assess each team across awareness, desire, knowledge, ability and reinforcement before training starts, and again before go-live. Short anonymous pulse surveys and comprehension checks show where people need more support.
What does the project sponsor do?
The sponsor makes a recorded go or no-go decision at each key gate, reads a short weekly update, and delivers the messages that need to come from leadership.
Can you help if our system is already live but not being used properly?
Yes. We assess adoption by team, fix the problems driving workarounds, agree the way forward with your sponsor, then re-check after 90 days.
Start with a readiness check
Whether you’re planning a new ERP or trying to get more from the one you have, a readiness check shows where your teams stand and what to focus on first.