Teaching UX Research Through Practice
I teach UX research as a practical discipline, not as a list of methods. The work starts before the framework, with a person trying to understand a page, complete a task, compare options, trust a service, or decide whether to continue. Sometimes the problem is explained clearly; more often, the evidence arrives in fragments: a pause, a repeated question, a skipped section, a hesitation before clicking.
That is the material students need to learn from. My teaching focuses on the movement from messy evidence to responsible action, using a simple sequence: listen, frame, map, and test. It is the same movement I use in professional research across ecommerce journeys, service experiences, accessibility reviews, behavioural analytics, and product decision-making.
Listen
Students begin with raw participant evidence, not polished insights or final recommendations. They work with real comments, contradictions, and moments of uncertainty, learning to separate what the participant says from what the behaviour may reveal.
A comment about unclear costs may also be about trust. A positive reaction to a visual explanation may not be about the image itself, but about confidence. A complaint about too much content may signal that the page is asking the user to work too hard. This is where research begins: in attention before interpretation.
Frame
The next step is to turn evidence into a better question. Students move from quote to structure by translating observations into a problem, an objective, and a How Might We question. This prevents the common mistake of jumping directly from one user comment to one design fix.
A weak response is to say, “make this clearer.” A stronger response asks what the user needed at that moment, why the current experience failed to provide it, and what the team needs to learn before deciding on a solution. Research becomes direction when it starts with the right question, not the nearest fix.
Map
Students then place the evidence into a journey. They identify the moment, the content block, the user action, the emotion, and the opportunity, so the problem becomes concrete rather than abstract.
Most UX issues do not live inside one isolated component. A trust signal, delivery message, review count, image, form field, or content module can change meaning depending on where it appears in the journey. Mapping shows where confidence builds, where it breaks, and where the system creates unnecessary effort.
Test
The final step is to turn an insight into a testable hypothesis: if we change this part of the experience, then this metric may improve, because the research showed this behaviour or risk. This is where teaching becomes close to real product work.
Not every insight should become a recommendation. Some ideas need to be tested. Some need more evidence. Some should be deprioritised because they are interesting but not consequential enough to act on. In digital commerce and service design especially, a change can increase engagement while failing to improve the outcome that matters.
What students learn
The aim is not to teach students to make research look tidy. The aim is to teach them how to handle evidence without flattening it. They work with participant quotes, behavioural signals, journey maps, hypotheses, and prioritisation frameworks, while understanding that qualitative and quantitative evidence can support each other but can also disagree.
Good UX research requires judgement. Judgement means knowing when a quote is a symptom, when a metric is misleading, when a journey map reveals a structural issue, and when a design idea needs to become an experiment rather than a recommendation. That distinction does not come from method. It comes from practice.
Why this matters
In real projects, evidence is incomplete, stakeholders need decisions, teams want clarity, and metrics can point in one direction while interviews point in another. Accessibility issues may be invisible until someone tests the journey differently. A service can look simple on the surface while creating operational pressure behind it.
Students need to practise that complexity — not a cleaned-up version of it. They need to learn how to slow down, structure the material, and move forward without pretending the evidence is cleaner than it is. That means tolerating ambiguity long enough for the real problem to become visible, and being precise about what is known, what is inferred, and what still needs to be tested.