Latest / MBA Training Data / Data contracts: how JPMorgan Chase named data owners
Transcript
- 0:00Host: Welcome to the Leaders Insights Podcast.
- 0:08Host: Today's episode, how JPMorgan Chase built data contracts across 50-plus domains.
- 0:12Host: JPMorgan Chase just published how they built data contracts across more than 50 business
- 0:17Host: domains.
- 0:18Host: Before we go further, what's a data contract in plain English?
- 0:22Expert: It's a formal agreement between the team that produces a dataset and the teams that
- 0:26Expert: consume it, spelling out the format, the quality, the update frequency, and who's on the hook
- 0:32Expert: when it breaks.
- 0:34Expert: Think of it like a service level agreement, a promise with consequences, but for data instead
- 0:39Expert: of uptime.
- 0:40Host: Fine, but JPMorgan is a bank with hundreds of business lines.
- 0:44Host: Why is this news in September 2026 and not something they sorted out a decade ago?
- 0:50Expert: Because for years they couldn't answer the most basic question.
- 0:53Expert: Who actually owns this data?
- 0:55Expert: They had hundreds of business lines all touching the same customer records and nobody accountable
- 1:00Expert: when the numbers didn't line up.
- 1:02Expert: What changed is they stopped treating governance as a policy document and started treating it
- 1:07Expert: as a contract with named owners across 50-plus domains, a domain being a coherent slice
- 1:13Expert: of the business, like mortgages or card payments.
- 1:17Host: Named owners sounds like a euphemism for someone to blame.
- 1:20Expert: It is, and that's the point.
- 1:23Expert: Balance without a name attached is theater.
- 1:25Expert: If your credit risk data goes stale and 40 downstream teams inherit garbage, the data
- 1:31Expert: team being responsible means nobody is.
- 1:34Expert: JPMorgan forced the question, which specific person signs off that this dataset meets the
- 1:40Expert: contract?
- 1:41Expert: That's uncomfortable, which is exactly why most banks avoid it.
- 1:45Host: So they solved accountability.
- 1:47Host: What did it cost them in speed?
- 1:49Host: Because the classic failure here is you formalize everything and the whole place seizes up.
- 1:54Expert: That's the trap.
- 1:56Expert: Organizational paralysis, where every data request needs three committees and a prayer.
- 2:01Expert: Their move was to make contracts lightweight at the edges and strict at the core.
- 2:06Expert: A domain publishing a dataset defines its contract once, and consumers subscribe against
- 2:11Expert: it.
- 2:12Expert: You're not renegotiating every time someone wants a table.
- 2:15Expert: You negotiate the interface, then you leave it alone.
- 2:19Host: Give me the failure mode they were escaping.
- 2:21Host: What actually breaks without this?
- 2:24Expert: Silent schema changes.
- 2:26Expert: Someone in one team renames a column from customer underscore ID to cussed underscore
- 2:31Expert: ID on a Tuesday.
- 2:32Expert: And by Wednesday, 12 dashboards are wrong and the fraud model is quietly degrading.
- 2:38Expert: Nobody told anyone because there was no contract saying you can't do that without
- 2:42Expert: notice.
- 2:43Expert: With a contract, that change is a breach.
- 2:45Expert: It gets flagged before it ships, not discovered three weeks later in a regulatory report.
- 2:50Host: You mentioned regulators.
- 2:52Host: Is this compliance dressed up?
- 2:54Host: Or does it genuinely move the needle for a CDO, a chief data officer, the person who
- 2:59Host: answers for all of this?
- 3:00Expert: Both, honestly.
- 3:02Expert: In banking, regulators expect you to trace where a number came from.
- 3:06Expert: Lineage, they call it.
- 3:08Expert: The full paper trail of how data got from source to report.
- 3:13Expert: Data analytics give you that almost for free because every data set has a declared owner
- 3:17Expert: and a declared shape.
- 3:19Expert: But the real win is internal.
- 3:21Expert: Your data scientists stop spending 60% of their time cleaning inputs they don't trust.
- 3:28Expert: That's the number vendors like Monte Carlo and Anomolo love to quote.
- 3:32Expert: Treat it as directional since they sell the fix.
- 3:35Expert: But the direction is right.
- 3:36Host: 60% from vendors trying to sell reliability tools.
- 3:40Host: Noted.
- 3:41Host: So what should a CDO who isn't JP Morgan actually do Monday morning?
- 3:45Host: They don't have that budget or headcount.
- 3:47Expert: Don't start with 50 domains.
- 3:49Expert: Start with one data set that already causes fights.
- 3:52Expert: The one where finance and marketing show up to the same meeting with different revenue
- 3:56Expert: numbers.
- 3:57Expert: Write a one-page contract for it.
- 3:59Expert: Who owns it?
- 4:00Expert: What the fields mean?
- 4:01Expert: How fresh it is?
- 4:02Expert: And who gets paged when it's wrong?
- 4:04Expert: Get the two teams to sign.
- 4:06Host: One page, one data set, two signatures.
- 4:09Expert: Write.
- 4:10Expert: The mistake is treating governance as a program you launch.
- 4:13Expert: It's a habit you build one contract at a time.
- 4:16Expert: JP Morgan didn't wake up with 50 domains covered.
- 4:19Expert: They earned each one by proving the last contract made someone's life measurably less miserable.
- 4:24Host: So the takeaway?
- 4:25Expert: Pick your most argued about data set, write a one-page contract with a named owner, and
- 4:31Expert: make two teams sign it this week.
- 4:33Expert: Everything else is procrastination.
- 4:35Host: That's it.
- 4:36Host: Your decision tools are live at MBA-training.com.