Enterprise transformation has consumed trillions of dollars globally, yet most organizations find themselves running harder to stay in place. The culprit, according to Goutham Parcha, Vice President of Application Development at Pegasystems, isn’t budget or ambition — it’s thinking. When businesses treat modernization as an upgrade rather than a reinvention, they don’t escape legacy systems; they rebuild them in newer clothes. Parcha, who oversees product engineering at a company where India drives nearly half of global innovation, argues that the architecture conversation must begin with outcomes, not systems. In this conversation, he dismantles the myth of incremental progress and makes a compelling case for why governance — not speed — is where AI-led platforms will ultimately prove their worth.
Vice President of Application Development
Pegasystems
CIO&Leader: Why do you believe legacy-led thinking continues to slow down enterprise transformation despite massive investments in modernization? –
Goutham Parcha: Today, organizations are still treating modernization as a continuation of what already exists, instead of using it as an opportunity to rethink how they operate. That’s where legacy-led thinking continues to hold transformation back. Even with increased investments, the focus often remains on preserving existing systems rather than reimagining how work gets done, how decisions are made, and how customers are engaged in a digital, AI-driven environment.
As a result, new technologies are often layered on top of legacy systems instead of replacing or restructuring them. Over time, this creates fragmented ecosystems, duplicated processes, and added complexity. While it may look like progress initially, it often leads to systems that are harder to scale, integrate, and respond to real-time business needs. The real challenge is not just the technology itself, but the mindset of clinging to continuity rather than building for adaptability.
At Pega, we have seen that transformation becomes far more effective when organizations shift their focus to architecture. By bringing together workflows, decisioning, and AI within a unified platform, businesses can move away from siloed systems and start building for continuous change. Ultimately, the goal is not just to modernize systems, but to modernize how the business operates. That’s where meaningful and lasting impact comes from.
CIO&Leader: At what point does incremental or “patchwork” modernization start to increase technical debt rather than reduce it?
Goutham Parcha: Incremental or patchwork modernization starts becoming a problem when it turns into a series of disconnected fixes rather than part of a bigger plan. On the surface, these changes can feel productive because they solve immediate issues. But over time, they tend to add layers of complexity that are difficult to untangle.
This usually plays out when legacy systems are extended with multiple point solutions or custom integrations, each addressing a specific need. Individually, they make sense. Collectively, they create an environment that is harder to manage, harder to change, and increasingly dependent on workarounds. What was meant to reduce technical debt slowly ends up shifting it elsewhere, often in less visible ways.
You start to notice the impact when even small changes take longer than expected, or when teams are spending more time maintaining what exists than building anything new. That’s typically the point where modernization efforts begin to lose momentum.
At Pega, we have seen that a more structured, architectural approach makes a significant difference. When capabilities are built in a modular, layered way, organizations can move step by step without losing control of the bigger picture. The goal is to simplify as you go, so the system becomes easier to evolve rather than more complex with every change.
CIO&Leader: How should CIOs rethink business architecture if they want transformation outcomes—not just system upgrades?
Goutham Parcha: Most modernization efforts fail not because of poor execution, but because the wrong question is being asked. When a CIO frames the challenge as a system upgrade, the answer will always be a newer version of what already exists. The architecture changes, but the business remains the same. What needs to change first is the framing: from which systems need replacing to what outcomes the business needs to deliver, and what architecture makes that possible.
Legacy environments actively work against this shift. They resist integration with cloud and AI, scatter data across incompatible systems, and consume budgets that should be funding new capabilities. When performance drags quarter after quarter, boards do not look at the systems. They look at leadership. Modernization has moved from a technology decision to a leadership mandate, and CIOs who have not made that transition are already behind.
Change has to start with the outcome, and not the system. A CIO who starts with the required business outcome and identifies the specific work process that is preventing it can execute the business transformation much more quickly than someone trying to do an entire overhaul. Therefore, the architecture is developed after the outcome has been established, not before.
CIO&Leader: What fundamentally differentiates a design-first approach from traditional code-first transformation models?
Goutham Parcha: Code-first models are built around the assumption that business intent can be accurately captured, translated into technical specifications, and handed off to engineering without losing meaning along the way. However, in reality, this assumption does not typically hold. The points of difference between the original intent and the final output are usually expensive to fill at that time, and misalignment before it is too late remains the primary cause of failure in enterprise transformation.
A design-first approach changes when that alignment happens. Business and technology teams work from a shared understanding of the process, the decisions, and the desired outcomes before a single line of code is written. The transition from design to build is not a handoff. It is a continuation of the same conversation. At Pegasystems, this is how we build.
The bigger difference is about who participates and when. At Pegasystems, we keep our generative AI approach deliberately open-ended, connecting with the best models available rather than building our own, and directing our energy toward governance, security, scalability, and resilience. That same discipline runs through how our platforms absorb complexity. For example, Constellation, Pegasystems’ modern UI architecture, is designed to remove the dependency on deep front-end expertise. It provides a standardized, design-driven framework for defining user experiences upfront and consistently delivering them across applications. Teams focus entirely on the outcome, not the tooling. That is the fundamental shift a design-first approach enables, and it is what separates meaningful transformation from incremental change.
CIO&Leader: How does PegaBlueprint translate business KPIs into executable system designs at scale?
Goutham Parcha: PegaBlueprint starts by emphasizing clarity on outcomes, and not just features, which is where most transformation efforts typically fall short. When you anchor the input in business KPIs, whether it is reducing onboarding time or improving first-contact resolution, the system maps those outcomes to workflows, decision logic, and data requirements in a structured way. What makes it scalable is that it does not treat each design as a one-off exercise. Instead, it establishes a consistent model of processes and rules so that the same KPI can be translated into repeatable system patterns across teams and markets.
What is more fundamental, however, is the shift in where design sits in the technology lifecycle. Design is no longer a static phase that precedes delivery; it becomes a living layer that continuously aligns systems to business outcomes. The output is not a slide or a concept note, but a working design that teams can build on immediately, with far less interpretation gap between business intent and execution. Over time, this creates a compounding advantage: organizations will not just be building systems faster; they will be building institutional knowledge into the design itself, which can be reused, adapted, and scaled with far greater consistency. This is central to Pega’s vision of the agentic enterprise- where AI moves beyond assistance and becomes an active participant in design, delivery, and continuous optimization.
CIO&Leader: Where do you see AI-led design platforms creating the biggest measurable impact—speed, cost, or governance?
Goutham Parcha: Speed is the most visible gain, but governance is where the real long-term value sits. Faster design cycles are useful, and cost efficiencies follow, but large enterprises in India are increasingly constrained by inconsistent and inadequate control as systems scale. AI-led design platforms bring discipline by standardizing how decisions, workflows, and compliance requirements are embedded from day one. That reduces rework, audit risk, and fragmentation across business units.
The deeper shift is that governance moves from being a control function to becoming part of the design logic itself. This changes how technology leaders think about scale. Instead of relying on oversight after deployment, enterprises can ensure that every new system already conforms to enterprise standards by design. In that sense, governance becomes an accelerator rather than a constraint, because teams spend less time correcting deviations and more time extending what already works.
In the next phase, the real advantage will come from how consistently an organization can replicate good decisions across use cases. AI-led design platforms make that possible by turning governance into something embedded, reusable, and measurable rather than reactive.
CIO&Leader: What role is Pegasystems India playing in shaping next-generation enterprise platforms for global markets?
Goutham Parcha: Pegasystems India today plays a foundational role in shaping next-generation enterprise platforms for global markets. What began as a strategy to scale engineering capacity has evolved into a deeply integrated model where India drives a significant share of product innovation. With nearly 50–60% of product engineering happening in India, the teams here are not just contributing to development, but are actively defining the architecture, scalability, and intelligence of Pega’s enterprise platforms.
Crucially, India is home to critical cloud infrastructure capabilities, signifying the strategic depth of work being led from India- spanning complex cloud-native systems, AI-driven decisioning, and mission-critical enterprise solutions that power global clients. Equally important is the talent transformation story. Pegasystems made an early and deliberate shift from outsourcing to building a strong, in-house ecosystem, investing in India’s exceptional engineering talent and integrating it into the company’s identity. Today, over 30% of Pega’s global workforce is based in India, with strong representation across engineering, consulting, technical sales, and corporate functions.
This evolution reflects a broader shift in how global technology companies view India, not just as a delivery center, but as a strategic hub for innovation, leadership, and product thinking. At Pegasystems, India is helping shape the future of enterprise platforms by driving agility, cloud transformation, and customer-centric innovation at scale.