Technical Readiness Gets Your ERP Live; People Readiness Gets You ROI

Prosci

3 Mins

Three professionals seated around a meeting table during a collaborative discussion, with a laptop and coffee cups visible in a bright office setting.

Enterprise resource planning (ERP) transformations promise a return on investment (ROI) that organizations won’t see without people readiness. Nearly half (45%) of ERP implementations don’t achieve their objectives, and seldom because of technology. Rather, they fail because the organization isn’t ready to receive, use, and adopt the ERP system.

In this episode of Built to Change, Emma de-la-Haye, Engagement Director for Prosci Europe, and Amber Severson, Principal Change Advisor for Prosci North America, look at how people readiness enables ERP transformations to deliver ROI, transformation, results, and business outcomes.

 

What go-live readiness looks like

When organizations say “we’re ready,” they’re often ready from a technical perspective, but that’s not the same as people being ready for the change.

Prosci defines change readiness as the level to which an organization is prepared, willing and able to implement change. It covers several facets, including organizational readiness, openness to change, and individual readiness.

There’s a specific group of people involved in conversations that lead to a final “we’re ready” decision in ERP implementations. Typically, the project team — leaders, key stakeholders, subject matter experts and technical team members — are part of the conversation. And these conversations are not always calm and organized, but rather have a layer of controlled tension.

Teams that are ready see project clarity, clear ownership, and decision-making at the right level. Importantly, there’s a shared awareness and understanding of what risks are acceptable going into go-live.

Who’s representing the end users in go-live conversations?

Frontline employees and end users don’t typically participate in conversations about whether the organization is ready to go live. But with consistent sponsorship, visibility, team engagement, and manager reinforcement of the change, feedback from these key stakeholders will trickle back up to the project team.

Continuous feedback breeds an ecosystem of active engagement throughout the organization.

What matters is that when organizations bring change management into an ERP implementation early on, teams are better able to structure and set up feedback systems. Activating end users early and bringing feedback to leaders and the project team helps the right people make the right decisions.

 

What’s driving the imbalance in technical readiness and people readiness?

Despite more organizations bringing change management into their ERP implementations early on, many continue to place a significant emphasis on technical readiness over people readiness.

The traditional operational mindset that prioritizes delivery and results is part of what’s driving this. Enterprises naturally gravitate toward what’s most comfortable: controllable, measurable outcomes. These are typically the technical aspects of the project, including scope, budget, and other metrics that can be clearly defined and measured.

Metrics that reflect the people side of change are often less visible. People-focused outcomes often require more time and effort to achieve. It’s much harder to measure outcomes like trust and end-user adoption than to achieve a technical milestone on a particular date, which forces organizations to prioritize what’s comfortable over what counts.

What’s missing from go-live conversations today

Organizations should ask: What are we asking our people to do?

More teams need to understand from the get-go how an ERP implementation will transform the work people do and how they do it. Organizations that can’t clearly articulate this will inevitably struggle to understand whether they are meeting their people objectives. Or worse, a lack of understanding of what people will have to do and how they will have to do it differently can lead to a delayed go-live or a failed ERP implementation.

The risk of prioritizing readiness late in an ERP implementation

Starting change management late in the ERP transformation is problematic and ineffective. When organizations play catch-up, there’s always a cost. Communication replaces engagement, training replaces readiness, and teams feel informed rather than involved in the process.

These tradeoffs lead to gaps in trust, rework that impacts timelines, and potentially the budget. There’s a domino effect of project-wide impact.

Late readiness work can help, but it’s not an ideal solution. Even when organizations do remedial change work immediately before go-live, it’s worth noting that change management needs to continue beyond go-live. Behavioral changes need reinforcing. Quick decisions require support and sustainment. Ownership is important to the ERP implementation success of post-go-live.

Organizations might also benefit from assessing their current state and pausing where they are in the work when readiness lags too far behind. Training completion doesn’t equate to skill proficiency. Without quality data to measure proficiency, teams typically find it worthwhile to facilitate conversations around the risk and what needs to be done.

Organizational readiness for ERP success

Prosci works with organizations at every stage of ERP implementation to ensure your organization is prepared, willing and able to implement change.

Prosci

Prosci

As the global leader in change management, Prosci helps organizations turn complex change into something people understand—so they can act with confidence and deliver results. Built on more than 30 years of research, Prosci partners with enterprises to scale change, enable adoption, and realize outcomes across complex transformations, including ERP and AI. Our work brings clarity and structure to change, helping leaders move from strategy to action and ensure results endure. That’s what change done right looks like.

See all posts from Prosci