The ERP Project Nobody Will Call
Monday, 9:00 a.m. Steering committee. Month fourteen of a nine-month ERP project.
The status slide says Yellow. It has said Yellow since April.
The CFO asks, "Are we on track for go-live?"
The IT director says, "We're working through some data issues."
The integrator says, "We're confident in the revised timeline." It's the third revised timeline.
Meanwhile, the warehouse is running on a spreadsheet called FINAL_v7_REAL.xlsx.
Everyone in the room knows the project is in trouble. Nobody says it. (This is a composite of several leadership teams. If it sounds like yours, you're not alone.)
What's really going on
An ERP project is a business decision dressed up as an IT project.
Finance wants clean books. Operations wants accurate inventory. Sales wants nothing to change, ever. Those are real disagreements about priorities. On most teams, they never get resolved in the room. They get configured instead, one customization at a time.
So why won't anyone call it?
Calling it means admitting the executive team was never aligned on what the project was for.
Calling it means someone has to own the money already spent.
Calling it feels like blaming a colleague, and nobody wants to be the one who "killed" the project.
So the slide stays Yellow. And Yellow becomes a place people live.
Signs it's happening in your organization
The status has been Yellow for months, but never Red.
Go-live has moved more than once, and the reason is always "data."
Steering committee meetings are presentations, not decisions.
Departments are quietly building workarounds.
Only the integrator can explain the plan.
Executives call it "IT's project."
The honest conversations happen in the parking lot.
What it costs
You're in crowded company. Gartner predicts that by 2027, more than 70% of recently implemented ERP initiatives will fail to fully meet their original business goals. As many as 25% will fail catastrophically.
Gartner also names strong alignment between the ERP initiative and corporate strategy as one of the top predictors of success. Yet in one survey Gartner cites, 75% of ERP strategies were not strongly aligned with overall business strategy.
Translation: the software usually isn't the problem. The leadership team is.
Then there are the costs no study captures. Your best people burn out covering the gaps. Trust between departments erodes. And every month the project drifts, the organization learns that bad news is something you manage, not something you say.
What to do instead
Call it out loud. Schedule a reset meeting, not another status meeting. Its only agenda item: "Where are we, really?"
Re-agree on what "done" means. Pick the three business outcomes this project must deliver. Not features. Outcomes. If the executive team can't agree on three, that's your real problem, and now you know it.
Give the business an owner. An ERP project needs an executive owner from the business side, not just IT. Someone who can make trade-offs across departments and is accountable for results.
Make the steering committee decide. Every meeting ends with a decision, an owner, and a date. If nothing was decided, it wasn't a steering committee. It was a slideshow.
Make Red safe. Thank the first person who calls something Red. Out loud. In front of everyone. You'll get more honesty, faster, and you'll execute on real information instead of wishful thinking.
The question for your team
If your biggest initiative were a patient, would anyone on your team read the chart out loud?
If the honest answer is "not in the meeting," let's talk. Book a 30-minute conversation.
Sources
Gartner, "What IT Leaders Must Do to Avoid Disappointing ERP Initiatives": gartner.com
Gartner, "Enterprise Resource Planning (ERP)" overview: gartner.com