‹ Back

Why Your ERP Went Live But Nothing Actually Changed.

Your ERP went live. The go-live party happened. The project was declared a success. And six months later your operations team is still running on spreadsheets, your planners are still overriding the system, and leadership is still asking why delivery performance hasn't improved.

 

If this is your situation, you are not alone. After 26 years of supply chain transformation work across companies like NetApp, Fitbit, and Cummins, I have seen this pattern more times than I can count. And almost every time, the root cause is the same.

 

The ERP worked exactly as designed. The operating model did not change to use it.

 

 

What ERP Actually Does (and Doesn't Do)

An ERP system is a data platform and process engine. It captures transactions, enforces data rules, and generates plans based on the logic you configured. What it cannot do is change how your organization makes decisions.

 

When a demand planner ignores the system forecast and builds their own version in Excel, that is not a system failure. It is a signal that the system's output is not trusted — and trust problems are organizational problems, not technical ones.

 

When a Supply Chain Manager overrides the production plan three days before month end, that is not a discipline failure. It is a signal that no one has clearly defined who owns that decision, what triggers it, and what information it should be based on.

 

The Three Gaps That Survive Every ERP Implementation

In almost every post-ERP environment I have walked into, I find the same three structural gaps that no software can fix:

 

Gap 1 — Decision Rights Are Undefined

Nobody explicitly defined who can change the plan, under what conditions, and using what information. So everyone does. The plan becomes a suggestion. Execution becomes whoever shouted loudest this morning.

 

Gap 2 — Planning Cadence Was Not Redesigned

The S&OP or planning meeting rhythm that existed before the ERP was not redesigned to align with how the new system generates and publishes information. Teams are meeting on the old schedule to review data that the system refreshed on a different cycle. The conversation is always behind.

 

Gap 3 — Master Data Was Not Governed Post Go-Live

Lead times, lot sizes, safety stock parameters — these were set during implementation based on best guesses or historical data that was already stale. Nobody owns updating them. Six months later the system is planning based on parameters that no longer reflect reality, and every planner knows it.

 

What I did at a High-Tech Manufacturing Client

When I led the supply chain planning transformation for a high-tech manufacturing client, across two separate engagements, the technical implementation — Oracle ERP and SAP IBP — was only part of the work. The harder part was redesigning how the planning organization actually functioned inside the system.

 

We built constraint-based IBP models that forced the planning process to account for real capacity limits rather than optimistic assumptions. We eliminated shadow planning systems — the Excel files, the offline trackers, the 'real' version of the plan that lived in someone's personal drive. And we built executive scenario planning capabilities that let leadership see the real trade-offs between service levels, inventory investment, and revenue risk before making decisions.

 

The result was a planning process that leadership trusted enough to actually use. Forecast accuracy improved from around 35% error down to under 15%. Not because the algorithm got smarter. Because the governance around it got designed.

 

What to Do If You Recognize This Pattern

If your ERP is live and execution still feels broken, the first step is a diagnostic — not another software implementation. The diagnostic should answer three questions:

• Where are decisions actually being made, and are they the right people using the right information?

• Is your planning cadence aligned with how your ERP generates and refreshes data?

• Does anyone own master data governance, and is it current?

 

These questions take 2-3 weeks to answer properly if you know where to look. What they reveal usually explains most of the operational friction that has persisted since go-live.

 

 

Frequently Asked Questions

 

Q: How long after ERP go-live should operations be stable?

A: Most organizations expect 3-6 months for stabilization. If you are beyond 6 months and still firefighting daily, the issue is structural — not a stabilization curve.

 

Q: Is this a change management problem or a process problem?

A: Usually both, but change management alone will not fix undefined decision rights. You need both governance design and organizational alignment.

 

Q: Do we need another consultant or can we fix this internally?

A: Internal teams can absolutely fix this with the right framework. The challenge is that the people closest to the problem are also inside it. An external perspective on where the decision architecture is broken is usually faster and more objective.

 

If you are an Operations Leader and this pattern sounds familiar, a 30-minute Ops Clarity Call can usually identify the 2-3 specific gaps that are driving most of the friction. No pitch, no deck — just a structured diagnostic conversation.