#61 Driving Value Through Participating in the Data Economy - Data Innovation Summit Takeover Interview w/ Jarkko Moilanen

Provided as a free resource by DataStax https://www.datastax.com/products/datastax-astra?utm_source=DataMeshRadio (AstraDB) https://www.patreon.com/datameshradio (Data Mesh Radio Patreon) - get access to interviews well before they are released Transcript for this episode (https://docs.google.com/document/d/1VjP8lguv5L3LNdgMV4MBnNw8SMCe_QNV83qr0a8NtRs/edit?usp=sharing (link)) provided by Starburst. See their Data Mesh Summit recordings https://www.starburst.io/learn/events-webinars/datanova-on-demand/?datameshradio (here) and their great data mesh resource center https://www.starburst.io/info/distributed-data-mesh-resource-center/?datameshradio (here) This episode is part of the Data Innovation Summit Takeover week of Data Mesh Radio. Data Innovation Summit website: https://datainnovationsummit.com/ (https://datainnovationsummit.com/); use code DATAMESHR20G for 20% off tickets Free Ticket Raffle for Data Innovation Summit (submissions must be by April 25 at 11:59pm PST): https://forms.gle/gRa8hCFQAkmbtmSJ7 (Google Form) Scott interviewed Jarkko Moilanen, a Data Economist and Country CDO ambassador for Finland. Jarkko will be presenting on "Data Monetization and Related Data Value Chain Requires Both Data Products and Services" on May 6th in track M6. Jarkko is approaching measuring the value of data and then trying to extract that value from data from many different angles. He is thinking about data products, data as a service, data as a product, etc. Per Jarkko, treating data like a product can apply a LOT of the learnings from the API revolution - this time around we can skip a lot of the sharp edges. APIs are about an interface to value creation - how can we treat data products the same way? We discussed the difference between return and return on investment. A data initiative may have a very high return but if the investment to get that return is too high, it's a bad initiative. How do we get to figuring out what quality level we need to solve our challenges - there is no reason to go for 5 9s qualit