Episode Details

Back to Episodes

Data contracts: how JPMorgan Chase named data owners

Episode 75 Published 1 month, 3 weeks ago
Description

Who owns a dataset, and what happens when it breaks? JPMorgan Chase could not answer that for years across hundreds of business lines, so it replaced governance policy documents with data contracts covering more than 50 domains, each with a named person who signs off on format, quality, freshness and escalation. The position here: accountability without a name attached is theater.

You get the design that avoids organizational paralysis, contracts strict at the core and light at the edges, where consumers subscribe to a published interface instead of renegotiating each request. You also get the failure mode being avoided, silent schema changes, the lineage case regulators care about, a caution on the vendor-quoted 60% cleanup figure from Monte Carlo and Anomalo, and a one-page contract to write this week.

Key takeaways

  • Name a specific person who signs off that a dataset meets its contract, since making the data team responsible means nobody is.
  • Define a contract once at the publishing domain and let consumers subscribe, so you negotiate the interface rather than every table request.
  • Write the contract to cover format, field meanings, update frequency and who gets paged when it breaks.
  • Treat an undeclared schema change, like renaming customer_id, as a breach that is flagged before it ships.
  • Start with the one dataset that already causes fights between finance and marketing, one page and two signatures, instead of launching a 50-domain program.

Chapters
0:00 What a data contract actually is
0:40 Why nobody owned the data
1:17 Named owners beat team accountability
2:19 Silent schema changes break dashboards
2:50 Lineage, regulators and analyst cleanup time
3:41 One-page data contract to start Monday

Go deeper, free lessons

Full article and transcript: https://www.mba-training.com/blog/data-contracts-ownership-domains-jpmorgan

MBA Training, mba-training.com

Listen Now

Love PodBriefly?

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

Support Us