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
"A backlog helps pace and define the design ops practice, managing what’s in scope and what’s aspirational."
Michelle ChinThe DesignOps Starter Kit
September 29, 2021
"We are still designers, we’re systems designers, we’re organizational designers, even if we’re not making things."
Louis Rosenfeld Jose Coronado Rachel Posman Guneet Singh Crystal YanThe Bigger Picture: A Panel Discussion
October 23, 2019
"Stay interviews ask why people choose to stay, which provides more actionable retention data than exit interviews."
Kristin Skinner Kamdyn MooreGroup Activity: A Deep Dive Into Value and Outcomes
October 23, 2019
"The prompt becomes part design spec, part requirement doc, and part programming language."
Josh Clark Veronika KindredSentient Scenes and Radically Adaptive Experiences
June 11, 2025
"Our subway lines are tool functions, and stations are where single-function tools live."
JP Allen Holly HoldenNavigating the UX Tools Landscape
October 1, 2021
"Building for humans is a huge challenge because humans are multi-layered, weird, and wonderful irrational creatures."
Dr. Jamika D. Burge Robert Fabricant Peter Merholz Noam Segal Teresa TorresA Genuine Conversation about the Future of UX Research
March 20, 2024
"I don’t want to be a troublemaker, I just want to poke holes so we can make positive outcomes for the people we serve."
Dan WillisEnterprise Storytelling Sessions
June 8, 2016
"Science cultures like CERN have a huge headwind against adopting design measurement tools because of skepticism."
Panel Discussion: Communicating the Value of DesignOps
November 7, 2018
"With great power comes great responsibility — that's our foundational context in exploring AI and ML."
Husani OakleyTheme Three Intro
June 6, 2023
Latest Books All books
Dig deeper with the Rosenbot
How should C-suite executives approach AI introduction differently from traditional software rollouts?
How do newsrooms identify and measure meaningful signals that show they are meeting audience information needs?
How can competitive analysis through the customer’s lens reveal unique value propositions?