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
"The biggest problem was to solve the engagement problem first with the sponsor, then the team, then external stakeholders."
Carl TurnerYou Can Do This: Understand and Solve Organizational Problems to Jumpstart a Dead Project
March 28, 2023
"Consumers are clamoring for payment to be embedded in their devices because payment can be a pain point in digital commerce."
Karen PascoeDeveloping Experience Teams and Talent in the Enterprise
June 8, 2016
"We couldn’t find just one word to describe our third value so we made one up: humbladent—humble and confident together."
Jilanna WilsonDistributed Design Operations Management
October 23, 2019
"Reliable access to veterans and other users is fundamental to running quality, inclusive research across many teams and products."
Shawna Hein Kevin HoffmanCreate a Cohesive Civic Design Practice Across Agency, Vendors, and Contracts
November 17, 2022
"Move fast and break things doesn’t work when you’re designing for cancer patients or disaster victims."
Barb SpantonDoing Work That Matters: A Look Beyond The Idealistic Notion of 'Doing Meaningful Work'
June 10, 2022
"As the delivery driver, I connected the dots, got people briefs, and sometimes said no to lofty leadership requests."
Briana ThomasThe Quiet Force: Uncovering Hidden Leadership in High-Impact Design Teams
September 24, 2024
"Mirroring content by repeating back what people say helps them understand their own ideas better."
Gina MendoliaTherapists, Coaches, and Grandmas: Techniques for Service Design in Complex Systems
December 3, 2024
"Being fluent in multiple data languages and understanding behavioral and attitudinal data will be essential."
Lija Hogan Milan Mijatovic Sam Proulx Louis RosenfeldThree Years Out: Perspectives on the Near-Term Future of User Research
March 15, 2024
"A design ops career ladder can look like a step stool unless you create multiple tracks for growth and specialization."
John Calhoun Rachel PosmanTwo Sides of the DesignOps Coin: Teams Ops and Product Ops
January 8, 2024
