Summary
Setting the right priorities and roadmaps can be challenging. Having a data-driven and evidence-based approach provides a robust way to prioritise value propositions and features that inform the roadmap to align stakeholders. UX research and product discovery methods that work in a complementary way are key. UX leaders can take the project-based, strategic approach to UX research to get key business and product insights. Product discovery lends itself to lean experimentation for refining products and the UX. Both are needed simultaneously for broad and focused research efforts. This session will explain how UX Research and Product Teams can collaborate to identify innovation opportunities and develop products and services customer and users need.
Key Insights
-
•
Only 33% of businesses conduct research throughout the entire product lifecycle to guide decisions, indicating widespread underutilization of research.
-
•
Chloe's move from UX researcher to product manager required unlearning detailed documentation habits and adopting more concise, stakeholder-appropriate communication.
-
•
Involving stakeholders directly in user interviews, with careful preparation, helps change assumptions and align business and product strategies.
-
•
A flexible, high-level product roadmap like the now-next-later framework is effective for managing stakeholder expectations around timelines.
-
•
Democratizing research by upskilling non-research team members expands research capacity and embeds a culture of user-centered thinking.
-
•
Collaborative synthesis methods like affinity mapping allow stakeholders to empathize with users and advocate for their needs.
-
•
In small teams with external developers, clear delineation of roles and frequent communication are vital to managing priorities and responsibilities.
-
•
Continuous discovery accelerates over time, shifting from slow, project-based research to rapid prototyping and iterative feedback.
-
•
Balancing product priorities involves weighing stakeholder expectations, resource constraints, and clear documentation of decisions for transparency.
-
•
Product trios ideally include more than one engineer to represent engineering perspectives adequately, but resource constraints often limit this.
Notable Quotes
"Only 33% of businesses conduct research throughout the whole product lifecycle to inform product and business decisions."
"When I first came into the role, I almost took the consultant approach of writing a big report with recommendations, but that overwhelmed the team."
"Taking stakeholders on the journey by involving them in interviews really changed how they saw the product and business strategy."
"A high-level roadmap with now, next, later helped us show we had a plan but kept flexibility for changing priorities."
"Upskilling customer success managers and others to help with testing meant we could do far more research than I alone could manage."
"We used affinity mapping with stakeholders to get them really into the mindset of the users and advocate for them."
"There was a lot of communication needed around roles, especially since our software developer was external and not always involved in day-to-day decisions."
"As the product journey progressed, research cadence got faster with prototypes and quicker feedback loops."
"For bigger decisions, having documented meetings was critical for transparency and defending choices later on."
"Researchers can overcome reluctance to include others by training them closely and collaborating on synthesis to maintain data quality."
Or choose a question:
More Videos
"Synthetic data is useful because it’s easier to generate more examples of something you already have than to create entirely new data."
Peter Van DijckBuilding impactful AI products for design and product leaders, Part 2: Evals are your moat
July 23, 2025
"Good generative research impacts take years, so we track milestones like citations and executive references."
Chris Geison Cristen Torrey Eric MahlstedtWhat is Research Strategy?: A Panel of Research Leaders Discuss this Emergent Question
March 4, 2021
"Component-driven prototyping means designing with coded UI components your development team already created."
Jack BeharHow to Build Prototypes that Behave like an End-Product
December 6, 2022
"I met with my partners and leaders to really dig into their hopes, fears, and dreams about where they wanted to go."
Abbey Smalley Sylas SouzaScaling UX Past the Size of Your Team
January 8, 2024
"Technology is reigning AI down on us across all industries, threatening our creativity and productivity."
Jon FukudaTheme One Intro
October 2, 2023
"Conversion means change, not just sales or profit."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024
"Design teams don’t want a design ops drill, they need a quarter inch hole that requires a little bit of program management."
John Calhoun Rachel PosmanMeters, Miles, and Madness: New Frameworks to Measure the (Elusive) Value of DesignOps
September 24, 2024
"I would in no way describe what we did as great UX, but constantly beating them over the head with UX solutions, they can’t unsee it."
Jacqui Frey Dan WillisPanel Discussion: Integrating DesignOps
November 7, 2018
"Starting with one line of business and showing success creates a trickle effect for broader organizational adoption."
Amy EvansHow to Create Change
September 25, 2024