Research Doesn't Live in a Report.. It Lives in the Room..
By Hakan Karaaytu, AU Assistant Professor & UX Researcher
There is a version of UX research that is methodologically impeccable and organizationally invisible. The study is well-designed. The analysis is rigorous. The report is thorough. And then it sits, unopened, in a shared drive while the design team makes decisions based on intuition and deadline pressure.
This is not a research quality problem. It is a communication problem. And it is far more common than the field likes to admit.
The difference between research that shapes decisions and research that merely documents them has little to do with sample size or methodology. It has everything to do with how researchers show up in the rooms where decisions are made — how they translate evidence into language that designers, engineers, and product leaders can actually use.
Why Good Research Loses Impact
Three failure modes account for most of the gap between insight and influence, and recognizing them is the first step toward closing it.
The first is language. Academic register creates distance. Writing that "participants exhibited cognitive friction during the navigation task" is technically accurate and practically useless. "Users got confused trying to find what they needed" says the same thing in a way that a designer can act on immediately. Precision and clarity are not opposites — but in design conversations, clarity has to come first.
The second is context. Researchers sometimes make recommendations without accounting for the constraints their colleagues are working within. Telling a team to rebuild their entire navigation architecture is not useful advice when they have two weeks and a reduced budget. This does not mean researchers should only recommend easy things. It means we need to understand the environment our recommendations land in, and calibrate accordingly.
The third is timing. Research that arrives after design decisions have already been made faces an uphill battle regardless of its quality. Once a team has built momentum around a direction, changing course feels costly — even when the evidence is compelling. Research has to enter the conversation early, not as a final checkpoint, but as an ongoing collaborator.
The underlying mindset shift is this: bridging the research-design gap requires collaboration, not persuasion. The goal is not to convince designers that you are right and they are wrong. It is to build a shared understanding of what users need — together.
What Collaboration Actually Looks Like
In student prototype projects I supervise, I have seen this play out concretely across two recurring dynamics: co-analysis and co-creation.
Co-analysis means reviewing research findings together, not in separate silos. After each round of usability testing, the research and design teams sit with the same recordings and notes simultaneously. Researchers surface patterns. Designers offer context about decisions that may have contributed to what users experienced. Together, the group builds a shared interpretation. There is no "researcher delivers verdict" dynamic — only collaborative sense-making that leaves everyone aligned on what the data is actually saying.
Co-creation follows naturally from that shared understanding. Once a problem is named and understood by the full team, solutions are roughed out together — quickly, at low fidelity, just enough to test a hypothesis. Designers bring visual thinking and technical knowledge. Researchers bring user context and evidence. The solutions that emerge from that combination are consistently stronger than what either party would have produced alone.
One moment that stays with me: a student researcher I worked with noticed that participants kept hesitating at a form field labeled "Instructor Affiliation." She could have documented the finding in her report and moved on. Instead, she caught the designer immediately after the session and said: "Can we look at this label together? I think people don't understand what 'affiliation' means here." The designer's response was immediate: "What if we just call it 'Department'?" They changed it on the spot. In the next round of testing, the hesitation was gone.
That is research living in real time, in the conversation, solving problems as they emerge. It is also the most efficient version of the research-design relationship — one where findings do not have to travel through layers of documentation before they become action.
The Art of Translation
The practical skill underlying all of this is translation — the ability to move between research language and design language without losing meaning in either direction.
My working rule: if I cannot explain a finding in one sentence, the team cannot apply it in a sprint.
This is not about dumbing things down. It is about removing unnecessary friction between what the researcher knows and what the team can do with that knowledge. Consider the difference:
"Qualitative analysis revealed thematic patterns around temporal anxiety" → "Users kept worrying about how long things would take."
"Participants demonstrated a preference for visual hierarchy" → "Users noticed the big buttons first and ignored the small links."
"Users indicated cognitive overload during the checkout process" → "Users got lost halfway through checkout."
The second versions are concrete. They are human. You can picture them. More importantly, you can design for them. Beyond language, the most effective way to make a finding land is to frame it as a story with a visible impact. Not "users struggled with navigation" — but "one user clicked through five screens looking for her order history. By the time she found it, she was questioning whether to complete the purchase at all." Now you have a person, a sequence of events, and a business consequence. That combination moves people in a way that abstracted data rarely does. The sequencing matters too. Lead with the insight — the clear, actionable statement. If someone wants the methodological detail, it is there. But starting with "across eight of ten participants, particularly first-time users, with a correlation to low system trust scores" buries the finding under its own evidence before anyone has had a chance to understand why it matters.
Influence Without Authority
Researchers rarely have formal authority over design decisions. We do not own the roadmap. We do not control the timeline. We cannot mandate that our recommendations be implemented.
What we can do is become indispensable — the person in the room who consistently makes everyone else's job easier because we have done the hard work of turning messy human behavior into clear direction.
That is a particular kind of influence. It does not come from speaking louder or from being the smartest person in the room. It comes from being the clearest. From showing up with specific examples, human stories, and recommendations that are grounded in evidence and sensitive to constraints. From treating collaboration as a genuine mode of working, not a performance of consultation.
The most persuasive researchers are not the ones with the most comprehensive reports. They are the ones who translate best — who can take the complexity of human behavior and render it in terms that a designer, an engineer, or an executive can immediately connect to their own work.
Research becomes powerful not when it is perfect, but when it is useful. The goal is not a flawless study sitting in a drive somewhere. It is a changed decision, a better product, a user experience that works because someone took the time to make sure the evidence reached the people who needed it.
Hakan Karaaytu is an Assistant Professor and UX researcher working at the intersection of journalism, academic inquiry, and human-centered design. He can be reached at hakanhakan@hakankaraaytu.com
The ideas explored in this post were inspired by The Research Room , a podcast about how research shapes design, education, and everyday life.
Comments