Short Take #4: 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
-
•
Engineers and product teams often use highly specific taxonomies and standards like NIST, ISO, and HL7, which UX professionals must learn to speak fluently to collaborate effectively.
-
•
UX design can be integrated into engineering requirements by embedding user-focused elements directly into technical standards.
-
•
Resistance to UX in product teams often stems from fears that UX slows down rapid product growth and misunderstands technical constraints.
-
•
Doing UX design early and iteratively aligns well with lean product development and reduces costly errors later in the process.
-
•
UX research methods can fit into short product cycles without adding bureaucratic delays.
-
•
Building trust between UX and product teams involves shifting conversations from technical engineering details to the value and usability that UX brings.
-
•
In resource-constrained startups, leveraging structured communication tools like debrief trackers enables collaboration without requiring UX presence in every user session.
-
•
A debrief tracker with sections for individual context, key learnings, design concept performance, and takeaways aids quick knowledge sharing.
-
•
Having explicit conversations about team structure, meeting roles, and artifact usage is essential for sustainable UX-product partnerships.
-
•
Trust developed through transparent communication allows UX to lean on product managers and engineers effectively and vice versa.
Notable Quotes
"One thing I learned from working with product people is how to speak their language like all disciplines."
"Product designers I have worked with have experience deeply grounded in standards like NIST, ISO, IEEE, and HL7 for healthcare."
"Some bias against human-centered UX comes from concern that ordinary folks don't understand technical software requirements."
"Doing design right early, just like failing early, helps to prevent time-consuming mistakes."
"UX people do have research methods that fit into shorter product development cycles."
"From an engineer's perspective, we don't have to talk about the engineering but talk about the value, including usability, and that is what builds trust."
"By understanding your environment and having those conversations with your product manager, you can create a relationship that is sustainable and efficient."
"Our debrief tracker helped the UX designer quickly absorb information and became a helpful reference and index."
"It's not just about the artifacts but the conversations had to come to that system or structure."
"Trust was so key to the product-UX relationship and it was further built by putting structure in place."
Or choose a question:
More Videos
"Tags are a balance; project tags are wild and flexible, global tags must be controlled to avoid chaos."
Taylor Jennings Joe Nelson Alex KnollRepository Retrospective: Learnings from Introducing a Central Place for UX Research
March 9, 2022
"How we orient ourselves to the future impacts how we experience the present."
Nicole AleongFuture Orientations to Everyday Life: Futures Anthropology as a Methodology
March 26, 2024
"Disruptive innovation doesn’t happen overnight; you have to practice, fail, learn, and have patience."
Jeff GothelfInnovation Studios: the Engines of Enterprise Experimentation
May 14, 2015
"Nothing about us without us is the mantra we embrace when doing inclusive design operations."
Saara Kamppari-MillerDesignOps for Inclusive Design and Accessibility
May 26, 2022
"You can’t make your team happy, no one can ever make anyone else happy ever, ever."
Tess DixonC'mon Get Happy
September 29, 2021
"Our skills matrix became the center of gravity for our practice—it started writing job descriptions and guiding recruitment."
Liam ThurstonWhy Your Design Team Is Quitting, And How To Fix It
June 10, 2022
"Leadership doesn’t only mean managing; it can be mentoring, product leadership, or technical influence."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"One researcher per team for at least three days a week was considered an outrageous luxury at GDS in 2013."
Leisa ReicheltOpening Keynote: Operating in Context
November 7, 2018
"A product designer said I can now see glaring inconsistencies before I got my head around design system patterns."
Rachael Greene Alison DavisBuilding a Design Ops Practice that Really Works (Most of the Time)
October 2, 2025
Latest Books All books
Dig deeper with the Rosenbot
Why is human storytelling stewardship still essential despite advances in AI and research democratization?
How does Rally’s research infrastructure facilitate participant management and integration with enterprise data systems?
What are practical strategies to build influence for research insights across multiple dispersed teams?