Summary
More and more researchers with no business or product backgrounds are in product research. In the day-to-day industry practice, we are called to march towards the same goal despite our different ways of knowing, talking, and past experiences. Failing to do so could lead to missing opportunities for innovation, reinventing the wheels, and building products that may pose risks to society. When ‘thought worlds’ collide, what can we do to better understand and support each other? This talk answers the question by taking a closer look at the differences and similarities between research and practice, and offering lessons learned about communication and collaboration within diverse product teams made up of a mix of academic and professional disciplines.
Key Insights
-
•
The research practice gap reflects mismatched expectations and communication styles between academia and industry that hinder impact.
-
•
Academic research values truth and self-criticism, whereas industry research prioritizes speed, actionability, and user value.
-
•
Different research 'thought worlds' (psychology, design, HCI) define research differently, complicating collaboration.
-
•
Research outputs in academia and industry share structural similarities, such as problem framing, methods, insights, and implications.
-
•
Trust and attention barriers often prevent research findings from influencing practitioners effectively.
-
•
Translating dense academic findings into concise, jargon-free, visual, and actionable formats greatly improves usability.
-
•
Timing research delivery to match designers’ work phases increases likelihood of uptake.
-
•
Teams with diverse backgrounds must accept conflict as normal and navigate it towards constructive debate.
-
•
Successful collaboration requires people-first empathy and self-awareness about how disagreements are communicated.
-
•
Empathy, patience, and seeing others fully beyond labels or roles are fundamental for bridging gaps across identities and disciplines.
Notable Quotes
"All my work, especially coming from CEOs, I felt deeply defeated by that comment."
"The research practice gap is frustrating, and I try to bridge it when it makes sense to."
"Design is fast, accessible, actionable, intuitive; science is slow, dense, behind paywalls, and self-critical."
"Practitioners, researchers, and hybrids don’t really hang out on Twitter; few translators exist between these worlds."
"Science is not pure and naive; advancing research is a matter of chance, strategy, and marketing too."
"To better collaborate is to tackle barriers around user researcher and the people we’re trying to inspire, often trust and attention."
"If you just want to prove someone wrong then you’re actually not seeing that person in front of you."
"Teams with different thought worlds should start by sharing what their roles are, goals, and passions in and outside work."
"Conflict is the norm in interdisciplinary teams and should be steered into debate rather than personal undermining."
"As you touch a human soul, be just another human soul."
Or choose a question:
More Videos
"A 101 conversation over coffee yields better insights than written reviews in 360 assessments."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"Many product managers got their roles because they know the business or subject matter, but they don’t know how to manage product development."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"Governance frameworks can facilitate whatever an organization wants to do, fast or slow, loose or tight."
Lisa WelchmanCleaning Up Our Mess: Digital Governance for Designers
June 14, 2018
"Transportation must evolve to be more sustainable and accessible for all."
Vincent BrathwaiteOpener: Past, Present, and Future—Closing the Racial Divide in Design Teams
October 22, 2020
"The squad model flopped for us after six months but created culture triads that stuck around."
Brenna FallonLearning Over Outcomes
October 24, 2019
"Never be afraid to get into good trouble; start by asking why."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"Research should be done the same way products are built, with stakeholders as your users."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"Knowledge needs to be thought of as a reusable circular process, not a linear one ending at project completion."
Designing Systems at Scale
November 7, 2018
"A lot of developers are way too confident they write perfect code; testing bug fixes often reveals hidden issues."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024