Short Take #2: UX/Product Lessons from Your Industry Peers
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
"Everyone wants to see themselves reflected in the research questions and findings."
Jerome “Axle” BrownHow to Use Self-Directed Learning to Ensure Your Research Insights are Heard and Acted Upon
March 11, 2021
"We had an engineering culture that confused uniformity with design, and consistency with design."
Phil GilbertA Consistent Culture of Design
May 14, 2015
"Synthetic users might be okay for finding average behaviors, but they won’t replace unique insights from real users."
Kate Towsey Basel Fakhoury Oren Friedman Graham GardnerParticipant Recruitment and Management Tools
March 12, 2026
"We showed that a skip is not a skip — it varies based on listener goals and trust in the playlist."
Sohit KarolDesigning Delightful Listening Experiences: Mixed Methods Research in the Age of Machine Learning
March 31, 2020
"Developers were hungry for the bigger picture, but the only information available to them was a set of user stories."
Christopher Taylor Edwards Valerie RoskeDesign as a Team Practice, A Practical Guide to Cross-functional Collaboration
September 30, 2021
"There is no silver bullet in system-level challenges; multiple interventions across different domains are needed."
Sheryl CababaExpanding Your Design Lens with Systems Thinking
February 23, 2023
"We had to push back on the idea that we could just use existing models without understanding our team’s needs."
Francesca Barrientos, PhDYou Need Your Own Definition of Design Maturity
June 8, 2022
"I’ve onboarded 80% of the design and CX department, and it really shapes their trajectory and connection to culture."
Allison SandersOperating with Purpose
January 8, 2024
"That's not a prototype."
Saara Kamppari-Miller"Prototype" vs "Prototype"--Breaking Down and Rebuilding Our Understanding of What We Do
October 24, 2019
