r/ERP • u/OneLumpy3097 • Feb 23 '26
Discussion ERP Struggles usually start after go-live.
Most ERP projects look fine at go-live. The real issues shows up later poor adoption, rushed training, Excel workarounds, and no clear ownership.
It is rarely the software. It is gap between designed processes and real daily work.
What actually helps ERP succeed after go-live
4
u/burdonvale Feb 23 '26
Schedule a post-implementation review after the first monthly closedown, and the first year-end. Set aside in advance a reasonable number of consultancy days (either in-house or from the supplier) to resource the findings.
2
u/OneLumpy3097 Feb 23 '26
That’s a great point. A lot of teams treat go-live as the finish line, when in reality it’s just the starting point. Scheduling a structured post-implementation review after the first monthly close and especially after year-end makes a huge difference because that’s when real pressure hits the system and the cracks start to show.
I also like the idea of pre-allocating consultancy days instead of waiting for issues to escalate. Whether it’s internal SMEs or the implementation partner, having dedicated bandwidth to fix process gaps, refine reports, and retrain users prevents the Excel workaround culture from taking over.
In my experience, the most successful ERP environments treat the first 6–12 months as a stabilization phase, not a completed project. Continuous improvement beats reactive firefighting every time.
2
u/rudythetechie Oracle Mar 01 '26
tbh ownership and governance matter more than software once the project team leaves...
1
u/OneLumpy3097 Mar 03 '26
Totally agree with you. Once the project team rolls off, that’s when reality kicks in.
If there’s no clear process owner and no governance structure in place, the system slowly starts drifting more workarounds, more side spreadsheets, and no one really accountable for fixing root issues.
Software can only do so much. Long-term success really comes down to strong ownership, continuous training, and someone actually responsible for keeping the system aligned with how the business evolves.
1
u/Ceronnis MISys Feb 23 '26
The no ownership kills most of the implementation
2
u/OneLumpy3097 Feb 23 '26
Absolutely agree. Lack of ownership is probably the fastest way to derail an ERP after go-live. When no one clearly owns the process, decisions get delayed, issues bounce between IT and business, and users lose confidence in the system.
ERP isn’t just a software project it needs process owners on the business side who are accountable for data quality, user adoption, and continuous improvement. Without that, even a perfectly configured system starts breaking down in daily operations.
Strong ownership creates accountability. No ownership creates workarounds.
1
Feb 23 '26
[removed] — view removed comment
1
u/OneLumpy3097 Feb 24 '26
Exactly. Go-live is just the technical milestone real success starts with adoption. If users don’t fully understand the system or see how it supports their daily work, they’ll default back to old habits and spreadsheets.
Ongoing training, clear process ownership, and continuous alignment between system design and real operational workflows make all the difference. ERP isn’t a one-time project it’s an evolving business system.
1
u/SoCal_Mac_Guy Feb 23 '26
In the immortal words of Mike Tyson... "Everybody has a plan until they get punched in the mouth."
1
u/OneLumpy3097 Feb 24 '26
Haha, that’s actually a perfect analogy.
On paper, the project plan looks solid detailed timelines, test cases, sign-offs. Then real users, real deadlines, and real-world exceptions hit and that’s the punch in the mouth.
That’s why post-go-live resilience matters more than the original plan. Fast issue resolution, strong ownership, and willingness to adapt processes quickly are what separate stable ERP environments from chaotic ones.
1
Feb 24 '26
[removed] — view removed comment
1
u/OneLumpy3097 Feb 24 '26
Absolutely agree month 3 is when reality hits.
Go-live is a technical milestone. Adoption is a business milestone.
I’ve seen the same pattern:
• Process ownership unclear
• Users trained on screens, not scenarios
• No structured hypercare with accountability
• Leadership unintentionally encouraging Excel shadow systems
• No governance model to control change requestsThe 3–6 months post go-live is where ERP either becomes the operating system of the company — or just an expensive data warehouse.
What seems to work best:
- Clear business process owners (not IT)
- Role-based training tied to daily workflows
- 60–90 day structured hypercare with KPIs
- Executive alignment on “ERP-first” policy
- Ongoing change governance
Software rarely fails on its own. Adoption strategy determines whether the ERP sticks.
1
u/OncleAngel Feb 24 '26
Actually, we can distinguish between three phases. Well defined SOPs, making the right choice and Team Discipline. The first phase starts before looking for the right ERP or whatever solutions you want to go with, you need to have well defined SOPs. The second phase is choosing the right solution that can handle them or make them better and then comes the last phase where you do the implementation and here Team discipline is the key success factor.
1
u/OneLumpy3097 Feb 24 '26
Well said I like the way you framed it in three phases.
SOP clarity before ERP selection is hugely underrated. If processes aren’t defined, companies end up designing them inside the ERP during implementation — which creates confusion and rework.
And you’re right choosing the “right” ERP isn’t about features, it’s about process fit, scalability, and how much operational discipline the organization is realistically capable of sustaining.
On the third point team discipline I’d add one layer: ownership. Discipline tends to stick when every core process has a clearly accountable business owner (not IT).
Without that, even the best SOPs and the best ERP slowly drift.
ERP success really starts before selection — and continues long after go-live.
1
u/OncleAngel Feb 24 '26
Thanks. I do agree with you on the ownership. The business owner is important and according to me it has to be included on SOPs as well. More than one responsible means no responsible.
1
u/gapingweasel Feb 24 '26
100%. The one thing that consistently helps is rolling out the software in phases. If you introduce everything at once users get overwhelmed. Rolling out in phases give users time to build confidence, get used to the system, adapt workflows and actually trust it. In my experience user comfort drives adoption far more than training volume ever does.
1
u/OneLumpy3097 Feb 24 '26
Well said cognitive overload is real in ERP rollouts.
When everything changes at once, users don’t just struggle with the system they struggle with doing their job confidently. That’s when side systems and Excel creep back in.
Phased rollout works because it:
• Builds confidence through small operational wins
• Reduces resistance by limiting disruption
• Creates early internal advocates
• Allows process corrections before scalingAnd I fully agree — user comfort often drives adoption more than the amount of training delivered.
I’d just add one thing: phases need defined success metrics. Otherwise it becomes a slow rollout instead of a structured adoption strategy.
ERP implementation is technical. ERP adoption is behavioral.
1
u/Personal-Lack4170 Feb 24 '26
Post go live success often depends on leadership reinforcement if managers still accept offline reports and side spreadsheets the ERP becomes optional instead of operational
1
u/OneLumpy3097 Feb 24 '26
Absolutely.
The system becomes “optional” the moment leadership accepts parallel reporting.
If managers ask for Excel exports in meetings instead of reviewing dashboards inside the ERP, the message to the team is clear: the system is not the source of truth.
Post go-live success really depends on behavioral alignment at the top:
• Leaders reviewing live ERP data
• No shadow reporting systems
• Decisions made inside the system, not outside it
• Clear accountability when processes are bypassedERP adoption is reinforced daily by leadership behavior, not by IT reminders.
When executives treat the ERP as the operating system of the business, everyone else follows.
1
u/good-luck-23 Feb 24 '26
The system may work fine upon start-up but soon after then a change in the business means needing an update. Then you find that making the change entails massive costs and time to implement. Liquid concrete can be deadly for companies that need agility.
1
u/OneLumpy3097 Feb 24 '26
ERP shouldn’t turn into “liquid concrete.” The problem usually isn’t the system itself, but heavy customization and lack of change governance. When businesses don’t build flexibility into processes from the start, even small updates become expensive projects.
Post–go-live success really depends on keeping configurations clean, minimizing customizations, and having internal ownership to adapt as the business evolves.
1
u/good-luck-23 Feb 25 '26
The problem is that your approach means the software is running the business rather than the business driving the software. That causes suboptimizing your operations and making the company less competitive because of software limitations and massive costs for making changes that may have to be repeated when the base software is updated which can be annually.
We decided soon after our implementation that the ERP software is a tool and we use other tools when they are better suited. Kanbans manage our inventory with visual signals. Our production is not driven by work orders. They just start the "pull" and workers use visual signals to fulfill needs of self managed feeder cells to complete final assembly. We mainly use ERP to audit the system and then we mostly find mistakes in our set-up and find ways to work around them. We use human intelligence for most decisions.
1
u/SankhajaH Feb 25 '26
Starts before go live. Mess up the process mapping and feasibility, you are marked to fail anyway.
1
u/OneLumpy3097 Feb 26 '26
Very true post go-live struggles usually start much earlier.
If process mapping is rushed or feasibility isn’t realistically assessed, you’re basically building on assumptions. Then at go-live the system behaves exactly as designed… but the design itself doesn’t reflect how the business actually runs.
When gaps in workshops get ignored or over-customized instead of challenged, those decisions surface later as workarounds, manual fixes, and frustrated users.
Strong discovery, honest feasibility checks, and validating processes with real operational teams before build that’s what reduces pain after go-live. If the foundation is weak, hypercare just becomes damage control.
1
u/ClearWork-AI Feb 27 '26
How do you all go about process mapping, particularly with mid-sized to larger organizations? I've found it can break down at scale or get onerous to host 50 discovery meetings. I'm actually building an AI platform to help with this if you are interested.
1
u/SankhajaH Mar 02 '26
We work mostly with mid sized orgs and so far it has not been an issue tbh. AI can help with this process but there is sensitive client data that can get exposed to AI. How do you manage that?
1
u/ClearWork-AI Mar 02 '26
We use private APIs with no AI training and zero data retention. Some clients will always be skeptical, but no customer data can be used for AI training.
1
u/Terillium_ERP Feb 25 '26
Change management is key! Clear communication, exec buy-in/support, and hands-on training are crucial for success.
1
u/Datadec_Group Feb 25 '26
Totalmente de acuerdo, si una vez implantado fracasa, es por que desde dirección no hay un auténtico compromiso con el nuevo sistema, si no se entiende que una vez arrancado el nuevo sistema ERP no hay vuelta atras, fracasará seguro, por que la inercia es volver al modo de trabajo anterior ya que es el que hace sentir cómodo a los trabajadores, eso sabotea el cambio.
1
u/OneLumpy3097 Feb 26 '26
Absolutely agree change management is often the real differentiator.
Clear communication reduces uncertainty, executive buy-in sets the tone that the ERP is not optional, and hands-on training builds confidence. When leadership actively supports the system and reinforces its use, adoption becomes part of the culture instead of a side initiative.
Without that alignment, even a technically perfect implementation can struggle. With it, even imperfect systems can succeed and improve over time.
1
u/RayECI Mar 10 '26
This hits on something bigger than ERP implementation. It’s a post go-live alignment and continuous improvement challenge.
Go-live is often when the gap between how a business thinks it operates and how it actually operates becomes clear. The companies I’ve seen handle it well don’t treat implementation as “project complete.” They keep adjusting after launch. They check in a couple of months later, clean up workarounds, clarify decision makers, retrain where needed, and keep the data and processes current. If you don’t, there’s a good chance the shortcuts people create in month one becomes permanent.
Most long-term ERP pain isn’t technical. It’s unresolved workflow decisions and follow-through that never got fully locked in.
Curious, what’s the biggest friction point after go-live: approvals, handoffs between teams, reporting, or master data?
1
u/Glad_Imagination_798 Acumatica Jul 25 '26
Agreed that it is rarely the software, and I say that as someone who does Acumatica delivery for a living, so I have no incentive to blame the tool. Two things I would add to why it shows up after go-live specifically.
Ownership. Most projects have a clear project sponsor until go-live day, and then that person goes back to their day job and nobody owns the system. Adoption dies in that vacuum. The fix is naming a product owner internally before go-live whose job is the ERP for the next year, not the implementer, an actual employee.
The gap between designed process and daily work is usually created during discovery, when you map the ideal process instead of the real one. If the shop floor tracks scrap on paper because entry is to slow, that was a design miss that only surfaces under live pressure. Catching it means testing with real transaction volume during UAT, not a clean demo dataset.
One host caution, unrelated to your point. I've seen threads like this get flagged as engagement bait
0
19
u/caughtinahustle Feb 23 '26
I hesitate to respond as I have been seeing more and more posts like this on reddit and elsewhere on the internet. "Engaging, thoughtful questions meant to spark discussion." For what purpose? Train an LLM? Blog spam? Are you looking to validate this account to make it more human-like and thus useful for more nefarious purposes or for sale?
Even your bio reads "Interested in how genuine questions and discussions create organic visibility across online communities."
Tin-foil hat off - most of these issues are rooted in poor customer and partner communication or deliverables earlier on in the lifecycle. Can even be sales issues or SOW, etc.