Summary
As a product designer, do you trust data when it defies your intuition? What about those times when following data leads you astray? How can you balance the need for experimentation and iteration with the dangers of over-optimization? What are some of the ways that being "data driven" can go wrong? Follow along and learn about the Amplitude design team's journey blending qualitative and quantitative research to drive design strategy—while balancing quality and velocity.
Key Insights
-
•
Designers using product analytics increased by roughly one-third in a year, signalling a shift to data-informed design roles.
-
•
Over-optimizing metrics can backfire, leading teams to improve numbers at the expense of user satisfaction.
-
•
A project ambiguity framework helps determine when and which metrics should guide product initiatives.
-
•
Blue sky (innovative) projects should not be constrained by short-term gating metrics to unleash creativity.
-
•
Aligning qualitative feedback with segmented data strengthens proposals and builds stakeholder confidence.
-
•
Connecting UX improvements via user journeys directly to business outcomes creates a common language for teams.
-
•
Data is not a one-time check but an ongoing feedback loop between research insights and user behavior.
-
•
Misleading data presentations, like altered graph axes, can distort truths and harm decision-making.
-
•
Building relationships with data scientists and sharing joint goals improves collaboration and data use.
-
•
To influence leadership decisions, designers must understand and speak the language of power and metrics relevant to their organization.
Notable Quotes
"It’s a great time to be a designer, and a great time to be making data-driven design decisions."
"We became addicted to our loop of over-optimization, driving metrics that made users frustrated."
"Blue sky projects should have no gating metrics and no short-term metrics."
"We broke down all of our qualitative feedback into different dimensions, which helped lend confidence."
"You can usually draw a convincing dotted line between a UX improvement and a hard business outcome."
"Data is a language you need to learn to speak it."
"Just because it’s a number or chart doesn’t mean it’s true, accurate, or fair."
"Sometimes you lose sight of the forest for the trees when over-optimizing for a single metric."
"Make two teams have the same goal to incentivize collaboration and melt away competing incentives."
"Data is a mindset. It’s never one and done, but a continuous process."
Or choose a question:
More Videos
"A 101 conversation over coffee yields better insights than written reviews in 360 assessments."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"UX directors often feel like this poor person in the middle here getting pulled in all these directions."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"Governance isn’t about choking creativity, it’s about putting bounds and clarity that enable purposeful collaboration."
Lisa WelchmanCleaning Up Our Mess: Digital Governance for Designers
June 14, 2018
"Sustainable practices are not just a luxury; they are a necessity for our survival."
Vincent BrathwaiteOpener: Past, Present, and Future—Closing the Racial Divide in Design Teams
October 22, 2020
"Design your processes around learning, have blameless post mortems and celebrate failures especially."
Brenna FallonLearning Over Outcomes
October 24, 2019
"It’s human infrastructure—community organizing, unions, activists—that saves the day when other infrastructures break down."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"If you don’t bring stakeholders into the research journey, they won’t believe or use the data."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"Knowledge needs to be thought of as a reusable circular process, not a linear one ending at project completion."
Designing Systems at Scale
November 7, 2018
"A lot of developers are way too confident they write perfect code; testing bug fixes often reveals hidden issues."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024
