The pursuit of optimal user experience is often clouded by misconceptions, leading even seasoned product managers astray. Are you sure you’re building the right thing, or just the thing you think users want?
Key Takeaways
- Data alone is insufficient; product managers need qualitative user research to understand the “why” behind user behavior, not just the “what”.
- User experience design is not solely the responsibility of the design team; product managers must champion UX from the initial product strategy phase.
- A/B testing should focus on validating hypotheses derived from user research, not simply throwing random changes at users to see what sticks.
- Accessibility should be a core requirement, not an afterthought, and should be integrated into every stage of the product development lifecycle.
Myth 1: Data is King – Qualitative Insights are Optional
The misconception here is that quantitative data, such as analytics dashboards and A/B test results, provides all the information needed to create an exceptional user experience. Product managers who fall for this believe they can simply track user behavior and iterate based on the numbers, without needing to actually talk to users.
This is simply wrong. While data provides valuable insights into user behavior – for instance, a Google Analytics dashboard showing a high bounce rate on a specific page – it doesn’t explain why users are bouncing. Are they confused by the content? Is the page loading too slowly? Is the call to action unclear? To answer these questions, you need qualitative data gathered through user interviews, usability testing, and contextual inquiry.
I had a client last year, a fintech startup based near the Flatiron Building in New York, that was experiencing low conversion rates on their onboarding flow. They poured over their analytics, trying different button colors and form layouts. Nothing seemed to work. Finally, they conducted a series of user interviews and discovered that new users were intimidated by the complex financial jargon used throughout the app. By simplifying the language, they saw a 40% increase in conversion within a month. According to a Nielsen Norman Group report on UX research methods Nielsen Norman Group, combining quantitative and qualitative data provides a more complete understanding of user needs and behaviors. Don’t skip the user interviews! For more on this, see our article on tech expert interviews.
Myth 2: UX is the Design Team’s Problem
This is a common and dangerous misconception. Many product managers believe their role is to define the product requirements and then hand them off to the design team to “make it pretty.” The design team is then solely responsible for ensuring a positive user experience.
The truth is that UX is everyone’s responsibility, but especially the product manager’s. Product managers are the voice of the user, and they need to champion UX from the very beginning of the product development process. This includes conducting user research, defining user personas, creating user journey maps, and advocating for user-centered design principles throughout the organization.
Think of it this way: if the product strategy itself is flawed from a UX perspective, no amount of visual polish can fix it. For example, if a product manager decides to prioritize a feature that users don’t actually need or want, based on internal stakeholder requests rather than user research, the design team is stuck trying to make a bad idea palatable. This is where effective testing for efficiency early can help.
Myth 3: A/B Testing is a Substitute for User Research
Many product managers see A/B testing as a quick and easy way to improve user experience. They believe they can simply test different variations of a design and let the data tell them which one is “better.” This approach often involves testing random changes without a clear hypothesis or understanding of the underlying user needs.
A/B testing is a valuable tool, but it should be used to validate hypotheses derived from user research, not to replace it. Without a solid understanding of why users are behaving a certain way, A/B testing can lead to incremental improvements at best, and misleading results at worst.
For instance, let’s say you’re testing two different headlines on a landing page. Version A converts at 5%, and Version B converts at 6%. While Version B appears to be the winner, you don’t know why it performed better. Did it resonate more with the target audience? Was it clearer and more concise? Without qualitative user feedback, you’re just guessing. As documented in “Trustworthy Online Controlled Experiments: A Practical Guide to A/B Testing” Ron Kohavi, Diane Tang, and Ya Xu, A/B tests are most effective when they are designed to test specific hypotheses based on user research.
Myth 4: Accessibility is an Optional “Nice-to-Have”
This is perhaps the most harmful misconception of all. Some product managers view accessibility as an optional feature that can be added later, if time and budget allow. They see it as a compliance issue, rather than an integral part of creating a great user experience for everyone.
Accessibility is not just about compliance with laws like the Americans with Disabilities Act (ADA). It’s about creating products that are usable by people with a wide range of abilities and disabilities, including visual impairments, hearing impairments, motor impairments, and cognitive impairments. According to the CDC, 27% of adults in Georgia have some type of disability CDC. Thinking about tech slowing you down? Consider accessibility improvements.
Accessibility should be a core requirement, not an afterthought. It should be considered at every stage of the product development lifecycle, from initial planning to design, development, and testing. Ignoring accessibility not only excludes a significant portion of the population but also leads to a poorer user experience for everyone.
I was working with a local Atlanta e-commerce business, near the intersection of Peachtree and Lenox, that launched a new website without considering accessibility. They quickly received negative feedback from users with disabilities who were unable to navigate the site or complete purchases. They were forced to spend significant time and money retrofitting the site to meet accessibility standards. Don’t make the same mistake. Prioritize accessibility from the start. The Web Content Accessibility Guidelines (WCAG) W3C provide a comprehensive set of guidelines for making web content more accessible.
Myth 5: “Best Practices” Guarantee a Great UX
This myth suggests that following industry “best practices” will automatically result in a positive user experience. Product managers who subscribe to this believe they can simply copy what other successful companies are doing and expect the same results.
While learning from others is valuable, blindly following “best practices” can be a recipe for disaster. Every product, every user base, and every context is different. What works for one company may not work for another.
Instead of blindly following “best practices,” product managers should focus on understanding their own users and their specific needs. This requires conducting user research, gathering feedback, and iterating based on the data. Don’t just copy what Amazon or Facebook are doing. Understand why they’re doing it, and then adapt their strategies to fit your own unique circumstances. Considering unlocking your app’s hidden potential? Dig deep into user research first.
Here’s what nobody tells you: “best practices” are often just someone’s opinion, dressed up in fancy language. They may be based on limited data or anecdotal evidence. Always question assumptions and validate them with your own research.
The truth is, the only “best practice” that truly matters is putting the user first.
Product managers must cultivate a deep understanding of their users, challenge assumptions, and continuously iterate based on data and feedback. Focusing on user needs, not just mimicking competitors, will lead to a truly exceptional user experience.
What’s the first step a product manager should take to improve UX?
Start by conducting user research. Talk to your users, observe their behavior, and understand their needs and pain points. This will provide a solid foundation for making informed design decisions.
How can product managers advocate for UX within their organization?
Share user research findings, create user personas, and demonstrate the ROI of UX improvements. Make UX a key performance indicator (KPI) and track its impact on business goals.
What are some common mistakes product managers make when it comes to UX?
Relying solely on quantitative data, neglecting accessibility, failing to conduct user research, and treating UX as an afterthought are all common mistakes.
How often should product managers conduct user research?
User research should be an ongoing process, not a one-time event. Conduct regular user interviews, usability tests, and surveys to stay informed about evolving user needs.
What’s the best way to integrate accessibility into the product development process?
Incorporate accessibility considerations into every stage of the process, from initial planning to design, development, and testing. Use accessibility checklists and tools to ensure compliance with WCAG guidelines.
Stop chasing mythical “best practices” and start listening to your users. The future of product management lies in a deep, empathetic understanding of user needs. By prioritizing user research and challenging assumptions, product managers can create truly exceptional user experiences that drive business success. One actionable step you can take today: schedule a user interview.
