Skip to main content

ERP Change Management

The technical implementation of an ERP system handles the 'what' of transformation; change management handles the 'how' — preparing the organization, stakeholders and users for the new way of working. Surveys consistently show that 60-70% of ERP implementations that underdeliver on business benefits do so because of weak change management, not weak technology. For US mid-market companies, change management is the single most underinvested area in ERP projects despite being one of the highest-leverage.

Core change-management components

  • Stakeholder analysis — identifying who is affected, their concerns and influence levels; tailoring engagement accordingly
  • Communication plan — structured communication of vision, timeline, impact, benefits across stakeholder groups
  • Training program — user training matched to roles and competence levels, delivered through varied formats
  • Change agents and key users (see key-user concept) — respected internal champions driving adoption
  • Resistance management — identifying, understanding and addressing resistance before it becomes obstruction
  • Process documentation — new procedures documented, accessible, training-supported
  • Performance monitoring — tracking adoption metrics; user-experience surveys; course correction
  • Recognition and celebration — milestone achievements visible across the organization

Change-management methodologies

Several methodologies provide structured frameworks. Prosci ADKAR: Awareness, Desire, Knowledge, Ability, Reinforcement — an individual-level change framework and one of the most widely used approaches in US ERP projects. Kotter's 8-step model: create urgency, build coalition, develop vision, communicate, empower action, generate quick wins, sustain momentum, anchor change — organizational-level approach. Lewin's 3-stage model: unfreeze-change-refreeze — classical foundation. McKinsey 7S framework: align strategy, structure, systems, shared values, skills, style, staff. ERP-implementation partners often have their own methodologies (Accenture HR & Talent, Deloitte Adaptive Workforce). The right methodology matters less than the discipline of applying it consistently and integrating it with the technical implementation plan.

Common change-management problems

Recurring patterns of weakness in ERP projects. (1) Late start: change management begins close to go-live, after key decisions have been made without affected stakeholder input. Resistance ferments. (2) Communication overload: high-volume but undifferentiated communication that stakeholders ignore. Better: targeted, role-relevant, consistent communication. (3) Training as afterthought: training designed and delivered in the last 2 months before go-live. Users absorb minimum information; go-live productivity drops severely. (4) Senior-management distance: executive sponsors absent from key communication, leaving the project team to carry the change message without senior authority. (5) Workforce blindness: methodology applied without adaptation to the company's actual culture — how decisions really get made, where informal influence sits, how distributed teams and multiple sites communicate, and, in unionized operations, the obligations that come with changing terms and conditions of work.

Realistic change-management budget

Realistic change-management investment levels for US mid-market ERP projects. Minimum viable (small projects, simple operations): 5-10% of total implementation budget. Risk: change-related issues likely post-go-live. Standard (mid-market): 10-15% of total implementation budget. Reasonable for typical situations. Transformation-oriented (greenfield implementations, major process change): 15-25% of total implementation budget. Required for ambitious projects with significant business-process redesign. Crisis (turnaround scenarios): above 25%. The investment includes external change-management consultants, training development and delivery, communication campaigns, internal change agents' protected time. Companies investing the right level report substantially better adoption and business-benefit realization than those underinvesting.

Practical recommendations

Five practical recommendations. (1) Start early: change management begins at project kick-off, not after design completion. Stakeholder engagement during design produces better requirements and reduces post-implementation resistance. (2) Address labor and HR obligations up front: in unionized operations, changes to systems that affect terms and conditions of work — time-and-attendance, monitoring, performance management — can trigger a duty to bargain under the National Labor Relations Act (NLRA), so engage HR and labor counsel before go-live. Even in non-union, at-will workplaces, transparent communication about monitoring and data use builds trust and reduces resistance. (3) Build a change-champion network: respected colleagues from each functional area act as change champions in addition to formal key users. Their peer credibility carries the message where official communications cannot. (4) Measure and adjust: structured measurement of adoption metrics, user-experience surveys, business-benefit indicators. Course correction based on data, not assumptions. (5) Invest in post-go-live support: the first 6-12 months after go-live are where adoption succeeds or fails. Maintain change-management capacity well beyond go-live, not just through the cutover weekend.

Related Topics