The Case for Keeping (or Bringing Back) Your UX Researchers
UX Researchers + Product Managers = BFFS4L
Product managers are CEOs of their products
A product manager is, in every way that matters, the CEO of their product. Their job is to understand the market, weigh the tradeoffs, and make product decisions that serve users and the company at the same time. That scope never shrinks — there are always more inputs than there is time, and the cost of a wrong call can be in the millions.
A UX researcher is the partner who lightens that load on the user side of the equation. They're trained in the half where many product decisions can go wrong: who the users actually are, what they're trying to do, what's getting in their way. THese people are not to be confused with that table of people you are demeaning the product to–the ones who make the buying decisions. These folks, especially in enterprise–are often two different sets of people. A PM working alongside a strong researcher isn't outsourcing that work — they're freed to focus on the bigger strategic calls, because they trust that the user side is being handled with rigor and that the evidence they need will be there when the decision lands on their desk.
Now to the specifics of what a UX Resarcher can deliver…
They can run low-cost usability studies so fast you might not even lose a day
The most common reason teams skip usability testing is "we don't have time" by which they mean “it will delay release.” A skilled UX researcher knows why that argument is almost always wrong. And in the most awkward pinch hitting moment, they can even to the testing after it’s in production, but I don’t recommend waiting that long. That said, I’ve seen it more often than not in the last 5 years.
A researcher can stand up a five-participant, unmoderated usability test in hours, not weeks. By the time engineering is in their next standup, results could be coming back. The cost is small, the impact on development velocity is close to zero, and the confidence you go into release with is far higher.
Just as important: a researcher knows when not to test, when a fast remote run is enough, and how to design tasks that don't telegraph the right answer. The output is something the team can act on, not a study that confirmed what everyone already believed.
They make Voice of Customer interviews worth the effort
Most teams either don't conduct Voice of Customer interviews at all, or conduct them and find the recordings never quite turn into anything actionable. Both are fixable, and a researcher is the fastest way to fix them.
A researcher can build a VoC program from zero — choosing the cadence, designing the interview guide, training the team on neutral questioning — or take a backlog of existing interviews and extract the patterns that should change what you build next. They know how to ask the one question that surfaces the workaround a customer didn't think to mention, which is where most unmet needs actually live.
They turn data mountains into a story PMs can act on
Product teams rarely lack data. They often have mountains of it, spread across dashboard, buried in Confluence and Jira, UserTesting (if they’re lucky), SalesForce, etc. Somewhere in those numbers is the story of where users get stuck and where opportunity is hiding — but raw analytics doesn't tell that story by itself.
A UX researcher can stand in front of mountains of analytical data and surface the why behind the numbers–and in absence of the why, the questions that will get them there. They pair the quantitative signal with qualitative evidence, segment by who actually does the behavior in question, and turn it into the kind of narrative a PM can take straight into a roadmap conversation: here are our three biggest user pain points, here is the evidence sized against our base, and here are the opportunities they point to.
That translation work is what can take a PM from a dashboard to a decision. And in many, many cases, companies already have mountains of data. They don’t need to repeat studies they already ran and forgot about. They just need to mine the data they have.
They map user journeys that read at a glance
Process diagrams are everywhere in product organizations. User journey maps that PMs actually use are rare–often only seen in the Fortune 100 tier where there is beaucoup bucks for UX Researchers, and they can prove the ROI.
A well-built journey map shows, at a single glance, where users are frustrated and where the product is winning. It collapses dozens of interviews and analytics snapshots into one picture, with the highest-pain moments flagged and the highest-opportunity ones marked for investment. A PM walks into a stakeholder meeting with that map and aligns the room in five minutes. The difference is research.
What all of this adds up to
These pieces — fast usability studies, rich Voice of Customer signal, narrative pulled from analytics, journey maps that read at a glance — are not four separate deliverables. They're four pieces of the same body of evidence.
Combined, they give a PM everything they need to walk into an executive conversation and make a real case for investment. Not "I think we should." But: "Here are our users' biggest pain points, sized by analytics, validated by interviews, mapped across the journey, and tested against early concepts. Here is where we should invest, and here is what we expect to see when we do."
That is the conversation that earns budget. And it is hard to have without a researcher on the team.
The not-very-hidden cost of cutting (it shows up later)
Cutting research feels like trimming the discretionary side of the team. In practice, it transfers a load of structural decision-making — what should we build, for whom, against what evidence? — onto product managers who are already running at capacity. PMs make the same calls regardless; they simply make them with less evidence and more guesswork.
The cost is rarely visible inside the same fiscal year. It shows up in the next one, in the form of decisions that turned out to be wrong, products that didn't land, and competitors who got there first because their teams were operating on better evidence.
What to do, in any market
If you have UX researchers on your team — keep them close. Pair them with PMs early in initiatives, not at the end when sessions need running. Give them visibility into the executive conversations they are producing evidence for. They will compound the value of every other role around them.
If you've let researchers go and the gap is starting to show — start bringing the capability back. Even one experienced researcher, partnered well with two or three PMs, can transform how a product team makes decisions.
A product manager runs their product like a CEO. A UX researcher makes sure the most important variable — the user — is never a guess.
In a market where AI is reshaping every part of how products get built, that partnership is your winning combination.
For practical, method-by-method detail on the work referenced here — quick usability runs, building a Voice of Customer program, journey mapping, and pulling narrative from analytics — see our User Research Playbook (coming soon).