Listening Is a Research Method: What Journalism and Ethnography Taught Me About UX

By Hakan Karaaytu, AU Assistant Professor & UX Researcher

Most of us enter user research convinced that the work lives in the questions we ask. We obsess over interview guides, agonize over phrasing, and rehearse our probes. What we spend far less time on — and what ultimately determines the quality of our insight — is what happens after we ask. How we listen. What we're actually listening for. And whether we've created enough space for answers we did not anticipate.

Listening, in research, is not passive. It is a discipline. And across three distinct professional traditions — journalism, ethnography, and UX — I have encountered three meaningfully different ways of doing it. Each one has sharpened how I practice and teach research today.

Journalistic Listening: Hearing What Is Being Avoided

Journalists listen under pressure. With a deadline approaching and a subject who may be evasive, guarded, or simply unaware of what makes their story important, you develop a particular acuity. You learn to track not just what someone says, but what they are careful not to say. You learn to hear the moment when the official narrative and the tone of voice stop matching.

In a seminar I teach on research methods, a student once interviewed a city official about a local zoning decision — a topic that had yielded only scripted, polished answers. Then the student asked: "What surprised you most about the community response?"

The official paused. And then gave five unguarded minutes of reflection on the tension between policy logic and the lived realities of the people it was supposed to serve.

One well-placed question cracked open the performance. That is what journalistic listening trains you to find: the question that makes someone stop presenting and start being honest.

Its limitation, though, is worth naming. Journalism listens for what is newsworthy — for the revealing quote, the conflict, the headline. It optimizes for impact, not for depth. That orientation serves a particular purpose. But understanding people in their full complexity requires a different kind of patience.

Instagram: UXHakanKaraaytu

Ethnographic Listening: Tracing Patterns, Not Headlines

Ethnography asks you to slow down radically. You are not after the quotable moment. You are tracing a pattern — observing how behavior actually unfolds in context, rather than how people describe it when asked directly.

In training students to conduct field observation, I once had them sit in the campus library with no interview guide, no agenda — just notebooks. The instruction was simply to watch. At first, they found it uncomfortable. "Nothing is happening," they would say.

I would tell them: Keep watching. Sit quietly until the silence speaks.

What eventually emerged was rich: the territorial logic of how students claimed space with objects. The unspoken hierarchy within study groups. The way individuals managed solitude and sociality simultaneously in a shared environment. None of it would have surfaced in a direct interview, because people do not narrate their own habitual behavior. They simply live it.

Ethnographic listening also demands ethical discipline — staying genuinely open to what participants find meaningful rather than confirming what you already suspected matters. In fieldwork studying teachers in under-resourced schools, I arrived expecting to hear about material scarcity. What teachers returned to again and again was psychological time — the persistent, guilt-laden feeling of being perpetually behind, of choosing which students to prioritize when full presence was impossible for everyone.

That was not in my protocol. It surfaced because I was listening for their frame, not mine.

UX Listening: Empathetic, Diagnostic, and Curious

UX research brings these two traditions together in a task-oriented context. We are not writing cultural theory or chasing a story. We are trying to understand how people pursue goals, where those efforts encounter friction, and what that friction reveals about design assumptions we did not know we were making.

During a volunteer research engagement with Expedia, one of my students was facilitating a usability session on a hotel booking flow. A user kept hesitating at the filter interface. The student asked: "Walk me through what's confusing here."

The user's response stopped the session cold: "I'm not confused. I'm just nervous I'm going to filter out something good."

This was not a comprehension problem. It was anxiety about loss — about delegating a consequential decision to a tool that might quietly exclude the best option. The redesign that followed did not make the filters clearer. It added a small, persistent note showing how many results had been excluded, with an option to view them. A minor intervention. A significant restoration of user confidence.

We arrived at that insight only because the facilitator resisted projecting a hypothesis onto the hesitation. She asked an open question and created space for something unexpected to emerge.

I teach this as curious neutrality — the discipline of being genuinely interested in what a participant is experiencing while remaining unattached to any particular explanation for it. Journalistic curiosity gives you the courage to ask the hard question. Ethnographic depth gives you the patience to sit with an ambiguous answer. Together, they produce something UX research urgently needs: the capacity to be surprised.

What Makes a Question Worth Asking

Across all three traditions, good research questions share a structure worth making explicit. They are:

• Open enough to reveal the unexpected. "What goes through your mind when you see this?" invites reflection. "Is this confusing?" closes it down.

• Precise enough to stay on track. Openness is not vagueness. "Tell me about the last time you tried to book a hotel and something went wrong" is specific, bounded, and generative.

• Human enough to make honesty feel safe. "Walk me through your thinking" invites. "Why did you do that?" judges. The difference in tone produces entirely different data.

Underlying all of this is one principle that applies regardless of method or context: a good question is not one that gets an answer. It is one that gets a story.

Stories carry context, emotion, and the layered detail that abstracted data cannot. When a participant tells you about a frustrating experience, they are giving you the sequence of events, the expectation that was violated, the workaround they invented, and the feeling that accompanied all of it. That is not just insight. That is the raw material of better design.

The Practical Takeaway

If you are conducting user research — whether you are seasoned or just beginning — consider auditing not your questions, but your listening posture. Are you truly open to being wrong about what the problem is? Are you creating enough silence for something unexpected to surface? Are your questions inviting stories, or just confirming what you already believe?

The most powerful research I have witnessed and conducted has rarely come from a brilliant question. It has come from a researcher who, after asking, went completely quiet — and let the participant fill the space.

That is where the real data lives.

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