Summary
Research is for everyone. User research is about connecting with customers, and learning from them to make better decisions for them, and for your business. Everyone in an organization can and should benefit from that. But that doesn't mean everyone is a researcher. In this session we'll cover: How to identify the right stakeholders for your research How to get different kinds of collaborators involved in your research How to make sure your research is being used and making an impact
Key Insights
-
•
Starting research projects by clearly defining the decisions and impact you want drives more actionable insights.
-
•
Involving stakeholders from across functions (product, engineering, marketing, sales, customer success) early ensures ongoing engagement and buy-in.
-
•
Collaboration brings multiple perspectives, reducing bias and strengthening the quality and nuance of research findings.
-
•
Using agreements to set clear roles and expectations for stakeholder involvement builds trust and prevents burnout.
-
•
Sharing incremental, even unpolished, research updates fosters transparency and appreciation among stakeholders.
-
•
Delegating parts of research analysis, like transcript review or note cleaning, helps manage workload and includes more team members.
-
•
Structuring research presentations as stories (with scene setting, conflict, climax, and resolution) captures attention and motivates action.
-
•
Research storytelling applies both to qualitative and quantitative data by framing evidence within the context of decisions.
-
•
Regularly revisiting stakeholder involvement agreements prevents overwhelm and maintains enthusiasm for ongoing research participation.
-
•
Even organizations relying mainly on surveys can surface stories by reframing survey questions with clear decisions and adding qualitative follow-ups.
Notable Quotes
"Many people have struggled to get engagement and adoption of their research insights; it's one of the most common problems we hear."
"Research is most effective when it's a collaborative activity and a team sport, not a solo endeavor."
"When you involve other people into your work, you get unique perspectives that include bias, but the variety strengthens the research."
"Begin every research project with the end in mind: what decision will this research unblock and who needs to make it?"
"Inviting stakeholders early through brainstorms and feedback loops helps build excitement and surface assumptions."
"Sharing small, incremental updates—even unpolished ones—helps reflect on learnings and provides visibility behind the scenes."
"Setting agreements that outline responsibilities and expectations for observers or note takers creates trust in the research process."
"A typical story has a beginning, middle, and end; use that same narrative structure to present research insights."
"Stakeholders appreciate seeing the craft behind the work, which sharing incremental updates can highlight."
"Storytelling isn't just for qualitative insights; framing quantitative data within decision contexts is equally powerful."
Or choose a question:
More Videos
"There’s never enough attention you can give to change management in scaling design impact — don’t do it alone."
Standardizing Product Merits for Leaders, Designers, and Everyone
June 15, 2018
"If I don’t have a map, I can’t see patterns or apply context-specific gameplay."
Simon WardleyMaps and Topographical Intelligence (Videoconference)
January 31, 2019
"Cisgender binary options in onboarding flows exclude non-binary and gender-expansive identities."
Sandra CamachoCreating More Bias-Proof Designs
January 22, 2025
"I held Jeff accountable by expecting criticism to come with rationale and intentional improvement."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"ChatGPT didn’t have the full context of what was most important to stakeholders, so I had to edit its output before sharing."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"How do you create a sense of craft in an environment fraught with ambiguity, complexity, and anxiety?"
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"Service blueprints would have helped business units understand backend impacts and responsibilities."
Davis Neable Guy SegalHow to Drive a Design Project When you Don’t Have a Design Team
June 10, 2021
"If you come with a big idea, they’ll try to dial you back to the smallest iota you can test first."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"Design Ops people want to standardize processes and reuse organizational knowledge for clarity and confidence."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
