As ERP programs move beyond implementation, many organizations are facing a harder question: How to make modernization hold after launch. A system may be live, integrations may be running, and core transactions may be working, but the long-term value of ERP modernization depends on whether new workflows, governance structures, and operating practices become part of daily execution.
ERP Today features Tirumala Rao Chimpiri’s perspective because his work across ERP implementation, systems integration, modernization initiatives, and post-go-live support gives him direct experience with a persistent challenge in enterprise transformation: converting technically live ERP systems into sustained operational value.
Chimpiri is a senior ERP and enterprise technology professional and Chair of the IEEE Computer Society Long Island Section. His work spans financial services, telecommunications, manufacturing, logistics, public higher education, and public health environments, including large-scale ERP implementations, regional consolidation, reporting modernization, systems integration, and user support across North America, EMEA, and APAC. His comments focus on an area of ERP modernization that is often less visible than implementation itself: The operational discipline required after launch to ensure enterprise systems support consistent workflows, trusted information, stronger governance, and lasting business value.
In this conversation, Chimpiri discusses why ERP modernization often falls short after go-live, how adoption and governance shape long-term value, and what organizations should measure beyond technical launch milestones.
Q: Why do some ERP modernization programs struggle even after a successful go-live?
TRC: A successful go-live does not always mean the organization has achieved ERP modernization. In many ERP programs, go-live confirms that the system is available, users can log in, core transactions can be processed, and major defects have been addressed. Those are important milestones, but they do not automatically mean that workflows are better, users are comfortable with the system, or decisions are being carried out more consistently.
The post-go-live phase is where the real value of modernization is either realized or lost. A lot of attention usually goes into configuration, data conversion, testing, cutover and launch. Those activities are critical. But after go-live, the organization still has to stabilize the environment, support users, resolve issues, manage enhancements, and make sure the new processes are actually working in day-to-day operations.
That’s where problems often begin to appear. The ERP platform may be live, but users may continue relying on manual workarounds, spreadsheets, and informal approvals because the new way of working has not fully settled. In those situations, the organization has completed the implementation, but it has not fully changed how work gets done.
So, the issue is usually not that the ERP system failed. More often, the operating model around the system needs more attention after go-live. Adoption, workflow discipline, process ownership, support readiness and measurable business value all need to be managed beyond the launch date.
Q: What do leaders often miss when they define ERP success?
TRC: Leaders sometimes define ERP success too narrowly. They look at whether the system went live on time, whether major defects were resolved, whether integrations are running and whether core transactions are working. Those are important indicators, but they mainly show that the system is operational. They don’t always show whether modernization has been achieved.
The bigger question is whether the ERP environment is helping the organization work better after go-live. That means looking at process consistency, clearer approvals, reduced work outside the system, trusted reports, faster issue resolution, and more reliable information for planning and execution.
That’s where I’ve seen organizations miss the mark. They measure the launch, but they do not always measure whether the new environment is improving the way work actually gets done. ERP success should include implementation milestones, operational improvement, adoption, governance discipline, workflow reliability, and the ability to sustain value over time. Otherwise, an organization may complete a technology project without fully achieving business transformation.
Q: Where do post-go-live problems usually show up first?
TRC: In my experience, post-go-live problems usually show up first in the spaces between teams, processes and systems. I have seen this in ERP environments involving HR, finance, reporting, integrations, and external platforms, where the system may be technically working but the handoffs between functions still need stabilization.
Within one department or one module, the system may appear to be working well. Transactions may process, reports may run and users may be able to complete basic tasks. But when work crosses finance, procurement, HR, operations, student services, compliance or external systems, the gaps become more visible.
Common signs include approvals happening outside the system, users exporting data to spreadsheets, inconsistent use of workflows, and unclear ownership of exceptions. Delays in resolving cross-functional issues can also create confusion about whether a problem is technical, process-related, or ownership-related.
These are not always system defects. In many cases, they are signs that the organization is still adjusting how people, processes and systems work together after implementation.
That is why post-go-live stabilization needs to focus not only on fixing technical issues, but also on strengthening process ownership, accountability, workflow discipline and coordination across teams.
Q: How should organizations think about adoption after go-live?
TRC: Organizations should think about adoption as a behavior change, not just a training activity.
Training is important, but completing training does not necessarily mean users are adopting the new ERP environment in the way it was intended. In many organizations, users may understand the system but still return to old habits because the surrounding process is unclear, approvals are not aligned, reports are not trusted or workarounds feel faster.
That’s why adoption should be measured through actual usage after go-live: whether users complete work inside the ERP system, approvals follow the intended workflow, and exceptions are handled consistently. Leaders should also watch whether reports support decisions and whether teams reduce reliance on spreadsheets, email approvals, and side processes.
If users are still depending heavily on offline tracking or informal coordination, then adoption is incomplete even if the system is live. Process owners and support teams need to clarify expectations, address user concerns and make sure teams are not quietly rebuilding old processes outside the system. That is how adoption becomes part of sustained modernization rather than just temporary compliance after go-live.
Q: What role does governance play after implementation?
TRC: In the ERP environments I have worked with, governance becomes even more important after implementation because that is when ERP moves from a project environment into daily operations.
During implementation, governance is usually focused on project delivery. Teams are making decisions about scope, timeline, testing, defects, cutover and readiness. But after go-live, governance has to shift. It needs to become more operational.
That means having clear ownership for process decisions, workflow changes, data quality, security roles, reporting priorities, exception handling, enhancements and continuous improvement. Without that structure, the ERP environment can start to drift.
Different teams may interpret processes differently, create their own workarounds, request conflicting changes or rely on informal approvals. Over time, that weakens standardization and reduces the value of the modernization effort. Strong post-go-live governance helps protect the ERP investment. It keeps teams aligned on how the system should be used, how exceptions should be handled and how improvements should be prioritized. It also helps ensure that the platform continues to support consistent operations, not just successful transactions.
Q: What should leaders measure after go-live?
TRC: Leaders should measure whether the ERP system is actually improving how the organization works after go-live.
Technical metrics are still important. Uptime, ticket volume, batch completion, defect resolution, interface stability and system performance all matter. But those metrics mainly show whether the platform is running. They do not fully show whether modernization is creating operational value.
Post-go-live measurement should also look at business and process outcomes: workflow completion inside the system, consistent approvals, and fewer manual workarounds. It should also assess whether reports are trusted and cross-functional issues are being resolved faster.
It’s also important to see where users leave the system. In support and enhancement work, those exit points often reveal problems with workflow design, reporting trust, data quality, integration timing, or ownership. The goal is not to create too many metrics. The goal is to understand whether the ERP environment is improving adoption, workflow reliability, governance discipline and execution over time. That is how leaders can tell whether modernization is producing value after go-live.
Q: How can organizations reduce manual workarounds after ERP modernization?
TRC: Manual workarounds usually exist for a reason. They may indicate that a workflow is too slow, a report is not trusted, or an approval path is not aligned.
The first step is not simply to eliminate workarounds. Leaders and process owners need to understand why people are using them. Are users leaving the system because the process is too complex? Because data is not reliable? Because approvals are delayed? Because the system does not handle a real operational exception?
Once the reason is clear, the organization can respond in a targeted way. That might mean redesigning a workflow, clarifying process ownership, improving reporting, changing an approval path or creating a formal exception process.
The important point is that workarounds should be treated as diagnostic signals. They show where the ERP environment is not yet supporting the business effectively.
If organizations listen to those signals after go-live, they can improve the system and the operating model. If they ignore them, workarounds can become permanent side processes, and the organization gradually loses the standardization and control that ERP modernization was supposed to create.
Q: What advice would you give ERP leaders preparing for go-live?
TRC: Plan for post-go-live value as seriously as the go-live itself. Before launch, teams should define what success should look like three months, six months and one year after go-live. That should include not only whether the system is stable, but whether the organization is improving the way work gets done.
That means identifying the most important business outcomes, assigning ownership for key processes, and establishing post-go-live governance. It also means defining how enhancements and exceptions will be managed, and deciding how adoption and value will be measured.
ERP modernization should not end when the system becomes available. Go-live is an important milestone, but it is also the start of value realization. The organization still needs to stabilize, reinforce adoption, reduce workarounds, improve workflows and make sure the new environment supports better decisions and more consistent execution.
Looking Ahead
As organizations continue investing in cloud platforms and ERP modernization, the post-go-live phase remains a critical test of whether transformation efforts translate into operational value. Chimpiri’s perspective shows that the work after launch is not simply support activity, but a continuation of modernization itself.
For ERP leaders, the distinction is crucial. A system can launch successfully and still fall short if workflows, governance, reporting, and process ownership are not reinforced in daily operations. Lasting ERP value depends less on the launch milestone alone and more on whether organizations can sustain new ways of working after implementation.
