The Interview vs. the Artifact: Why Stakeholders Trust a Mockup More Than Research They Didn't Watch¶
A finished-looking mockup lands in a meeting and is immediately, viscerally convincing - it looks real, it looks resolved, and reacting to it feels effortless. A research finding, delivered as a summary slide with a few quotes and a chart, rarely lands with anywhere near the same weight, even on projects where the research is genuinely what should be driving the decision. This isn't because stakeholders don't value research in the abstract. It's because a polished artifact and a secondhand research summary are asking for two completely different kinds of trust, and one of them is much easier to give.
A Mockup Asks for Reaction. A Research Summary Asks for Trust in a Process You Didn't See.¶
Reacting to a mockup requires no leap of faith - it's right there, and a stakeholder's own eyes are doing the evaluating. Reacting to "we talked to eight users and found X" requires trusting an entire chain of decisions that happened out of view: who was recruited, what was actually asked, how the responses were interpreted, whether the finding generalizes. None of that untrustworthiness is really about the research being bad - it's that the stakeholder has no direct access to any of it, and secondhand trust is always a harder ask than direct observation, no matter how rigorous the underlying work actually was.
Watching Research Happen Changes What People Believe Afterward¶
The single most reliable way to close this gap isn't a better slide - it's getting stakeholders to actually watch a research session happen, even just one or two, rather than only receiving the summary afterward. Someone who's watched a real user struggle with a specific flow, in their own words, forms a belief about that finding that a bullet point summarizing the same struggle can't replicate, because they now have direct evidence instead of a claim about evidence. This is a genuinely different psychological category from being told a finding secondhand, and it's worth treating as a distinct, valuable activity rather than an optional nice-to-have when stakeholder schedules are tight.
A Summary Slide Compresses Away the Part That Was Actually Persuasive¶
Research summaries tend to compress a session down to its conclusion - "users found the checkout flow confusing" - which strips out the actual moment that made the finding real: the hesitation, the specific wrong click, the exact words someone used to describe their confusion. That compression is necessary for a readable summary, but it also removes almost everything that made the original observation compelling in the first place. A short clip or a direct quote, even a single one, preserved alongside the summary conclusion, recovers some of what a pure bullet-point summary loses.
Recognize When a Mockup Is Winning an Argument It Shouldn't Be Winning¶
The practical risk here isn't research being ignored outright - it's a well-executed mockup quietly outcompeting a real but less viscerally presented finding, in a room that isn't consciously aware that's what's happening. Naming this dynamic directly in a meeting - "this looks resolved, but it hasn't been tested against real users yet, and the research we did run on the previous version found X" - reintroduces the research into a comparison it would otherwise lose by default, simply because it's less immediately convincing to look at.
FAQ¶
Is it realistic to get busy stakeholders to actually watch research sessions?
Not for every session, but even a single observed session per major project changes how research is received afterward - it's worth treating as a deliberate ask, not an optional invitation people are expected to decline.
How can research findings be made more compelling without misrepresenting the data?
Preserving specific, real moments - direct quotes, short clips, exact language a participant used - alongside the summarized conclusion keeps the finding grounded in something concrete, without needing to exaggerate or oversell what was actually found.
What if stakeholders consistently prioritize a polished mockup over research regardless of how it's presented?
That's worth naming as an explicit pattern rather than re-litigating each time it happens - a direct conversation about how decisions are actually getting made in this specific team or company is a more durable fix than hoping the next presentation format finally works.