Why can an ERP be live but still underperform?
An ERP system can be live and still underperform when the business has not moved from project completion to managed value recovery. The warning signs are usually familiar: users export data, rebuild reports in spreadsheets, rekey information, avoid standard processes and question the numbers. The issue is rarely one fault. It is usually a mix of adoption, process design, data quality, reporting trust and support ownership.
Go-live is not the point where ERP value is secured. It is the point where value starts being tested.
During selection and delivery, the focus is often on scope, build, migration, testing and the launch date. Those things matter. Yet the real test comes when finance, operations, warehouse, production, sales and leadership teams start using the system under normal pressure.
That is when weak spots surface.
A report takes too long to produce. A team exports data because the standard view does not answer the management question. A planner keeps a separate tracker because stock confidence is low. A finance user rechecks figures outside the system before month-end. A department head asks for “the real numbers” because different teams are seeing different versions of performance.
None of this means the ERP was the wrong choice. For organisations using Dynamics 365, Business Central or Dynamics 365 Finance & Supply Chain Management, the system may be capable enough. The gap may sit in how the system has been adopted, governed, configured, supported or measured after launch.
That distinction matters because it changes the next decision.
If leaders treat ERP underperformance as a software failure, they may rush towards replacement, extra tools or more reporting layers before the real cause is clear. If they treat it as an operating problem, they can diagnose where value is leaking and recover it in a lower-risk way.
The most useful question is not, “Did the ERP go live?”
It is, “Can the business run from it with confidence?”
That means looking at outcomes the board and leadership team can feel: fewer manual workarounds, cleaner data, faster reporting cycles, stronger controls, clearer ownership and better decisions. ERP optimisation should start there, not with a list of features.
A practical ERP health check gives leaders a safer first step. It tests whether the problem sits in process design, user experience, data quality, integrations, training, reporting logic, support model or business ownership. It also separates quick wins from deeper redesign work.
The goal is not to blame the project team or the users. The goal is to find out why the system is not yet trusted enough to become the business’s real operating core.
Spreadsheets are not the problem. They are the signal.
When teams keep building spreadsheets around a live ERP, they are usually telling you something useful: the system is not yet trusted enough for daily decision-making. The workaround may look like personal preference, but it often points to a deeper issue in data quality, process fit, reporting design or user confidence.
A finance team may export trial balance data before producing a board pack. A warehouse manager may keep a shadow stock file because transactions are not posted consistently. A planner may run demand calculations outside the ERP because the standard process does not reflect operational reality. A sales or service team may rekey information because the integration between systems is incomplete or unreliable.
Each workaround solves a short-term frustration. At business level, it creates a control problem.
The risk is not Excel itself. Most businesses use spreadsheets sensibly. The risk appears when spreadsheets become the unofficial system of record. At that point, leaders may be making decisions from information that is late, manually adjusted, inconsistently owned or detached from the process that created it.
The ERP Workaround Risk Map
| Weak input | Visible workaround | Business risk | Diagnostic question |
| Poor master data | Users cleanse exports manually | Reports become slow and disputed | Which data fields are not trusted, and who owns them? |
| Process does not match daily work | Teams create side trackers | The ERP stops reflecting reality | Where does the standard process break under pressure? |
| Reporting gaps | Managers rebuild reports offline | Leadership sees conflicting numbers | Which decisions cannot be made from ERP reports today? |
| Weak integration | Users rekey between systems | Errors, delay and duplicate effort increase | Which handovers still depend on manual transfer? |
| Low user confidence | Teams keep shadow records | Adoption falls and support demand rises | What do users check outside the system before acting? |
This is where many organisations misread the problem. They ask for more dashboards when the real issue is that the underlying inputs are weak. A dashboard built on inconsistent transactions does not create confidence. It simply makes inconsistent working habits easier to see.
For Dynamics 365, Business Central and Dynamics 365 Finance & Supply Chain Management, better reporting depends on the foundations: clear process ownership, clean data, usable role-based screens, reliable integrations and support that closes the loop between user frustration and system improvement.
The practical next step is to catalogue workarounds without judgement. Which files are business-critical? Which reports are rebuilt every month? Which teams export before they trust? Which manual checks are protecting the business from errors the ERP should prevent?
That evidence gives leaders a sharper view of where ERP optimisation should begin. Not with a vague push for “better adoption”, but with the specific points where people step outside the system to protect speed, accuracy or control.
Weak adoption turns ERP into an expensive reference point
Weak ERP adoption is not a user behaviour problem first. It is a business performance problem. When people do not use the system consistently, leaders lose the one thing ERP was meant to protect: a reliable view of how work, cost, stock, orders and performance move through the business.
The system may still be live. Transactions may still be processed. Month-end may still happen. Yet if teams only use the ERP when they have to, and then rely on private checks before they act, the business has not gained a true operating platform. It has gained a formal record that people work around.
The causes are often practical. Training may have focused on launch rather than proficiency. Role-based screens may not reflect how people actually work. Super-users may have drifted back into full-time operational roles. Process owners may be unclear. Integration issues may create enough friction for users to build their own routes around the system.
Leadership feels the cost of that drift quickly. Decisions slow down because numbers need checking. Reporting becomes patchy because teams define the same measure differently. Managers spend time reconciling rather than improving. IT receives more support tickets, yet the same root issues keep returning.
The TRUST Test for ERP Value Recovery
Use this five-part test to judge whether poor ERP outcomes are really adoption, process or ownership issues.
| TRUST factor | What to check | Why it matters |
| Trusted data | Are key records complete, current and owned? | Bad data weakens every report and workflow built on it. |
| Role-fit | Do screens, tasks and approvals match daily work? | Poor fit pushes users back to offline habits. |
| User confidence | Do teams trust the system enough to act without rechecking? | Low confidence creates delay and duplicate effort. |
| Support ownership | Is there a clear route from issue to fix to learning? | Unresolved friction becomes accepted workaround. |
| Targeted improvement | Is there a prioritised backlog tied to business value? | Optimisation needs focus, not a growing wish list. |
This is where a proactive ERP partner makes a measurable difference. For Dynamics 365, Business Central and Dynamics 365 Finance & Supply Chain Management, value is rarely recovered by adding isolated features. It is recovered by improving the way people, process, data and support work together.
GO ERP’s role in this conversation is practical: diagnose the adoption gap, identify where the system is not supporting the way work happens, and build a safer route to improvement. That may mean retraining key user groups, simplifying screens, reviewing reporting logic, fixing integrations, tightening permissions, clarifying process ownership or reshaping the support model.
The strongest ERP systems are not merely available. They are trusted, used and improved.
Diagnose before you spend again
The first fix for ERP underperformance is structured diagnosis, not another rushed technology decision. Replacing systems, buying add-ons or commissioning new reports can increase cost before leaders understand where value is leaking. A good ERP health check shows whether the issue sits in process, data, integration, adoption, support or ownership.
That diagnosis should be practical, not theoretical. It should review how the system is used in daily work, where people step outside it, which reports are trusted, which processes create rework, and which problems keep returning through support.
ERP value recovery decision checklist
| What you find | Likely issue | Sensible next step |
| Reports are rebuilt offline | Weak data or reporting logic | Review data quality, report design and KPI definitions |
| Users keep side trackers | Poor process fit or confidence | Map the workaround and redesign the process step |
| Support tickets repeat | Root cause not being fixed | Review support ownership and escalation routes |
| Teams avoid certain screens | Poor role-fit or training gap | Simplify user experience and refresh role-based training |
| Systems need rekeying | Integration or handover weakness | Assess integration points and manual transfer risks |
| Leaders lack one version of performance | Ownership and governance gap | Define data ownership, reporting rules and improvement cadence |
For Microsoft Dynamics 365, Business Central or Dynamics 365 Finance & Supply Chain Management, this review can often reveal quick wins: removing duplicate fields, correcting master data, simplifying approval flows, improving dashboards, fixing broken handovers, retraining key users or prioritising a backlog around business value.
The point is sequencing. Diagnose first. Then decide what deserves investment.
FAQs
Why are teams still using spreadsheets after ERP go-live?
Teams usually keep spreadsheets when they do not fully trust the ERP process, data, report or user experience. The spreadsheet is a symptom. The cause may be poor adoption, weak master data, missing reports, integration friction or unclear ownership.
What is ERP optimisation?
ERP optimisation is the process of improving a live ERP system so it works better for the business. It can include process refinement, data clean-up, reporting improvements, user training, configuration changes, integration fixes and support model improvements.
When do we need an ERP health check?
An ERP health check is useful when users rely on workarounds, leaders dispute reports, processes feel slower than expected, support demand is rising or the business cannot clearly see the value it expected after go-live.
Should we replace or optimise our existing ERP?
Replacement should not be the first assumption. Many ERP problems come from adoption, process, data or support gaps rather than the platform itself. A structured review helps leaders decide whether to optimise, remediate or plan a larger change.
ERP value recovery works best when it is calm, evidence-led and commercially grounded. GO ERP can support that through a focused ERP optimisation review or value recovery workshop, looking at how your Microsoft business applications are really being used and where practical improvements will protect control, reporting confidence and spend.
