Anand Naidu is a veteran in the ERP space, specializing in the critical transition from “launch” to “leverage.” With a deep understanding of both technical architecture and the human elements of digital transformation, he helps organizations navigate the often-turbulent waters that follow a system’s go-live date. In this discussion, we explore the post-go-live framework necessary to transform a static software implementation into a dynamic engine for business growth, focusing on stabilization, performance tuning, and the long-term governance required to prevent systems from becoming obsolete.
The first 90 days after an ERP launch often reveal gaps that initial testing missed. How do you distinguish between minor technical bugs and fundamental process misalignments during this phase, and what specific steps should a team take to stabilize data integrity without disrupting daily operations?
Within the first 30 to 90 days, the adrenaline of the launch fades and the reality of high-volume transactions sets in. We distinguish technical bugs—like a button not triggering or an access control error—from process misalignments by looking at where users are consistently overriding the system’s logic or struggling with transaction cycle times. To stabilize data integrity without stalling the business, teams must validate data in real-time while refining user access controls so that the right people have the right tools for their specific roles. It feels like a high-stakes balancing act where you are tuning an engine while the car is moving at sixty miles per hour. By focusing on operational reliability during this window, we prevent early frustrations from hardening into a permanent distrust of the new platform and ensure the system becomes a reliable part of daily life.
Approval bottlenecks and reporting delays often persist even after a system becomes operational. What measurable indicators should leaders track to identify these inefficiencies, and how can configuration adjustments—like refining approval thresholds—be implemented to improve cycle times while maintaining strict internal controls?
When leaders see approval bottlenecks, they need to look at hard metrics like transaction cycle times for order processing and financial closing. If a support ticket for a “stuck” approval keeps appearing, it’s a sensory signal that your configuration is too rigid for the speed of your business and requires immediate attention. We address this by making granular configuration adjustments, such as refining approval thresholds or simplifying the flow of digital documents to remove unnecessary human intervention. It’s about finding that sweet spot where internal controls remain ironclad but the workflow feels fluid and intuitive for the staff. Using dashboards to track these shifts ensures that every small adjustment compounds into a significant measurable gain in overall efficiency and reporting reliability.
Without clear ownership, ERP systems can quickly become outdated as business priorities shift. How should an organization structure its post-launch governance to ensure accountability for KPI tracking, and what specific risks arise when responsibility for system oversight is fragmented across different departments?
Fragmented ownership is perhaps the silent killer of ERP value because when everyone is responsible for a system, effectively no one is held accountable for its long-term health. To combat this, organizations must establish a strict governance rhythm, involving monthly or quarterly performance reviews that link system usage directly to strategic business objectives. Without a designated owner for data integrity and KPI tracking, you risk a scenario where reporting accuracy drifts and access controls become a tangled mess that no longer serves the business. This fragmentation creates a vacuum where the system begins to age prematurely, losing its alignment with the company’s shifting priorities and growth plans. By assigning clear accountability, you ensure that the ERP evolves alongside the business rather than becoming a relic of the day it was launched.
When operational teams encounter friction, they frequently revert to manual spreadsheets or workarounds. How can leadership systematically capture user feedback to refine workflows, and what specific metrics best demonstrate that a system is being used to its full potential rather than just being “active”?
The moment a team member opens a manual spreadsheet to do a job the ERP should handle, the implementation has failed in that specific moment, creating a hidden pocket of inefficiency. We capture this friction by encouraging operational teams to report “points of pain” immediately, treating user feedback as a roadmap for optimization rather than a list of complaints. To see if a system is truly reaching its potential, we look at user adoption metrics, specifically checking for a minimal reliance on external tools and consistent usage of core modules. It is about moving beyond “active” users—which is just a heartbeat—and looking for “optimized” users who are leveraging management dashboards for actionable insights. Seeing a team move from manual reconciliation to automated, real-time reporting provides a palpable sense of relief and professional empowerment for everyone involved.
Evaluating ERP success requires looking beyond simple system uptime to actual business impact. What is your process for conducting a periodic performance review that links automation gains to strategic growth, and how do you determine if a module is underused due to poor training versus poor design?
Evaluating success is a deep dive into how automation gains translate into actual strategic growth and measurable productivity gains across the organization. During our periodic performance reviews, we scrutinize whether a module is underused; if the design is sound but the usage is low, it’s almost always a training deficit that requires a more empathetic approach to user education. However, if the workflow itself is clunky and causes significant delays in financial closing or order processing, we recognize it as a design flaw that needs a configuration overhaul. We measure the business impact by looking at reduced manual tasks and the absolute reliability of the data coming out of the system. When a manager can finally trust their dashboard without double-checking the math in a side-file, we know the ERP has moved from a technical expense to a strategic asset.
Do you have any advice for our readers?
Never view your ERP go-live as a finish line or a completed project, because the real work of extracting value starts the day after you flip the switch. You must maintain a disciplined focus on the stabilization and optimization phases, treating the first 90 days as a critical learning period for the entire organization to find its footing. Build a culture where user feedback is valued and where governance is treated as a routine part of operations, much like a financial audit or a standard safety check. If you treat your ERP as a living system that requires continuous tuning and adjustment, it will support your growth for a decade; if you treat it as a “set it and forget it” tool, it will be obsolete in two years. Stay curious about your data, stay committed to the people using it every day, and always look for that next small refinement that can lead to a major competitive advantage.
