https://www.patreon.com/datameshradio (Data Mesh Radio Patreon) - get access to interviews well before they are released Episode list and links to all available episode transcripts (most interviews from #32 on) https://docs.google.com/spreadsheets/d/1ZmCIinVgIm0xjIVFpL9jMtCiOlBQ7LbvLmtmb0FKcQc/edit?usp=sharing (here) Provided as a free resource by DataStax https://www.datastax.com/products/datastax-astra?utm_source=DataMeshRadio (AstraDB); George Trujillo's contact info: email (george.trujillo@datastax.com) and https://www.linkedin.com/in/georgetrujillo/ (LinkedIn) Transcript for this episode (https://docs.google.com/document/d/1I0dD4CGQyVxfQHzEF6EbEqN-ossHUnGtjt2zRrL_bPw/edit?usp=sharing (link)) provided by Starburst. See their Data Mesh Summit recordings https://www.starburst.io/learn/events-webinars/datanova-on-demand/?utm_campaign=starburst-brand&utm_medium=outbound&utm_source=&utm_type=&utm_content=dmradiodnvid&utm_term= (here) and their great data mesh resource center https://www.starburst.io/info/distributed-data-mesh-resource-center/?utm_campaign=starburst-brand&utm_medium=outbound&utm_source=&utm_type=&utm_content=dmradiodmcenter&utm_term= (here). You can download their Data Mesh for Dummies e-book (info gated) https://starburst.io/info/data-mesh-for-dummies/?utm_campaign=starburst-brand&utm_medium=outbound&utm_source=&utm_type=&utm_content=dmradiodnvid&utm_term= (here). Jill's LinkedIn: https://www.linkedin.com/in/jillianmaffeo/ (https://www.linkedin.com/in/jillianmaffeo/) Developing Interoperable Channel Domain Data (blog post): https://vista.io/blog/developing-interoperable-channel-domain-data (https://vista.io/blog/developing-interoperable-channel-domain-data) In this episode, Scott interviewed Jill Maffeo, Senior Data Product Manager at Vista. Before jumping in, Jill gives a lot of very useful examples of outcomes they've been able to drive that could be abstracted to apply to your own organization's business challenges. Outcomes like better customer segmentation, faster time to launch new offerings, etc. If you are having difficulty with stakeholder buy-in, especially for someone in marketing, this episode could help you frame things in their language.

Some key takeaways/thoughts from Jill's point of view: "When you're thinking about interoperability, it's just playing nice, right?" If you think of interoperability as a key part of your culture, it's easier to implement. Let people know why interoperability is good for them and the whole company. Taxonomies help drive interoperability because there is already an established language even if things don't fit perfectly. New concepts can emerge and your taxonomies should change. But it makes the interoperability discussions have at least a common starting point. Taxonomies are a living thing - make sure they aren't overly rigid and be prepared to continually evolve and improve them. Within your taxonomy structure, if there is a reason for things to be unique for a domain or use case, that is okay. Look for potential ways to also convert that data to best fit your taxonomy but you don't want to force a square peg through a round hole. Taxonomies really start to add a lot of value at scale. They are somewhat costly upfront with likely moderate return on investment early; but, if you do them right, will pay back a lot as you move forward. They make historical analysis - especially with interoperability - far easier because you've done the work ahead of time. Taxonomy, when done well, is about balancing standardization and flexibility. Much like most things in data mesh, it's about finding the right balance for your organization. Most customer journeys are cross domain. The more you make domain data interoperable, the more insight you have into the customer that can drive better business with your organization as a whole instead of only trying to locally optimize value by domain....