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
"Some of the most important decisions for service design happen on whiteboards among engineers, often without service design representation."
John CutlerOxbows, Rivers, and Estuaries: How to navigate the currents of change (without burning out)
December 3, 2024
"By observing Jeff's concerns and asking questions, I was able to show empathy and distract myself from getting defensive."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"You don’t have to sit through two hours a day; we’ll spend about 15 minutes on setup then you’ll pair up and do the exercise."
Dave GrayGroup Activity: Making Sense of DesignOps
November 7, 2017
"What would it look like if we could ask, how do I make this the absolute best environment for complex problem solving, instead of how do I take away all the annoying hard problems?"
John CutlerThe Alignment Trap
November 29, 2023
"Simplicity is not always the answer to complexity, but understanding often is."
Abby CovertStuck? Diagrams Help
October 27, 2022
"You can see our organization through the homepage of our site — we each owned a rectangle."
Mark InterranteCollaboration Flows in Product Development
June 9, 2017
"The future will be struggle; we need to face that forward, not deny it."
Devon PowersImagining Better Futures
March 9, 2022
"You should not be struggling with best practices, recruitment, or documentation when conducting your own research as a designer."
Prayag NarulaHow to Empower Your Designers to Do Good Research – And Why You Want To
June 10, 2022
"Don’t overcomplicate workflows; the simplest thing that could possibly work is often best."
Peter Van DijckHands on AI #3: Claude Code for UX people
October 22, 2025
Latest Books All books
Dig deeper with the Rosenbot
When is it best to use interviews versus surveys during product and UX research?
How does including metadata like methodology, market, and date improve the quality of research repository search results?
How do enterprises balance qualitative and quantitative tools while integrating AI into UX research workflows?