Why ERP Fails Without Active and Visible Sponsorship
3 Mins
Published: June 17, 2026
Most ERP implementations don't fail because the technology is wrong. They fail in the space between a signed charter and sustained leadership, where approval ends and active sponsorship never quite begins. In this episode of Built to Change, Emma de-la-Haye, Engagement Director for UK & Ireland, and Kelli Smith, Director and Engagement Leader for Prosci North America, look at what that gap looks like in practice: why it opens, what it costs, and what the executives who get it right do differently.
One pattern they keep returning to: executive resistance to ERP can run higher than in any other group in the organization. That matters because sponsorship is the single biggest driver of ERP success.
How sponsorship quietly breaks down
Sponsorship failure is rarely dramatic and almost never intentional. It's behavioral, and it's gradual.
It usually starts with a missed forum. A delegate goes in the sponsor's place, a reasonable call given competing priorities. Then it happens again. Cross-functional decisions stack up with no one senior enough to resolve them. The project team starts working around the sponsor instead of through them, reaching sideways for alignment that should come from the top. Timelines stretch, and outcomes ultimately stall.
The signal does more damage than the delay. People read executive absence as a statement of priority. When the sponsor stops showing up, the message lands as, “maybe this isn't as critical as we were told.”
Part of what makes this hard is that executives underestimate how much their own resistance shapes their behavior. ERP introduces process standardization, data transparency, and a level of governance that changes how senior leaders operate, including how much control they hold. That friction is real, and it surfaces at the exact moment sustained engagement matters most.
What working around the sponsor costs
When teams lose reliable access to executive decisions, they adapt. Those adaptations get expensive.
People start making calls in the interest of the region or function they can actually reach, rather than the organization as a whole. Process inconsistency gets built into the foundation of the system. On an ERP, where the whole premise is standardized data and cross-functional efficiency, that inconsistency undermines the value case directly. Rework after go-live is costly. Benefits that never materialize cost more.
It’s ironic that fragmented, siloed decision-making is precisely what the ERP was meant to solve.
What effective sponsorship actually is
The most common misconception executives bring to an ERP is that sponsorship means more meetings. It doesn't.
Effective sponsorship is targeted, visible engagement at the moments that decide the outcome. Early on, that means being present for fit-to-standard decisions, where the organization determines how core processes will be shaped by the new system. Those calls require executive judgment. Made without it, the wrong priorities get embedded.
As the program moves toward go-live, the commitment shifts rather than disappears. It becomes about visibility: reinforcing the priority and making training non-negotiable, with the right people allocated to do the work. The change team can prepare the messages, find the moments, and build the forums. The sponsor's job is to show up with authority and consistency.
This is where a sponsor coalition matters. A single sponsor, however engaged, can't carry an enterprise-wide transformation alone. The coalition needs leaders from the regions and functions most affected, not as a gesture of inclusion but as an operational necessity. Brought in, they become owners of the change for their areas. Left out, they become resisters. Organizations that build the coalition before selecting an implementation partner are far better positioned than those who scramble to assemble one mid-implementation.
How much time this really takes
Less than most executives fear, when a capable change team is behind them. The commitment ebbs and flows. Early on, when key decisions are being made, weekly engagement is right. Through configuration, every other week. As go-live approaches, the cadence picks back up around testing, training, and milestone communications. None of it is open-ended, and a well-built Sponsor Plan makes each commitment explicit.
The reframe that tends to land: time spent upfront isn't added to the cost of the program. It's the alternative to a much larger cost later, in extended adoption curves, remediation, and value that never shows up.
Is your ERP transformation set up to succeed on the people side?
Prosci works with organizations at every stage of ERP implementation to make sponsorship structured, active, and tied to results. If you're concerned your sponsorship model isn't where it needs to be, talk to a Prosci consultant.