

134.5K
Downloads
167
Episodes
Is the value of your enterprise analytics SAAS or AI product not obvious through it’s UI/UX? Got the data and ML models right...but user adoption of your dashboards and UI isn’t what you hoped it would be? While it is easier than ever to create AI and analytics solutions from a technology perspective, do you find as a founder or product leader that getting users to use and buyers to buy seems harder than it should be? If you lead an internal enterprise data team, have you heard that a ”data product” approach can help—but you’re concerned it’s all hype? My name is Brian T. O’Neill, and on Experiencing Data—one of the top 2% of podcasts in the world—I share the stories of leaders who are leveraging product and UX design to make SAAS analytics, AI applications, and internal data products indispensable to their customers. After all, you can’t create business value with data if the humans in the loop can’t or won’t use your solutions. Every 2 weeks, I release interviews with experts and impressive people I’ve met who are doing interesting work at the intersection of enterprise software product management, UX design, AI and analytics—work that you need to hear about and from whom I hope you can borrow strategies. I also occasionally record solo episodes on applying UI/UX design strategies to data products—so you and your team can unlock financial value by making your users’ and customers’ lives better. Hashtag: #ExperiencingData. JOIN MY INSIGHTS LIST FOR 1-PAGE EPISODE SUMMARIES, TRANSCRIPTS, AND FREE UX STRATEGY TIPS https://designingforanalytics.com/ed ABOUT THE HOST, BRIAN T. O’NEILL: https://designingforanalytics.com/bio/
Episodes

Tuesday Dec 01, 2020
053 - Creating (and Debugging) Successful Data Product Teams with Jesse Anderson
Tuesday Dec 01, 2020
Tuesday Dec 01, 2020
In this episode of Experiencing Data, I speak with Jesse Anderson, who is Managing Director of the Big Data Institute and author of a new book
titled, Data Teams: A Unified Management Model for Successful Data-Focused Teams. Jesse opens up about why teams often run into trouble in their efforts to build data products, and what can be done to drive better outcomes.
In our chat, we covered:
- Jesse’s concept of debugging teams
- How Jesse defines a data product, how he distinguishes them from software products
- What users care about in useful data products
- Why your tech leads need to be involved with frontline customers, users, and business leaders
- Brian’s take on Jesse’s definition of a “data team” and the roles involved-especially around two particular disciplines
- The role that product owners tend to play in highly productive teams
- What conditions lead teams to building the wrong product
- How data teams are challenged to bring together parts of the company that never talk to each other – like business, analytics, and engineering teams
- The differences in how tech companies create software and data products, versus how non-digital natives often go about the process
Quotes from Today’s Episode
“I have a sneaking suspicion that leads and even individual contributors will want to read this book, but it’s more [to provide] suggestions for middle,upper management, and executive management.” – Jesse
“With data engineering, we can’t make v1 and v2 of data products. We actually have to make sure that our data products can be changed and evolve, otherwise we will be constantly shooting ourselves in the foot. And this is where the experience or the difference between a data engineer and software engineer comes into place.” – Jesse
“I think there’s high value in lots of interfacing between the tech leads and whoever the frontline customers are…” – Brian
“In my opinion-and this is what I talked about in some of the chapters-the business should be directly interacting with the data teams.” – Jesse
“[The reason] I advocate so strongly for having skilled product management in [a product design] group is because they need to be shielding teams that are doing implementation from the thrashing that may be going on upstairs.” – Brian
“One of the most difficult things of data teams is actually bringing together parts of the company that never talk to each other.” – Jesse
Links
- Big Data Institute
- Data Teams: A Unified Management Model for Successful Data-Focused Teams
- Follow Jesse on Twitter
- Connect with Jesse on LinkedIn
Comments (0)
To leave or reply to comments, please download free Podbean or
No Comments
To leave or reply to comments,
please download free Podbean App.