The ERP Implementation Failure Nobody Saw Coming — Until It Was Too Late
A CEO fired his VP of Technology after two years of missed milestones and shifting excuses on a critical ERP implementation. The warning signs were there from the beginning. Here is what they were — and the two services that could have prevented it.
The Call That Comes Too Late
We received a call from a CEO. He needed an interim CIO — immediately. His VP of Technology had just been fired.
The reason: nearly two years into a critical ERP implementation, the project was still not complete. Milestones had been missed repeatedly. Each time, the VP of Technology had an explanation — the business environment was complex, processes were inefficient, the vendor needed more time. The CEO, busy running the company, had given his IT leader the benefit of the doubt. He accepted the delays. He justified them.
Then came one more update. Another delay. Another new delivery date — this time six months out. The CEO pressed harder than he ever had before. He wanted to understand the real issues, not the summary. He asked the VP of Technology to go directly to the ERP vendor and get a committed date. The vendor came back with six more months.
That was the last conversation the VP of Technology had as an employee.
The CEO needed someone to come in with no political stake, assess the real situation honestly, define a path forward, and lead the implementation to completion. That is the call we received.
What Actually Went Wrong
The most visible failure in this story is integrity. The CEO's IT leader was not being honest — about the project's status, the risks, or the vendor's performance. That is the hardest thing to protect against, because it requires trust in a person, and some people do not operate with the transparency that role demands.
But beneath the integrity failure were structural problems that created the conditions for it:
- ▸No clearly defined implementation plan with milestones, owners, and dependencies
- ▸No independent project governance or executive steering committee
- ▸No mechanism for the CEO to independently verify project status
- ▸An ERP vendor with no accountability structure — delays accepted without consequence
- ▸Insufficient requirements definition at the start of the program
- ▸Possible skills gaps on the internal IT team and/or the vendor's delivery team
- ▸No project management discipline around change control and scope
Continually missing delivery dates is never just a scheduling problem. It is a symptom. The root causes are almost always found in one or more of these areas — and they are findable before the project spirals, if someone is looking.
This situation is not unusual. ERP implementation failures are one of the most documented and recurring problems in enterprise technology. Companies have lost hundreds of millions of dollars — and in some cases, their business entirely — to failed ERP programs. The pattern is almost always the same: a combination of poor planning, vendor misalignment, weak governance, and an IT leader who filtered the truth before it reached the executive team.
6 Warning Signs Every CEO Should Know
Looking back at this engagement, the warning signs were present well before the situation became irreversible. Here is what to watch for on any major technology initiative:
1. Milestone dates keep moving — with a different explanation each time
One missed deadline is a project problem. Repeated missed milestones with shifting explanations is a leadership and transparency problem. The underlying issues are not being surfaced, fixed, or reported honestly.
2. The IT leader meets with the vendor one-on-one to get status updates
When your IT leader is the only conduit between you and the ERP vendor, you are one layer removed from the truth. Vendors will tell your IT leader what your IT leader wants to hear. An independent voice in that room changes everything.
3. There is no formal project governance
No steering committee. No change control process. No formal escalation path. When governance is absent, problems get managed informally — which means they get managed inconsistently, or not at all.
4. The project plan is not visible to executives
If you have never seen the actual project plan — the detailed workplan with tasks, owners, dates, and dependencies — you do not have visibility into where the project actually stands. Status reports are summaries. The plan is the truth.
5. The vendor controls the timeline narrative
When the ERP vendor is the one setting new delivery dates — and your IT leader is simply relaying them — you have lost control of the program. The vendor's incentives are not aligned with yours. Their goal is to manage their own costs and exposure, not to deliver your business case.
6. Budget overruns are explained as 'scope changes'
Some scope change is normal. Continuous scope expansion is a symptom of insufficient requirements definition at the start, inadequate change control during execution, or a vendor that is expanding scope to cover their own delivery problems.
Two Services That Prevent This From Happening
This situation — a CEO blindsided by a two-year ERP failure — is preventable. It requires either the right IT leadership in the building from the start, or an independent set of eyes at the right moment. Full On Consulting offers both. But two specific services address exactly this scenario.
1. IT Assessment (IT Health Check)
The IT Assessment addresses the IT function itself — how it operates, the skills and capabilities of the IT team, the processes, the technologies, and how effectively IT serves the business. It is the service that answers the question the CEO in this story never thought to ask until it was too late: is my IT organization actually capable of delivering what I am asking of it?
The result is an honest grade across the critical dimensions of IT — people, processes, governance, technology, vendor management, and business alignment — along with a prioritized set of recommendations to get IT back on track.
Think of it as a small insurance policy. The cost of an IT Assessment is a fraction of what a single failed project will cost you. And the findings often surface issues that would have caused exactly the kind of failure described above.
2. Project & Program Assessment (Project Health Check)
The Project Assessment is specifically designed for companies that are about to launch — or are already running — a mission-critical technology implementation. This is the service that would have caught the ERP failure described above before it consumed two years and cost an executive his job.
Our team reviews the project plan, team skills and availability, governance processes, requirements documentation, vendor SOW and agreements, workplan structure, change control processes, and risk management approach. The output is an honest assessment of what is working, what is missing, and exactly what needs to happen to position the initiative for success.
When companies embark on mission-critical implementations — ERP, CRM, cloud migrations, platform rebuilds — they cannot afford to fail. The stakes are too high. A Project Assessment before launch, or at the first sign of trouble, is the most cost-effective intervention available.
What This Looks Like in Practice
We have seen this pattern across multiple engagements — a board with no visibility into what IT is actually doing, a CEO who received a C grade across six IT dimensions and had no idea, a global SAP program running without proper governance until it became an emergency. In every case, an independent assessment early in the process would have surfaced the problems before they became crises.
In the engagement described above, we stepped in as interim CIO, conducted an independent assessment of the ERP program, established proper governance, held the vendor accountable to a realistic plan, and drove the implementation to completion. The outcome was what the CEO needed. But it came at a significant cost — in time, money, and leadership disruption — that a Project Assessment at the start of the program would have largely prevented.
Don't Wait for the Crisis to Call Us
The most expensive version of this conversation is the one that happens after two years of missed milestones and a fired executive. The least expensive version is a direct conversation before the project launches — or at the first sign that something is off.
If you are a CEO or board member with a major technology initiative underway and any of the warning signs above sound familiar, let's talk. No sales pitch. Just a direct conversation about what you are seeing and what it may mean.
Frequently Asked Questions
What are the warning signs of a failing ERP implementation?
The most common warning signs of a failing ERP implementation are: repeated milestone delays with vague or shifting explanations; a project plan that lacks clear owners, dates, and dependencies; an IT leader who meets with the ERP vendor one-on-one without including the CEO or CFO; budget overruns justified as scope changes; a go-live date that keeps moving without a root cause analysis; and an absence of formal governance — no steering committee, no escalation process, no change control. Any one of these is a yellow flag. Multiple together is a serious problem.
What should a CEO do when an ERP implementation keeps missing deadlines?
When an ERP implementation repeatedly misses deadlines, a CEO should: stop accepting explanations and demand a root cause analysis; request an independent review of the project plan, vendor SOW, and staffing model; meet directly with the ERP vendor — not just through the IT leader; and bring in a senior outside advisor to give an unbiased view of where the project stands and what it will take to complete it. Waiting for the IT leader to self-report an accurate status is a high-risk strategy when the project is already off track.
What is an IT Project Assessment?
An IT Project Assessment (also called a Project Health Check) is an independent review of a technology project or program — typically conducted before a major initiative launches or when a project is showing signs of trouble. The assessment reviews the project plan, team skills and availability, vendor agreements and SOWs, governance processes, requirements definition, and risk management. The output is an honest scorecard of where the project stands and a prioritized list of actions needed to position the initiative for success. It is a small investment relative to the cost of a failed implementation.
What is an IT Assessment?
An IT Assessment (also called an IT Health Check) is a comprehensive review of the IT function — its people, processes, technologies, governance, and alignment with the business. It is typically conducted when a company suspects IT is underperforming, when a new executive wants an independent baseline, or when a board needs visibility into technology risk. The output is an honest grade of the IT organization across multiple dimensions, along with a prioritized roadmap of recommended improvements. Full On Consulting delivers IT Assessments in 6 to 10 weeks.
How much does an ERP implementation failure cost?
ERP implementation failures are among the most expensive technology disasters a company can experience. Research consistently shows that more than 50% of ERP implementations exceed budget, with average overruns of 24% to 59% above original estimates. Beyond direct costs, failed ERP implementations create operational disruption, lost productivity, executive credibility damage, and in some cases, material harm to the business — delayed invoicing, broken supply chains, compliance failures. The cost of a proper Project Assessment before launch is a fraction of one percent of the total program cost.