Episode Details

Back to Episodes

Master data management: how Salesforce made MDM stick

Episode 72 Published 1 month, 3 weeks ago
Description

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.

Key takeaways

  • Assign one named person, not a committee, to own each core data domain such as customers or products.
  • Start master data work with the records that touch revenue, like customer accounts, before marketing or event data.
  • Build duplicate checks into the workflow so the system matches records before a rep saves a new account.
  • Measure success by the absence of duplicates rather than the volume of records cleaned up after the fact.
  • Do the governance work before feeding data to large language models, which average conflicting records into new wrong ones.

Chapters
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

Go deeper, free lessons

Full article and transcript: https://www.mba-training.com/blog/master-data-management-salesforce-case-study

MBA Training, mba-training.com

Listen Now

Love PodBriefly?

If you like Podbriefly.com, please consider donating to support the ongoing development.

Support Us