Built to Change

ERP drift rarely announces itself.

Ninety days after go-live, the project team has moved on and sponsors are focused on the next priority. Help desk tickets are falling, which looks like adoption. Often it means people stopped asking for help because they found a workaround.

Prosci's 2025 Unlocking ERP Implementations research found that human factors matter six times more than technical factors in improving ERP benefits. When value stalls after go-live, the system is usually working fine. Adoption, proficiency and reinforcement are where it leaks.

In this episode, Celine Simon, Vice President of Delivery for Prosci Europe, joins host Emma de-la-Haye to explain what sustaining ERP value takes once the launch is over. Drawing on post-go-live work with organizations in energy, media and beyond, Celine walks through how managers can catch drift early, which workarounds are worth keeping, and how to hand reinforcement from the project team to the business with clear ownership.

In this episode:
- What ERP drift looks like, and why fewer support tickets can be a warning sign
- The skills gap and measurement gap behind stalled ERP benefits
- Why managers spot drift first, and the CLARC roles they find hardest after go-live
- A simple test for telling a helpful workaround from a shadow system
- What a sustained reinforcement plan includes, and who should own it
- One move to make 30 days after go-live, and how to recover 6 to 12 months in using the Prosci ADKAR® Model

Built to Change is Prosci's video and podcast series for the people who make change happen. Season 1 takes on ERP, with new episodes monthly. Subscribe to follow along.

New to Prosci? Be sure to follow us on LinkedIn or engage with our content further on our website. 

Bad ERP metrics are worse than no metrics at all.

Prosci's 2025 Unlocking ERP Implementations research found that organizations with poor metrics succeed 7% of the time. Organizations with no formal metrics at all succeed 26% of the time. Comprehensive metrics maturity delivers outcomes four times better than measuring poorly.

Most ERP dashboards are built from activity: hours trained, communications sent, milestones hit, and tickets closed. Those numbers are easy to generate, and they feel objective, which is exactly why they become the default. What they measure is whether the change management work was performed, not whether people are working differently.

In this episode, Prosci's Claire Guyot joins host Emma de-la-Haye to separate the metrics that drive decisions from the metrics that create noise. Drawing on years of work with ERP leaders across industries, Claire explains why training completion is the most misleading number on the dashboard, what five people metrics actually signal whether a rollout is on track, and how to tell a reporting metric from one that changes what leaders do next.

In this episode:
- Why activity metrics dominate ERP dashboards, and what they can and can't tell you
- Speed of adoption, ultimate utilization and proficiency as the human factors behind ERP ROI
- How poor measurement creates false confidence and hides real risk
- The five people metrics worth tracking, starting with readiness against the Prosci ADKAR® Model
- Reporting metrics vs. steering metrics, and the one question that tells them apart
- How to rebalance a dashboard partway through an implementation

Built to Change is Prosci's video and podcast series for the people who make change happen. Season 1 takes on ERP, with new episodes monthly. Subscribe to follow along.

New to Prosci? Be sure to follow us on LinkedIn or engage with our content further on our website. 

Technical readiness gets you live. People readiness gets you the return.

Most ERP transformations treat go-live as the finish line. The organization signs off, the system switches on, and everyone assumes readiness has been achieved. But the room that approves go-live rarely includes the people who have to adopt the change, and "we've done the training" is not the same as "our people are ready."

In this episode, Prosci change advisor Amber Severson joins host Emma de-la-Haye to unpack what real readiness looks like on an ERP transformation. They cover the risks teams quietly accept before go-live, the cost of a late change catch-up, why a pause can be a sponsor's bravest decision, and the assessments that help leaders de-risk the final stretch: the Prosci Change Triangle (PCT) Model and the ADKAR® Assessment.

One question reframes the whole conversation. What are we actually asking people to do?

New to Prosci? Be sure to follow us on LinkedIn or engage with our content further on our website. 

Most ERP implementations don't fail because of the technology. They fail in the gap between approving the change and actively leading it.

In the first episode of Built to Change, Prosci's Emma de-la-Haye talks with Kelli Smith about executive sponsorship in ERP transformations, and why active, visible sponsorship is the single biggest predictor of whether an ERP delivers value. Drawing on years of work alongside executives, Kelli explains what sponsorship failure looks like in practice, why leaders so often underestimate their own role, and how the best sponsors build a coalition that carries the change across the whole organization.

In this episode:

• Why approval and active sponsorship are not the same thing
• The behavioral warning signs that sponsorship is slipping
• How much time sponsorship really takes across the ERP lifecycle
• Why coalition building is the most overlooked move in ERP change
• A practical first step for any sponsor

Built to Change is Prosci's video and podcast series on the real challenges behind change. Season 1 takes on ERP, with new episodes monthly. Subscribe to follow along.

New to Prosci? Be sure to follow us on LinkedIn or engage with our content further on our website.