Silhouette of a person standing before a network of interconnected nodes, symbolizing digital transformation and change management.
Services | ERP & Technology

ERP and Technology Change Management

Reduce implementation risk. Drive adoption. Transform your organization. IMA Worldwide helps enterprise teams reduce ERP implementation risk using the Accelerating Implementation Methodology (AIM), developed by Don Harrison.

ERP and technology change management is the structured discipline that closes the gap between system go-live and sustained user adoption. IMA Worldwide applies the Accelerating Implementation Methodology (AIM), developed by Don Harrison, to surface implementation risk before go-live and build the leadership, readiness, and reinforcement structures that turn system investment into measurable behavior change.

By the Numbers

The Cost of Treating ERP as a Technology Project

70%+ of ERP initiatives fail to fully meet original business case goals. The dominant cause is people and process, not technology. Source: Gartner
#1 Leadership alignment with strategic goals is the top predictor of ERP success. Lack of executive engagement is a leading failure factor. Source: Gartner
<5% of total project budget is what most ERP programs allocate to organizational change management. Programs that succeed at change typically invest 10 to 15 percent. Source: Prosci
Why Change Fails

Three Reasons ERP Implementations Stall After Go-Live

Organizations invest millions in software licenses and technical configuration while underinvesting in the human adoption work. Employees who do not understand why the system is changing, how their roles will shift, or what success looks like will resist. Actively or passively. Regardless of how well the platform is configured.

Implementation Risk Underestimated

Organizations frequently proceed with ERP timelines based on vendor estimates and technical milestones alone. A rigorous organizational readiness assessment identifies the structural, cultural, and capability gaps that will create friction, allowing project teams to address them proactively rather than reactively managing a failed rollout.

Limited Management/Leader Involvement

Visible, sustained leadership commitment is the single strongest predictor of ERP adoption success. When executive sponsors disengage after go-live planning, middle management receives conflicting signals and frontline staff lose confidence in the transformation's permanence. Change requires authority, not just a project plan.

Change Management as an Afterthought

Change management is too often scoped as a communications plan appended to the technical workstream. Effective organizational change management must be integrated from the earliest stages of implementation planning, shaping governance, readiness assessments, training architectures, and resistance mitigation in parallel with technical design.

Understanding Implementation Risk

Most ERP Implementations Do Not Fail Because the Software Was Wrong

They fail because the organization was not prepared for the scope of change the technology demanded. Implementation risk is the gap between what the technology assumes and what the organization can absorb. The structural, cultural, and capability factors that determine whether users will change their behavior after go-live, or revert to the old way.

Warning Signals Your Implementation Is at Risk

If two or more of these signals are present in your current program, your implementation carries measurable organizational risk. IMA's Implementation Risk Assessment provides a structured diagnostic to surface these gaps before go-live, when correction is still cost-effective.

  • Change management team assembled after system configuration is already underway
  • Executive sponsorship limited to project initiation; sponsors disengaged through deployment
  • Training strategy limited to system navigation, with no role-based process change guidance
  • Go-live success measured by technical deployment rather than adoption metrics
  • Post-implementation support plan underfunded or undefined
  • Stakeholder resistance treated as a communications problem rather than a structural one
The AIM Approach

The People Side of ERP Transformation

Technology implementations succeed when people change how they work. IMA's Accelerating Implementation Methodology (AIM), developed by Don Harrison, positions organizational change management as a primary program workstream, not an afterthought. The result: enterprise teams prepared, aligned, and equipped to adopt new ERP systems with confidence and speed.

A Methodology Built for Enterprise Complexity

ERP transformation programs span years, cross organizational boundaries, and require sustained executive commitment. AIM was purpose-built for this scale of complexity. IMA advisors have guided enterprise organizations through SAP, Oracle, Microsoft Dynamics, and cloud ERP transitions, bringing structured change management discipline that integrates with existing project governance.

Mitigating the People Risk in ERP Programs

Research consistently shows that ERP failures are rarely technical. Resistance to change, inadequate training, unclear role ownership, and weak communication account for the majority of implementation setbacks. IMA's change management practice addresses these risk factors directly, providing enterprise clients with structured interventions that reduce the probability of cost overruns, delayed go-lives, and post-go-live adoption failures.

Six Pillars

Six Pillars of the AIM Approach

IMA's engagement model operationalizes the AIM methodology through six integrated workstreams, each designed to address a distinct dimension of organizational change during ERP transformation.

Stakeholder Mapping

We map every stakeholder group impacted by the ERP transformation, from executive sponsors to frontline users, identifying influence, resistance risk, and engagement requirements before go-live.

Organizational Readiness

IMA conducts structured organizational readiness evaluations that expose gaps in leadership alignment, process ownership clarity, and user preparedness before they become critical-path blockers.

Change Architecture

We design a bespoke change architecture for each engagement, defining communication cadences, training pathways, and support structures that reflect the organization's culture and operating model.

Adoption Measurement

Transformation success is measured by sustained adoption, not system activation. IMA embeds adoption KPIs into program governance, tracking behavioral change throughout and beyond go-live.

Reinforcement & Sustainment

Post-implementation support structures prevent the adoption curve from flattening. We build internal change capability so organizations own their ERP change competency long after the engagement ends.

Embedded Advisor Model

The AIM methodology operates alongside the technical workstream, not downstream of it. IMA's change advisors are embedded in your program governance from project initiation through stabilization.

Deliverables

Core Change Management Deliverables

IMA change management advisors work as embedded members of your program team, attending steering committee meetings, participating in design workshops, and providing real-time guidance to project managers and business leads. This integration model keeps the organizational change workstream synchronized with the technical timeline and surfaces risk signals before they escalate.

IMA measures success by adoption velocity, user proficiency, and business process stabilization metrics, not consulting hours. Every engagement is scoped around measurable change outcomes tied to your organization's strategic objectives.

  • Implementation Risk Assessment (IHA-informed diagnostic)
  • Stakeholder map and influence analysis
  • Executive sponsorship roadmap and coaching
  • Change architecture and communication plan
  • Role-based training and process change guidance
  • Go-live readiness scorecard and risk dashboard
  • Post-go-live adoption tracking and reinforcement planning
  • Change champion network activation and enablement
Frequently Asked Questions

ERP Change Management Questions

Why do ERP implementations fail at adoption?
Gartner projects more than 70 percent of ERP initiatives fail to fully meet their original business case goals, with people and process issues as the dominant cause, not technology. The pattern repeats because programs treat go-live as the finish line. Technical deployment proceeds on schedule while leadership commitment, readiness, role clarity, and reinforcement are deferred or treated as secondary.
How does AIM support ERP implementations?
The Accelerating Implementation Methodology (AIM), developed by Don Harrison, runs alongside the technical workstream from project initiation through stabilization. AIM diagnoses the specific organizational factors blocking adoption (absent sponsor behavior, insufficient readiness, concentrated resistance, missing reinforcement) and designs interventions against those root causes. Diagnostic instruments are delivered on the Comparative Agility platform.
How is AIM different from a training-only approach?
Training-only approaches assume users will adopt a system if they know how to operate it. AIM recognizes that knowledge is one factor among several. Most post-go-live adoption failures are driven by unclear leadership expectations, misaligned performance management, unresolved process conflicts, and weak reinforcement. AIM addresses those directly, in parallel with training.
What is the Implementation Risk Assessment?
The Implementation Risk Assessment is a structured diagnostic that surfaces leadership alignment gaps, organizational readiness shortfalls, and reinforcement gaps before go-live, when correction is still cost-effective. It maps stakeholder influence, resistance risk, and engagement requirements across every group impacted by the ERP transformation.
How long does an IMA ERP change engagement run?
IMA engagements typically span the full implementation timeline, from pre-go-live readiness through the post-go-live reinforcement period. Major ERP programs commonly run twelve to twenty-four months. The most critical AIM work concentrates in the six months before go-live and the three to six months after, when adoption behaviors are being established or abandoned.
What industries does IMA serve for ERP change?
IMA Worldwide and Peacock Hill Consulting deliver AIM-based ERP and technology change programs across global health philanthropy, Fortune 50 pharmaceutical and healthcare manufacturers, hyperscale technology platforms, diversified transportation and logistics groups, major US health insurance carriers, and government, education, and financial services. Specific client identities are protected under non-disclosure agreements.
How much of an ERP budget should go to change management?
Prosci research shows most ERP projects allocate less than 5 percent of total budget to organizational change management, well below the 10 to 15 percent used by organizations that consistently execute change well. Underinvestment in the people side of change is one of the most common drivers of ERP cost overruns and post-go-live adoption failure.
Implementation Risk Assessment

Is Your ERP Implementation at Risk?

Identify hidden risks before they derail your timeline. Receive a structured action plan aligned to the AIM methodology. Move from technical milestones to adoption outcomes.

Request an Implementation Risk Assessment

Subscribe to IMA's Blog