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
Join us for a different type of Quant vs. Qual discussion: instead of discussing how data science and quantitative research methods can power UX research and design, we’re going to talk about designing enterprise data products and tools that put ML and analytics into the hands of users. Does this call for new, different, or modified approaches to UX research and design? Or do these technologies have nothing to do with how we approach design for data products? 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
"Day one is all about ensuring craft on a massive scale, led by Uday Gahender."
Bria AlexanderOpening Remarks
June 9, 2021
"When I started, I was the first designer among engineers who already prized ease of use as a key advantage."
JJ KercherA Roadmap for Maturing Design in the Enterprise
June 15, 2018
"Ops-first means standardizing processes so we can scale and onboard new team members quickly."
Clemens Janssen Jane DavisEfficiently Scaling Research as a Team of One
March 28, 2023
"The company created a new perk that allows us to have half day Fridays to help with work life balance."
Kurdin Bazaz Liz Rytting Alex KarrCulture, DIBS & Recruiting
June 10, 2021
"Ethnio allowed us to track participants' total compensation and set annual caps, reducing fraud risk and improving compliance."
Sarah Sgarlato Pierini Kevin NewtonFrom Passion to Execution: A Story of Evolving Research Maturity at LinkedIn
September 9, 2022
"No matter the circumstances, the answer to 'Can we?' is always yes, we can."
Lada GorlenkoTheme 2 Intro
June 9, 2022
"People are re-evaluating their lives and careers, which inspired me to start a podcast exploring these shifts."
Bria Alexander Meredith Black Tim GilliganState of DesignOps Panel
October 1, 2021
"You can connect tools like Zapier or Integromat to Coda packs to automate processes and integrate with external systems."
Scott StephensThe Next Generation in DesignOps Toolsets
July 28, 2022
"We took all the leadership admins to a call center for a week to make them feel what customers go through."
Panel Discussion: Communicating the Value of DesignOps
November 7, 2018
