ERP Change Management
The technical implementation of an ERP system handles the 'what' of transformation; change management handles the 'how' — preparing the organisation, 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 DACH mid-market, 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 programme — 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 organisation
Change-management methodologies
Several methodologies provide structured frameworks. Prosci ADKAR: Awareness, Desire, Knowledge, Ability, Reinforcement — individual-level change framework, widely used in DACH ERP projects. Kotter's 8-step model: create urgency, build coalition, develop vision, communicate, empower action, generate quick wins, sustain momentum, anchor change — organisational-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 DACH 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) Cultural blindness: methodology applied without adaptation to DACH-specific cultural factors (consensus orientation, hierarchical communication norms, works-council co-determination, regional differences within DACH).
Realistic change-management budget
Realistic change-management investment levels for DACH 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 realisation than those underinvesting.
Practical recommendations
Five practical recommendations. (1) Home 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) Identify and engage works councils: in Germany and Austria, works councils have legal co-determination rights on systems affecting employees. Early engagement and proper Betriebsvereinbarungen (works-council agreements) are essential. (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
Frequently Asked Questions
Do we need external change-management consultants?
For mid-market and larger projects, typically yes. Specialists bring methodology, comparative experience and a perspective independent of internal politics. Smaller projects can succeed with internal capability plus light external support. The right scale: above 100,000 EUR implementation budget, change-management consulting investment pays back.
How do German works councils affect ERP change management?
Significantly. Works councils have co-determination rights on systems monitoring employees (time-and-attendance, performance management, certain workflow tools). Engaging the works council early, agreeing Betriebsvereinbarungen (works-council agreements) on permitted uses, providing transparent communication — all are essential for German operations. Skipping or rushing this engagement risks injunctions blocking go-live.
Can we cut change management to meet budget?
Possible but costly later. Change-management underinvestment shows up post-go-live as productivity loss, user resistance, workarounds, shadow systems and re-work. The savings disappear quickly. Better discipline: cut customisation or scope rather than change management.