Understand the needs and obstacles before proposing an interface.
These sheets describe activities and teaching exercises. They do not constitute job offers, certifying courses or recruitment promises.
All job descriptions
Support product decisions with observations of behaviour, needs and obstacles. UX research helps distinguish evidence, assumptions and questions needing investigation.
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.
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
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.
An anonymized summary, the tasks used, a route map and the questions remaining to be explored.
Observable tasks and a summary that makes it possible to find the elements that led to a decision.
For each check, note the context, the action, the expected result and what has been observed. Distinguish a successful verification from a remaining hypothesis. Another person must be able to understand the deliverable without attending all its manufacture.
Use the Functional Validation BookA 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.
Specify the sharing of responsibilities: who provides the information, who decides, who checks and maintains the result. A good handover retains the constraints and decisions, not just the final file.
Employment, trades and trainingAssess research through the trace from question to observation to decision. Interview count is insufficient: useful research explains who was heard and what the observations support.
| Skill | Evidence to examine | Failure to spot |
|---|---|---|
| Framing | A research question tied to a decision and explained recruitment. | The protocol only seeks to confirm a predetermined solution. |
| Observation | Notes separating observed action from interpretation. | One opinion is presented as a measured frequency. |
| Reporting | Traceable findings, sample limitations and testable next steps. | Quotes lose context or expose participants. |
Download the editable CSV checklist
The file contains this table and blank columns for the observed result, owner and follow-up. It opens in a spreadsheet; downloading it does not send your observations to the site.
To improve, revisit a disputed finding and find the note supporting it. If no usable observation exists, turn it into a hypothesis and propose a focused test rather than presenting it as a result.
W3C WAI: involving users in evaluation.
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.
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.
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.
Choose research methods for a precise question. Distinguish understanding needs before designing a workflow from observing difficulties in an existing solution.
Leading questions or premature help can change the result. Record these interventions to explain the limitations.
Link each recommendation to an observation and its consequence. Choose a verifiable change and a comparable task for the next session.
It allows you to show an approach and its limits. It is neither a diploma, nor a certification, nor proof of a production experience.
Specify that this is an exercise, your role, constraints, decisions and checks. Use test data and media whose rights are established.
Observable tasks and a summary that makes it possible to find the elements that led to a decision. Add the difficulties encountered and what remains to be verified rather than presenting absolute validation.
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.
