Customer Research Task
Observe a realistic user task
Feedback describes preferences, while the team still cannot see where the prototype blocks real work.
“This is costing me design effort while the real task failures remain unseen.”
Outcome
The result to aim for
Observed problems lead to a specific change and another test.
Best practices
- Choose a prototype that can answer the research question.
- Write a scenario with a goal, starting state, and observable completion condition.
- Select one change tied to a supported problem and define the same task for the next round.
- Confirm that the task has an observable completion condition.
- Report accessibility or prototype failures separately from product findings.
Related sources
Further information
- Documented guidance: Hacker News: Ask HN: Do you find it challenging to talk to your users?
- Related guidance: GOV.UK: Usability testing: qualitative studies
- Related guidance: Google Design: Global UX Research Tips