Not only do many businesses have more data than they know what to do with, but they also often struggle to gain insights from some of the most valuable data in their possession, leading to many of their crucial data assets going unused. Whether it's issues with data quality, visualization, or management, getting lost in the sea of enterprise data at your possession can make it impossible to make smart, data-driven decisions that improve your business.
The "Don't Panic! It's Just Data" podcast delves deep into the power of enterprise data. From groundbreaking vendor solutions to expert-backed best practices for making the most of your data assets, join us as we gather insights from leading tech vendors and professionals who depend on data daily.
Advertise on Don't Panic! It's Just Data
Advertise on Don't Panic! It's Just Data to promote your brand to thousands of podcast listeners
Unlock Don't Panic! It's Just Data podcast Email contact info, Listeners & Audience details
Email contact information
Direct podcast contact details
Listeners
Audience numbers & engagement insights
Audience details
Podcast Insights
Social media
Check Don't Panic! It's Just Data social media presence
Check latest episodes from Don't Panic! It's Just Data podcast
Big Data LDN: Why MDM is Back on the C-Suite Agenda
2026/11/05
A massive organisation in the pharmaceutical industry deploys about six to seven master data management (MDM) platforms in addition to a few customised solutions. After facing challenges of scattered systems and their tools, the pharma company has decided to consolidate them.
The problem is that every drug, clinical trial, or product is named differently across the world. On top of that, if you had to prompt an AI agent to decipher the proportion of the business that comes from every product, it would have to read through several systems, with no agreement between them, and no way of knowing which one is right.
This is the challenge that LakeFusion, a master data management vendor, was tasked with solving for a major pharmaceutical firm.
In this episode of the Don’t Panic, It’s Just Data Podcast, recorded live at Big Data London, Podcast Host, Producer and B2B Tech Journalist, Shubhangi Dua sits down with three guests: Sanjeev Mohan, Principal at SanjMo; Cooper Kenny, Founding Sales and Alliances Manager at LakeFusion; and Panos Athanasiou, Chief Field Technologist at Databricks. They explain why agents are unable to make up for poor master data, what it means to govern context rather than just data, and the reason why MDM has to cover the tools and data products that agents depend on.
Key TakeawaysMDM is forecast to grow from $20 billion to $42 billion by 2030.Humans spot wrong records. Agents don’t.Governance now has to cover context, not just data.Context is generated at query time, so it is hard to inspect.LLMs can match structured records to audio, PDFs and social posts.Zero-copy architecture removes the need for CDC pipelines in MDM.Ontology needs semantics and connections, not only graphs.Human operators still decide what counts as a golden record.Bloated context drives token costs up and invites hallucination.Agentic data stewards can work through human-review backlogs.Start with a thin slice of value deliverable in weeks.
Chapters00:00 Introduction to Big Data London and Participants05:02 Master Data Management: Evolution and Trends09:54 AI Native MDM: The Future of Data Management15:07 The Role of Context in Data Governance19:55 Challenges of Bad Data and Its Impact24:36 Cultural and Technological Shifts in Data Management25:00 The Importance of Master Data in AI Initiatives25:24 The Future of Data Management Solutions26:43 Lake Fusion's Unique Position in the Market29:30 The Role of AI in Understanding Business Dynamics32:06 The Evolution of AI Agents in Workflows35:37 Key Takeaways for C-Suite Executives
@Bigdataldn @LakeFusionAI @Databricks
Read the full article: https://em360tech.com/podcasts/big-data-ldn-why-mdm-back-c-suite-agendahttps://em360tech.com/podcasts/big-data-ldn-why-mdm-back-c-suite-agenda
LakeFusion: https://lakefusion.ai
EM360Tech: https://em360tech.com
Watch more from the Don’t Panic, It’s Just Data Podcast: https://www.youtube.com/playlist?list=PLXoSlBGE35NoUm5jhXSTu4DdytBNXTgwY
Follow EM360Tech on X: https://x.com/EM360Tech
Follow EM360Tech on LinkedIn: https://www.linkedin.com/company/em360/posts/
#BigDataLDN #MasterDataManagement #MDM #AgenticAI #AIAgents #DataGovernance #Databricks #EnterpriseAI #DontPanicItsJustData #EM360Tech
master data management, MDM, AI agents, agentic AI, golden record, data governance, context layer, Big Data LDN, Databricks, LakeFusion, enterprise AI, data management
Does Vendor Lock-In Belong in an Enterprise AI Data Platform?
2026/10/30
An acquisition is just about to close this Friday. That means, by Monday, finance wants to know where the group is losing margins. The problem is the new enterprise functions on its own systems, and onboarding a single data source is quoted at weeks or months. Meanwhile, the foundation model your board approved last quarter sits on top of all of it, waiting for data it cannot yet read.
That is the position one of Advancing Analytics' hospitality customers, a global food and beverage group built through acquisitions, was in before it changed how it brings data on board.
In this episode of the Don't Panic It's Just Data podcast, recorded live on the show floor at Big Data London, host Shubhangi Dua, Podcast Host and B2B Tech Journalist, speaks with Andrew Phethean, UKI Industry Lead, Enterprise Growth at Databricks, and Terry McCann, CEO of Advancing Analytics.
This podcast episode is especially relevant to CDOs, CEOs, and CEOs who are now beyond AI experimentation and are now pursuing plugging agentic systems into production. The speakers cover why the foundation of the platform’s model is the key factor when it comes to the outcome, what Databricks calls the four C's, and why the cost of doing nothing rarely makes it into the business case.
"I think a lot of the time enterprises are experimenting with the big vendors of the world and putting a lot of investment in that, but not necessarily putting that into production properly,” Phethean tells Dua.
Key TakeawaysBuying a foundation model without a governed data platform stalls projects.Newer models aren't needed for every business operation, says Phethean.Open source, lower-cost models and machine learning can carry production work.Databricks frames AI obstacles as four C's: context, control, cost, choice.Cost discipline now means maximising value, not tokens.Vendor lock-in isn't a strategy: choice spans vendors, clouds and LLMs.Data governance now serves AI agents as well as people.LakeForge cut data source onboarding from weeks or months to minutes.The cost of inaction can outweigh the ROI case for investing.CDOs and chief AI officers need a seat at board level.McCann's CDO advice is speed to market; Phethean's is translating IT to business.
Chapters00:07 – Welcome and introductions00:48 – How has Big Data London been?02:32 – From generative AI to agents to context04:33 – The biggest challenge: getting the plumbing right05:49 – The four C's (and a fifth)07:31 – The Advancing Analytics and Databricks partnership09:52 – Customer story: LakeForge and Genie Code11:22 – The shift CEOs aren't watching15:08 – ROI versus the cost of inaction16:44 – What the tech industry gets wrong about AI18:38 – If your AI agent had a personality20:02 – One takeaway for CDOs21:30 – Closing and where to find the guests
For more information, visit: advancinganalystics.co.uk
Check out more data podcast episodes in the enterprise tech landscape: https://youtube.com/playlist?list=PLXoSlBGE35NoUm5jhXSTu4DdytBNXTgwY&si=iQzaMGoNb7wnRUaF
@AdvancingAnalytics @Bigdataldn @enterprisemanagement360
#BigDataLDN #BigDataLDN2026 #AdvancingAnalytics #Databricks #AIAgents #LakeForge #GenieCode #AIROI #AIProfit #AILoss #AIMarketValue #AIValue #AIProduction #AIinProduction #AICosts #DataAnalytics #aianalytics #AIData
Data Pipelines For Agentic AI: An Edgy, Shift-Left Live BDL Podcast
2026/10/28
With the boom in online shopping, the risk of parcel theft has scaled to an unprecedented level. According to security.org, the 2025 porch piracy data shows that 64 million Americans (one in four) have experienced package theft, with 9 million adults falling victim within the past three months alone. Cameras exist, but robbers wear masks and steal anyway; the risk grows every hour. That was United Parcel Service (UPS), an American parcel delivery company, in that position. The fix, however, was built with Striim and Google BigQuery. They came together and calculated the risk score for every delivery in real time, delivering enhanced security.
In this episode of the Don't Panic! It's Just Data podcast, recorded live at Big Data LDN in the Y-Axis theatre in front of 200 people, host Christina Stathopoulos, Founder of Dare to Data, sat down for a fireside-style chat with Alok Pareek, Founder and EVP of Product Development at Striim.
They critically examine how agentic workloads impact cost, predictability, performance, and consistency. Pareek also explains why data pipelines that simply move data can no longer keep up, and where processing should happen. Pareek, who in his early career worked on the Oracle database kernel and later served as CTO of GoldenGate, also strongly opposes zero-copy ETL.
For CIOs, CDOs, and leaders in the field of data engineering who already manage mission-critical pipelines for use in operations, analytics, and business intelligence, the fact is that a new type of consumer is now situated atop these pipelines.
“A simple question posed to an AI agent is quickly becoming a distributed computing problem,” states Pareek. “Especially when asking relatively complex inquiries such as ‘is this customer really someone I need to care about deeply?’”
So when accessing a Large Language Model (LLM) for inference, the AI agent might be accessing its own tools, going through multiple database systems, files, websites, or simple search functions. He says the agent may be exasperated and, as a result, it ends up creating a classic GPU cost problem and a distributed computing problem.
Also Watch: Can AI Agents Make Decisions Without Real-Time Enterprise Data?
Key TakeawaysAgents create databases at 4x the human rate; half last under 10 seconds.Snowflake saw agent queries scanning trillions of records to return two.One agent question becomes a distributed computing problem.Agents querying several systems receive states from different moments.Pipelines built only for data movement can't explain why they break.Shift-left analytics acts on data in flight, before the warehouse.Stale data compounds agents' hallucination and people-pleasing tendencies.AI sovereignty now covers where models run, not only where data sits.Agent-guarded replicas keep agents away from production systems.Zero-copy ETL moves complexity onto the source database.UPS scores delivery addresses from 100 to 1000 in real time.The four Cs: current, consistent, consumable, contextual.
Chapters03:13 Welcome and Alok Pareek's background06:17 What the agentic era demands of data pipelines14:34 Moving data versus intelligent pipelines18:40 Shift-left analytics20:49 Data and AI sovereignty25:05 Why zero-copy ETL falls short28:51 UPS Defense Delivery and real-time risk scoring31:26 The four Cs
MORE RESOURCES:
Striim: https://www.striim.com/
Episode article: Subscribe to the podcast: https://open.spotify.com/show/4jgUESBM1jQpq4Wx2xfou8
@striiminc @enterprisemanagement360 @Bigdataldn
#AIGovernance #AgenticAI #DataPipelines #EnterpriseAI #BigDataLondon #Striim
AI governance, enterprise AI, agentic AI, data pipelines, real-time data, shift-left analytics, AI sovereignty, data governance, Striim, Alok Pareek, Big Data London, tech podcast
Can AI Agents Be Trusted With Enterprise Data? | Big Data LDN Special
2026/10/20
Two different teams in an enterprise built two AI agents, but both asked the AI the same question: What are last quarter’s customer stats? Both agents answer promptly and quite assertively. However, the figures on the same inquiry are different. The agents’ answers don’t match. Nothing has broken because neither team is aware of the other’s AI agent.
What happened here is that each agent drew the answer from different contextual data. The business holds two variations of truth delivered with equal confidence.
This is the kind of oblivious failure Angelita Frozza Sanches, Head of Data at Scout24, is working to prevent at the leading German real estate platform where AI agents have already been deployed in production.
In this episode of the Don't Panic It's Just Data podcast, recorded live at Big Data London 2026 in Kensington Olympia, host Mike Ferguson, Managing Director of Intelligent Business Strategies and Conference Chair of Big Data London, sits down with Sanches and Suresh Srinivas, CEO and Co-Founder of Collate and OpenMetadata.
They talk about who now consumes enterprise data, how much of the context layer should be centralised, and why enterprises making progress are the ones that start small and tie every agent to a business outcome.
According to Sanchez, the concerns from 20 years ago to now remain the same, and it comes back to governance. “How people consume, how they interact with data,” remains the same. What’s new is that “AI has changed the velocity and the impact of all those aspects.”
“Now we can take advantage of AI to help us build governance,” Sanchez says. “How can we prepare everything not just for humans but agents–another persona in the game.”
Also Watch: How to Increase Agent Accuracy & Reduce Cost with Context
#AIAgents #DataGovernance #ContextLayer #AgenticAI #OpenMetadata #BigDataLondon #EM360Tech #AIAgents #DataGovernance #ContextLayer #AgenticAI #OpenMetadata #BigDataLondon #EM360Tech
How SAP BW Migration Prepares Enterprises for AI
2026/10/09
Companies pouring money into AI are seeing only incremental gains, and One Data Chief Executive Officer Dr Andreas Böhm says poor data is a major reason. In a recent episode of the Don't Panic. It's Just Data podcast, Böhm joined the data whisperer Scott Taylor to discuss why SAP Business Warehouse migrations can give enterprises a valuable opportunity to improve the quality and usability of their data.
Böhm, who started his first data company 20 years ago, told host Taylor that the underlying task has not changed through successive waves of big data, data science and machine learning. Organisations still need to get the right data to the algorithms. The algorithms are what have improved.
Why AI Projects Stall Without Trusted DataBöhm said enterprises are spending heavily on AI but are not yet seeing the return on investment (ROI). This is especially true when it comes to large jumps in efficiency, cost savings or product development. In his view, the cause is that data is not being used properly. He identified three factors that determine whether AI is adopted in practice.
The first is trust. If finance controllers do not believe the data a system produces, for example because it does not match their own spreadsheets, they will not act on it. Böhm questioned how an AI agent could be expected to act on data that people themselves distrust.The second is consistency over time. Getting data right once is relatively easy, he said, but keeping quality high day to day is a continuing challenge. He compared it to asking his daughter to tidy her room: it looks fine for a day.The third is context. Data accurate enough for a forecast, where a five per cent swing may be acceptable, may not be good enough for a profit and loss statement or regulatory reporting to the US Securities and Exchange Commission.
Taylor noted that AI amplifies the consequences of poor-quality data. The familiar principle of “garbage in, garbage out” becomes a much larger enterprise risk when flawed data is processed and scaled across AI systems. As Böhm put it, the result is “scaled garbage.”
Why BW Migration Is an Opening for AI ReadinessBöhm said SAP BW systems hold decades of financial and operational data, along with business logic buried in ABAP code, mappings and calculation views. That logic covers how sales forecasts are calculated and how controlling processes work, and the people who built it have often left the company. Simply lifting and shifting that content to a new platform carries the old problems with it, the two agreed. Taylor said it amounts to building a faster way to repeat the same mistakes.
Böhm recommended instead starting with a landscape analysis and end-to-end lineage mapping to see what is actually used. Typically, he said, about 50 per cent of legacy objects can be discarded, and reducing scope raises quality on its own. His team then uses an explainer agent to document what past logic did, so new staff and AI agents can understand it.
He described a client with 32 SAP systems, a mix of BW and ERP, that wanted to free up capital by understanding how cash flowed across the group. BW was trusted at the level of individual organisations but not company-wide. One Data translated the BW logic into a modern lakehouse architecture, then built a group-wide model on top of it. The migration took months rather than years, Böhm said, and the improvement in managed cash was visible in the company's profit and loss account.
Böhm cautioned that AI is not a shortcut around the work. Pasting ABAP code into a large language model does not capture logic spread across classes, reusable objects, hidden calls and customer exits. What has changed, he said, is that AI agents can now handle tasks such as migrating code, quality checks and fixing syntax errors, which would have been far harder four years ago. He dismissed the idea that LLMs remove the need to clean data. The funding angle matters too. Migration spending is already required, Böhm noted, so it can double as the investment in data management that organisations often struggle to secure.
How to Keep Migrated Data Trusted After Go-LiveBöhm said governance after migration should follow a data product approach, built on several practices:
Ownership: Someone must understand and be responsible for the data, or it will not stay clean.Readability: Business users need understandable column and table names, not cryptic technical labels.Business validation: Checks should go beyond technical rules such as "revenue must be a number" to business rules, such as whether negative revenue is valid because of returns.Focus: Not everything needs governing. Priorities should be core entities such as customers, revenues, purchase orders and product lifecycles.
Taylor described governance as a lifestyle rather than a project. Böhm added that it remains a people business, in which data owners take pride in their work and promote it internally.
His closing advice to organisations preparing SAP BW data for AI was to use the migration as a chance to clean up the data landscape and to apply the budget to making at least one or two areas AI-ready. If you would like to find out more, visit onedata.ai or follow Dr Andreas Böhm on LinkedIn.
TakeawaysThe recurring hype cycles in AI and the importance of data quality.The critical role of trust, context, and governance in AI adoption.Transforming legacy SAP BW systems into modern data architectures.Strategies for cleaning up and understanding enterprise data landscapes.The significance of data ownership, understanding, and management in data governance.
How to Increase Agent Accuracy & Reduce Cost with Context
2026/09/22
What happens when an enterprise data agent asks you: “What is our churn this quarter?” The AI agent has access to the warehouse, the tables, and the query engine. It carries out the necessary calculations. However, the answer it provides turns out to be inaccurate. Why?
It’s not because the model is inadequate. It’s because it didn’t know which definition of the term 'churn' the business had in mind, which table was out of date, or which join resulted in customers being counted twice. When you apply this situation to all the questions your enterprise directs at AI, you begin to understand why so many agent projects come to a halt at the demo stage.
In this episode of the Don't Panic, It's Just Data podcast, host Shubhangi Dua, Podcast Producer and B2B journalist at EM360Tech, sits down with Suresh Srinivas, the CEO and Co-Founder of Collate and also a Co-Founder of the open-source project OpenMetadata. They talk about the context layer and the reasons why AI agents fail when it comes to enterprise data, even though the underlying models are continually getting better. He explains why the solution must be an open context layer rather than a proprietary one.
Also Read: OpenAI's self-service AI data agent, built on OpenMetadataWhat OpenAI's internal data agent shows about scaleSrinivas cites a use case to Dua to explain how the solution can be deployed at scale. He talks about OpenAI's own internal data agent, Kepler, which is used by more than 3,500 people and carries out reasoning across about 70,000 datasets and over 600 petabytes of data, as proof that the issue is not particular to Collate's customers.
OpenAI developed a seven-layered context system based on OpenMetadata, and is one of its largest users as well as a major open source contributor. Srinivas maintains that even though there are seven layers, they all come down to three basic elements: the context of the data (what exists), the ontology and semantics (what it means, expressed in business terms such as "revenue" or "churn"), and memory (the corrections and feedback that the agent learns from).
Srinivas states that after OpenAI had invested in the context layer, query performance on Kepler decreased from 22 minutes to 90 seconds, representing a roughly 16-fold improvement, together with improvements in token efficiency.
Anthropic too has published its own research on the importance of context layers for data agents, which shows that there is convergence among the leading research labs, not merely a point made by Collate.
Key TakeawaysMcKinsey: fewer than 10 per cent of enterprises have scaled AI agents to value80 per cent of enterprises cite data limitations as the scaling barrierOn the Spider 2.0 benchmark, the top models achieved only 59 per cent accuracy when tested on enterprise data.Collate's context layer raised accuracy from 59 per cent to 94 per cent on the same benchmarkThat's an 86% reduction in wrong answers from context alone, not a bigger modelToken spend fell 75 per cent once a context layer was addedDatabase queries per question dropped from 190 to 27, an 86 per cent reduction in computeOpenAI's Kepler agent spans 70,000 datasets and 600+ petabytes, built on OpenMetadataOpenAI's query performance improved from 22 minutes to 90 seconds with contextContext layer reduces to three primitives: data context, ontology/semantics, memoryOpenMetadata has 15,000+ community members and 4,000 production deploymentsCollate curates context per persona rather than serving the full context to every agentCollate's AI Governance Studio audits what agents access and the risk they pose
Chapters00:00 Introduction to AI and Data Context Challenges02:16 The Root Cause of Data Problems: Missing Context04:20 Evolving Definition of Context in AI and Data06:52 Why Data Limitations Still Hinder AI Scaling07:22 The Impact of Context on AI Model Accuracy and Cost09:21 How Providing Context Improves AI Performance11:02 Verifying Data Accuracy in a Constantly Changing Enterprise12:25 AI Agents and Continuous Data Quality Management14:25 OpenAI's Use of Context Layers for Better AI Performance16:03 Avoiding Noise and Cost in Context Management18:47 The Role of Persona-Based Context Curation19:45 Open Source as a Foundation for Context Layers21:37 Accountability for Incorrect or Stale Context22:24 Collaborative Role of Data Teams and AI Agents in Context Management24:01 Guardrails and Deterministic Answers in Enterprise AI25:53 Reducing Token Consumption with Context Layers28:47 Key Takeaway: Building a Robust Context Layer for AI30:37 Upcoming Industry Discussions and Challenges at Big Data London32:28 The Future of AI Agents and the Importance of Context in Data Strategy33:12 Closing Remarks and Next Steps for AI and Data Leaders
@CollateData @enterprisemanagement360
#AIagents #EnterpriseAI #DataGovernance #OpenMetadata #ContextLayer #AIaccuracy #AgenticAI #CIO #DataStrategy #EM360Tech #DontPanicItsJustData #opensourcesoftware #opensourceai
AI agents, enterprise AI, CIO, CTO, IT leadership, data governance, AI governance, context layer, OpenMetadata, data strategy, agentic AI, digital transformation, tech podcast, enterprise technology
Can AI Agents Make Decisions Without Real-Time Enterprise Data?
2026/09/21
Envision a fraud detection model embedded in a bank's AI system, continuously monitoring transactions for unusual activity. The warehouse behind it updates itself every 15 minutes; however, that seems like a short interval. A fraudulent transaction took place 13 minutes ago, and the model still hasn't picked it up.
The thing is, the model is not faulty. The data being fed to it had already overlooked the critical moment. But how?
In this episode of the Don't Panic! It's Just Data podcast, host Shubhangi Dua, Podcast Producer and B2B Tech Journalist at EM360Tech, sat down with guest Sundar Nathan, VP of Product Marketing, Enablement and Academy at Striim. They discuss the gap that exists between the time an event takes place in a production system and the time an AI agent becomes aware of it.
As the frontier models from companies such as OpenAI and Anthropic become more commonplace, the model ceases to be a source of competitive advantage for any enterprise. What remains then is the data beneath the model and the speed at which that data actually moves.
“I'd go even a step further and state that in 18 months the model you select will be less important to you than the data which is feeding that model,” Nathan said.
'Everybody Is Renting The Same Brain'Alluding to his personal experience, Nathan tells Dua that his "superpower was memory,” particularly, the ability to remember circuit diagrams and organic chemistry structures as clearly as in a photograph when taking an exam. But with the introduction of Google search, that memory ceased to be an advantage since everyone had the same tool at their disposal.
Why is that experience relevant? It’s similar to the use of AI in the enterprise today. "Your competitor next door has access to the same frontier models at the same price, roughly on the same day," he says.
According to the Striim Marketing VP, what a competitor cannot rent is an enterprise’s operational data, its business insights and "the institutional knowledge accumulated over decades", in particular, how close an agent's view of production data is to the actual data.
"The time gap between the agent and where your production data is measured is the new source of competition," he adds.
Also Read Use Case: UPS Leverages Striim and Google BigQuery for AI-Secured Package Delivery
Read Use Case: The Hyper-Responsive Payments Organisation
TakeawaysThe model matters less than the data feeding it within 18 months, Viswanathan predicts.Four Cs of AI-ready data: current, consistent, consumable, contextual.Only 23% of enterprises scale AI agents past pilot stage (McKinsey).Change data capture reads transaction logs directly, in real time.Governance built for non-human users masks PII/PHI before agents see it.
Chapters00:00 - Why AI advantage is moving from models to real-time data
02:06 - Sundar’s path from memory-based learning to simplifying complex tech
04:10 - Why “everyone is renting the same brain”
06:52 - Why impressive pilots fail in regulated production workflows
08:30 - The four audit questions that block deployment
10:43 - Why 15-minute refreshes are not real time for fraud
13:25 - Why enterprises need a nervous system, not a warehouse scan
15:52 - How consumable data turns raw events into agent-ready context
18:29 - What Stream’s intelligent pipe does in practice
21:12 - Governance for non-human users and mission-critical guarantees
22:26 - Stop benchmarking models and start benchmarking data staleness
25:45 - Final takeaway: it really is just data, but it must move faster
What Happens When Your AI Agent Finds Two “Correct” Answers?
2026/09/02
Two teams pitch the same figure for ‘active customers’ right before a leadership meeting. One dashboard displays 40,000 while the other dashboard displays 52,000. No mistakes were detected by the teams; however, the difference in the stats is due to one team or employee deploying a different data filter and the other using another join path.
Now there's an AI agent involved, who is simply asked to 'retrieve the most recent number of active customers'. Not realising that there are two versions, it selects one, states that figure with complete confidence, and then goes about its business. In that moment, the semantic gap ceases to be merely an internal discussion and becomes a business risk.
On this episode of the Don't Panic! It's Just Data podcast, host Shubhangi Dua, Podcast Producer and B2B Tech Journalist at EM360Tech, is joined by Ananya Devraju, a Business Intelligence Developer at Premier Inn, to discuss the semantic gap and how AI is rendering an old data problem. They look at the situation in which metric definitions are spread across five different dashboards rather than kept in a single central location, and explain why an AI agent can produce a perfectly valid SQL query yet return a completely incorrect answer.
The problem, consistent even with AI in the picture, is governance. AI has just made the issue of governance more apparent. “It was never a data quality problem, but it's a governance of meaning problem, and it's been sitting there long before AI showed up. AI has just made it louder now,” Devraju tells Dua.
Devraju will be presenting a talk at Big Data LDN (BDL) this year on Thursday, September 24, on When Migrations Break Your Metrics: Rebuilding Data for Commercial Analytics. The talk is scheduled for 3:20 pm to 3:50 pm in the Data Architecture Modernisation Theatre.
TakeawaysSemantic gaps existed before AI; AI has only made them louder and faster.The same metric is displayed on different dashboards, each using different date logic, filters, or join paths.There can be five different definitions of an "active user" across the five dashboards, all of which are incompatible.SQL can be syntactically correct and yet provide the wrong answer to a business question.Validation should be placed at the definition level, not at the SQL level.AI agents can query the raw staging tables rather than referring to the governed marts by name alone.Incorrect joints or the wrong grain result in numbers that look plausible but are actually wrong.According to dbt Labs research, 72 per cent of peopleprioritise AI-assisted coding while 24 per cent prioritise validation.Incorrect data is more dangerous than having no data; it is the confident errors that pose a risk.Since end users are unable to check the answers at the time they occur, trust has to be established earlier on.Provide a semantic layer that is governed and has version control, with designated owners for each metric.Ad hoc SQL statements on no side-channel should generate the "official" figures that are reported.
Chapters00:00 Introduction to the Semantic Gap in AI02:56 Understanding Data Interpretation and Governance05:56 The Importance of Centralized Definitions09:05 AI Hallucinations and Data Validity12:02 Navigating Governance in AI14:56 The Role of AI in Data Validation17:56 Final Thoughts on AI and Data Meaning
GuestAnanya Devraju — Business Intelligence Developer, Premier Inn
HostShubhangi Dua — Podcast Producer & B2B Tech Journalist, EM360Tech
Listen to more episodes of Don't Panic! It's Just Data on EM360Tech.
#SemanticGap #AIAgents #DataGovernance #DataAnalytics #SemanticLayer #AIData #BusinessIntelligence #DataEngineering #EnterpriseAI #DataQuality
What Is "Agent Debt" and Why Is It Breaking Your AI Code?
2026/08/20
While AI-generated code, also known as vibe coding, is aiding developers in releasing software faster than ever, it seems to be simultaneously causing a greater number of production failures.
According to research carried out by New Relic, 94% of technology leaders think that AI-generated code is of higher quality when it is reviewed, but 78% say they are experiencing more incidents after deployment. Let’s explore why this is happening.
In the recent episode of the Don't Panic It's Just Data podcast, host Christina Stathopoulos, Founder of Dare to Data, was joined by Nic Benders, Chief Technology Strategist at New Relic to talk about "agent debt,” what happens when AI writes great code that breaks in production, and why SREs (Site Reliability Engineers) are left cleaning it up.
Benders states that the issue does not lie with AI itself but rather with a growing phenomenon that he refers to as "agent debt".
After gathering telemetry data, New Relic discovered that the core issues stem from Large Language Models (LLMs). These problems date back to the early days of ChatGPT, when the models were remarkably convincing at generating software code.
“The code looks really good, but it doesn't work in production. It creates incidents down the road,” he tells Stathopoulos.
This is where agent debt comes in.
TakeawaysAI-generated code can increase production incidents despite passing code reviews.'Agent debt' is emerging as the AI-era equivalent of technical debt.Observability must extend beyond applications to AI development workflows.Engineering teams should measure AI value—not just token consumption.AI may deliver greater value reviewing code than writing it.SRE agents will compete on data quality, not model intelligence.Human judgement remains essential for high-risk engineering decisions.
Chapters00:00 Introduction to the episode and guest00:30 Overview of Nick Benders and New Relic's mission01:14 Impact of AI on software development speed and review process02:55 Shift from coding to downstream operations and role changes06:31 Discrepancy between AI-rated quality and incident reports08:08 Understanding agent debt and its signs09:35 The role of observability in AI-generated code in production12:22 Measuring and understanding agent debt through observability14:10 Rethinking the AI software development lifecycle17:30 Automating code review and process checks with AI20:18 Production debugging and the role of AI in incident management21:09 Use case of SRE agents in production environments24:00 Future trends in SRE agents and data focus25:27 Key advice for using AI tools effectively in software and operations
For more information on SRE and agent debt, visit newrelic.com and em360tech.com.
#AgentDebt #AICodingAgents #AIGeneratedCode #AIObservability #SREAgents
agent debt, agent debt explained, agent debt in software development, AI-generated code failures, AI-generated code incidents, AI coding agents, AI coding agents in production, autonomous coding agents, AI code reliability, AI software reliability, AI technical debt, AI-generated software, AI-generated software observability, observability for AI-generated code, AI observability, software observability, production reliability, production incidents, AI incident management, AI-assisted incident response, SRE agents, AI SRE agents, site reliability engineering, AI code review, AI production readiness, AI developer tools, enterprise software development, LLM-generated code, large language model code, New Relic, Nic Benders
How Does a Unified Data Platform Improve Financial Crime Compliance?
2026/07/28
For a long time, financial crime prevention has been a massive issue for banks. This is because of several often complex navigation around rules and regulations, such as AML, KYC, CTF, and SAR. However, a bigger issue has emerged. As more and more transactions happen and financial crime networks get smarter, the bigger problem is the way banks handle data.
In the recent conversation on the Don’t Panic It’s Just Data podcast, host Herb Blecher, Research Director, Data and Analytics, Enterprise Management Associates (EMA), sat down with guest Manish Andhy, Financial Services AI & Industry Executive at Teradata.
They talked about how criminal enterprises are changing fast, like the internet, while compliance systems are still using old methods. Andhy tells Blecher, "The difference between how fast criminals can change and how slow compliance systems are is a big weakness."
More than $3 trillion in money moves through the global financial system every year, but only a small part of it is caught. Banks have spent a lot of time and money building systems to stop money laundering. Many of them still have separate systems for onboarding, transaction monitoring, investigations and risk management.
The strange thing is that big financial institutions have already spent a lot of money to solve this problem. They built data warehouses to get rid of systems and data lakes to put all the information in one place. In fact, they often created the same separate systems they were trying to get rid of.
Also Watch: What is AI Hyper-Personalisation in CX and Why Does it Matter?
TakeawaysOver $3 trillion of illicit funds moves through the global financial system annually.Only about 1% of illicit funds are detected or intercepted.AML programs have grown in a fragmented, siloed way across enterprises.The pace of change in compliance has historically been slow.Traditional rule-based systems generate enormous amounts of false positive alerts.Data silos persist due to organizational and technology issues.Data products allow for a unified view of data without creating new silos.Generative AI can automate parts of the compliance process.Financial institutions must treat data as a strategic asset.Compliance can inform broader business decisions beyond regulatory obligations.
Chapters00:00 Introduction to Financial Crime and Data Analytics05:06 Challenges in Financial Crime Compliance10:05 Data Silos and Their Impact15:12 The Concept of Data Products19:57 Modernizing Financial Crime Strategies24:59 Conclusion and Key Takeaways
For more information on financial crime and how financial institutions should manage their data securely and compliantly, follow Terada across its official channels:
Website: Teradata YouTube: @TeradataLinkedIn: @TeradataX: @Teradata
For more information on enterprise tech analyst-led insights, please visit em360tech.com
EM360Tech YouTube: @enterprisemanagement360EM360Tech LinkedIn: @EM360TechEM360Tech X: @EM360Tech
#Teradata #FinancialCrime #AML #Compliance #DataStrategy #AIinBanking #FinTech #DataSilos #DataManagement #DonTPanicItsJustData #EM360Tech #B2BMarketing #B2BPodcasts
Context, Cost, & AI: Strategies to Optimise Agent Performance & ROI
2026/07/15
After months of experimenting with large language models (LLMs), enterprises are moving from isolated pilots to broad deployments. However, as adoption speeds up, many tech leaders find that the biggest challenge isn't selecting the right AI model but managing the cost of optimising it.
While AI models might be getting more expensive owing to geopolitical tensions and expanding use cases, the added challenge is that the price per token continues to rise. The problem is that enterprise AI is using a lot more tokens as companies scale new applications across different departments.
In the recent episode of the Don’t Panic It’s Just Data podcast, host Kevin Petrie, VP of Research at BARC, sat down with Eudald Camprubi, Co-Founder of Nuclia (acquired by Progress) and Software Fellow at Progress and Michael Marolda, Senior Product Marketing Manager, Agentic RAG.
They talked about how the next phase of enterprise AI will focus less on model selection and more on context engineering, retrieval strategies, and governance.
What Does the Future of Enterprise AI Rely on?As enterprises progress beyond experimentation, success will rely less on picking the next game-changing model and more on using existing models wisely. That means providing precise context instead of excessive context.
Enterprises should select the right model instead of just the latest model. That means they should treat observability, retrieval strategies, and governance as foundational capabilities rather than second priorities.
Camprubí said that enterprise leaders should be wary of industry hype. "Don't trust everything you read on LinkedIn.” In enterprise AI, measurable results will determine which enterprises effectively scale intelligent systems.
Listen to the full episode of Don't Panic! It's Just Data to hear Michael Marolda and Eudald Camprubí discuss Agentic RAG, token optimisation, context engineering, and the future of enterprise AI at scale.
TakeawaysToken costs are climbing, making cost management critical for enterprises.Context is essential for effective AI implementation and user satisfaction.Enterprises must focus on providing the right context to LLMs to avoid hallucinations.Modularity in AI platforms allows for flexibility and adaptability in solutions.Quality metrics are vital for evaluating AI outputs and ensuring reliability.The latest AI models are not always the best choice for every use case.Understanding user intent is crucial for effective data retrieval.FinOps teams are increasingly involved in managing AI costs and strategies.Enterprises should consider RAG as a service to reduce maintenance burdens.Collaboration among stakeholders is essential for successful AI implementation.
Chapters00:00 Introduction to AI and Data Context03:26 Understanding Token Costs in AI09:03 The Importance of Context in AI14:37 Exploring the Context Layer and Retrieval Strategies22:31 Model Selection and Cost Management in AI29:11 Key Takeaways for AI Leaders
For more enterprise AI, Agentic RAG, data governance, and enterprise knowledge layer insights, follow Progress Software across its official channels:
Website: Progress SoftwareYouTube: @ProgressSWLinkedIn: Progress SoftwareX: @ProgressSW
For more information on enterprise tech analyst-led insights, please visit em360tech.com
EM360Tech YouTube: @enterprisemanagement360EM360Tech LinkedIn: @EM360TechEM360Tech X: @EM360Tech
#EnterpriseAI #ContextEngineering #AgenticRAG #AIROI #TokenCosts #AIStrategy #DataManagement #DonTPanicItsJustData #ProgressSoftware #Nuclia
How Enterprise Data Architecture Must Evolve for the Age of AI
2026/06/15
Most enterprises believe they have a data problem. In reality, it is an architecture problem in disguise, and the rise of agentic AI is making that distinction impossible to ignore. That is the central argument Karthik Ranganathan, CEO of Yugabyte, makes in this episode of Don’t Panic! It’s Just Data, hosted by Scott Taylor of MetaMeta Consulting.
The conversation traces 30 years of infrastructure evolution in 30 minutes. From Oracle’s dominance as the monolithic backbone of enterprise applications, to the NoSQL revolution of the mid-2000s, and the cloud-native era of the 2010s, it builds toward the rise of agentic AI. In this new phase, systems do not just store and retrieve data; they act on it autonomously.
“The challenges of current architectures under pressure are no longer theoretical. Agentic systems expose every seam, every silo, every bottleneck you've been quietly managing around,” says Ranganathan.
Why Current Architectures Crack Under Agentic PressureTaylor opens the episode by asking the question many enterprise data leaders are quietly asking: Are today’s architectures actually fit for AI workloads? Raghanathan’s answer is measured. Most are not, and the reasons are structural rather than superficial.
The core issue is fragmentation. Decades of 'good enough' tooling decisions have produced estates where relational databases sit in silos next to document stores, vector indexes live apart from transactional systems, and data pipelines patch the gaps. For traditional applications, this messiness is manageable. For agentic AI, systems that must reason across context, execute multi-step decisions, and maintain coherent state across interactions, it’s a fundamental blocker.
Ranganathan identifies three compounding failure modes: siloed knowledge stores that prevent AI systems from drawing on the full breadth of enterprise information; disconnected memory systems that can't persist context reliably across agent runs; and non-deterministic outputs from large language models (LLMs) that make it difficult to design stable data models around AI-generated results. Together, these problems don't just slow down AI projects; they erode the trust enterprises need to deploy agentic systems at any meaningful scale.
Knowledge vs. MemoryOne of the episode's sharpest conceptual moves comes when Ranganathan draws a clean line between knowledge and memory in AI systems, two concepts that get conflated constantly, and at high cost.
Knowledge, in this framing, is the structured, long-term body of facts and context an AI system can draw on: product catalogues, customer histories, domain documentation, and enterprise policies. Memory, by contrast, is the short-term, session-aware state that lets an AI system track what just happened, what's been decided, and what step comes next in a workflow.
Most current architectures treat these as interchangeable or ignore memory entirely, forcing every agent interaction to start cold. The result is factually capable AI but contextually amnesiac; it knows the company's product catalogue but forgets it already recommended three options to this customer ten minutes ago.
This is the gap Meko, YugaByte's knowledge-memory engine, is designed to close. By building a unified layer that handles both the persistent knowledge graph and the operational memory of active agent sessions, Meko allows enterprises to run agentic workflows without patching together vector databases, caches, and relational stores by hand. It's an architectural bet that the knowledge-memory distinction is not a nuance but a first-class design requirement and that enterprises ignoring it will pay the integration tax repeatedly.
Bridging AI Capability To Business ValueTaylor pushes Ranganathan on the perennial tension between AI capability and business value, a conversation that lands differently now that agentic systems are making decisions, not just recommendations. Raghanathan's view is that the critical role of context in AI workflows is still being underestimated by most enterprises.
He cites YugaByte customers who have moved from proof-of-concept AI deployments to production-grade agentic systems by making one architectural shift, treating context as infrastructure, not as application logic. When context management is embedded in the data layer, versioned, auditable, and available across agent boundaries, the reliability bar for AI systems rises dramatically.
For enterprises ready to act, Ranganathan’s guidance is clear: start by auditing existing architectures for knowledge and memory silos before evaluating AI tooling, invest in unified data models that support both relational and non-relational workloads, and treat the context layer as a core engineering concern rather than an afterthought added to LLM integrations. If you would like to find out more, visit yugabyte.com or connect with Karthik Ranganathan on LinkedIn.
TakeawaysEvolution of data infrastructure for agentic AI.Limitations of current architectures and silos.The role of knowledge and memory in AI systems.Strategies for enterprise data architecture in the AI era.
Chapters00:00 Introduction to Data and AI Infrastructure
03:02 The Evolution of Data Infrastructure
05:53 Understanding Agentic Applications
08:55 The Architecture War in Data Management
11:58 Knowledge vs. Memory in AI
15:00 Operational Challenges in Multi-Agent Environments
17:58 The Importance of Context in AI Workflows
20:49 Bridging the Gap Between AI and Business Value
24:10 Customer Success Stories with YugaByte
26:47 Rethinking Data Architecture for Enterprises
No Use Case, No Value: Why Managing AI Use Cases is Key to Demonstrating Business Value
2026/06/02
AI investment is growing fast, but proving its value remains one of the biggest challenges facing data leaders today. Dashboards are built, models are deployed, and yet when the budget question arrives, most teams still can't clearly demonstrate return on investment.
Speaking on Don't Panic, It's Just Data with host Christina Stathopoulos, Nadiem von Heydebrand, CEO and co-founder of Mindfuel, identified where most organisations go wrong: the interface between data teams and the business. According to von Heydebrand, the reason is straightforward: no use case, no value.
"We get a demand, we believe we've understood it, and we start executing immediately," he explained. Months pass, and nobody can answer why the project exists or what problem it was supposed to solve in the first place. The fix isn't more technology. It's better use case management.
The 3 Pillars of Effective AI Use Case ManagementOne of von Heydebrand’s core principles is straightforward: before you build anything, you need to really understand the business challenge you're trying to solve. "You have to fall in love with the problem, not with the solution," he said. This matters more than ever in the era of generative AI. With token costs attached to every AI interaction, building the wrong solution isn't just a wasted effort; it's an ongoing financial drain. Use case management has moved from being a nice-to-have to an operational necessity. Good use case management, according to Nadiem, rests on three pillars:
Demand exploration: Don't assume you understand the problem. Engage stakeholders, ask deeper questions, and uncover the real business challenge before a single line of code is written.Value management: Every use case needs a value hypothesis. What outcome is expected if this problem is solved? As Nadiem puts it: "The solution itself has a value of zero. Value lives in the problem space."Value tracking: Once live, track performance against the original hypothesis. Define a realistic ROI timeframe and review it consistently.
Adoption Metrics Are Not Proof of ValueOne of the most common mistakes? Measuring AI success through usage and adoption data alone. "I have enough examples where usage is high, and value is zero or even negative," von Heydebrand warned.
Clicks and logins are a proxy. Business outcomes are the goal. If there's no correlation between the two, the metric is misleading.
Output vs. Outcome: The Shift That MattersThe most important distinction in the conversation was the difference between output and outcome. Data teams have historically been measured on output like model accuracy, number of dashboards, and features delivered. But output without impact is just activity. Outcome means the value created for the recipient of your work. Organisations that make this mindset shift from measuring what they produce to measuring what they change are the ones that change their data functions from cost centres into genuine value generators.
For leaders under pressure to prove ROI from AI initiatives, Mindfuel’s CEO advises a pragmatic approach: start now, start small, and be honest. As Stathopoulos summarised: "It all comes back to being intentional about what you build and why." For more information, visit mindfuel.ai, the platform built to help data and AI teams demonstrate, manage, and maximise business value.
Connect with the guest:
Nadiem von Heydebrand: LinkedIn | Mindfuel
TakeawaysThe importance of structured use case managementLinking AI initiatives to business valueThe impact layer and value tracking in AI projects
Chapters00:00 – Introduction to Data and AI Impact Management
03:16 – The Challenge of Connecting AI to Business Outcomes
11:38 – Understanding Use Case Management
17:40 – The Missing Value Layer in Data and AI Initiatives
22:23 – Evolving Mindsets in Data and AI
27:36 – Advice for Leaders on Proving AI ROI
Why Enterprise RAG Systems Still Produce AI Hallucinations
2026/05/22
Podcast: Don’t Panic! It’s Just Data
Guest: Michael Marolda, Senior Product Marketing Manager for Agentic RAG at Progress Software
Host: Shubhangi Dua, Podcast Producer and B2B Tech Journalist at EM360Tech
Generative AI has been brewing in the enterprise tech industry for at least three years now. AI pilots are launching every other day, internal copilots are deployed across enterprise divisions, and now teams themselves are experimenting with large language models (LLMs) to automate business workflows. Such additions have sped up research and notably improved productivity.
While the excitement is valid, the truth beneath is often disregarded. Many enterprise AI systems produce answers that sound convincing, even when they are completely wrong.
In the recent episode of the Don’t Panic! It’s Just Data podcast, Michael Marolda, Senior Product Marketing Manager for Agentic RAG at Progress Software, sat down with host Shubhangi Dua, Podcast Producer and B2B Tech Journalist at EM360Tech.
Marolda argued that the problem is not necessarily with the AI models themselves. The real issue is with the enterprise data foundations supporting them.
“Your AI is only as good as the knowledge it has access to,” Marolda explained during the conversation. The question is what the gap is alluded to in the AI enterprise tech space.
Also Read: Build vs. Buy: The Reality of Production-Grade RAG
What’s the Hidden Risk Costing Enterprises?According to Marolda, around 80 per cent of enterprise data remains unstructured. This includes PDFs, contracts, emails, audio files, presentations, scanned documents, videos, and handwritten notes. This is the kind of information that traditional AI systems struggle to process reliably.
While enterprises are heavily investing in AI infrastructure and model testing, many still do not have systems capable of organising, retrieving, and validating this scattered knowledge. The outcome often turns into a situation where AI tools begin to generate responses without the necessary business context, despite excellent prompt engineering.
“We’ve seen enterprises rush into AI implementations,” Marolda said. “But many pilots fail to scale because the information isn’t grounded in real business data.” It ultimately poses major operational risks for companies, especially in highly regulated industries.
During the podcast, Marolda mentioned a high-profile case involving an airline chatbot that provided customers with incorrect policy information, leading to legal consequences for the company. The issue was not due to malicious intent or a technical failure at the model level — it was due to unreliable data grounding.
For enterprises using AI in customer service, HR, legal operations, finance, or internal knowledge systems, such errors are not rare. In fact, they’ve become a governance issue.
Is Modern RAG the Solution?Enterprises tend to rely on data lakes as centralised storage for vast amounts of information. However, Marolda makes a point about how storage is no longer enough in the age of AI. “A data lake is just cheap storage,” he explained. “A knowledge layer is what actually activates that information for AI.”
This difference is increasingly important as enterprises move from testing to operational AI deployment. Traditional storage systems can hold documents, but they cannot interpret relationships between data points, retrieve context semantically, or validate AI-generated outputs against source material.
An enterprise knowledge layer, on the other hand, is designed to fill that gap. Marolda tells Dua that modern retrieval-augmented generation (RAG) systems can process unstructured data, apply optical character recognition (OCR), convert speech to text from video and audio, and build semantic connections across enterprise content.
This enables AI systems to retrieve not just documents, but highly specific pieces of contextual information, including paragraph-level citations and timestamped video references.
For enterprise leaders, the implications are significant. Rather than viewing AI as a separate assistant, enterprises are increasingly seeing AI as a retrieval and reasoning layer built on top of their knowledge ecosystems.
How Should Enterprises Prioritise Efficiency Over Hype?The economics of AI was a critical discussion Marolda had with Dua. He noted that while many AI providers continue to push for higher token consumption and larger workloads, enterprises such as Progress Software are now beginning to value efficiency instead.
Unlike NVIDIA’s enterprise philosophy, as proposed by its CEO Jensen Huang, is a new compensation model where engineers receive annual AI token budgets worth half their base salary on top of regular pay. During a live interview on the All-In Podcast, recorded in San Jose, California, in March 2026 at Nvidia's GPU Technology Conference (GTC), Huang stated:
"If a $500,000 Engineer Did Not Consume At Least $250,000 Worth of Tokens, I'm Going To Be Deeply Alarmed."
“We’re actually trying to reduce token consumption,” he explained. Such an approach contrasts with broader industry trends focused on maximising AI use at scale. As enterprise AI budgets become more established, CIOs and CFOs are scrutinising infrastructure costs, energy consumption, and long-term operational sustainability.
It’s particularly relevant as enterprises pit multiple LLMs against each other for quality, relevance, and cost efficiency. According to Progress’s Sr. Product Marketing Manager, the next phase of enterprise AI adoption won’t be driven by model capability alone. It will be guided by practical governance, meaning identifying which systems produce the best results at reasonable costs.
Overall, successful AI adoption is not just about selecting the right model but, in fact, pivoting towards building the right knowledge architecture.
For instance, enterprises continue to invest in generative AI; the enterprises that thrive may be the ones that can effectively structure, govern, retrieve, and validate their institutional knowledge.
Key TakeawaysEnterprise AI hallucinations increase without grounded enterprise data.Agentic RAG helps enterprises reduce AI hallucinations and improve accuracy.Unstructured data is the biggest challenge in enterprise AI adoption.Enterprise knowledge layers improve AI governance and traceability.AI token reduction lowers enterprise AI infrastructure costs.RAG architecture helps enterprises scale trustworthy AI systems.
Chapters00:00 Introduction to Enterprise AI and Knowledge Layer02:13 Challenges with Unstructured Data in AI08:11 The Importance of a Knowledge Layer12:04 Trust and Governance in AI Solutions16:48 Progress's Unique Approach to AI Solutions19:15 Agentic RAG: A New Paradigm in AI Retrieval24:52 Real-World Applications of Agentic RAG26:39 Maintaining Quality and Performance in AI Systems28:01 Key Takeaways for IT Decision Makers
For more enterprise AI, Agentic RAG, data governance, and enterprise knowledge layer insights, follow Progress Software across its official channels:
Website: Progress SoftwareYouTube: @ProgressSWLinkedIn: Progress SoftwareX: @ProgressSW
For more
Is “Frankenstein Data” Slowing Down AI Transformation in Insurance Enterprises?
2026/05/07
Podcast Series: Don’t Panic It’s Just Data
Guest: Mark Duffy, Senior Director, Artificial Intelligence & Analytics at Cognizant and Mark Blake, FSI Industry Practice Lead, Stibo Systems
Host: Scott Taylor, The Data Whisperer and Principal Consultant, MetaMeta Consulting
Artificial intelligence (AI) is prevalent in the insurance industry now, but many firms are not seeing the results they expected. The issue isn’t with the AI models; it’s pertinent to the data.
In the recent episode of the Don’t Panic It’s Just Data podcast, host Scott Taylor, The Data Whisperer and Principal Consultant at MetaMeta Consulting, is joined by Mark Duffy, Senior Director, Artificial Intelligence & Analytics at Cognizant and Mark Blake, FSI Industry Practice Lead at Stibo Systems.
The data industry experts address a key misunderstanding about enterprise AI – that companies can innovate their way out of poor data quality. “Some people think AI is a quick fix for data governance,” said host Scott Taylor. “If I need better data, I just use AI.” Experts warn that this belief is what’s holding insurers back.
How Frankenstein Data is Impacting AI?Despite significant investments in AI, cloud, and analytics, many insurers remain stuck in pilot mode. According to Mark Blake of Stibo Systems, the problem is the infrastructure. “AI itself isn’t the challenge,” he said. “It’s the ability to scale it, and that comes back to fixing the data.”
In reality, most insurance enterprises face fragmented, siloed data across systems. Customer, policy, claims, and product data often don’t align. This results in what Taylor calls “Frankenstein data,” where inconsistent records lead to unreliable outputs.
For AI to function effectively at scale, insurers need trusted, governed, and unified data. That’s where data governance and master data management (MDM) come in.
“For us to truly gain benefits from AI, the end user really has to trust the data,” stated Mark Duffy of Cognizant. “That trust comes from having the right data foundation in place.”
Also Watch: Can Your MDM Strategy Survive the Shift to Real-Time AI Decision-Making?
How Master Data Management (MDM) Unlocks Scalable AI?One of the key drivers of AI success in insurance is multi-domain master data management, a system that connects core business data across the enterprise. “You always have to have a starting point,” Blake explained. “Then you expand horizontally across the enterprise.”
The “horizontal data layer” enables insurers to unify key entities like customers, products, and partners—often referred to as the “nouns of the business.” When these are standardised, AI models can work consistently and accurately.
The business impact is substantial, including more accurate underwriting decisions, reduced claims leakage, improved customer experience and retention and better cross-sell and upsell opportunities.
Duffy shared a real-world example in which enhancing data management directly sped up AI adoption. “It gave them trust in the data,” he said. “They could run models faster and gain more value because they weren’t constantly fixing issues.”
Instead of spending 80 per cent of their time cleaning data, teams could finally focus on using it.
Why AI Is Coercing a Data Strategy ResetFor years, data governance struggled to gain executives' support, but now AI has shifted that.“There’s been a refocus,” Blake said. “They’re looking at data in a way they maybe haven’t done historically.”
Today, AI is a priority for boards, driving alignment among CIOs, CDOs, and IT enterprise leaders. “Every C-suite executive wants to do more AI,” Duffy said. “But they’ve realised they can’t do that without the data foundation.”
Still, some enterprises believe AI can fix poor data quality. Experts warn that this is a mistake. “You can use AI to support data quality,” Duffy said. “But you’re not going to use AI to build an MDM solution.”
What’s the Solution to Frankenstein DataAs insurers develop their AI strategies for the next 12 to 24 months, one key ideology was spotlighted – success depends less on speed and more on structure. “Go back to the root cause,” Blake said to Taylor. “Fix that, and then you can move forward with confidence.”
In other words, AI highlights the need for strong data foundations; it doesn’t eradicate them. For insurers serious about AI transformation, that’s no longer optional—it’s where they must begin.
Also Watch: From Chaos to Launch: Your Product is Ready, Your Data Isn't
Key TakeawaysAI in insurance fails without strong data governance and quality foundations.Master Data Management (MDM) is critical for scaling AI across insurance enterprises.Fragmented “siloed data” is the biggest barrier to AI adoption in insurance.Trusted, unified customer and policy data improves AI accuracy and business outcomes.AI cannot fix bad data—insurers must modernise data management first.
Chapters00:00 Introduction to AI Readiness in Insurance03:08 The Importance of Data Foundations06:02 Challenges of Fragmented Data09:06 Modernising Data Foundations for AI11:56 Real-World Use Cases in Insurance15:03 The Role of Master Data Management17:56 Aligning Business and Data Strategies21:06 Final Thoughts on AI and Data Governance
For more information, please visit em360tech.com and stibosystems.com.
To learn more about AI in the MDM space and how they’re progressing enterprise analytics intelligently, follow:
Stibo Systems LinkedIn: @StiboSystems
Stibo Systems X: @StiboSystems
Stibo Systems YouTube: @StiboSystemsGlobal
EM360Tech YouTube: @enterprisemanagement360
EM360Tech LinkedIn: @EM360Tech
EM360Tech X: @EM360Tech
#MasterDataManagement #DataGovernance #AIinInsurance #EnterpriseTech #BigData #DataStrategy #AIReadiness #InsuranceTechnology #cioinsights #StiboSystems #frankensteindata
master data management, MDM, data governance, AI strategy, insurance, enterprise technology, big data, chief data officer, CDO, CIO, data quality, data unification, Stibo Systems, Scott Taylor, Mark Duffy, Mark Blake