search
Enter at least two characters without personal information.

    LibraryArticles and FAQs Your projectRequest a quote
    LanguageEN ▾
    Methods and learning

    UX research: responsibilities and practical exercise

    UX research examines what people are trying to accomplish and the obstacles they encounter. It turns interviews, observations and task testing into evidence for decisions, with context and limitations. Its work helps decide what to investigate or change before designing a solution.

    These sheets describe activities and teaching exercises. They do not constitute job offers, certifying courses or recruitment promises.

    All job descriptions
    Illustration of design and review work on a computer
    AI-generated illustration

    Explore all 28 review cases — One testimony becomes a general rule

    Missions and responsibilities

    Support product decisions with observations of behaviour, needs and obstacles. UX research helps distinguish evidence, assumptions and questions needing investigation.

    Typical activities

    • Frame a research question and choose interviews, observation or task testing.
    • Prepare participant recruitment, instructions and appropriate consent arrangements.
    • Analyse observations while retaining context and sample limitations.

    Responsibilities to agree with the team

    Researchers provide findings and recommendations; they do not decide budgets or product scope alone. Product design and project owners use the evidence to make decisions.

    A first piece of work to demonstrate

    Present a synthesis linking each recommendation to an observation and recording unresolved questions.

    This is an editorial description of common activities. Job titles and scope vary across teams; it is not a certification framework.

    W3C: organising accessibility responsibilities across a team

    Practice exercise

    Study appointment booking without presuming that the form is the cause of the problem.

    Work on a copy or demo environment. Define the data used and the expected result before you begin. Keep your decisions and the difficulties encountered in order to be able to explain the process.

    1. Define the audiences to meet and the questions the research must answer.
    2. Prepare open tasks without suggesting the expected path or response.
    3. Separate observation, remarks collected and interpretation in the notes.
    4. Compare the obstacles and propose a decision accompanied by its limits.

    Deliverable and checks

    Provide the tasks, recruitment criteria and an anonymised synthesis. Link each booking obstacle to an observed action or statement, then separate interpretation, open questions and a hypothesis to test.

    A reader who did not attend the sessions should be able to trace the evidence behind each conclusion. Keep contradictory cases visible and describe the observed group without presenting its experiences as frequencies for all visitors.

    Prepare website checks

    Risks and collaboration

    A preference expressed is not in itself proof that a solution will work. Do not present a few interviews as a measure of the entire population.

    Collaboration to explore: product design.

    Fictional deliverable excerpt : During the observed task, a person opens Prices and then returns home without finding availability. Keep that observation separate from its interpretation.

    What passes between the roles : The task context, observed obstacles and content constraints inform interface proposals. The solution is then checked in use; a design alone does not establish that the obstacle has disappeared.

    View the role comparison : UX designer and UI designer →

    Employment, trades and training
    An example to examine

    Separate observation from interpretation

    Fictional teaching material: this excerpt illustrates part of a deliverable. It is not a client reference, a complete specification or evidence of professional qualification.

    Sample excerpt
    Task: find the cancellation conditions.
    Observation: the person opens the FAQ, then returns to the listing.
    Quote: “I thought the conditions would be here.”
    Hypothesis: the current link is difficult to notice.
    Next check: observe the same task with other people.

    What the author should be able to explain

    1. The task names neither the link nor the route to take.
    2. Behaviour and words remain separate from the proposed explanation.
    3. The hypothesis leads to a further check rather than turning one observation into a general fact.
    Does this establish that the link must move?

    This note supports further investigation. Examine the content, link visibility and other observations before choosing a change. State the context and limits of the sample in the report.

    Assess the quality of the work

    In the exercise, someone needs to reschedule an appointment and the team is considering clearer information or an extra control. Research should inform that decision before choosing a screen to change. Examine recruitment, instructions and counterexamples: one successful session does not describe every use.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    Assess the quality of the work
    SkillEvidence to examineFailure to spot
    Question and recruitmentPresent the intended decision, situations sought and recruitment rationale. Prepare a task whose instructions do not name the button to use.The protocol recruits only colleagues familiar with the interface or asks them to confirm that the proposed solution is clear.
    Situated observationRetain task, starting information, observed action and relevant statements in anonymized form. Separate the participant’s explanation from the researcher’s interpretation.Hesitation is immediately assigned an assumed cause, or feedback after a demonstration is presented as spontaneous use.
    ReportingTraceable findings, sample limitations and testable next steps.Quotes lose context or expose participants.
    Observation traceabilityLink each recommendation to an anonymised observation and the task used.Another reviewer can distinguish quotation, observation and interpretation without personal data.

    A focused next step

    Review a disputed conclusion with someone absent from the sessions. They should be able to recover the observation and suggest another plausible explanation. If the data do not distinguish those explanations, define a next task that can provide evidence without turning disagreement into a statistical result.

    W3C WAI: involving users in evaluation. · Source consulted

    Documented reference points for this topic

    Documented reference points for this topic
    ReferenceValue or syntaxScope
    WCAG 2.2 · 2.5.8
    24 × 24 CSS pxA smaller target can satisfy the criterion through spacing; other exceptions apply.
    WCAG 2.2 · 1.4.10
    320 CSS pxVertical content without two-dimensional scrolling; exceptions cover inherently two-dimensional content.
    WCAG 2.2 · 3.3.7
    A · same processWithin one process, previously supplied information must be auto-populated or available to select, subject to the criterion’s exceptions. Browser autocomplete alone is insufficient; the site must offer the information already received or avoid requesting it again.

    Dates indicate when references were consulted. These facts are neither a site audit nor an overall compliance statement.

    A review case to reproduce

    One testimony becomes a general rule

    Situation to examine
    A synthesis turns one participant’s difficulty into a conclusion about every user. Notes mix observation and interpretation.
    Proposed check
    Find the task, context and statements underlying the finding. Restate its scope and unresolved questions. Propose an additional observation that could confirm or challenge the hypothesis.
    Evidence to retain
    An anonymised note connects context, finding and recommendation. Sample limits are stated; expressed preference is not described as measured impact.
    Fictional finding example
    Five participants attempt the same task; two cannot find the contact route. The record retains each person’s instructions, journey and difficulty.
    Interpret this outcome
    Write “observed among 2 of the 5 participants”, then propose a follow-up check. This small group does not measure prevalence across the whole customer population.

    Three complementary checks

    Fictional cases: adapt these expectations to your test contract and retain the limits of the check.

    1. Neutral task
    2. Traceable observation
    3. Bounded hypothesis

    Scroll the table horizontally if needed; with a keyboard, focus it and use the arrow keys.

    Scenario variations and expected evidence
    Variation to testExpected result in this caseEvidence to hand over
    The task reveals the linkRewrite without naming the expected routeOriginal and revised task
    One person completes the taskKeep this counterexample in the summaryAnonymised note linked to the task
    Another audience is observedDescribe its context separatelyGroup criteria and open questions

    Decision to hand over : Hand over conflicting observations with the hypothesis, without reducing them to one overall score.

    Method reference : W3C WAI — Planning and Managing

    Learning scenario

    Extended exercise and expected deliverables

    In-depth exercise: Study how volunteers find information in a library prototype. Present the task without indicating the path to take. Prepare a clear agreement on what will be observed and preserved, then use anonymized notes. Compare the formulations heard with the behaviors observed. A difficulty seen during a session becomes a contextualized observation, not a conclusion on all users. Finish with a design question that the team can actually deal with.

    What to deliver with your work

    • Research question and decisions it should inform
    • Session guide with neutral tasks and reminders
    • Anonymized notes separating facts and interpretations
    • Summary of limits and next verification

    Acceptance criteria

    These criteria are a working basis to adapt to the context. For each, note the action taken, the expected result, the observed result and the information remaining to be confirmed.

    1. Each conclusion refers to an observation described.
    2. Follow-up prompts do not suggest the expected answer.
    3. Identifying information is removed from shared deliverables.
    4. The number and profile of participants are explained without abusive generalization.

    Understand pre-launch checks

    Ongoing management and handover

    Transmit the question, method, observations and limits with the synthesis. A team must be able to distinguish a quote, an interpretation and a proposal. If a result remains uncertain, propose a targeted additional trial. Keep only the necessary data for the planned and agreed follow-up with the participants; A pedagogical report does not need to expose their identities.

    Organize site maintenance

    Compare two approaches

    Choose research methods for a precise question. Distinguish understanding needs before designing a workflow from observing difficulties in an existing solution.

    Interviews about a concrete situation

    When to choose it
    Useful for understanding tasks, constraints and practices. Ask about actual experiences rather than preferences for an imagined solution.
    What to plan for
    Document participant recruitment and sample limitations. Separate reported statements from interpretation; a few accounts do not establish a general frequency.

    Observation of a workflow or prototype

    When to choose it
    Useful for finding where a task becomes difficult. Give clear instructions and let participants act without explaining every step.
    What to plan for
    Record actions, hesitation and results. An incomplete prototype cannot support conclusions about the whole workflow.

    A risk to anticipate

    Leading questions or premature help can change the result. Record these interventions to explain the limitations.

    How to decide

    Link each recommendation to an observation and its consequence. Choose a verifiable change and a comparable task for the next session.

    Explore this decision further

    Compare scope and costs

    Setup
    Compare the research question, audiences and protocol rather than interview count alone. Include task preparation, recruitment and synthesis in deliverable scope.
    Recurring operation
    Specify when to repeat observations after changes and who maintains records. Additional interviews and indicator tracking are distinct activities with different interpretation limits.
    Exit and handover
    Request usable synthesis, tasks and anonymised decision evidence. Protect participants; being able to resume the method differs from receiving raw files.

    Compare the costs of three web solutions

    Frequently asked questions

    What should be shown when observations conflict?

    Keep divergent observations with their task and context. Check whether they concern different audiences, expectations or starting information. The synthesis may recommend another check rather than settle the issue by voting. An isolated statement remains identifiable as such.

    Can the exercise be done without recording participants?

    Yes. Prepare notes focused on actions and obstacles, without names or unnecessary personal details. Explain the session and intended uses beforehand. If a recording is unnecessary for the research question, structured notes may be enough.

    Can a few tests support conclusions about all users?

    Observations reveal problems in a particular context. They do not automatically represent every audience. Describe participant profiles, tasks and limitations, then extend the research when important uses remain unexplored.

    Further reading

    Browse other resources