During a recent conversation on The Executive Outlook, Sudhir Nandamuru shared perspectives shaped by more than two decades of enterprise data transformation across some of the largest healthcare organizations in the United States. He currently leads the data analytics organization at Triple-S, part of the GuideWell Group, one of the largest Blue Cross Blue Shield organizations in the country.
What stood out immediately was his honesty. He does not describe a data modernization strategy as a technology exercise. He sees it as an organizational discipline. For him, the difference between success and failure almost always comes down to one thing: treating modernization as a business problem first and a technology problem second.
He did not begin his career thinking about data leadership. He started as an engineer who was deeply interested in solving business problems with technology. A startup experience in the early 2000s, where he helped build a data product for a major credit card organization, became a turning point in his journey.
Reflecting on that phase, Sudhir Nandamuru puts it simply: “I started seeing the real value of data and how it can enable someone to make a decision.”
That realization kept him moving forward for more than 20 years.
But one of the moments that shaped his leadership most deeply was not a success. It was a failure.
Early in his career, he worked on a platform modernization initiative that looked strong on paper. The technology was sound. The idea was relevant. The business case made sense. But the organization, its people, and its processes were not fully ready for the change.
The platform did not take off the way it was expected to.
That experience taught him a lesson that still guides his leadership today: data transformation is never only about building the right system. It is about bringing people, processes, and business teams along with the system.
For him, three things matter most when moving from a technical role into a leadership role.
First, change management comes before technology adoption. A new platform only works when people understand why it matters and how their work will change.
Second, talent mix matters. The right people must be connected to the right problems. Technical skill alone is not enough if the team does not understand the business context.
Third, strategic goals need tactical wins. Large transformation programs can take months or years, but stakeholders need to see progress early. Without short-term wins, confidence fades and momentum slows down.
Before committing to any major data initiative, He asks one simple but powerful question:
“Can we execute this?”
For him, this question is not about doubt. It is about readiness.
Does the organization have the right people? Are the processes mature enough? Is the talent available? Are stakeholders ready to embrace the change? Can the team deliver early value while still building toward a larger strategic goal?
These questions matter because data projects are expensive. They often take longer than expected. They also require strong coordination across business, technology, governance, and leadership teams.
Sudhir’s approach is practical. Before saying yes to a large-scale initiative, he checks whether the organization is truly prepared to execute it. If the answer is not clear, then planning must happen before delivery begins.
That mindset is one of the most important parts of his data modernization strategy. It protects organizations from starting ambitious projects without the foundation needed to make them successful.
He is currently involved in a large-scale data platform modernization effort using Snowflake in the healthcare sector. Because he has seen modernization from different angles, he understands where organizations often lose direction.
One of the biggest mistakes, he explains, is waiting too long to show business value.
In one earlier modernization project, the platform took nearly two years before it reached actual users. By that time, business needs had changed. What had been built no longer fully matched what users needed.
The investment had been made, but the value had not arrived at the right time.
That experience shaped Sudhir’s belief that modernization cannot be treated as a long technical build with value pushed to the end. Organizations need to identify early use cases, deliver tactical wins, and show stakeholders that the transformation is moving in the right direction.
A strong data modernization strategy should not make the business wait 12 to 24 months before seeing impact. It should create visible progress while the larger platform continues to mature.
He also points to another common mistake: designing data models without deeply understanding the business.
Data models are not built to solve technical problems. They are built to solve business problems. If teams do not understand how the business operates, what users need, and how decisions are made, the platform may become technically strong but practically weak.
He also highlights the hidden cost of legacy platforms. Older systems often carry heavy licensing costs, maintenance effort, resource dependency, and integration complexity. These costs may not always appear clearly on the surface, but they affect the organization every day.
Modern platforms such as Snowflake and Databricks can make cost more visible and manageable. But Sudhir is careful not to present cloud modernization as an automatic cost-saving exercise. Cost improves only when the organization understands usage, resource needs, governance, and operating models clearly.
Another practical lesson he shares is the value of the right partnership model. If an organization does not have internal talent ready for a new platform, it should not pretend otherwise. A build, operate, and transfer approach can help. In this model, an external specialist helps build and operate the capability while the internal team gradually becomes ready to own it.
One of the most powerful moments in the conversation came when Sudhir connected data quality to patient care.
He described work involving a data repository integrated with health plans to identify patients who needed home-based care. The system used patient data, quality checks, analytical models, and risk indicators to help teams decide which patients needed outreach.
But when the data was messy, the model could not identify the right patients with confidence.
That meant people who may have needed care could be missed. Not because the care team did not want to help. Not because the technology had no purpose. But because the data underneath was not clean, reliable, or trusted enough.
He explained that teams need to get the data, perform the right quality checks, run analytical models, identify risk, and then reach out to doctors or care teams.
This example makes data quality feel real.
In healthcare, poor data is not just an operational issue. It can affect patient engagement, risk identification, care delivery, and business outcomes. That is why Sudhir treats data modernization as more than platform migration. For him, it is about building the trusted foundation that allows better decisions to happen at the right time.
Self-service analytics is one of the biggest goals for many organizations. Every business wants users to access insights faster without depending on technical teams for every report or dashboard.
But Sudhir makes it clear that self-service analytics does not work just because an organization buys a visualization tool.
It needs a strong foundation.
The first block is a data catalog. A catalog helps users understand what data exists, where it comes from, and what it means. Without a shared understanding of data, business users may create different interpretations of the same metric.
The second block is a business glossary and governance model. Data owners and stewards must define important terms, domains, and data meanings. This helps users trust the information they are using.
The third block is a simple user experience. He compares this to a retail store. When people walk into a store, products are arranged clearly with labels that help customers understand what they are looking at. Data should work in a similar way. Business users should be able to browse data topics, understand definitions, and use the right information without confusion.
The fourth block is community sharing. When teams do not communicate, duplicate reports and conflicting KPIs start appearing across the organization. One team may define a metric one way, while another team defines it differently. This creates confusion at leadership levels.
A shared catalog, governance structure, and analytics community help prevent that.
For Sudhir, self-service analytics works only when data foundation, governance, tools, and culture come together. Without that balance, self-service can create more confusion instead of better decisions.
When the conversation moved to AI, He offered a grounded perspective.
He does not see AI as a complete replacement for people. He sees it as a productivity multiplier.
In software development, AI can support programmers by helping them move faster, generate ideas, and improve productivity. But it still needs business understanding. A tool can generate output, but people must know whether that output fits the business scenario.
As Sudhir explains, the business hat still has to be worn.
His view of AI is also shaped by real healthcare and operations use cases. He has seen AI support work such as reducing financial submission risk, identifying risky patients, improving proactive care, and reducing call waiting times.
For example, reducing a call wait time from eight minutes to two minutes is not just a technology improvement. It improves customer experience, operational efficiency, and business scalability.
That is the real value of AI when applied correctly.
It does not replace judgment. It strengthens it. It helps teams work faster, identify patterns earlier, and make better use of the data already available to them.
He also points out that many organizations in the United States are now investing in AI literacy programs. These programs are not just for technical teams. Business users also need to understand how to work with AI, where to use it, and where human judgment remains essential.
The organizations that succeed with AI will not be the ones that simply adopt the newest tools. They will be the ones that build AI awareness across teams and connect AI initiatives to real business problems.
He is not simply offering a framework for modernization. He is offering a discipline built from more than two decades of experience, including both success and failure.
His message is clear.
Understand the business before designing the model. Check execution readiness before committing to the project. Secure tactical wins before claiming strategic success. Build governance before enabling self-service. Improve data quality before trusting analytics and AI. Treat AI as a productivity multiplier, not a shortcut for business thinking.
In a world where many organizations confuse platform migration with transformation, Sudhir’s perspective is timely and practical.
A strong data modernization strategy is not about moving from one system to another. It is about building the people, processes, governance, and trusted data foundation that help businesses make better decisions.
That is where modernization delivers real value.
For more leadership conversations on data strategy, AI, governance, healthcare transformation, and enterprise modernization, explore The Executive Outlook and learn from the leaders shaping the future of business and technology.
Listen in for business strategies and interviews with business experts to help you build a business and a life that you love.
About Us
