How to treat your data as a product
summary
Argues for shifting ownership left so domain teams deliver and own reusable datasets, citing the four data mesh principles and recommending data mesh thinking rather than new tooling; prescribes a data contract (points to the Open Data Contract standard based on PayPal’s template) that includes schema, SLAs, security and pricing; shows a filled Data Product Design Canvas, calls for self-serve data platform, observability and event-storming to discover domains, and warns that governance and interfaces — not specific storage tech — decide success.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:08Data needs product thinking
- 6:29Data mesh and decentralized management
- 9:42Data as a product
- 13:37Organizational shifts for ownership
- 14:40Technical structure of data product
- 18:39Interfaces between teams
- 20:05Role of data contracts
- 23:40New roles in data teams
- 24:45Steps to start journey
- 27:33Conclusion and Q&A
related talks
51mData Mesh – Successful with People, Process, and Technology
52mFrom Data Mess to Data Mesh: Navigating People, Process & Platforms
39mData Mesh: Why, What and How
01h 00mData Mesh: Beyond the Data Lake
43mWhen design meets data: Using Data Mesh for a consumer and business-driven data strategy
43mUntangling Data Mesh: A paradigm shift in Big Data
20mEmbracing Data Mesh: A Modern Strategy for Scalable Data Management
38mData Mesh, Now