The Data Product ABCs
summary
Defines a data product by concrete rules: named owner roles (product domain, technical steward, business steward), a drawn boundary (table/API/S3 in a cloud data warehouse), and a contract—fields guaranteed, SLA (near‑real‑time with up to one hour lag), test and quality checks. Requires enumerated downstream consumers and a roadmap for unknown use cases, explicit schemas and semantics (one email per user), adoption metrics as baseline, life‑cycle decisions to market or kill unused products, and an agile loop for iteration.
AI-written summary · about
chapters (12)
- 0:00Introduction and speakers
- 2:50Data mesh and data products
- 5:35The data products ABCs framework
- 7:01Accountability in data products
- 8:26Boundaries and contracts
- 10:12Downstream consumers and value
- 13:43Explicit knowledge and semantics
- 15:25Example: user data product
- 18:51Agile data governance approach
- 21:19Iteration and lifecycle
- 22:22Metrics and adoption
- 24:46Data marketing and summary
related talks
30mData Products 101: From Data Chaos to Clarity
22mData as a Product: Transforming Analytics for Business Success
29mHow to treat your data as a product
23mApplying Data Mesh to Your Organization
41mData Quality: The Holy Grail For A Data Fluent Organization
40mData Products and AI: A Conversation on Success Factors and Hurdles
17mSpeeding Data Product Delivery from Model to Marketplace
13mData for product