One of the challenges of talking about user research methods in technical communication is that we often assume we are all talking about the same thing when we are not.
In some contexts, user research is treated as a carefully scoped, methodologically rigorous activity tied to theory, ethics, and disciplinary expectations. In others, it is framed much more pragmatically, as a way to get useful answers quickly enough to shape design decisions. Both approaches matter. But the gap between them can make it harder for technical communicators, UX professionals, teachers, and students to know what user research is supposed to look like in practice.
That is one reason I am excited to share a recent article I coauthored with Amanda Stockwell and Michael Kerr Griffin, “User Research Across Contexts: Integrating Academic Rigor and Industry Innovation.” You can find it here: https://ieeexplore.ieee.org/document/11526980. The article examines how user research is defined and practiced across academic and industry settings and offers a framework for thinking more clearly about user research methods in technical communication.
At its core, the article argues that user research remains central to UX and technical communication, but there is still little shared understanding of what it entails, how it is conducted, or what purposes it serves. Academic literature tends to emphasize theoretical framing, methodological rigor, and disciplinary variation, while practitioner literature foregrounds pragmatism, speed, and actionable outcomes. That divergence creates real challenges for researchers, educators, and practitioners trying to move between those worlds.
Why This Matters for User Research Methods in Technical Communication
For those of us working in technical communication, this split is not just an abstract issue. It shows up in classrooms, on project teams, in consulting work, and in everyday conversations about what counts as good research.
If you teach user research, you have probably run into the challenge of helping students understand why some methods are expected to be rigorous, documented, and theoretically grounded, while others are valued because they are fast, flexible, and good enough to move a product forward. If you practice user research in industry, you have probably felt the tension between wanting to do careful, thoughtful work and needing to deliver insights quickly enough for a team to act on them.
That is exactly the terrain this article tries to map. Drawing on 75 sources published between 1994 and 2025, including 40 academic sources and 35 practitioner sources, we synthesize how user research is defined, operationalized, and valued across contexts. Rather than assuming that user research has a single stable meaning, we trace the conceptual terrain and identify where academic and practitioner perspectives align and where they diverge.
A Few Things the Article Makes Visible
One of the key takeaways from the article is that academic literature often defines user research inconsistently. It appears alongside terms like usability testing, user involvement, user advocacy, contextual inquiry, and UX research, often without clear boundaries between them. Practitioner literature, by contrast, tends to define user research more directly as a systematic process for understanding users’ behaviors, needs, motivations, and contexts in order to inform design decisions.
That difference matters because it shapes not only how research is discussed but also how it is done.
The article also shows that academic sources are more likely to frame user research as foundational. In that view, research helps define the problem, shape project direction, and advocate for users from the beginning of a design process. Practitioner sources often value that same goal, but they also have to work within timelines, budgets, agile workflows, and organizational constraints. That pressure can push research toward more “scrappy” or lightweight methods, even when teams understand the value of more foundational inquiry.
This is one of the reasons I think user research methods in technical communication need to be discussed more explicitly. Too often, we inherit assumptions about methods without talking about the context that gives those methods meaning.
What the Article Offers
The article is structured as a tutorial, which means it is meant to be useful, not just descriptive. After reviewing the literature, we present four key concepts and seven key lessons for navigating the academic-practitioner divide in user research. Those lessons include things like clarifying what user research is at the start of a project, calibrating rigor to fit the context, using mixed methods with purpose, attending to researcher positionality and user representation, translating research into design through narrative, building feedback loops instead of just reports, and designing research for transfer between academic and industry settings.
I think these lessons are especially relevant for technical communicators because our work so often sits at the intersection of research, design, documentation, teaching, and advocacy.
We are often asked to move between institutional contexts that reward very different things. In one setting, methodological transparency may matter most. In another, what matters is whether findings can be used by a team this week. In one setting, a persona may be understood as an interpretive and ethical artifact. In another, it may simply be a quick way to get stakeholders aligned. Neither context is inherently wrong. But they do create different expectations for what user research methods in technical communication should accomplish.
Why I Think This Article Is Useful
What I like most about this piece is that it does not try to “solve” the tension between academic and practitioner approaches by declaring one of them correct.
Instead, it tries to make that tension visible so we can work with it more intentionally.
That matters because technical communication has a long history of engaging with users, contexts, and real-world communication problems. But as the article suggests, the field still needs more cumulative and transferable ways of talking about user research across settings. If we want stronger connections between scholarship and practice, we need clearer language, clearer expectations, and better ways of translating knowledge across those boundaries.
In that sense, this article is not just about UX research broadly. It is very much about user research methods in technical communication and what it means to practice them well in different environments.
If that sounds useful to you, I hope you will take a look at the article here: https://ieeexplore.ieee.org/document/11526980.
It is meant for people who teach user research, people who practice it, and people who are trying to bridge those worlds. And in my view, that includes a lot of us in technical communication.