You did everything right. You hired a consulting firm. You evaluated vendors. You ran demos. You negotiated the contract. You went through a 12-month implementation. You went live on time and reasonably close to budget.
Six months later, you’re sitting in an operations review and you realize: nothing has actually changed.
Your quoting process still takes too long. Your on-time delivery is still inconsistent. Your team is still spending hours in spreadsheets reconciling data they don’t trust. The software is new. The problems are the same.
If this sounds familiar, you’re not alone. And the explanation is almost never the technology.
The selection process set you up to fail
The root cause of most underwhelming ERP implementations can be traced back to how the selection was run. Traditional ERP selection is built around a simple question: which software has the features we need?
That question produces a 500-line requirements matrix, a series of scripted vendor demos, a weighted scoring model, and ultimately a Statement of Work that says things like “configure Advanced Planning and Scheduling module” and “implement quality management workflows.”
Notice what’s missing. There is no target outcome. No measurable result the implementation is accountable for. No definition of what “success” looks like beyond going live.
Software doesn’t change organizations. Outcomes do.
An ERP system is an enabler, not a solution. If your on-time delivery is 68% today, new software alone will not make it 92%. That improvement requires changes to how your team plans, schedules, communicates, and makes decisions. The technology supports those changes, but it doesn’t create them.
When the selection process focuses on features, the implementation focuses on configuring features. Nobody is asking: what organizational changes need to happen alongside this technology for us to actually improve on-time delivery?
That question never gets asked because it was never part of the selection process. And if it wasn’t part of the selection, it won’t be part of the implementation.
What an outcomes-driven approach changes
When you start the selection process with business outcomes instead of software features, the entire downstream chain shifts.
The discovery phase quantifies what the current state is actually costing you: lost quotes, late deliveries, manual workarounds, margin erosion. These aren’t hypothetical. They’re measured.
The evaluation phase tests whether each vendor can help you achieve those specific outcomes, not whether they can check feature boxes.
And critically, the resulting Statement of Work reads differently. Instead of “configure APS module,” it says: “Improve on-time delivery from 68% to 92% within 6 months of go-live, with the following process changes, technology configurations, and organizational accountability.”
That’s a project the implementation team can actually deliver against. And it’s a result your operations team is motivated to achieve because they helped define it.
It’s not too late
If you’re already past go-live and wondering why nothing changed, the good news is that this work can happen retrospectively. The system you selected likely has the capability to support the outcomes you need. What’s missing is the clarity about what those outcomes are and the organizational commitment to achieving them.
Start by asking the question that should have been asked at the beginning: What does this company need to look like in 12 months, and what’s preventing us from getting there? The answer to that question will tell you exactly where to focus your optimization efforts and whether the technology gap is really a process, training, or change management gap instead.
Starting a new ERP evaluation?
Make sure the selection process sets you up for outcomes, not just software. Learn how our approach works →