UX Research · 10 min read
UX Research
Plan, run and synthesise research that changes decisions: interviews, usability testing, surveys, synthesis and research operations. With labs.
Seven steps in order, then five labs and a part for people who lead design teams. It goes deeper than the research steps of UX Design Foundations, and links back to them.
Step 1 · Why research
- What research is forResearch is how a team stops guessing about the decisions that matter. What it's for, the three jobs it does at different moments of a product, the difference between what people say and what they do, and what research is not.
- Research questions that lead to decisionsA study is only as good as the question it answers. How to climb from a vague business worry to a research question you can actually study, why it's different from the questions you'll ask participants, and how to write down, before you start, what result would change the plan.
- When not to do researchA study costs time, money, and other people's attention. How to tell when a new study is worth it, the signs that it isn't, what to do instead, and how to say "not now" without sounding like you don't care about users.
- Research ethics and consentPeople lend you their time, their stories and sometimes their faces. The three principles behind research ethics, what informed consent really needs, a consent form you can adapt, and the special cases: colleagues, disabled participants, children and sensitive topics.
Step 2 · Plan the research
- Choosing a research methodThere are dozens of research methods, and three questions narrow them down to two or three. The map NN/g uses (what people say or do, why or how many, and in what context), how the words of a research question point to a method, and why the best studies combine two.
- Writing a research planA research plan is a one-page agreement, written before any work starts, about what you'll learn, from whom, by when and for which decision. What goes in it, a filled-in example, the timings that make a schedule realistic, and the pilot session that saves the first real one.
- Recruiting participantsThe right six people beat the wrong sixty. Who to recruit, how to write a recruitment brief, where to find people and the bias each channel brings, how much to pay and when, and how to plan for the people who won't show up.
- Screeners and samplingA screener decides who gets into your study, and people who want the incentive will try to guess the right answers. How to write screener questions that can't be gamed, how qualitative sampling works, what saturation really means, and how quotas keep a small sample from being all the same person.
- Research data and privacyAlmost everything a study produces is personal data: names, faces, voices, screens, notes. What Europe's GDPR and Brazil's LGPD say that matters for designers doing research, the difference between anonymous and pseudonymised data, and a simple life cycle from collecting to deleting.
Step 3 · Interviews
- The interview guideA guide is not a script: it's a short plan that keeps a free conversation on the questions your study has to answer. How to build one from your research questions, order it as a funnel, give it a warm-up and a wrap-up, and pilot it before the first real session.
- Asking good questionsThe words of a question decide what kind of answer you can get. Why opinions and predictions are weak data, how to ask about specific moments, the six weak question patterns and their rewrites, and how to stop pitching your idea in the middle of a research interview.
- Running the session and listeningThe guide is ready; now there's a person in front of you. How to open so people relax, build trust without trying to be liked, follow up without leading, use silence, handle the questions they ask you, and close well. Most of the craft is listening, and listening is a skill you can practise.
- Notes, recordings and transcriptsAn interview you can't find again might as well not have happened. How to take notes that keep what was said apart from what you think it means, when to record and how to ask, what a transcript is good for and where automatic ones go wrong, and the ten-minute debrief that saves your synthesis.
- Contextual inquiry and diary studiesInterviews give you what people remember. Two methods get closer to what they really do: contextual inquiry, where you watch and ask while the work happens, and diary studies, where people log moments over days or weeks. How each one works, how to run it, and when it's worth the extra effort.
Step 4 · Usability testing
- Planning a usability testA usability test is simple to run and easy to waste. How to start from the decision the test will inform, choose between qualitative and quantitative, moderated and unmoderated, in person and remote, write a one-page plan, and pilot it so your first participant isn't also your rehearsal.
- Tasks and scenariosIn a usability test, the task is the question, and a badly worded task gets a misleading answer. How to turn user goals into realistic scenarios, avoid giving away the path, order tasks from exploratory to directed, define success before the session, and check your tasks against the ten most common mistakes.
- Moderating and thinking aloudThinking aloud is the most useful usability method there is, and the easiest to spoil by talking. How to brief participants, keep them talking without steering them, answer their questions without answering them, ask follow-ups after a task, and know when you've biased a session.
- How many participants"Test with five users" is the best-known number in UX, and the most misread. Where it comes from, what the formula really says, what Faulkner found when she tested 60 people, how the answer changes for problems that are rarer, for different user groups and for measuring, and how to choose a number you can defend.
- Measuring usabilityUsability can be measured, if you're clear about what you measure. The ISO definition in three parts, the metrics for each (success rate, time on task, the Single Ease Question and the System Usability Scale), how to score SUS by hand, what 68 means, and why numbers need many more people than findings do.
Step 5 · Surveys and data
- Writing survey questionsA survey question works when every respondent reads it the same way and can answer it truthfully. What a survey is for, the four steps people go through to answer, the classic mistakes and their rewrites, open and closed questions, rating scales, and why you pilot before you send.
- Bias in surveysA survey can be wrong in two ways: it can ask the wrong people, or it can ask the right people in a way that bends their answers. The main biases by name, real experiments that show how big they are, and what you can do about each one.
- Sample size and margin of errorHow many responses a survey needs depends on how precise the decision needs the number to be. What a margin of error means, the one formula behind it, worked examples, why halving the error costs four times the responses, and what the margin of error doesn't cover.
- Analytics and A/B tests for designersAnalytics tells you what people do in your product, at scale; it can't tell you why. What analytics is good for, its traps, how an A/B test works, how to plan one before launch, why you mustn't peek, and where designers add the most value.
Step 6 · Synthesis
- From notes to themes, affinity mappingAffinity mapping turns a wall of research notes into a few themes a team agrees on. Where the method comes from, how to write notes that cluster well, why you need a focus question, how to sort without keyword matching or groupthink, and how to name themes so they say something.
- Thematic analysisThematic analysis is the most widely used way to find patterns of meaning in qualitative data, and the most often misused. What codes and themes are, the six phases, why themes don't 'emerge', the difference between a theme and a topic summary, and how to do it well in a design team.
- Personas and journeys from dataA persona or a journey map is only as good as the evidence under it. How to go from themes to behavioural segments, how to build a persona and a journey that point back to their sources, how jobs to be done fit in, how to show confidence and gaps, and when to update them.
- Writing insights that change decisionsA finding says what you saw; an insight says why it matters to a decision. The difference between data, findings, insights and recommendations, a template for one insight with a worked example, how to show evidence and confidence, and how to write recommendations someone will own.
Step 7 · Share and scale
- Research reports people readA report is only useful if it changes what someone does next. How to write one that a busy person can read in a minute and a careful one can check in an hour: three reading depths, one finding per slide, timing, and formats that aren't a 40-page PDF.
- Research repositoriesA research repository is the team's memory: one place where studies, insights and evidence can be found again. What goes in one, the three ways to build it, what atomic research and nuggets are, and why most repositories fail, with the numbers from a survey of more than 400 practitioners.
- ResearchOpsResearchOps is the people, tools and processes that let research happen well, more often, and with impact. What it covers, the ResearchOps Community's eight pillars, NN/g's six components and Kate Towsey's eight functions side by side, and how to start without building a bureaucracy.
- AI in UX research, carefullyAI can save hours in research and quietly put things in your report that nobody said. The risks that matter most for a research team, from invented quotes and synthetic users to AI respondents inside your own survey data, and the checks that keep the evidence honest.
Labs
- Write a research planA guided lab: pick a real decision your team faces, and write a one-page research plan for it, from the research questions to the participants, the method, consent and how you'll share the results. Then review it with one stakeholder. About an hour and a half, with any document tool.
- Run three interviewsA guided lab: write a short interview guide, run three 30-minute interviews with consent and a recording, debrief after each one in an interview log, and change the guide between sessions. About four hours over a week, with a video call tool and a notes app.
- Write and pilot a surveyA guided lab: write a short survey tied to your research questions, pilot it with five people thinking aloud, time it, run a small online pilot, and fix every question that was misread. About three hours, with any survey tool and five patient people.
- Synthesise a studyA guided lab: take the notes from a small study and turn them into themes, findings and actions on a board, with your team, in one session. Three colours of sticky note, one observation per note, and every finding traced back to the people who said or did it. About two to three hours.
- Present findings in ten minutesA guided lab: turn a study into a ten-minute readout that ends in a decision. One sentence of answer, three findings with evidence, recommendations with owners, and a clear ask, rehearsed against a timer. About two hours to prepare, ten minutes to deliver.
For leads
- Building a research practiceFor leads: how to turn occasional studies into a practice the team relies on. Read your organisation's maturity, start from real demand, make research safe and visible before you make it big, and set a rhythm the team can keep.
- Democratising research without losing qualityFor leads: there will always be more research to do than researchers to do it. How to let designers, product managers and others run studies well: match the study to the skill, give people guardrails instead of gates, coach rather than police, and check the results.
- Showing the impact of researchFor leads: "we ran 24 interviews" is effort, not impact. How to show what research changed: track every recommendation to adoption, link the metrics design moves to the metrics leadership watches, and stay honest about what you can and can't claim. With a worked Recommendation-Adoption Score.
Reference
- Glossary185 terms defined in this course's lessons, A to Z.
- Frameworks11 frameworks and techniques this course's lessons use, by area.
- Library137 books, articles, videos and courses cited in this course, grouped by the step they appear in.
Saved only on this device.