The Hidden Skill That Separates Good Researchers from Great Ones

By Hakan Karaaytu, AU Assistant Professor & UX Researcher

Anyone can collect data. Sitting with a participant, asking questions, filling notebooks — that part is learnable quickly. What is far harder to learn, and far less often taught, is what comes next. The moment when the interviews end, the recordings stop, and you are left alone with a pile of observations that do not yet mean anything.

That moment — and what you do with it — is where research either becomes valuable or stays merely descriptive. The skill that determines the difference is synthesis.

The Freeze Every Researcher Recognizes

Early in my journalism career, I covered a story about education funding policy. I did everything right. I interviewed administrators, teachers, and parents. I attended school board meetings. I filled a notebook with quotes, statistics, and policy details. Then I sat down to write — and froze.

I had collected everything. I had synthesized nothing.

Every UX researcher knows some version of this moment. The last session ends. The notes are immaculate. The recordings are timestamped. And yet no clear story has emerged. In a panic, some teams respond by collecting more data, assuming clarity will eventually surface on its own.

It will not. Data does not speak for itself. It needs someone to look at all the fragments and say: here is what this means, here is what matters, here is what we should do. That is synthesis — and it is the most important thing a researcher does.

Instagram: UXHakanKaraaytu

A Five-Step Process for Turning Noise into Direction

Synthesis is not mysterious, but it is methodical. Here is the process I use in my own research and teach to my students:

Step 1: Externalize the data. Synthesis requires visibility. Move your notes out of documents and onto a surface where you can see everything simultaneously — a physical wall, a Miro board, index cards. Relationships between observations only become visible when you stop scrolling and start seeing the whole field at once.

Step 2: Cluster by meaning, not by topic. You are not building a taxonomy. You are looking for patterns in underlying behavior, emotion, and need. Three participants might use completely different language — "rushed," "not enough time to think," "worried about deciding too quickly" — while describing the same thing: anxiety about time pressure. Different words, one cluster.

Step 3: Name the patterns. Give each cluster a short, specific phrase that captures the essence of what is happening. Not a generic label like "navigation issues," but an interpretive statement like "Users need permission to go slow." These names become the shared vocabulary your team uses to discuss what you found.

Step 4: Derive insights. Move from observation to interpretation. For each pattern, ask: what does this reveal about the user? What is the deeper truth? In a volunteer research engagement I conducted with Expedia, dozens of quotes mapped to one unavoidable pattern: users were not primarily frustrated by price. They were anxious about time — time zones, layover lengths, arrival windows. The insight was not "users mentioned timing." It was: users experience timing anxiety during travel booking because temporal information is fragmented and difficult to mentally calculate. That is not a summary. It is an interpretation — and it is what design can act on.

Step 5: Translate into recommendations. Every insight earns a corresponding action. Not "improve navigation," but "add a persistent breadcrumb in the checkout flow so users can return to previous steps without losing progress." Specificity is not pedantry. It is the thing that makes research usable.

Instagram: UXHakanKaraaytu

The Difference Between Reporting and Insight

Poor synthesis reports what users said. Good synthesis explains why they said it and what it means for design. The contrast is worth making explicit:

Reporting: "Several users clicked the wrong button. One user said they didn't know where to go next."

Insight: "Users struggled with navigation because button labels used internal terminology rather than task-based language, creating a mismatch with their mental models. Relabeling buttons to reflect user goals rather than system architecture would reduce disorientation at key decision points."

The second version does more work. It connects observation to cause to recommendation. That is the full arc of synthesis — and shortcutting any part of it weakens the whole.

The Mindset Behind the Method

The process matters, but so does the disposition that makes the process productive. Three qualities are non-negotiable:

• Patience. You cannot rush synthesis. The patterns that matter most are often not the most obvious ones. They surface slowly, under sustained attention.

• Humility. Researchers do not own the data. We interpret it on behalf of users whose stories we are responsible for representing faithfully. That means checking our assumptions, staying open to being surprised, and distinguishing between what we expected to find and what is actually there.

• Narrative thinking. The best research deliverables are structured like stories: here is what we wanted to understand, here is what we found, here is what it means. Synthesis without narrative is just a list of findings. Synthesis with narrative is a case for change.

Find the Tension

Here is the practical prompt I return to at the end of every study: What tension keeps repeating in my notes?

Not what users said most often. What tension — what conflict between desire and experience, what gap between expectation and reality, what unmet need that users have learned to work around.

Tension is where insight lives. When users are caught between wanting to move quickly and needing to feel confident, that friction is not a complaint to log. It is an opportunity to explore. Find it. Name it. Address it.

That is synthesis. And it is what transforms listening into design.

Hakan Karaaytu is an Assistant Professor at Alfred University 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.