Summary
Curated from community-contributions, these brief video clips feature winning submissions from industry pros sharing their most important lessons on navigating the intersection of UX/Product.
Key Insights
-
•
Design can be treated as an evolving strategy where parts can be shipped incrementally.
-
•
The Judgment of Solomon metaphor helps recognize that shipping partial features is sometimes necessary.
-
•
Investing in slow, steady relationship-building with product partners deeply impacts product success.
-
•
Rapport and shared understanding among team members are key drivers for sustained incremental progress.
-
•
Product development is more about cultivating relationships than moving fast and breaking things.
-
•
UX research roles often expand to facilitating collective knowledge rather than just user data collection.
-
•
Helping a team build on prior research avoids starting from ground zero in every cycle.
-
•
A thriving product team grows its knowledge over time through synthesis and collaboration.
-
•
Research inspires positive change in both teams and end products rather than simply reporting findings.
-
•
Shifts in partnership perspectives can lead to more effective collaboration and better final products.
Notable Quotes
"They’re not living out the Judgment of Solomon every day, where the baby can be split in half."
"Sometimes it’s reasonable to consider your design as strategy and ship a piece now and other pieces later."
"I wish I knew it was okay to invest in relationships; that’s how incremental change happens."
"It’s not move fast and break things; it’s slow and steady."
"Rapport building is slow and steady synthesis that leads to really big ideas."
"I didn’t invest enough in slow and steady relationship building early on, and that led to major shifts."
"Facilitating a shared understanding among everyone on product takes a lot of time."
"It became less important to keep doing fresh research and more important to grow the collective team knowledge."
"Research helps make a positive change on the product team and our end users."
"Both of our perspectives changed, and now we’re seeing that come to fruition through the product we’re building."
Or choose a question:
More Videos
"Our general public, even advanced enterprise users, often struggle to interpret even the most basic charts."
Theresa NeilJust Build Me a Dashboard!
April 9, 2019
"What role does time play as a form of currency in contributing to extractive methods of research?"
Sahibzada MayedThe Politics of Radical Research: A Manifesto
March 27, 2023
"You get a dashboard that shows who applied, who qualified, and even who didn’t qualify—all in real time."
Lily Aduana Savannah Hobbs Brittany Rutherford5 Reasons to Bring Your Recruiting in-House (and How To Do It)
March 12, 2021
"If we could make something really easy for developers, we would drive adoption and continually improve user experiences."
David CroninThe GE Design System and Thoughts about Craft at Scale
May 13, 2015
"We haven’t just invited them, we’ve set the damn table, and sometimes we have to host the damn party."
Jacqui Frey Alison RandSetting the Table for Dynamic Change
October 24, 2019
"You can’t evaluate bias if the AI can’t explain itself."
Daniel J. RosenbergDesigning with and for Artificial Intelligence
August 11, 2022
"Testing with people who have low vision shows that even passing contrast ratios can still result in unreadable text if font weights are too thin."
Kate KalcevichIntegrating Accessibility in DesignOps
September 23, 2024
"Design always means change; if it amplifies what’s already working, that itself is change."
Bob Baxley Sara Asche Anderson Sharon Bautista Frank Duran Jamie Kaspszak Abbey Smalley Sylas SouzaTheme 4: Discussion
January 8, 2024
"We were educated to minimize the value of our own practice and just reproduce what was done elsewhere."
Verónica Urzúa Jorge MontielThe B-side of the Research Impact
March 12, 2021
