I first talked about my definition of Data Product in Episode 105 of my podcast, because I didn't want to be guilty of talking about a concept for years without actually defining what I mean.

I consider my definition the "producty" one, one which focuses less on the technical output and asset being made, and rather, on the innate value and benefits the output enables. Myself, and folks in our DPLC community, tend to also believe that producty data product salso leverage the methods of software product management and UX design as well—and that this is what enables them to create value worth paying for.

Data Product, Defined but Evolving

Like with code, sometimes seeing the evolution and change log is helpful. Products are also about getting started, shipping it, getting feedback. So, I'm having fun doing that with this evolving definition.

Here's the latest definition:

v2. 7/21/23 A data product is a managed, end-to-end software solution that organizes, refines, or transforms data to solve a problem that's so important customers would pay for it or exchange something of value to use it.

v1. 11/29/22 A data product is a data-driven end-to-end, human-in-the-loop decision support solution that’s so valuable, users will pay to use it if they have to.”*

*Version 1 of these definitions was first contemplated in my deep-dive solo podcast episode #105.

Photo by Suresh Designer on Unsplash