ERP implementations are among the most disruptive initiatives a midsized company can take on, not because the technology is complex, but because every department feels the impact of new workflows, responsibilities, and dashboards. When change is not managed deliberately, users resist, workaround spreadsheets multiply, and the financial return that justified the project never fully appears. The gap between technical go-live and actual business value is where many ERP investments quietly stall.
Why change management frameworks matter
Most ERP projects underperform not because the software is misconfigured, but because people are not ready or willing to use it as designed (Hiatt, 2006). Research in organizational change consistently highlights employee resistance and poor communication as top reasons technology projects miss their objectives (Kotter, 1995; Kotter, 2012). A structured change management framework gives leaders a repeatable way to anticipate resistance, sequence communication, and support adoption before behavior hardens around workarounds.
Without that structure, the investment in the platform sits idle while teams revert to familiar habits like offline spreadsheets, legacy tools, and informal processes. Unmanaged change shows up as extended parallel runs, rework on reports pulling bad or incomplete data, and IT hours spent “fixing” issues that turn out to be user errors. For finance leaders tracking ERP ROI, these costs are real and avoidable when change management is treated as a core workstream rather than an afterthought (Prosci, 2021).
Core elements of an effective framework
Every effective change management framework shares a set of building blocks: leadership sponsorship, structured communication, and training and readiness. These components do not guarantee smooth adoption on their own, but skipping any one of them tends to produce predictable problems like confusion, resistance, and missed milestones (Hiatt, 2006; Kotter, 1995).
Leadership sponsorship. Active sponsorship from senior leaders is consistently cited as the single most important contributor to successful change (Prosci, 2021). Leaders who visibly champion the transition, explain why it matters, and reinforce expectations signal that adoption is non-negotiable. Passive approval—signing a business case but staying out of the day-to-day change—is rarely enough to overcome organizational inertia.
Structured communication. People resist what they do not understand, especially when they fear losing competence or control. A clear communication plan explains what is changing, why it is happening, when it will occur, and how it affects each role (Kotter, 2012). Effective plans segment audiences—finance, operations, warehouses, executives—and tailor messages to their concerns rather than relying on one generic announcement.
Training and readiness. Training and readiness checkpoints translate intent into capability. Role-based training tied to real workflows builds confidence and reduces the temptation to fall back on old tools. Readiness assessments before go-live help leaders verify that users can execute core tasks in the new ERP, that process owners have validated their flows, and that support resources are in place (Hiatt, 2006). Treating readiness as a formal gate, not a vague assumption, sharply improves early adoption.
Comparing leading change management models
No single model fits every organization, but three of the most widely used frameworks—Kotter’s 8-Step Model, ADKAR, and Lewin’s Three-Stage Model—cover most ERP and finance-led change scenarios.
Kotter’s 8-Step Model
Kotter’s 8-Step Model describes change as a sequence of steps: creating urgency, building a guiding coalition, forming a vision, communicating that vision, empowering action, generating short-term wins, consolidating gains, and anchoring new approaches in culture (Kotter, 1995; Kotter, 2012). It is especially useful for large, cross-functional transformations where executive alignment and coalition-building must precede system rollout.
For ERP projects, this model helps sequence leadership and cross-department alignment before configuration and training accelerate. Skipping early steps like urgency-building and coalition formation often produces surface-level compliance—users log in because they must—without genuine adoption. In practice, finance leaders can apply Kotter by (a) quantifying the current pain (e.g., slow close, manual reconciliations), (b) assembling a cross-functional steering group, and (c) planning visible short-term wins such as faster period closes in the first quarters after go-live.
ADKAR Model
The ADKAR model (Awareness, Desire, Knowledge, Ability, Reinforcement) focuses on the individual journey through change rather than the organization as a whole (Hiatt, 2006). Each element represents a milestone a person must reach for sustainable behavior change: awareness of the need, desire to participate, knowledge of how to change, ability to perform new behaviors, and reinforcement to sustain them.
In an ERP rollout, different departments and roles progress through ADKAR at different speeds. A controller may have strong awareness and desire but lack hands-on ability in new period-close workflows, while warehouse staff may have ability in the new handheld processes but little desire if they do not see the benefit. Using ADKAR allows project teams to diagnose exactly where individuals or groups are stuck—awareness, desire, knowledge, ability, or reinforcement—and target interventions accordingly instead of applying blanket communication.
Lewin’s Three-Stage Model
Lewin’s model frames change as three stages: unfreeze, change, and refreeze (Lewin, 1947). Unfreezing involves challenging the status quo and preparing people to let go of existing habits; the change stage introduces new processes and systems; refreezing stabilizes new behaviors with policies, incentives, and cultural reinforcement.
For finance-led ERP projects, Lewin’s model offers a simple mental map that is easy to communicate across the organization. In the unfreeze stage, leaders highlight the cost of current processes—such as slow reporting or error-prone reconciliations—and explain why the ERP is necessary. During change, they provide training, support, and time to practice. In refreeze, they align performance metrics, approvals, and reporting expectations to the new system so old practices do not quietly return.
How to build a practical change management framework
Building a change framework for ERP does not need to be theoretical; it can be treated as a sequence of concrete decisions and checkpoints.
1. Define scope and stakeholders.
Start by mapping every role and department the ERP will touch: finance, operations, warehouse, sales, customer service, and leadership. Stakeholder analysis is a standard practice in change management because it allows leaders to anticipate sources of resistance and assign accountable sponsors for each group (Kotter, 1995; Prosci, 2021). A stakeholder map created before the project starts is far more valuable than an escalation plan written after resistance appears.
2. Connect each phase to measurable outcomes.
For ERP projects, each phase of change should tie to a financial or operational outcome such as faster month-end close, reduced manual reconciliations, improved cash flow visibility, or better inventory accuracy. Linking communication, training, and readiness milestones to quantifiable outcomes helps users understand why their adoption behaviors matter and how they affect organizational performance.
3. Build checkpoints before go-live.
Formal readiness checkpoints reduce the risk of “fake green” status, where a project looks on track but users are not prepared. Each checkpoint should verify that:
-
core users can complete end-to-end tasks in the new system,
-
process owners have validated workflows, and
-
unresolved gaps are addressed before go-live.
This approach is consistent with leading change and project management guidance that emphasizes stage gates and go/no-go criteria for high-impact rollouts (Prosci, 2021).
Examples: applying frameworks in ERP and finance-led change
NetSuite rollout at a wholesale distributor
Consider a wholesale distributor replacing a legacy system with NetSuite. Warehouse staff are used to paper-based receiving, and the finance team has relied on manual reconciliations for years. Applying the ADKAR model, the project team treats each group as a distinct change audience: finance receives early awareness and desire-building communications linked to faster closes and better reporting, plus deep training on new close processes; warehouse teams receive simple, operationally focused messages that tie new scanning workflows to fewer stockouts and faster order fulfillment, followed by hands-on practice.
In this scenario, finance may be at “knowledge but not ability,” requiring more lab-style sessions, while warehouse staff might still be at “low awareness,” requiring more emphasis on why the change is happening. Using ADKAR as a diagnostic tool keeps interventions targeted rather than generic (Hiatt, 2006).
Acumatica adoption in a manufacturing company
A mid-sized manufacturer deploying Acumatica across production, procurement, and finance can benefit from Kotter’s 8-Step Model because cross-departmental alignment is hard when each function has its own rhythms and priorities. Leadership starts by creating urgency with concrete data: excess inventory carrying costs, delayed financial closes, and late orders, then builds a guiding coalition of department heads who co-own the ERP case for change.
Short-term wins might include a measurable reduction in stockouts or a faster monthly close within the first quarter after go-live. By anchoring these wins in public reporting and recognition, leaders “refreeze” new behaviors and make regression to manual tracking less likely (Kotter, 2012). This structured approach helps ensure the ERP delivers the financial and operational benefits used to justify its selection.
Next steps for your change plan
A workable change management framework for ERP does not have to be complex, but it does have to be deliberate. Choosing a model that fits your culture—Kotter for large cross-functional transformations, ADKAR for behavior-level diagnostics, or Lewin for simple, high-level communication—gives you a shared language for driving adoption. The earlier you assign ownership, define stakeholder groups, and link phases to measurable outcomes, the better your chances of closing the gap between go-live and realized ROI.
If internal teams are already stretched with configuration, testing, and reporting, partnering with specialists who combine ERP implementation with structured change management can de-risk the project. For finance leaders, treating change management as a financial responsibility, not just an HR or IT concern, is one of the most direct ways to protect the ERP business case and ensure the system is used as designed.
FAQs
1. Why do so many ERP projects struggle with user adoption?
Most ERP projects underestimate how much behavior change is required, focusing on configuration and timelines while assuming people will adapt on their own. Research shows that lack of sponsorship, poor communication, and insufficient training are among the most common causes of failure (Kotter, 1995; Prosci, 2021).
2. Which change management model is best for ERP implementations?
There is no universal “best” model. Kotter’s 8-Step Model is well-suited to large, enterprise-wide transformations, ADKAR is effective for diagnosing individual adoption gaps, and Lewin’s Three-Stage Model offers a simple structure for planning and communication (Hiatt, 2006; Lewin, 1947; Kotter, 2012).
3. How early should change management start in an ERP project?
Change management should begin as early as the business case and vendor selection stages, not just before training. Early sponsorship, communication, and stakeholder mapping create the conditions for smoother configuration, testing, and rollout (Prosci, 2021).
4. What metrics should finance leaders track to measure ERP change success?
Useful metrics include time to close, number of manual journal entries, volume of shadow spreadsheets, error rates on key processes, user adoption rates, and cycle times for reporting and approvals. These measures link user behavior directly to financial outcomes.
5. Can a change management framework help recover a struggling live ERP implementation?
Yes. Even after go-live, applying a framework like ADKAR can help diagnose where users are stuck and guide targeted interventions in communication, training, or reinforcement. Many organizations stabilize and improve struggling ERPs by retrofitting structured change practices post-launch (Hiatt, 2006).
References (APA style)
Hiatt, J. (2006). ADKAR: A model for change in business, government and our community. Prosci.
Kotter, J. P. (1995). Leading change: Why transformation efforts fail. Harvard Business Review, 73(2), 59–67.
Kotter, J. P. (2012). Leading change. Harvard Business Review Press.
Lewin, K. (1947). Frontiers in group dynamics. Human Relations, 1(1), 5–41.
Prosci. (2021). Best practices in change management (12th ed.). Prosci Research.