# ERP Change Management Readiness Assessment: Will Your People Adopt the New System? > Source: https://netray.co/tools/erp-change-management-assessment > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Score your organization's readiness for the people side of ERP change: sponsorship, communication, training, capacity, and resistance handling. ## Category erp-migration ## Tool **Kind:** assessment **Questions:** #### How visible is executive sponsorship of the change to frontline employees? **Options:** ##### Employees would not know executives support this project **Score:** 0 ##### Leadership mentioned it once at kickoff **Score:** 1 ##### Executives communicate about it periodically **Score:** 2 ##### Executives regularly and personally explain why, in operations settings **Score:** 3 #### Has a change impact analysis been done by role? **Help:** A real impact analysis lists, for each role, which daily tasks change, which disappear, and which are new. **Options:** ##### No; we assume people will adapt **Score:** 0 ##### High-level department impacts identified **Score:** 1 ##### Role-level impacts documented for major roles **Score:** 2 ##### Role-level impacts documented for all roles and validated with those roles **Score:** 3 #### What does your communication plan look like? **Options:** ##### No plan; news travels by rumor **Score:** 0 ##### Occasional project emails from IT **Score:** 1 ##### Scheduled updates through multiple channels **Score:** 2 ##### Audience-specific messaging with two-way channels and feedback loops **Score:** 3 #### Do you have a super-user or change-champion network? **Options:** ##### No; the project team will handle everything **Score:** 0 ##### Names on a list but no defined role or time allocation **Score:** 1 ##### Active champions in most departments with defined responsibilities **Score:** 2 ##### Trained champions in every department with allocated time and direct project access **Score:** 3 #### How is training designed? **Options:** ##### Vendor-supplied generic training near go-live **Score:** 0 ##### Generic system training scheduled for everyone **Score:** 1 ##### Role-based training on our configured system **Score:** 2 ##### Role-based, hands-on training with our data, plus follow-up reinforcement **Score:** 3 #### Where does middle management stand? **Help:** Supervisors and department managers translate change to the floor. Their private skepticism kills adoption faster than any software defect. **Options:** ##### Openly skeptical or disengaged **Score:** 0 ##### Passively compliant but privately doubtful **Score:** 1 ##### Generally supportive with some holdouts **Score:** 2 ##### Actively championing the change with their teams **Score:** 3 #### Are goals and incentives aligned with the new ways of working? **Options:** ##### Metrics and incentives still reward old behaviors **Score:** 0 ##### Misalignments known but unaddressed **Score:** 1 ##### Key metrics being updated for the new processes **Score:** 2 ##### Goals, KPIs, and reviews explicitly updated to reinforce new processes **Score:** 3 #### How did your last major change initiative go? **Options:** ##### Badly; employees cite it as a reason to distrust this one **Score:** 0 ##### Mixed results; some cynicism persists **Score:** 1 ##### Reasonably well with lessons learned **Score:** 2 ##### Successfully; the organization trusts leadership to deliver change **Score:** 3 #### Do impacted employees have real capacity to absorb the change? **Options:** ##### No relief; project and training stack on top of full workloads **Score:** 0 ##### Ad hoc relief when someone escalates **Score:** 1 ##### Workload adjustments planned for peak project phases **Score:** 2 ##### Backfill and adjusted targets funded for training and the stabilization period **Score:** 3 #### How is resistance identified and handled? **Options:** ##### It is not; resisters are ignored or labeled difficult **Score:** 0 ##### Managers deal with it informally case by case **Score:** 1 ##### Feedback channels exist and concerns get responses **Score:** 2 ##### Resistance is actively surfaced, root causes addressed, and vocal skeptics engaged directly **Score:** 3 **Bands:** #### Unprepared: Adoption Failure Likely **Min:** 0 **Max:** 39 **Verdict:** Your organization is on track to receive a new system it did not ask for, does not understand, and has no capacity to absorb. In this band, expect shadow spreadsheets, workarounds, and data quality collapse within months of go-live. The system will be blamed for what is actually an unmanaged change. **Recommendations:** - Get executives personally communicating the why in operational settings, starting this month - Commission a role-level change impact analysis before any training is designed - Recruit and formally charter a champion network with allocated time - Fund backfill for training and stabilization; capacity cannot be wished into existence - Add a named change management lead to the project with real authority, not a sideline duty #### Developing: Structure Exists, Depth Missing **Min:** 40 **Max:** 69 **Verdict:** You have the visible artifacts of change management, but the depth that drives adoption, particularly middle-management conviction, aligned incentives, and real capacity, is not yet there. Projects in this band go live successfully and then bleed adoption over the following two quarters unless the gaps close. **Recommendations:** - Invest directly in middle managers: private briefings, input into decisions, and early hands-on system access - Audit KPIs and incentives for anything that still rewards old-process behavior - Upgrade generic training plans to role-based, hands-on sessions using your configured system - Create genuine two-way feedback channels and publicly respond to what comes in - Plan reinforcement for 90 days post-go-live, not just launch-week support #### Ready: Sustain Momentum Through Go-Live and Beyond **Min:** 70 **Max:** 100 **Verdict:** Your change foundation is strong, which is rarer than good project management and a better predictor of realized ROI. The risk now is complacency: change readiness decays under project fatigue, and the period from go-live to day 90 is where committed organizations either lock in new habits or quietly regress. **Recommendations:** - Keep executive communication cadence going after go-live, when attention naturally fades - Give champions a formal post-go-live role in issue triage and continuous improvement - Track adoption metrics such as transaction compliance and shadow-system usage, not just tickets - Celebrate visible early wins publicly within the first 30 days - Schedule a 90-day adoption review to catch regression before it becomes culture ## Content **Intro:** This assessment measures whether your organization is ready for the human side of an ERP implementation, the side that determines whether the system you paid for is actually used as designed. It is built for manufacturers where adoption failure has a distinct signature: supervisors keep planning in spreadsheets, inventory accuracy erodes, and the expensive new system becomes a data-entry afterthought. Ten questions cover sponsorship, impact analysis, communication, champions, training, middle management, incentives, change history, capacity, and resistance handling, and your result includes an action plan matched to your readiness band. **Sections:** #### Why change management decides ERP ROI **Body:** An ERP system produces returns only through changed behavior: planners trusting MRP instead of spreadsheets, operators reporting production in real time, buyers working exception messages instead of expediting by phone. Every benefit in your business case assumes those behavior changes happen. Research across ERP programs consistently attributes the majority of adoption failures to organizational factors rather than software defects, and the pattern is visible in any post-go-live audit: sites with strong change programs run the standard process, while sites without them rebuild their old world in Excel within two quarters. That is why this assessment weights middle management, incentives, and capacity as heavily as the more familiar topics of communication and training. #### The factors teams most often underestimate **Body:** Most project teams do communication and training in some form, because those activities are visible, budgetable, and easy to report progress on. The questions where manufacturers score lowest, and where scores most strongly predict adoption trouble, are the less visible ones: the private conviction of supervisors, the quiet pull of old KPIs, the hours that training actually requires, and the residue of past initiatives. These factors resist project management because they are not tasks to complete but conditions to change, and they respond to sustained leadership attention rather than plan lines. Review your own answers against these four, because they are the difference between launch-day compliance and lasting behavior change. **Bullets:** - Middle-management conviction: supervisors privately skeptical of the system will quietly authorize workarounds - Incentive alignment: people optimize what they are measured on, and old KPIs reward old behavior - Absorption capacity: training stacked on full workloads produces attendance, not competence - Change history: unresolved cynicism from past failed initiatives transfers directly onto this one #### Reading your score and sequencing the work **Body:** Scores below 40 percent call for a genuine pause on the assumption that go-live equals adoption; the correction starts at the top with sponsorship and impact analysis, because communication and training built on unknown impacts is guesswork. Scores in the middle band typically reflect a project doing change management as a task list rather than a leadership activity; the highest-leverage move is almost always investing in middle managers, who multiply or nullify everything else. High scores shift the question from readiness to endurance: the critical window is the 90 days after go-live, when reinforcement, adoption metrics, and visible wins determine whether new processes become habit. In all bands, assign each recommendation an owner and date; unowned change actions do not happen. #### How Netray builds adoption into ERP delivery **Body:** Netray treats change management as part of implementation, not a parallel slide deck. Our delivery methodology for Infor SyteLine and LN builds role-level impact analysis directly from the process design work, generates role-based training materials from your actual configuration, and equips champion networks with the same AI-assisted support tools our consultants use, so answers reach the shop floor in seconds rather than through ticket queues. We also instrument adoption after go-live, tracking transaction compliance and exception behavior so regression is caught in weeks, not quarters. Share your assessment result and a specialist will map the fastest path to closing your specific gaps. **Cta:** Get a specialist review of your change readiness gaps and a sequenced adoption plan for your rollout. **Faq:** #### When should change management work start on an ERP project? **Answer:** At selection, not at training time. The highest-value activities, including building the case for change, involving users in requirements and demos, and briefing middle managers, all happen months before configuration begins. Programs that bolt change management on during the testing phase are limited to communication and training, which are the last mile of change, not the substance. A useful rule: if your change lead joined after the design phase started, you started late. #### How much should we budget for change management? **Answer:** Benchmark guidance across ERP programs puts organizational change management at roughly 10-15 percent of total project cost, covering a change lead, impact analysis, communication, champion time, role-based training development, and post-go-live reinforcement. Manufacturers routinely budget a fraction of that and pay the difference in stabilization consulting and lost productivity after go-live. If the budget conversation is difficult, price the alternative: a 10 percent productivity dip across a 200-person plant for two quarters dwarfs the change budget. #### What are the earliest warning signs of adoption failure? **Answer:** Watch for them before go-live: training sessions with poor attendance excused by workload, supervisors who stop attending project meetings, champions who cannot get time released, and a rumor mill outrunning official communication. After go-live, the signature signs are parallel spreadsheets reappearing, transaction backlogs entered in batches at day-end, declining data accuracy in cycle counts, and departments requesting old reports rebuilt exactly as before. Each signals people working around the system rather than through it, and each is recoverable if caught within weeks. ## Search terms erp change management, erp change readiness assessment, erp user adoption, change management manufacturing, erp training plan, erp resistance to change, organizational readiness erp --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json