Show Notes
Can a company that sells data quality run on fragmented records of its own? Salesforce did for years, inheriting duplicate customer and product records from Tableau, Slack, MuleSoft and Demandware until the same account appeared five times across five systems and quietly inflated its own pipeline numbers. The position here is that master data management fails the moment it is funded like a project with a ribbon cutting.
You come away with the three moves Salesforce used: name one accountable owner per data domain, sequence the revenue critical records first, and embed duplicate checks at the point of entry. Also covered: Gartner's $13 million poor data quality estimate, the 10 to 1 prevention versus remediation ratio, and why large language models amplify bad master data rather than fix it.
0:00 Salesforce's own fragmented customer records 0:46 Why MDM dies as a project 1:15 Account hierarchies and inflated pipeline 2:14 Three fixes any CDO can copy 3:07 Why prevention loses budget to cleanup 3:36 Why AI amplifies bad master data
More from MBA Training Data
Who pays when a fund's NAV is wrong and the manager never saw the error? Under CSSF Circular 24/856 the investment fund manager corrects and compensates, even when the administrator calculated the price. The episode argues that managers should own one position and pricing record, backed by a written pricing policy, rather than inheriting whatever the administrator used.
How did hackers send a ransom note through the real Asos app? Reporting points to a conned employee and, per researcher Kevin Beaumont, Simon AI, a composable customer data platform owned by Monetate that reads straight from Snowflake with MFA optional and off by default. That route is unconfirmed. The episode argues the real failure is ownership: marketing bought it, data engineering wired it to the warehouse, and nobody owned the login.
Agents dominated dbt Summit, but does smart orchestration or a context layer make data agent-ready on its own? The episode argues no. Fanatics Betting and Gaming saw about 0.2% model reuse from dbt State until it declared source freshness and model-level SLAs, which raised reuse to roughly 15%. The same pattern runs through Fivetran's Context Layer, AI audit trails and token costs.
How did an attacker using ARTEX, an open-source agentic AI penetration-testing tool, take data on more than 67,000 customers from seven South Korean firms, including Shinhan, KB Kookmin and Hana, without touching core banking? The episode argues the failure was data access design. Broker portals and employee apps returned income, loan limits and resident registration numbers to callers who did not need them, despite nearly 124 billion won in security spending.
What happens when a data platform is legally defensible, operationally embedded and publicly distrusted at the same time? More than 44,000 people have filed Article 21 objections under UK GDPR against NHS England's Palantir-powered Federated Data Platform, live in 142 trusts, weeks before a February 2027 contract break clause comes into reach. The position here: objection handling is a throughput problem, not a policy document.