Key takeaways
- ERP projects rarely fail overnight. Missed milestones, expanding scope and delayed decisions usually show up well before the project reaches a crisis point.
- Your software vendor manages its scope and risk. Your organization still needs clear internal ownership, governance and decision-making authority.
- Repeated testing issues may point to unclear requirements or inconsistent business processes, not just a system defect. Requirements need to be defined and tied to test cases from day one.
- If the project does not feel right, pause and reset. Continuing without addressing the root cause usually costs more than taking the time to correct it.
Moving to a new ERP is a major investment of time, money and internal capacity. When an implementation starts to drift, the cost is not limited to the software or the consulting fees. Your team spends more time in meetings, repeats work, delays decisions and loses confidence in the project.
The good news is that troubled implementations usually provide warning signs. The key is recognizing them early and being willing to address the problem before another missed milestone becomes the new plan.
Here are ERP implementation problems to be on the lookout for:
Milestones keep moving
The most visible sign that an ERP implementation is in trouble is a go-live date that keeps getting pushed back.
One delay can be a scheduling issue. Two can be a planning problem. When several milestones move, there is usually a deeper issue, such as unclear requirements, unresolved decisions, resource constraints or a team that is not ready to execute.
Do not focus only on the go-live date. If user acceptance testing sign-off keeps getting pushed back without a clear end date, that’s an early indicator something is wrong with the implementation. Testing shouldn’t run indefinitely. When it does, it’s usually a symptom, not the root cause.
Scope is expanding
If, during implementation, you find yourself adding new features, data migrations, business processes or integrations that weren’t part of your initial plan, that’s scope expansion. It can be one of the biggest causes of budget overruns, delays and user fatigue.
Think of it like a home renovation that starts with a kitchen remodel and ends up touching every room in the house, not because the plan changed, but because no one agreed on what “done” looked like from the start. Setting your requirements up front, locking in your project plan and establishing a clear escalation path for change management are the best defenses against runaway scope. Additional scope is not always bad, but unapproved or untracked scope can become problematic. Escalation plans and a consistent approach to tying requirements out to test cases and status reporting with IT and business sponsors can reduce implementation risk.
Users and leaders are disengaging
Low engagement is often treated as a “person” problem. So and so doesn’t understand or isn’t devoting enough time, or this person is not making decisions. Project leads may try to replace the “problem” when in reality it is more than that. The key is to ask why. It is usually a project management and change management problem. When an implementation drags on, steering committee members become less involved, process decisions stall and employees stop seeing how their work connects to the outcome.
People also disengage when they do not understand what the vendor is asking them to decide. Mid-market organizations may not have employees who have been through multiple ERP implementations. The project team needs enough context to understand the options, the trade-offs and what happens if a decision is delayed.
When leadership disengages, decisions do not get made. When decisions do not get made, tasks and testing fall behind. The impact compounds quickly.
Testing results in compounding defects
Testing failures don’t always mean the system is broken. Sometimes they reveal that an organization’s processes haven’t been thought through clearly enough and requirements went undefined. During testing, businesses often discover that each time someone runs a test case, a different issue arises that wasn’t on the radar.
Sometimes defects persist because the organization has lifted and shifted an old process from their legacy ERP without reconsidering whether it’s the most efficient and effective way to work.
Test cases need to be tied directly to business requirements. Often, businesses wait for the vendor implementer to tell them what the test cases should be, rather than doing the homework to identify what their business actually needs. Oftentimes, vendor implementers provide a ‘library’ of test cases that are generic. It is up to the business to align them to their processes. Risk rating requirements and tying requirements to test cases also help project leads right-size test scenarios to perceived risk.
Governance breakdowns
Poor governance is a common structural failure behind almost every troubled implementation. It’s hard to acknowledge until things start falling apart.
Governance breakdowns often stem from not having:
- Escalation paths
- Risk and issue logs
- A consistent project plan
- A consistent status reporting process
When roles and responsibilities aren’t clear, capacity planning becomes difficult or nonexistent and project tracking suffers, leading to unnecessary delays. Communication is a common challenge during implementation. Good governance improves communication.
Be sure your steering committee has the authority and clarity to make binding decisions.
Vendor accountability issues
There’s often a fundamental misunderstanding of what the vendor implementer is actually supposed to be doing. The implementer is managing their scope and managing risk for their own organization — not for yours. As the customer in this relationship, you need to manage risk for yourself. Organizations frequently overestimate what the project manager on the vendor side is going to do, and that leads directly to missed milestones, scope issues and cost overruns.
Communication with the vendor at the beginning of the project is key to establishing what the vendor is and isn’t accountable for. Your organization needs a strong internal program manager to steer the ship on your side and maintain constant communication with the vendor.
What to do if your ERP implementation is going sideways
The clearest advice for any leader who feels something is off is to stop and reset to avoid going further down the wrong path.
Start by looking at your project governance. Do you have requirements set? Is there someone internally responsible for ensuring all implementation tasks are completed? If you don’t have an internal lead identified, start there.
Typically, the problems that surface aren’t related to the original scope, but to people and process. When that’s the case, calling a time-out to reset governance and then move forward will save significant cost and stress.
Read more
Wipfli’s implementation risk advisory and optimization services provide an independent, real-time assessment of active technology implementations that identifies and mitigates risk across people, process and technology so organizations can course-correct or continue with confidence. Wipfli also has fractional support for project management, change management and business analyst/advisory. Put your implementation on the path to success.

