How do you manage the situation when people question the value of usability research?

Question

Anonymous · Accepted Answer

My first move isn't to defend research — it's to figure out where the skepticism
is actually coming from, because the response is different depending on the
cause. Sometimes it's a bad past experience, where a previous study felt slow or
vague and didn't actually change anything. Sometimes it's velocity pressure —
research feels like a blocker when a team is trying to ship fast. And sometimes
it's overconfidence in existing data — a team feels like their analytics already
tell them what's working, which conflates knowing what happened with
understanding why it happened.

Once I know which of those it is, I try to speak in terms the stakeholder
already cares about rather than defending research as inherently valuable. That
usually means cost — a usability issue caught in a few days of research is cheap
to fix, but the same issue found after launch means engineering rework, support
tickets, and possibly churn. If I have a past example where a study caught
something before it became expensive, I'll use it, tied to a metric they already
track.

I also try to make the ask small rather than arguing philosophy. Instead of
debating whether research is valuable in the abstract, I'll offer something
low-risk and fast — five rapid sessions before a decision gets finalized, for
example — and frame it as low-cost either way: if it doesn't change anything,
they've lost half a day, and if it does, they've avoided a much bigger cost
downstream. That lets the result make the case instead of me having to.

Part of this is also about visibility. A lot of research value gets lost because
findings live in a long deck nobody actually reads. So I try to make findings
legible — a one-page synthesis, a short highlight reel, something a skeptical
stakeholder can absorb in two minutes and refer back to later. That visibility
is what actually builds trust over time, more than any one study does.

And I think the credibility move here is not over-claiming. I'm upfront that not
every decision needs research — a low-risk, easily reversible choice, or
something already well-established, doesn't need a study. Recognizing when
research isn't necessary is part of being a good partner, not a research
maximalist, and it's honestly what earns the trust to be taken seriously the
next time research really is needed."

Anonymous · Answer

I first try to understand where the scepticism may be coming from and try to
address it from there. Most times, it is because there is a lack of awareness of
the benefits and outcomes of usability research. In those cases, I do present
previous cases and show how the data that we collected helped us to mitigate
risks and help develop the pipeline for new features

Anonymous · Answer

I have never had this problem. If there is one thing that stakeholders at all of
the companies I have worked with have embraced, it has been usability. The
problem I have faced most has been skepticism about interviewing a handful of
people and taking the responses seriously.

To address this, I invite stakeholders to interviews so that they can have a
deeper sense of how the interviews actually work. I also share quantitative
metrics that more often than not coincide with what we hear 5 or 6 or 7 people
say.

How do you manage the situation when people question the value of usability research?

Practice this question with AI

Go Premium

Community Answers

Unlock Full Access

Unlock Full Access

Unlock Full Access

Practice More Questions