James Blagg explains why data modernization costs rise when data grows without structure, business purpose, trust and the right operating model.
During a recent conversation on The Executive Outlook, James Blagg shared a reality that many data modernization conversations avoid. Data modernization does not become expensive only because technology costs more than expected. It becomes expensive when data grows without structure; business teams lose trust and leaders underestimate the operating model needed to make modern platforms work.
James did not begin his career expecting to become a data and analytics leader. He studied history and politics at university and never imagined a technical path. But during the dot com boom, his curiosity pulled him toward the world of websites, HTML, programming and technology. That curiosity eventually led him to complete a master’s in IT and spend the next twenty-five years working across almost every kind of data role.
Over that time, he has led data modernization and analytics programs across some of the UK’s largest financial services organizations. He has seen what happens when data environments grow organically. He has also seen what it takes to turn fragmented platforms into business capabilities that create trust, speed on-making value.
In financial services, James has also seen the role of data evolve. Earlier, much of the focus was on compliance, lending decisions, credit performance and proving regulatory confidence. Over time, the focus expanded toward understanding customer behavior, improving acquisition and retention and using digital interaction data to design better products and services. That shift is one reason data modernization has become so important. The business is no longer only asking for reports. It is asking for faster, deeper and more useful answers.
His message is clear.
Data modernization in business is not just about moving to a new platform. It is about building the structure, story, operating model and leadership commitment that allow the platform to deliver value.
One of the strongest examples James shared was an organization that built a centralized data warehouse with good intentions.
The problem was not the idea of the warehouse. The problem was that the organization did not build the right operating model around it. Business users were not properly supported. Their needs were not fully understood. The platform did not evolve fast enough with changing requirements.
So business teams started building their own systems.
One team created an independent data warehouse. Then another team did the same. Then another. Over time, the organization ended up with five or six competing data warehouses, each with slightly different definitions, different maintenance needs and different interpretations of the same data.
What started as a central capability became a fragmented environment supported by hundreds of people.
For James, this is one of the most common data modernization challenges. The cost does not always appear as one large failure. It appears slowly. It becomes accepted. It becomes part of the business. Nobody questions it because nobody has stepped back to calculate the real cost of duplication, confusion and repeated maintenance.
That is why data modernization strategy must begin with structure. Without it, organizations do not modernize. They multiply complexity.
James also pointed to another pattern many data leaders will recognize.
Some data platforms are built too heavily from an engineering perspective. The architecture may be strong. The models may be technically correct. The platform may even be impressive to the teams that built it.
But if business users do not understand how to use it, they will not wait.
They will create their own reports, their own data models, their own definitions and their own local solutions. This usually happens not because business teams are trying to create chaos, but because they need answers and the central platform is not helping them quickly enough.
That is where data modernization in business often breaks down. The platform exists, but the adoption does not.
James believes a modern data platform must come with a broader operating model. That means education, literacy, support, clear ownership and a way for business users to engage with the platform as their needs change.
A data modernization framework is not complete if it only includes architecture and technology. It must also include the people and processes that help the business use what has been built.
James explained that the need for modernization often becomes visible when business questions become harder to answer.
A company may start asking more sophisticated questions about customers, performance, risk, products, or operations. But the existing infrastructure cannot keep up. The right data may not be consolidated. The level of detail may be missing. Batch processes may be too slow. The business may need insight faster than the platform can provide it.
At that point, modernization is no longer a technology preference. It becomes a business requirement.
James also sees automation as another signal. Data is a powerful enabler of automation, but only when it is available in the right place, at the right time and in the right form. If the infrastructure cannot support those opportunities, the business starts missing value that competitors may already be capturing.
This is why leaders should not wait until the data estate is visibly broken. By the time everyone agrees that modernization is necessary, the organization may already be paying the price through slow decisions, manual work, duplicated systems and missed opportunities.
One of James’s most relatable observations is that many organizations approach data modernization as if they are downloading an app.
Press a button. Wait a few seconds. Start using it.
He is clear that this mindset does not work in serious enterprise environments, especially in regulated industries like financial services. If integration does not matter, security does not matter and governance does not matter, then perhaps modernization can be simple. But in real organizations, all of those things matter deeply.
A proper modernization journey requires analysis and scoping. Leaders must understand the business drivers and define the outcomes they are trying to achieve. Architects must design the principles, frameworks and structure that will support those outcomes. Teams must build infrastructure, networking, security, CI and CD pipelines, deployment patterns, engineering frameworks and operating controls.
And much of this work happens before the organization even starts building the data pipelines that business users are waiting for.
This is where senior expectation management becomes critical. James has seen leaders surprised by how long modernization takes, how much it costs and how much foundational work is required. That surprise can weaken sponsorship if it is not handled early.
The leaders who succeed are the ones who understand the journey before they approve the budget.
One of the most powerful examples James shared involved an organization that had around three hundred business questions it could not answer without significant effort.
That is a simple but serious problem.
The business did not just need a new platform. It needed the ability to answer the questions that shaped strategy, operations, risk, regulation and growth. For James, that became the real test of the modernization program.
Could the new platform and data pipeline roadmap help the organization answer those questions in a structured and measurable way?
This is the kind of thinking that separates a real data modernization strategy from a basic technology upgrade. The question is not whether the platform has been built. The question is whether the platform helps the business answer what it could not answer before.
That is why James consistently returns to business outcomes. Without them, modernization becomes a long technical project. With them, it becomes a clear business journey.
James also touched on an important point many leaders underestimate after modernization.
Once data moves from an old environment to a new one, the business must trust that the numbers still make sense. This is especially important in regulated industries, where transparency, confidence and resilience are not optional.
The goal is not simply to move data. The goal is to improve trust in the data.
A successful data modernization framework should help the organization bring in more data, integrate sources at different speeds, improve transparency and answer business questions with greater confidence. It should also strengthen resilience, especially when the platform supports external reporting or regulatory commitments.
For executives, this is a critical reminder. Migration is not success by itself. Success is when the business trusts the new environment enough to make decisions from it.
When asked for one piece of advice for anyone starting a modernization journey, James returned to a simple principle.
Start with the business purpose.
Before designing architecture, selecting tools, or planning delivery, leaders need to answer one question clearly. Why should a non technical stakeholder invest in this program?
The answer might be customer growth. It might be deeper insight into customer behavior. It might be audit findings. It might be regulatory confidence. It might be the need to improve external reporting. Whatever the reason, it must be clear enough for sponsors to understand and strong enough for them to stay committed when the journey becomes difficult.
James believes leaders must build the story before they build the platform.
That story should explain why the modernization is needed, what it will deliver, what it will cost, what commitment it requires and how it connects to the business strategy.
Without that story, data modernization loses support the moment complexity becomes visible.
James also warns that technical teams must remain connected to the business outcome throughout the journey.
He has seen teams get lost in technical perfection. They focus on building the most elegant solution, but lose sight of whether that solution is helping the organization achieve the result it set out to achieve.
That does not mean technical quality is unimportant. It means quality must serve purpose.
The best modernization programs give technical teams a voice in how work is done while keeping them anchored to why the work matters. This balance helps prevent the program from becoming either too business led without technical reality or too technical without business impact.
Data modernization at scale works best when business and technology teams move together.
Across the full conversation, James is not speaking about data modernization from a distance. He is speaking as someone who has lived through the complexity of modernization programs inside large organizations.
His message to leaders is practical and direct.
Data modernization costs more than expected when organizations underestimate the work beneath the platform. It fails when business purpose is unclear, when operating models are missing, when business users are unsupported, and when technical teams become disconnected from outcomes.
But when it is done right, modernization creates a data capability that can keep pace with business demand. It helps teams answer harder questions faster. It improves trust, resilience, insight and confidence. It gives the business a platform that supports strategy rather than slowing it down.
Technology matters. But the story, sponsorship, operating model, trust and honest expectation setting matter just as much.
That is where data modernization is really won.
Want to hear more conversations with leaders who have led data modernization from the ground up? Explore more on The Executive Outlook.
Listen in for business strategies and interviews with business experts to help you build a business and a life that you love.
About Us
