Stakeholders as users: Why research fails without internal alignment

Stakeholders are the first users of research, and when we design for them, everything changes.

Photo by Adrien Olichon from Pexels

I’ve seen research clearly identify the right problems and still fail to change decisions. We knew what was wrong. We documented it. We shared the insights.

And still, the decisions didn’t move.

Unfortunately, good research alone doesn’t always change decisions. For many UX researchers, that is one of the most frustrating parts of the job. We’ll produce valuable insights, but if they’re not applied, the problems remain. Insight alone does not guarantee impact.

We are UX researchers. We investigate problems, uncover needs, and clarify experiences. When users struggle, we conduct research to understand what is going on. We share the insights, hoping they lead to better solutions and a better user experience.

But what about our stakeholders? Are we giving them the user experience they need from our research?

Stakeholders Are Users, Just Not Our End Users

We understand our end users well. They have goals, constraints, incentives, fears, and assumptions. They operate under time pressure, financial constraints, and the need to succeed in their tasks.

But end users are not the only ones who use research. They are not even the first. To influence decisions and truly improve the user experience, we must start with the first users of our research: stakeholders.

These are the people inside the organization who influence, interpret, or act on research — from product and design to leadership and support teams.

Stakeholders operate inside systems: OKRs, deadlines, budget cycles, executive pressure. Their needs are not identical to those of end users. But they are just as real. They have:

• Goals
• KPIs and success metrics
• Deadlines and resource constraints
• Reputational risk and accountability

If we design studies without understanding the people who will interpret, defend, and act on the findings, we design research for ourselves rather than for impact. We misread pressures. We underestimate political constraints. We miss the questions that actually matter. We may not uncover real issues and meaningful insights.

When we don’t treat stakeholders as users, the consequences are predictable:

• Research questions remain vague
• Scope expands without clarity
• Insights arrive too late to influence the roadmap or key decisions
• Findings feel abstract or risky to act on
• Research becomes “nice to have” instead of operational
• Under pressure, teams default to intuition (“remember that one user who said…”)
• Improvements are driven by urgency or internal preference rather than evidence

When research doesn’t influence decisions, end users feel the impact. Their pain points persist. In some cases, the experience may even get worse for them.

If we do not design the research for our stakeholder users, our research is unlikely to have an impact. We lose efficiency. We lose an opportunity. We leave influence to chance. And eventually, we lose users.

Designing for stakeholders means designing for the system in which decisions are made and the stakeholders who use them. If we want to influence those decisions, we need to treat stakeholders as users.

Moving from “Selling” to Good UX

I learned this lesson the hard way.

At one company, I was hired to build the UX research function from scratch. Part of my job was to champion research. I scheduled one-on-one meetings with stakeholders to explain how research could benefit them.

I was trying to sell research. It didn’t work the way I hoped.

I was treating stakeholders as an audience, not as users. Then I shifted. Instead of explaining why they needed research, I started asking questions:

• What keeps you up at night?
• What decisions are you accountable for?
• What would make this research useful?

I treated those conversations as research. I stopped pitching research and started trying to understand the people requesting it and the context in which it was being requested. That was the turning point. That was the moment research began to scale.

The questions changed. The framing changed. The uptake changed.

Those early interviews were not administrative intake. They were discovery. They helped me understand the ecosystem: the incentives, pressures, and definitions of success shaping decisions.

Those conversations were also where credibility began: through dialogue rather than a deck.

Once the stakeholders felt understood, engagement changes. Research was invited in earlier. Insights were shared more broadly. Research moved from “interesting” to “useful.” Eventually, research became a key step in the development cycle rather than an optional checkpoint.

Now, whenever I step into a new role, I start by listening.

I start with research.

Photo by Anna Shvets

Research Scales With Stakeholder Empathy

Over time and across multiple organizations, I’ve seen what happens when stakeholders are treated as users.

• Research begins to influence roadmaps, not just retrospectives.
• Curiosity spreads laterally, not just top-down from leadership.
• Stakeholders reference insights in planning conversations.
• Research shifts from persuasion to expectation.
• Our relationships become more collaborative.

When stakeholders feel understood, they want research to be involved earlier in the process. They see it as a tool for reducing risk, not as a hurdle to clear.

This also benefits us, the researchers. When we understand stakeholder pressures and constraints, it becomes easier to approach those conversations with empathy instead of frustration. Advocacy stops feeling like a contest and starts feeling like collaboration.

We fight for user empathy. Why not stakeholder empathy too?

Treating stakeholders as users makes it easier to fosters stakeholder empathy. This is how research scales behavior, not headcount.

This Isn’t Just My Experience

Over time, I’ve realized this shift isn’t isolated.

Nikki Anderson-Stanier at Dscout advocates intentional one-on-ones to deepen alignment before studies begin. Destiny Delary at *truematter *outlines structured activities designed specifically for stakeholder users.

When experienced practitioners arrive at similar conclusions from different angles, it’s a signal that our discipline is evolving.

We are beginning to recognize that influence is not an outcome of research. It is something we design for.

Photo by Kampus Production

Designing for the Whole Room

If we want research to shape decisions, we have to design for the people making them.

Not just the end user. Not just the product or the data.

The system. The stakeholders. The organization.

Research earns its seat at the table when it is designed with the entire ecosystem in mind.

And sometimes, the most strategic thing a researcher can do isn’t launch a study.

It’s listen first.

Jennifer L. Bowie, Ph.D.