Do you ever find it hard to get the requirements, problems, or needs out of your customers, stakeholders, or users when creating a data product? This week I’m coming to you solo to share reasons your stakeholders, users, or customers may not be making time for your discovery efforts. I’ve outlined 10 reasons, and delve into those in the first part of this episode.

In part two, I am going to share a big update about the Data Product Leadership Community (DPLC) I’m hoping to launch in June 2023. I have created a Google Doc outlining how v1 of the community will work as well as 6 specific benefits that I hope you’ll be able to achieve in the first year of participating. However, I need your feedback to know if this is shaping up into the community you want to join. As such, at the end of this episode, I’ll ask you to head over to the Google Doc and leave a comment. To get the document link, just add your email address to the DPLC announcement list at http://designingforanalytics.com/community and you’ll get a confirmation email back with the link.

Links

Join the Data Product Leadership Community at designingforanalytics.com/thecommunity
My definition of “data product” is outlined on Experiencing Data Episode 105
Product vs. Feature Teams by Marty Cagan
Email Brian at brian@designingforanalytics.com.

From the Vault: The Universe in 100 Colors, with Tyler Thrasher

Stuff To Blow Your Mind

Cultural and Historical Colors: Mummy Brown

The AI-powered Podcast Player