Why Change Management Matters
Technology is the easy part of an ERP implementation. People are the hard part. Studies consistently show that ERP failure is more often caused by poor change management than technical issues. Users resist change, departments protect their workflows, and executives lose patience. A structured change management approach prevents these failure modes.
Common Resistance Patterns
- "My spreadsheet works fine" — users comfortable with current tools
- "This is more steps than before" — initial learning curve feels like a step backward
- "Why are we changing?" — lack of understanding of the why behind the change
- "I was not consulted" — feeling excluded from the decision
- "It does not work the way I need it" — configuration gaps or training gaps
Change Management Framework
Phase 1: Awareness (Pre-Project)
- Communicate the why — business case, pain points, future vision
- Announce the project with executive sponsorship
- Identify change champions in each department
- Address fears directly (no one is losing their job)
Phase 2: Involvement (During Implementation)
- Include key users in requirements gathering
- Demonstrate progress with regular demos
- Solicit feedback and show how it is incorporated
- Create a feedback channel (dedicated chat/email)
Phase 3: Preparation (Pre-Go-Live)
- Provide hands-on training with real scenarios
- Give users sandbox access to practice
- Document new processes with step-by-step guides
- Set clear go-live date and communicate expectations
Phase 4: Adoption (Post-Go-Live)
- Provide hyper-care support (first 2-4 weeks)
- Celebrate early wins publicly
- Address issues rapidly (build trust)
- Monitor usage metrics and follow up with non-adopters
Phase 5: Optimization (Ongoing)
- Collect improvement suggestions quarterly
- Implement quick wins from user feedback
- Provide refresher training
- Share success stories and ROI metrics
Stakeholder Engagement
| Stakeholder | Concern | Engagement Strategy |
|---|---|---|
| Executives | ROI, timeline, risk | Regular dashboards, milestone reports |
| Department Heads | Team productivity, workflow disruption | Involvement in requirements, demo sessions |
| Daily Users | Learning curve, job security | Hands-on training, sandbox access, champion support |
| IT Team | Technical complexity, support burden | Technical training, documentation, escalation paths |
Communication Plan
# Timeline:
# 8 weeks before: Executive announcement (why + what)
# 6 weeks before: Department briefings (how it affects you)
# 4 weeks before: Training schedule announcement
# 2 weeks before: Training begins
# 1 week before: Go-live reminder, final prep
# Go-live day: Support presence, encouragement
# Week 1-2: Daily check-ins
# Week 3-4: Bi-weekly reviews
# Month 2-3: Monthly reviews
# Quarterly: Optimization sessionsMeasuring Adoption
- Login frequency — are users actually using the system?
- Record creation — are transactions being entered in Odoo (not spreadsheets)?
- Feature usage — which features are used vs. configured but ignored?
- Support tickets — volume should decrease over time
- User satisfaction — survey at 30, 60, 90 days
DeployMonkey Advantage
DeployMonkey's AI agent reduces the change management burden by making Odoo configuration feel intuitive. Instead of complex manuals and weeks of training, users interact with an AI assistant that guides them through workflows and answers questions in real-time.