As a veteran in the field of enterprise architecture and digital transformation, Anand Naidu has spent years navigating the complex intersection of legacy systems and modern innovation. His recent oversight of massive ERP migrations has given him a unique vantage point on how global organizations can shed decades of technical debt to regain their competitive edge. In this discussion, he shares the strategic blueprint for moving toward a clean core, explaining how a disciplined approach to process standardization can actually unlock more agility than custom coding ever could.
Moving from 10 million lines of custom code to 95% process standardization is a massive shift. What specific cultural hurdles did your teams face during this transition, and how did you convince stakeholders that losing custom features would actually improve rather than hurt operational flexibility?
The primary cultural hurdle was overcoming the “not invented here” syndrome, where teams believed their unique ways of working were the secret sauce of the company’s success. When you have 10 million lines of custom code, people become emotionally attached to specific features they spent years perfecting, fearing that standardization means regression. We had to shift the narrative from “losing features” to “gaining speed,” demonstrating that heavy customization was actually a golden cage that made every update a multi-month nightmare. By showing stakeholders that a clean core allows us to adopt new innovations and cloud updates instantly, we convinced them that flexibility comes from a nimble platform, not from rigid, hard-coded logic.
Achieving a 50% reduction in documentation while standardizing nearly all global processes suggests a major cleanup. What specific criteria did you use to decide which workflows stayed and which were discarded, and how has this leaner approach changed the daily experience for employees on the ground?
Our cleanup was guided by the APQC Process Classification Framework, which allowed us to benchmark our internal workflows against global best practices to see where we were over-engineering. If a process didn’t provide a verifiable competitive advantage or meet a strict regulatory requirement, it was discarded in favor of the standard SAP S/4HANA Cloud template. This rigorous filtering led to a 50% reduction in documentation volume, which has been a breath of fresh air for our employees who previously struggled with fragmented and conflicting manuals. Now, the daily experience is defined by clarity; staff across three business units use the same 6,829 structured activities, meaning they spend less time figuring out “how” to work and more time actually delivering value.
Using process modeling alongside enterprise architecture visibility creates a powerful duo for transformation. How do these two disciplines interact to prevent new technical debt from creeping back in, and what metrics do you track to ensure the core remains clean as new business needs emerge?
The interaction between process intelligence and architectural visibility acts as a double-gatekeeper for the enterprise. We use SAP Signavio to model and govern the “business view” of how work flows, while SAP LeanIX provides the “IT view” by mapping every system dependency and integration point. This prevents technical debt because any request for a new customization must now be justified against both the process map and the architectural blueprint before a single line of code is written. To keep the core clean, we track the percentage of process standardization—which we’ve pushed to 95%—and the frequency of “out-of-the-box” feature adoption versus custom extensions.
Governance is often seen as a bottleneck, yet it can be redesigned as a proactive tool for agility. What structural changes were necessary to turn governance into an enabler of speed, and how does this new framework specifically accelerate technology decision-making for leadership during rapid market shifts?
We moved away from a “policing” model of governance to a “paving” model, where the Global Process Office provides pre-approved, standard paths for the business to follow. By establishing a single, integrated platform to govern our processes, we eliminated the long analysis cycles that usually happen when leadership tries to understand the impact of a change. Now, when a market shift occurs, leaders can look at our architectural transparency and see exactly which systems and roles are affected in real-time. This structural visibility reduces friction and allows us to make technology decisions based on data rather than gut feelings, drastically accelerating our reaction time.
Building a connected knowledge graph that links roles, systems, and performance insights is a sophisticated future goal. What are the practical, step-by-step phases required to implement this level of transparency, and how will it change the way staff access training and real-time performance data?
The implementation begins with mapping every role to a specific set of governed processes, ensuring that a “Warehouse Manager” in one country sees the exact same workflow as their counterpart elsewhere. The second phase involves layering system data onto these roles so that the software interface itself becomes the training manual, providing role-specific guidance directly within the workflow. Finally, we integrate performance insights so that real-time data flows back into the graph, identifying exactly where a process is lagging. For the staff, this means the end of generic training sessions; instead, they receive personalized, real-time performance feedback and support that is relevant to their specific tasks and tools.
What is your forecast for ERP modernization?
I predict that the era of the “monolithic, customized ERP” is officially over, and we are moving toward a “composable, clean-core” future where the ERP acts merely as a stable foundation. In the next five years, the focus will shift entirely from building features to orchestrating processes, as AI-driven insights become standard in every workflow. Organizations that fail to standardize their core today will find themselves unable to integrate the AI tools of tomorrow, while those with disciplined architectures will see their innovation cycles shrink from years to weeks. Success will no longer be measured by how much a system can do, but by how little friction it creates between people, information, and strategy.
