Composition of Data Products
Fawad A. Qureshi
Field CTO @ Snowflake | LinkedIn Learning Instructor | Sustainability ??, Data Strategy, Business Transformation
Let's talk about the forms of Data Products and why companies need help to build usable ones.
Most organizations think sharing raw data from their source systems qualifies as a usable data product. However, this is far from the truth. Most internal data needs to make more sense to someone outside the organization.
For example, a telecom organization might generate many low-level network signaling data. This data is useless to most organizations in its current form, but once transformed, it could be precious to a retailer tracking foot traffic nationwide. The problem is that converting this signaling data into foot traffic data requires complex transformations. The telecom signaling data comprises of low-level signaling handshake and keep-alive messages. Most companies outside the telecom world need the tools or skills to convert this noisy data into something useful.
The same is true for data products. The more work put into transforming and enriching the data, the more usable and valuable the data product will be. Unfortunately, many companies struggle to build functional data products. They either need more resources or the expertise to do so. As a result, they are often stuck selling raw data, which could be more valuable to their customers.
An airline's Chief Data Officer once told me after listening to my Pizza analogy, "Fawad, forget pizza dough! Most of our data providers give us raw wheat grains, and it takes us several days of ETL to make it usable."
This is a missed opportunity. By taking the time to build finished data products, companies could create much more valuable products that their customers would be willing to pay for.
领英推荐
What to do about it?
So, are you selling your customers raw wheat grains or ready-to-eat pizza slices?
You leave much money on the table if you sell raw wheat grains. By taking the time to transform and enrich your data, you could create much more valuable products that your customers would be willing to pay for. The next time you go to the market, check the prices of pizza dough, frozen pizza, and ready-to-eat pizza slices on a per kilogram basis (or per Pound if you prefer).
Think about the following three points:
If you like, please subscribe to the FAQ on Data newsletter and/or follow Fawad Qureshi on LinkedIn.
Senior solution leader for Data, Analytics, and AI with 23 years experience
1 年I love good analogies. Totally stealing this for my next conversation on data products. You are a masterful story-teller Fawad A. Qureshi
Data Strategy | Data & AI Solutions | Microsoft Azure | Data Management | Data Governance
1 年Great writeup Fawad - Data Products are supposed to solve business problems - Strongly agree - Organizations should think of consumable slices and create a pizza of the right size. "Data as a product" should be implemented if any organization wants to see the real fruits!
Growth Advisor | Business Strategy | Data & AI, Cloud Computing | Entrepreneur
1 年Fawad A. Qureshi you are bang on the money! Loved your pizza lifecycle analogy. To take it a step further, sometimes we, consultants, are even asked to go and find the "wheat grains in a barn"!! ??
Facade, this write up is so spot on, transformation and enrichment is where the hard work occurs including getting the business to tell you what’CORRECT’ data looks like. Great read my friend!!
Make data your greatest asset.
1 年Fawad, I like your analogy of the pizza. You could add the complexity of the 3 stages. As an example, while flour or dough has a better shelf life than a slice of pizza maybe better than a frozen pizza. The pizza slice must be eaten within the shortest possible time or it will no longer taste good. The result is that the valuable data products deteriorate more quickly and therefore entail higher and more complex maintenance. Nevertheless, your statements are aptly correct.