What Your Stakeholders Know About Your Users, and What They Don’t

Two colleagues stand at a gray wall covered in colorful sticky notes, one pointing at a note while the other looks on thoughtfully.

Ask a customer service lead what frustrates your users and you’ll get an answer in seconds. Ask a development director why donors drop off and you’ll hear a theory backed by years of conversations. Stakeholders are among the richest sources of user insight an organization has. They hear from users every day, and they understand the business context behind user behavior in ways no outside researcher can.

But stakeholder knowledge has limits. It is filtered through assumptions, internal priorities and the loudest feedback people happen to hear. The most useful stakeholder interviews capture what people have actually observed, then test it against what users actually do. Done that way, stakeholder insight stops being a list of requirements and becomes a strong foundation for design decisions.

What Stakeholders Know, and Where it Gets Filtered

Stakeholders bring context you can’t get anywhere else. Nielsen Norman Group’s Stakeholder Interviews 101 notes that “every project comes with history: the origin of the project, known constraints, solutions tried before.” Stakeholders know which campaigns drive traffic, which complaints come up every week and what the organization needs a page to accomplish.

What they know about users, though, usually reaches them secondhand. Three filters shape it:

  • Who they hear from. A support team hears from people who got stuck. A sales team hears from people close to a decision. Neither group hears from the quiet majority who leave without saying anything.
  • What they’re responsible for. Each department sees the experience through its own goals. That’s why the same page can have several competing “top priorities.”
  • What has never been tested. Long-standing design decisions start to feel like facts. Nobody questions a pop-up or a homepage layout that has been live for years.

None of this makes stakeholders wrong. It makes their knowledge partial, the same way users’ own reports are partial. In his classic article First Rule of Usability? Don’t Listen to Users, Jakob Nielsen warns that self-reported data is “typically 3 steps removed from the truth.” Stakeholders’ reports about users are one step further removed still.

Ask About the Page’s Job, Not User Opinions

The structure of a stakeholder interview decides what kind of insight you get. Broad questions about users invite opinions. Questions about the page’s job keep stakeholders on what they know best, the organization’s goals and audiences, and leave questions about user behavior for testing.

Instead of asking…Try asking…
“What should this page include?”“What is the primary purpose of this page?”
“What do users want to do here?”“What action should users take on this page?”
“Who visits this page?”“Which audience segments matter most for this page?”
“What’s the most important thing on the homepage?”“What does success look like for this experience, and how would you know it’s working?”
Questions about the page’s job keep stakeholders on what they know best and leave user behavior for testing.

Three habits keep the conversation grounded:

  1. Separate the business goal from the user theory. “We need more first-time donors” is a goal you can design toward. “Our visitors don’t scroll far” is a theory to test.
  2. Ask how they know. Follow up on any claim about users with a question about where it came from: a call log, an analytics report, one memorable email. The 18F methods guide recommends asking lots of “why is that” and “how do you do that” questions, and asking directly what assumptions are being made.
  3. Talk to more than one department. Patterns that come up across teams are stronger signals than any single view. The UK Government Digital Service’s user research team makes a similar case for treating internal stakeholders as a research audience in their own right.

Turn What You Hear Into Hypotheses

The output of stakeholder interviews shouldn’t be a requirements list. It should be a set of hypotheses, each tied to the goal it supports and the user behavior that would confirm or challenge it.

The translation is usually simple. Take a statement about users, make it specific enough to be proven false, then pick a method that shows what users actually do:

What a stakeholder saysThe hypothesis to testHow to test it
“New visitors don’t understand what we do.”First-time visitors can’t describe the organization’s purpose after a quick look at the homepageA five-second test, then ask participants what the organization does
“People can’t find our upcoming events.”Visitors looking for events don’t recognize the navigation label that leads to themA first-click test or tree test on the navigation
“The registration form is too long.”Specific fields, not overall length, cause people to hesitate or quitA task-based usability test that watches where people pause, backtrack or drop off
“Our audience mostly visits on mobile.”Key tasks are harder to complete on a phone than on a desktopAnalytics to confirm the device split, then the same usability test on both
Testing confirmed what stakeholders knew and surfaced what no one inside the organization could see.

Some hypotheses will hold up. Others will turn out to be more complicated than anyone expected. Both outcomes are useful, because both replace a debate with evidence.

Treat Stakeholder Insight As Evidence to Test

Watching users is what closes the gap between what an organization believes and what actually happens on its site. Nielsen’s research found that you can only predict about a quarter of how well a design works from how much users say they like it. Behavior tells you the rest: where people hesitate, what they skip and where they give up.

That makes stakeholder interviews most valuable as the start of the research, not a substitute for it. Use them to learn the organization’s goals, constraints and history. Draw out what people have actually observed, and turn it into hypotheses that user testing can confirm or challenge.

This approach respects what stakeholders know and gives them something better than opinions to work from. When recommendations rest on how real users behave, teams spend less time debating and more time deciding.

Want to find out what your stakeholders know about your users, and what they don’t? Learn more about Spruce’s UX Research services.


Spruce DX is the digital experience division of Spruce Technology, helping organizations design and build accessible, human-centered digital products.