Though I shouldn’t be, I’m always surprised by the ever-expanding role of product managers. It seems every job posting gets longer and longer, and their plates get fuller and fuller. As a UX researcher, this concerns me a great deal. User research is a full-time job. There is no way a product manager can do eight full-time jobs at once, nor can they do it well. So, let me help clarify what product managers should and should not be doing, specifically as it relates to gathering user insights.
CREATE AND MANAGE THE VISION
The PM’s job is to ensure that every aspect of product development—from design to prototypes to testing to final production and marketing—aligns with the best available information to set up the product for success. That means establishing the standards and principles that must be followed, and then ensuring they are.
FIND AND USE SKILLED RESEARCHERS OR PARTNERS
Oddly, I have found that many PMs appreciate and rely heavily upon user research and will take on the responsibility if there isn’t a person available or room in the budget. While noble, there are a few reasons PMs shouldn’t be conducting user research interviews, which are very different from customer relationship interviews.
User research requires specific skills in unbiased interviewing, data collection, storytelling, and, most importantly, managing customer expectations. Far too many promises are made in PM-led user sessions. And because the customer often knows they are talking to the “boss,” they often assume you can make good on other issues, which can lead to inflated expectations and eventual disappointment. When a researcher conducts the interview, it’s understood that it is data, not a promise.
The other pitfall of PM-led research sessions is the inherent need to solve a person’s problem without understanding the root cause of the issue. In many instances, the squeaky wheel causes PMs to make product decisions that may resolve a few issues but add no additional value to the masses. Look at some unused features from your favorite product and trace the origin of that feature request. I’m willing to bet it came directly from a customer via the PM.
The researcher’s only agenda should be to get accurate, objective information. Their findings aim to ensure that the product is the best it can be before it goes to market. That ultimately benefits the PM more than anyone.
CHAMPION AND LOBBY FOR ACTIONABLE INSIGHTS
No one is better positioned to champion user research and ensure its findings are incorporated into product design and development than the PM. Let me repeat… No one is better positioned to champion research than the PM. No one can be more effective in seeing how research guides decisions about product features, branding, and marketing. It is the job of the PM to act in the best interest of the product. As much as I would love to say research drives business, it’s not true. The execution of research drives business, and that comes from leadership—i.e., the PM, executive team, c-suite, etc.
COMMUNICATE, ASSIGN, AND TRACK LEARNINGS FROM RESEARCH
Product managers strengthen the entire team by communicating user research findings and establishing information as benchmarks for finalizing the product. They ensure that the roadmap of the user experience aligns with what the research suggested.
PMs should plan the development process with the expectation that outside research is part of the process—and part of the budget—along with final tweaks in response to what the researcher finds. That way, there will be no undue pressure to cut corners, save money, or save time at the expense of product excellence.
While I personally love seeing them in the trenches alongside user researchers, my hope is that product managers will assume their roles and positions at the helm of the ship. Doing so can help product teams ensure no one gets lost in the weeds and everyone is moving in the right direction.
Adrienne Guillory is Chief Operating Officer at Usability Sciences and leads research operations, marketing, and business development.