A direct letter to the C-Suite executive who greenlit an ERP implementation they now regret — and who feels too deep in to turn back.

You approved it. You signed the business case, shook hands with the vendor, and stood in front of your board and declared it transformational. Eighteen months later, you are sitting across from a project that is over budget, under-delivered, and politically radioactive. Your team is exhausted. Your CFO is asking questions you do not have clean answers to. And quietly, in the back of your mind, a thought keeps surfacing: I made a mistake.

This article is for you. Not to judge the decision. Not to relitigate it. But to help you understand what kind of decision you made — and more importantly, what to do now.

“One wrong choice doesn’t end the story. It changes the direction. And direction, unlike a decision, can always be redirected.”

In technology strategy, there are two kinds of decisions. Reversible ones — where you can course-correct cheaply. And one-way doors — where once you walk through, the cost of going back is enormous. ERP selection is almost always the latter.

A bad one-way decision in ERP doesn’t just affect your technology stack. It begins reshaping everything downstream: your team’s habits, your operating model, your organisation’s behaviour, your data integrity, and ultimately, the culture of how your people interact with systems. The ripple doesn’t stop at go-live. It keeps moving.

And here is what no one tells the Project Sponsor: you don’t just feel the business impact. You feel it personally. There is guilt — a quiet regretting of the original choice. There is pain — the tension of trying to preserve your professional credibility while the platform struggles to perform. And there is shame — for the meetings you can no longer walk into with confidence, for the benefits that were promised and not realised.

That emotional weight is real. And it is also a distraction from the only question that matters now: what do you do from here?

The single most dangerous thing a C-Suite executive does after a bad ERP decision is double down to protect the original call. You’ve seen it. The escalating commitment. The “we just need to push through.” The refusal to re-scope because re-scoping feels like admitting failure. It is not failure. It is adaptation. And adaptation is the only currency that matters now.

Here is the truth your advisors may not be saying directly: the organisation already knows something is wrong. Your people know. Your middle managers know. The question is not whether this will be talked about — it already is. The question is whether you lead the narrative, or whether the narrative leads you.

“Commit: no more bad one-way decisions. That doesn’t mean paralysis — it means clarity. From here, every major call gets pressure-tested before it becomes irreversible.”

This is not about writing off what has been spent. It is about projecting the future you can actually construct — with the constraints you now have. That is a different, more honest, and ultimately more powerful exercise than the original business case.

First, name the situation clearly — internally first. Stop using language that obscures reality. “Challenges” and “learnings” are fine for public communications, but in your leadership team, speak plainly. A shared honest diagnosis is the foundation for any recovery.

Second, separate the sunk cost from the forward decision. What has been spent is gone. The only decision in front of you is: what is the best path forward from this position? Model three futures — continue as-is, re-scope aggressively, or strategic pivot — and evaluate each on forward cost and forward value only.

Third, change your relationship with the vendor — now. If the implementation partner is the wrong fit, that conversation cannot wait for the next steering committee. Renegotiate scope, escalate to executive contacts, bring in an independent advisor, or consider a structured exit. Silence is not a strategy.

Fourth, do a lot of work on yourself as a sponsor. This is the uncomfortable truth: ERP implementations fail most often at governance and sponsorship, not technology. Review your own involvement. Are you getting the right information? Are you making decisions fast enough? Are you shielding the team or creating pressure that distorts reporting upward?

Fifth, project your potential future — and commit to it publicly. Once you have a credible forward path, own it with the same conviction you brought to the original decision. Not false optimism — honest vision. Here is what we now know. Here is what we are doing. Here is what we will achieve. That shift in posture changes everything.

This is the part no one says out loud in a board presentation, but it is the part that matters most: you do not walk through an experience like this unchanged. The executives who handle failed ERP implementations with clarity, honesty, and decisive adaptation do not just survive professionally — they become markedly better leaders.

The sacrifice is real. There will be difficult conversations. There will be write-downs and re-forecasts. There will be a lot of work on yourself and your organisation. But on the other side of that work is something most executives never develop: the judgment that only comes from having navigated a high-stakes failure and chosen truth over self-protection. That judgment is worth far more than the avoided embarrassment of any single decision.

“Keep taking care of yourself and working hard to make your future goal your reality. The decision is behind you. The direction is still yours.”

If you are a Project Sponsor sitting inside a technology implementation that is not working, the most important thing you can do today is resist the urge to protect the past — and start building the most credible future you can construct from where you actually stand. The organisation is watching how you lead from here. Make it worth watching.