Log in or create a free Rosenverse account to watch this video.
Log in Create free account100s of community videos are available to free members. Conference talks are generally available to Gold members.
Does Designing and Researching Data Products Powered by ML/AI and Analytics Call for New UX Methods?
Summary
The session’s host will be Brian T. O’Neill who is also the host of the Experiencing Data podcast and founder of Designing for Analytics, an independent consultancy that helps data products leaders use design-driven innovation to deliver better ML and analytics user experiences. In this session, we’ll be sharing some rapid [slides-optional] anecdotes and stories from the attendees and then open up the conversation to everyone.
We hope to get perspectives from both enterprise data teams doing “internal” data analytics or ML/AI solutions development as well as software/tech companies as well who may offer data-related platform tools, intelligence/SAAS products, BI/decision support solutions, etc. Slots are open to both experienced UX practitioners as well as data science / analytics / technical participants who may have participated in design or UX work with colleagues. Please share! If folks are too quiet in the session, you may be subject to a drum or tambourine solo from Brian. Nobody has all of this “figured out yet” and experiments and trials are welcome.
Key Insights
-
•
UX researchers in ML-heavy environments often face steep domain knowledge gaps requiring strong interview facilitation to bridge communication.
-
•
Designing for AI data products demands a shift from generic user interfaces to tools tailored for expert users who need explainability over polish.
-
•
Cross-functional collaboration thrives by creating shared spaces that respect differing expertise while focusing on a unifying product goal.
-
•
Decision culture focusing on how decisions are made is more useful than a vague data culture mindset when designing AI/ML products.
-
•
Besides customers and stakeholders, data labelers who curate training data form a critical, often overlooked human part of the ML ecosystem.
-
•
Model interpretability can be more important than raw accuracy because users must trust a system to adopt it and generate value.
-
•
Prototyping data products requires believable data and can be facilitated by testing edge cases like false positives and trust thresholds early.
-
•
Incremental learning loops involving user feedback can improve models over time and should be designed into AI products.
-
•
Contextualizing data model outputs with business rules and user environment (e.g., seasonal factors) increases relevance and trust.
-
•
No-code data science tools and scenario building help teams quickly experiment with data products despite the usual slow model training cycles.
Notable Quotes
"Smoke comes out of my ears when I'm talking to some of the more advanced applications in machine learning."
"Design is about creating that shared space where we look at problems through different lenses."
"Decision culture is a better lens than data culture for thinking about what decisions we're trying to facilitate with AI."
"Not everyone using machine learning is your user; think also about the people labeling the data feeding these models."
"If nobody uses this because they don’t trust it, it doesn’t matter how accurate the model is."
"You need to prototype with real or believable data so the data doesn’t change the context of use."
"Some things that look like blockers, like domain expertise gaps, actually force you to become a better interviewer."
"We’re not always trying to use machine learning everywhere—sometimes the answer is to ignore it."
"Users want to understand why this happened, what will happen, and how can we make it happen—explainability is critical."
"The presenting problem might be a dashboard with a score, but the real need is deciding what to do with that information."
Or choose a question:
More Videos
"Think of a creative professional as an ideas athlete or a creativity Olympian."
Dr. Karl JeffriesThe Science of Creativity for DesignOps
January 8, 2024
"Find your senior executive ally who understands design and go talk to them first — it works."
Amy MarquezINVEST: Discussion
June 15, 2018
"Visualizing data in a way executives can interpret is key to shifting from I think to I know."
Steve Portigal Chris Chapo Kelly Goto Christian RohrerDiscussion
May 13, 2015
"Splitting people’s allocation across different teams created work-life balance issues requiring more oversight."
Alicia MootyDesign Staffing Models
September 30, 2021
"We may not have tech prowess but our sticky notes, card sorts, and test reports are our real superpowers."
Ana Maria Montero Barrantes Aditi Dhar Michelle Kaplan Nate Osborne Matt LaurenceThe Authentic UX Talent Show
January 8, 2024
"We can’t complain about not having a seat at the table if we don’t offer one of our own."
Lada Gorlenko Sharbani Dhar Sébastien Malo Rob Mitzel Ivana Ng Michal Anne RogondinoTheme 1: Discussion
January 8, 2024
"Data entry is the enemy; automation is the key to making research repositories successful."
Sofia QuinteroThe Product Philosophy Behind EnjoyHQ
March 10, 2021
"If you think innovation can happen without buy-in from the CEO, I would love to see that; I have not seen it work."
Laura KleinUnique challenges of innovation in enterprises
April 23, 2020
"You’ve got to take control of the backlog and position your team as value-driven, not just servicing individual teams."
Andrew MichaelBuilding a Product Insights Team
March 10, 2022
Latest Books All books
Dig deeper with the Rosenbot
How does context influence the behavior of AI products beyond the model itself?
How can senior designers coach junior designers to maintain intentional design decisions while using AI?
What are the challenges of demand charges in residential solar rate plans and how can they be managed automatically?