Overcoming Challenges When Product Owners Undervalue UX Research
- Philip Burgess

- Aug 15
- 3 min read
Updated: 3 days ago
By Philip Burgess | UX Research Leader
When product owners doubt the value of UX research, teams often face roadblocks that slow progress and reduce product quality. UX research provides critical insights into user needs, behaviors, and pain points. Without it, products risk missing the mark, leading to wasted resources and frustrated users. This post explores common challenges when product owners undervalue UX research and offers practical ways to address them.

Why Some Product Owners Undervalue UX Research
Understanding the root causes helps tailor solutions. Some common reasons include:
Focus on speed and deadlines: Product owners may prioritize quick releases over thorough research, seeing UX research as a time-consuming luxury.
Lack of awareness: They might not fully understand what UX research entails or how it benefits the product.
Budget constraints: Research can seem like an added cost with unclear immediate returns.
Overconfidence in assumptions: Product owners sometimes rely on their own experience or intuition instead of user data.
Recognizing these reasons helps teams approach the issue with empathy and targeted strategies.
Challenges Faced When UX Research Is Undervalued
When product owners do not support UX research, teams often encounter:
Limited user insights: Without research, teams guess user needs, increasing the risk of building features no one wants.
Reduced product quality: Lack of user feedback leads to usability issues and poor user satisfaction.
Lower team morale: UX researchers may feel undervalued, which affects collaboration and creativity.
Inefficient resource use: Time and money spent on features that don’t solve real problems.
These challenges can stall product success and damage the team’s ability to deliver value.
How to Demonstrate the Value of UX Research
Showing clear benefits can shift product owners’ perspectives. Try these approaches:
Share success stories: Present case studies where UX research improved product outcomes, such as increased user engagement or reduced support tickets.
Use quick wins: Conduct small, fast research activities like usability tests or surveys that provide immediate, actionable insights.
Quantify impact: Translate research findings into numbers, such as potential revenue gains or cost savings from avoiding redesigns.
Involve product owners: Invite them to observe user sessions or review findings firsthand to build empathy with users.
For example, a team once ran a 2-day usability test that uncovered a confusing checkout flow. Fixing it increased conversions by 15%, a clear win that convinced the product owner to invest more in research.
Integrating UX Research into Agile Workflows
Many product owners worry UX research slows down agile development. To address this:
Embed research in sprints: Plan research activities early in the sprint cycle to inform design and development.
Use lightweight methods: Employ guerrilla testing or remote surveys that fit tight timelines.
Prioritize research questions: Focus on the most critical user issues to maximize impact.
Communicate clearly: Share concise summaries and visuals that highlight key findings without overwhelming stakeholders.
This approach keeps research aligned with delivery goals and shows it as a tool for faster, smarter decisions.

Building a Culture That Values UX Research
Long-term change requires cultural shifts within the product team and organization:
Educate stakeholders: Run workshops or lunch-and-learns to explain UX research methods and benefits.
Celebrate research wins: Highlight how research led to product improvements in team meetings or newsletters.
Create shared goals: Align UX research objectives with business outcomes to show relevance.
Encourage collaboration: Foster open communication between product owners, designers, and researchers.
When everyone sees UX research as a shared responsibility, it becomes a natural part of the product process.
Practical Tips for UX Researchers Working with Skeptical Product Owners
Speak their language: Frame research findings in terms of business impact, user retention, or cost reduction.
Be concise and visual: Use charts, videos, or prototypes to make insights clear and memorable.
Offer alternatives: Suggest research methods that fit the project’s constraints.
Build trust gradually: Start with small research efforts and expand as confidence grows.
For example, instead of presenting a long report, a researcher might share a 3-minute video of users struggling with a feature, which can be more persuasive.



Comments