Episode 44: Designing Data Products People Actually Want to Use

Dr. Genevieve Hayes and Brian T. O'Neill kick off the episode by discussing the critical but often overlooked role of UI/UX design in the development of data products. They emphasize that merely fulfilling stakeholder requests is not enough—it's essential to create products that are user-friendly and truly meet the underlying needs of users. Brian shares his unique journey from music to data product design, illustrating how his diverse background informs his approach to creating valuable data tools.

A major discussion point revolves around the common disconnect between what stakeholders ask for and what they actually need. Brian explains that often stakeholders articulate solutions instead of problems, leading to a mismatch in expectations. He encourages data scientists to engage in deeper conversations with stakeholders and to practice active listening to uncover true needs—this approach is rooted in user-centered design principles.

The conversation shifts to the importance of routine interaction with end-users. Brian advocates for integrating user feedback throughout the design process, suggesting methods like 'shadowing' to gain insight into users' pain points. This practice helps data scientists and product designers to better understand users' experiences and challenges, ultimately leading to products that are more likely to be adopted.

Brian challenges the notion that self-serve analytics tools are universally beneficial. He argues that while customization options can seem appealing, they often lead to ambiguity and frustration among users who may not fully understand how to utilize them effectively. Instead, he advocates for delivering clear, actionable insights without overwhelming users with raw data.

Brian introduces the concept of value exchange in the context of data products, where users should see enough benefit to willingly adopt new tools or solutions. He stresses the need for data scientists to shift their focus from outputs to outcomes, underlining that the ultimate objective should be to generate positive user experiences that translate into business value.

Brian discusses the CED framework, which stands for Conclusions, Evidence, and Data. He highlights the importance of leading with conclusions in data product design, ensuring that users can grasp the implications of the data at a glance and simplifying their decision-making process. He elaborates on how this framework can enhance the effectiveness of dashboards and other data solutions.

In wrapping up, Brian offers valuable final advice for data scientists: develop empathy for users through direct exposure and dialogue. He promotes the idea that understanding the user experience is crucial for creating effective data products. He also emphasizes the collaborative nature of design and the necessity of involving users in the design process.