Data Product

A platform that nobody adopts is not a product; the work is to treat data as something with users and owners. The page starts with a definition checklist and a framework for a data product, then moves to treating the data platform itself as a product.

A product needs a contract with its consumers and a platform to run on. The same notes are in Data Contract and Data Platforms.

The definition comes as a checklist: the Definition, phdata.io starts by asking whether there is a general description of what you want to do with the data and what the user is looking for. A checklist says what to ask; a framework says who answers. The (good) A framework for a data product is good on accountability, boundaries, contracts, expectations, consumers, and knowledge.

The same thinking applies one level up, to the platform that serves those products. A meta discussion on a data platform as a product is one team's account of building their data platform as a product. Build a data platform as a product, read through its archived copy, is Filipe Rigueiro's breakdown of the challenges, teachable moments, frameworks, and recommendations for delivering a data platform successfully.

Deprecated links

These links and images no longer work. The original wording is kept here. A same-resource copy, when one was checked, is used above.

• build a data platform as a product. This address no longer opens: https://productcoalition.com/how-to-design-and-build-a-data-platform-as-a-product-d22329ff5a3f