Data Science and Design: A Tale of Two Tribes
Summary
In this talk, Jon explores the often misunderstood relationship between data scientists and designers and how their collaboration can create significant customer value. Drawing on his experience at Intuit, he discusses developing an enterprise-wide A/B testing platform that initially struggled with adoption until working closely with designers to identify key leading metrics like platform ease of use and time to deployment, rather than just lagging outcomes. Jon also recounts a retail case where overwhelming daily data was distilled by studying top-performing store managers in context, enabling the team to design a focused dashboard that increased sales conversion by 10%. Lastly, he highlights eBay's approach to extracting meaningful signals from vast transaction data by partnering designers with 300 data analysts to streamline workflows and reduce insight time from weeks to a day, democratizing access across the company. He concludes that integrating data science fully into product teams alongside design and development creates more delightful, insight-driven products.
Key Insights
-
•
Less than 1% of global data is used to generate human insights, showing the value in efficient data utilization.
-
•
A data scientist combines statistical skills, hacking mindset, and entrepreneurial thinking to solve complex problems.
-
•
At Intuit, pairing designers with data scientists uncovered that ease of use and awareness were key to increasing adoption of an A/B testing platform.
-
•
Lagging indicators like number of experiments performed or features deployed are insufficient alone; leading indicators such as time to consumption and user awareness better drive adoption.
-
•
Ethnographic studies can reveal user behaviors and misalignments in what enterprise teams measure versus what actually drives business outcomes.
-
•
Studying the best-performing store leaders on the floor uncovered critical behaviors that informed a focused dashboard replacing overwhelming 424-page daily reports.
-
•
A simple data product tracking live customer-to-employee ratios, transaction progress, staff availability, and service queue length helped retail store managers improve performance and customer experience.
-
•
eBay’s approach to ‘signal extraction’ from massive data involves time series analysis, decision trees, and close designer-analyst collaboration to cut insight delivery from weeks to a day.
-
•
Democratizing data insights across an enterprise empowers broader decision-making beyond traditional analyst-only access.
-
•
Integrating data science as a core pillar alongside design, development, and product management can transform teams into more effective problem solvers and innovators.
Notable Quotes
"Since we started this presentation, enough data has been collected to fill everyone’s hard drive about 500,000 times, and fewer than 1% is ever used for insights."
"Data scientists are part stats geek, part hacker, and part entrepreneur."
"Develop deep customer empathy — really understand who’s using a product and why — walk a day in their shoes."
"Rapid experimentation with customers is key. Iterate, iterate, iterate."
"It doesn’t matter what the insight is if no one does anything with it."
"We realized we were measuring the wrong things — we focused on lagging indicators rather than the leading ones we could influence."
"Surprisingly, many developers didn’t even know our testing platform existed."
"By studying the best store leaders, we learned patterns that informed a dashboard reducing 424 pages of data to a few key, actionable metrics."
"eBay cut the time it took to get answers from weeks to one day by integrating design with data analysis workflows."
"Bringing data science into the core product process is like adding a fourth leg to the stool — design, development, product management, and data together create delight."
Or choose a question:
More Videos
"I spent too much time trying to change company culture and should have focused more on just getting things done."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"When we understand organizations as ecosystems, we recognize the need for organic simplicity."
Peter MorvilleThe Architecture of Understanding
May 13, 2015
"You’re not one of them. And that is your strength, Renee. That is your power."
Renee ReidBecoming a ResearchH.E.R (Highly Enterprise Ready)
June 3, 2019
"Gesture and embodied actions will be a key tool for understanding user experience as computing moves beyond traditional screen-based interactions."
Dane DeSutterKeeping the Body in Mind: What Gestures and Embodied Actions Tell You That Users May Not
March 26, 2024
"Multiple payment providers aren’t just a feature; they’re an accessibility lifeline for people who can’t read or reach their credit card easily."
Sam ProulxOnline Shopping: Designing an Accessible Experience
October 3, 2023
"Balance UX and CX—making the site work technically is not enough if the content or experience isn’t meaningful."
Andrew Custage Michael MallettThe Digital Journey: Research on Consumer Frustration and Loyalty
March 29, 2023
"Silence is productive—resist the temptation to fill it immediately after asking a question."
Shelby SwitzerMaking Space for Community Knowledge-sharing in a Distributed World
December 10, 2021
"AI can empower researchers to solve pain points — like anticipating trends or critiquing discussion guides — amplifying impact rather than replacing work."
Llewyn PaineCoexisting with AI: A practical guide for researchers to navigate tools, ethics, and integration
March 11, 2025
"The techno-optimist hacker lens believes growth is the only metric that matters, enabling disruption but causing blind spots."
Robin BeersNavigating organizational systems: Rethinking researcher’s role in driving change
March 13, 2025
Latest Books All books
Dig deeper with the Rosenbot
What is the neuroscientific opposite of love and how does it manifest in business?
How should I choose communication channels and message formats to effectively share research insights?
How can teams create lightweight visibility systems that improve workload transparency without reducing productivity?